You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 v1.20.10-up.1 is being cut, after upstream crossplane/crossplanev1.20.10 has been released
according to the declared schedule, you should have:
Synced the release-1.20 release branch in upbound/crossplane, with upstream crossplane/crossplane release branch, up to the v1.20.10 tag, adding any required change specific to the fork, see here for more details.
Running the Tag workflow on the release-1.20 branch with the proper release version, v1.20.10-up.1. Use Release v1.20.10-up.1 as message (FYI: the format suggested is only for consistency, there is no actual dependency on it).
Running the CI workflow on the release-1.20 branch to build and publish the latest tagged artifacts.
Create a new release for v1.20.10-up.1 with autogenerated notes and any additional note needed.
Confirm the image has been successfully published using: docker buildx imagetools inspect docker.io/upbound/crossplane:v1.20.10-up.1
Created and merged a PR for upbound/uxp to either the main branch, if cutting a patch for the latest supported release, taking care to label it backport release-1.20, or directly to the release-1.20 branch, if cutting a patch for an older supported release. With the following changes:
Update any reference to the old latest release to v1.20.10-up.1, such as CROSSPLANE_TAG and CROSSPLANE_COMMIT in the Makefile.
Update the dependencies in cluster/charts/crossplane/Chart.yaml to reference the latest versions available and supported:
Cut UXPv1.20.10-up.1 release from the release-1.20 branch by:
Running the Tag workflow on the release-1.20 branch with the proper release version, v1.20.10-up.1. Use Release v1.20.10-up.1 as message (FYI: the format suggested is only for consistency, there is no actual dependency on it).
Running the CI workflow on the release-1.20 branch to build and publish the latest tagged artifacts.
Verify that the tagged build version exists on the releases.upbound.iobuild channel, e.g. build/release-1.20/v1.20.10-up.1/...
Verify the produced helm chart available in the build channnel at build/release-1.20/v1.20.10-up.1/charts by doing some sanity checks:
Installs on a cluster properly with helm -n crossplane-system upgrade --install crossplane <path-to-chart.tgz> --create-namespace.
Uses the correct image versions of upbound/crossplane, e.g. kubectl -n upbound-system get pods -o yaml | grep image:
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 crossplane-system upgrade --install crossplane <path-to-chart.tgz> --create-namespace
Run the Promote workflow from the release-1.20 branch, to promote v1.20.10-up.1 to stable, here you should find upbound-crossplane-1.20.10-up.1.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.
Drafted, validated with the rest of the team and then published well authored release notes for UXPv1.20.10-up.1. See the previous release for an example, these should at least:
enumerate relevant updates that were merged in u/xp and u/uxp.
Added a release-notes entry in docs/reference/release-notes/uxp.md matching the format of previous entries, stripping links to private repos.
Only if this patch is cutting the new latest UXP release (patch on the latest supported minor): Refreshed docs/reference/uxp-helm-reference.md by fully replacing the existing values table with a freshly-generated merged table for v1.20.10-up.1: the main UXP chart values merged with each dependency subchart's values at the version pinned in cluster/charts/crossplane/Chart.yaml (e.g., uxp-webui under webui.*, uxp-apollo under apollo.* — use the alias from Chart.yaml, not the chart name). Skip this item for patches on older minors — the reference doc only tracks the latest release.
Ensured that users have been notified of the release on all communitcation channels:
Slack: crossposting on Crossplane's Slack workspace channels #announcements, #upbound and #squad-crossplane on Upbound's Slack.
Twitter: ask #marketing on Upbound's Slack to do so.
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
v1.20.10-up.1is being cut, after upstreamcrossplane/crossplane
v1.20.10has been releasedaccording to the declared schedule, you should have:
release-1.20release branch in upbound/crossplane, with upstream crossplane/crossplane release branch, up to thev1.20.10tag, adding any required change specific to the fork, see here for more details.v1.20.10-up.1from therelease-1.20branch by:release-1.20branch with the proper release version,v1.20.10-up.1. UseRelease v1.20.10-up.1as message (FYI: the format suggested is only for consistency, there is no actual dependency on it).release-1.20branch to build and publish the latest tagged artifacts.v1.20.10-up.1with autogenerated notes and any additional note needed.docker buildx imagetools inspect docker.io/upbound/crossplane:v1.20.10-up.1mainbranch, if cutting a patch for the latest supported release, taking care to label itbackport release-1.20, or directly to therelease-1.20branch, if cutting a patch for an older supported release. With the following changes:v1.20.10-up.1, such asCROSSPLANE_TAGandCROSSPLANE_COMMITin theMakefile.cluster/charts/crossplane/Chart.yamlto reference the latest versions available and supported:make generateto import any changes in the upstream Helm chart.v1.20.10-up.1release from therelease-1.20branch by:release-1.20branch with the proper release version,v1.20.10-up.1. UseRelease v1.20.10-up.1as message (FYI: the format suggested is only for consistency, there is no actual dependency on it).release-1.20branch to build and publish the latest tagged artifacts.buildchannel, e.g.build/release-1.20/v1.20.10-up.1/...buildchannnel atbuild/release-1.20/v1.20.10-up.1/chartsby doing some sanity checks:helm -n crossplane-system upgrade --install 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 crossplane-system upgrade --install crossplane <path-to-chart.tgz> --create-namespacerelease-1.20branch, to promotev1.20.10-up.1tostable, here you should findupbound-crossplane-1.20.10-up.1.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.v1.20.10-up.1. See the previous release for an example, these should at least:docs/reference/release-notes/uxp.mdmatching the format of previous entries, stripping links to private repos.docs/reference/uxp-helm-reference.mdby fully replacing the existing values table with a freshly-generated merged table forv1.20.10-up.1: the main UXP chart values merged with each dependency subchart's values at the version pinned incluster/charts/crossplane/Chart.yaml(e.g.,uxp-webuiunderwebui.*,uxp-apollounderapollo.*— use thealiasfromChart.yaml, not the chart name). Skip this item for patches on older minors — the reference doc only tracks the latest release.#announcements,#upboundand#squad-crossplaneon Upbound's Slack.#marketingon Upbound's Slack to do so.