Closed jeanduplessis closed 3 months ago
Waiting on v1.15.2-up.1 helm chart release to include https://github.com/upbound/universal-crossplane/issues/449. Is this targeted for this week ? Thanks.
@ravilr we are working on the release today.
Closing in favor of https://github.com/upbound/universal-crossplane/issues/459
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.1
is being cut, after upstream crossplane/crossplanevX.Y.Z
has been released according to the declared schedule, you should have:release-X.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.1
release from therelease-X.Y
branch by:release-X.Y
branch with the proper release version,vX.Y.Z-up.1
. Message suggested but not required:Release vX.Y.Z-up.1
.release-X.Y
branch to build and publish the latest tagged artifacts.docker pull xpkg.upbound.io/upbound/crossplane:vX.Y.Z-up.1
main
branch of upbound/universal-crossplane with the following changes:vX.Y.Z-up.1
, such asCROSSPLANE_TAG
andCROSSPLANE_COMMIT
in theMakefile
.make generate
to import any changes in the upstream Helm chart.release-X.Y
branch frommain
branch in UXP.vX.Y.Z-up.1
release from therelease-X.Y
branch by:release-X.Y
branch with the proper release version,vX.Y.Z-up.1
. Message suggested but not required:Release vX.Y.Z-up.1
.release-X.Y
branch to build and publish the latest tagged artifacts.build
channel, e.g.build/release-X.Y/vX.Y.Z-up.K/...
main
branch,vX.<Y+1>.0-up.1-rc.0
by:main
branch with the proper release version,vX.<Y+1>.0-up.1-rc.0
. Message suggested but not required:Release vX.<Y+1>.0-up.1-rc.0
.build
channnel atbuild/release-X.Y/vX.Y.Z-up.K/charts
by 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 cluster
up uxp install
helm -n upbound-system upgrade --install universal-crossplane <path-to-chart.tgz> --create-namespace
release-X.Y
branch, to promotevX.Y.Z-up.1
tostable
, here you should finduniversal-crossplane-X.Y.Z-up.1.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.1
. 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.