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:
[x] Synced the release-X.Y release branch in upbound/crossplane, with upstream crossplane/crossplane release branch, up to the vX.Y.Z tag, adding any required change specific to the fork, see here for more details.
[x] Tagged upbound/crossplanevX.Y.Z-up.K from the release-X.Y branch by:
[x] Running the Tag workflow on the release-X.Y branch with the proper release version, vX.Y.Z-up.K. Use Release vX.Y.Z-up.K as message (FYI: the format suggested is only for consistency, there is no actual dependency on it).
[x] Running the CI workflow on the release-X.Y branch to build and publish the latest tagged artifacts.
[x] Confirm the image has been successfully published using: docker buildx imagetools inspect docker.io/upbound/crossplane:vX.Y.Z-up.K
[x] Created and merged a PR for upbound/universal-crossplane to either the main branch, if cutting a patch for the latest supported release, taking care to label it backport release-X.Y, or directly to the release-X.Y branch, if cutting a patch for an older supported release. With the following changes:
[x] Update any reference to the old latest release to vX.Y.Z-up.K, such as CROSSPLANE_TAG and CROSSPLANE_COMMIT in the Makefile.
[x] Cut UXPvX.Y.Z-up.K release from the release-X.Y branch by:
[x] Running the Tag workflow on the release-X.Y branch with the proper release version, vX.Y.Z-up.K. Use Release vX.Y.Z-up.K as message (FYI: the format suggested is only for consistency, there is no actual dependency on it).
[x] Running the CI workflow on the release-X.Y branch to build and publish the latest tagged artifacts.
[x] Verify that the tagged build version exists on the releases.upbound.iobuild channel, e.g. build/release-X.Y/vX.Y.Z-up.K/...
[x] Verify the produced helm chart available in the build channnel at build/release-X.Y/vX.Y.Z-up.K/charts by doing some sanity checks:
[x] Installs on a cluster properly with helm -n upbound-system upgrade --install universal-crossplane <path-to-chart.tgz> --create-namespace.
[x] Uses the correct image versions of upbound/crossplane, e.g. kubectl -n upbound-system get pods -o yaml | grep image:
[x] Upgrading from the latest supported version works, for example run:
create a kind cluster: kind create cluster
install the current stable version: up uxp install
install one of the above reference platforms
upgrade to this new version as above: helm -n upbound-system upgrade --install universal-crossplane <path-to-chart.tgz> --create-namespace
[x] Run the Promote workflow from the release-X.Y branch, to promote vX.Y.Z-up.K to stable, here you should find universal-crossplane-X.Y.Z-up.K.tgz. Verify everything is correctly working by running up uxp install against an empty Kubernetes cluster, e.g. kind create cluster, which should result in an healthy UXP installation with expected image versions.
[x] Drafted, validated with the rest of the team and then published well authored release notes for UXPvX.Y.Z-up.K. See the previous release for an example, these should at least:
[x] enumerate relevant updates that were merged in u/xp and u/uxp.
lsviben
commented
8 months ago
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.Kis being cut, after upstream crossplane/crossplanevX.Y.Zhas been released according to the declared schedule, you should have:release-X.Yrelease branch in upbound/crossplane, with upstream crossplane/crossplane release branch, up to thevX.Y.Ztag, adding any required change specific to the fork, see here for more details.vX.Y.Z-up.Kfrom therelease-X.Ybranch by:release-X.Ybranch with the proper release version,vX.Y.Z-up.K. UseRelease vX.Y.Z-up.Kas message (FYI: the format suggested is only for consistency, there is no actual dependency on it).release-X.Ybranch to build and publish the latest tagged artifacts.docker buildx imagetools inspect docker.io/upbound/crossplane:vX.Y.Z-up.Kmainbranch, if cutting a patch for the latest supported release, taking care to label itbackport release-X.Y, or directly to therelease-X.Ybranch, if cutting a patch for an older supported release. With the following changes:vX.Y.Z-up.K, such asCROSSPLANE_TAGandCROSSPLANE_COMMITin theMakefile.make generateto import any changes in the upstream Helm chart.vX.Y.Z-up.Krelease from therelease-X.Ybranch by:release-X.Ybranch with the proper release version,vX.Y.Z-up.K. UseRelease vX.Y.Z-up.Kas message (FYI: the format suggested is only for consistency, there is no actual dependency on it).release-X.Ybranch to build and publish the latest tagged artifacts.buildchannel, e.g.build/release-X.Y/vX.Y.Z-up.K/...buildchannnel atbuild/release-X.Y/vX.Y.Z-up.K/chartsby doing some sanity checks:helm -n upbound-system upgrade --install universal-crossplane <path-to-chart.tgz> --create-namespace.upbound/crossplane, e.g.kubectl -n upbound-system get pods -o yaml | grep image:kind create clusterup uxp installhelm -n upbound-system upgrade --install universal-crossplane <path-to-chart.tgz> --create-namespacerelease-X.Ybranch, to promotevX.Y.Z-up.Ktostable, here you should finduniversal-crossplane-X.Y.Z-up.K.tgz. Verify everything is correctly working by runningup uxp installagainst 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,#upboundand#squad-crossplaneon Upbound's Slack.#marketingon Upbound's Slack to do so.