Update default registry to xpkg.crossplane.io #6296
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of your changes
This is related to recent governance changes in #6290. All community extension projects must be published to
ghcr.io
(withxpkg.crossplane.io
in front for pulls), and now the the default registry for Crossplane will be updated toxpkg.crossplane.io
. This change affects a few different places:xpkg.crossplane.io
crossplane/crossplane
container image will now also be published toghcr.io
(withxpkg.crossplane.io
in front for pulls) and the helm chart fromcharts.crossplane.io
will now pull the crossplane image fromxpkg.crossplane.io
by default.I have:
earthly +reviewable
to ensure this PR is ready for review.Addedbackport release-x.y
labels to auto-backport this PR.Followed the API promotion workflow if this PR introduces, removes, or promotes an API.Need help with this checklist? See the cheat sheet.