Closed turkenh closed 1 year ago
Running validations UXP v1.12.1-up.1 with reference platforms.
❯ helm -n upbound-system ls
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
universal-crossplane upbound-system 1 2023-05-16 13:03:01.601021 +0300 +03 deployed universal-crossplane-1.12.1-up.1 1.12.1-up.1
Platform Ref AWS
Successful Installation:
❯ kubectl get configuration
NAME INSTALLED HEALTHY PACKAGE AGE
platform-ref-aws True True xpkg.upbound.io/upbound/platform-ref-aws:v0.5.0 12m
❯ kubectl get providers.pkg.crossplane.io
NAME INSTALLED HEALTHY PACKAGE AGE
crossplane-contrib-provider-helm True True xpkg.upbound.io/crossplane-contrib/provider-helm:v0.15.0 10m
upbound-provider-aws True True xpkg.upbound.io/upbound/provider-aws:v0.35.0 12m
End to End validation:
❯ kubectl get clusters.aws.platformref.upbound.io
NAME SYNCED READY CONNECTION-SECRET AGE
platform-ref-aws True True platform-ref-aws-kubeconfig 20m
Platform Ref GCP
Successful Installation:
❯ kubectl get configurations.pkg.crossplane.io
NAME INSTALLED HEALTHY PACKAGE AGE
platform-ref-gcp True True xpkg.upbound.io/upbound/platform-ref-gcp:v0.3.0 5m10s
❯ kubectl get providers.pkg.crossplane.io
NAME INSTALLED HEALTHY PACKAGE AGE
crossplane-contrib-provider-helm True True xpkg.upbound.io/crossplane-contrib/provider-helm:v0.15.0 4m48s
upbound-provider-gcp True True xpkg.upbound.io/upbound/provider-gcp:v0.32.0 5m6s
Platform Ref Azure
Successful Installation:
❯ kubectl get configurations.pkg.crossplane.io
NAME INSTALLED HEALTHY PACKAGE AGE
platform-ref-azure True True xpkg.upbound.io/upbound/platform-ref-azure:v0.5.0 4m43s
❯ kubectl get providers.pkg.crossplane.io
NAME INSTALLED HEALTHY PACKAGE AGE
crossplane-contrib-provider-helm True True xpkg.upbound.io/crossplane-contrib/provider-helm:v0.15.0 2m45s
upbound-provider-azure True True xpkg.upbound.io/upbound/provider-azure:v0.32.0 4m45s
Release completed https://crossplane.slack.com/archives/CEFQCGW1H/p1684236021382929
This issue can be closed when we have completed the following steps (in order). Please ensure all artifacts (PRs, workflow runs, Tweets, etc) are linked from this issue for posterity. Assuming
vX.Y.Z-up.K
is being cut, after upstream crossplane/crossplanevX.Y.Z
has been released according to the declared schedule, you should have:release-vX.Y
release branch in upbound/crossplane, with upstream crossplane/crossplane release branch, up to thevX.Y.Z
tag, adding any required change specific to the fork, see here for more details.vX.Y.Z-up.K
from therelease-X.Y
branch by:release-vX.Y
branch with the proper release version,vX.Y.Z-up.K
. UseRelease vX.Y.Z-up.K
as message (FYI: the format suggested is only for consistency, there is no actual dependency on it).release-vX.Y
branch to build and publish the latest tagged artifacts.docker buildx imagetools inspect docker.io/upbound/crossplane:vX.Y.Z-up.K
main
branch, if cutting a patch for the latest supported release, taking care to label itbackport release-X.Y
, or directly to therelease-X.Y
branch, if cutting a patch for an older supported release. With the following changes:vX.Y.Z-up.K
, such asCROSSPLANE_TAG
andCROSSPLANE_COMMIT
in theMakefile
.make generate
to import any changes in the upstream Helm chart.vX.Y.Z-up.K
release from therelease-X.Y
branch by:release-vX.Y
branch with the proper release version,vX.Y.Z-up.K
. UseRelease vX.Y.Z-up.K
as message (FYI: the format suggested is only for consistency, there is no actual dependency on it).release-vX.Y
branch to build and publish the latest tagged artifacts.release-vX.Y
branch to promotevX.Y.Z-up.K
to stable, it should containuniversal-crossplane-X.Y.Z-up.K.tgz
. Verify everything is correctly working by runningup uxp install
against an empty Kubernetes cluster, e.g.kind create cluster
, which should result in an healthy UXP installation with expected image versions.vX.Y.Z-up.K
. See the previous release for an example, these should at least:#announcements
,#upbound
and#squad-crossplane
on Upbound's Slack.#marketing
on Upbound's Slack to do so.