crossplane
/
docs
mirror of https://github.com/crossplane/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #948 from phisco/bye-bye-default-registry 

Dropped default registries in crossplane v2
This commit is contained in:
Jared Watts 2025-07-01 08:55:50 -07:00 committed by GitHub
parent 3ca6127a9b 9a01f6633b
commit 5ba4c88fe4
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 16 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
content/v2.0-preview/whats-new/_index.md
View File

@ -221,6 +221,7 @@ Crossplane v2 makes the following breaking changes:
* It removes native patch and transform composition. * It removes native patch and transform composition.
* It removes the `ControllerConfig` type. * It removes the `ControllerConfig` type.
* It removes support for external secret stores. * It removes support for external secret stores.
* It removes the default registry for Crossplane Packages.
Crossplane deprecated native patch and transform composition in Crossplane Crossplane deprecated native patch and transform composition in Crossplane
v1.17. It's replaced by composition functions. v1.17. It's replaced by composition functions.
@ -231,11 +232,26 @@ Crossplane deprecated the `ControllerConfig` type in v1.11. It's replaced by the
Crossplane added external secret stores in v1.7. External secret stores have Crossplane added external secret stores in v1.7. External secret stores have
remained in alpha for over two years and are now unmaintained. remained in alpha for over two years and are now unmaintained.
Crossplane v2 drops the `--registry` flag that allowed users to specify a default
registry value and now requires users to always specify a fully qualified URL when
installing packages, both directly via `spec.package` and indirectly as dependencies.
Using fully qualified images was already a best practice, but it's now enforced
to avoid confusion and unexpected behavior, to ensure users are aware of the
registry used by their packages.
{{<hint "important">}} {{<hint "important">}}
As long as you're not using these deprecated or alpha features, Crossplane v2 is As long as you're not using these deprecated or alpha features, Crossplane v2 is
backward compatible with Crossplane v1.x. backward compatible with Crossplane v1.x.
{{</hint>}} {{</hint>}}
{{<hint "important">}}
Before upgrading to Crossplane v2, please ensure all your Packages are using fully
qualified images that explicitly specify a registry (`registry.example.com/repo/package:tag`).
Run `kubectl get pkg` to look for any packages that aren't fully qualified, then
update or rebuild any Packages to use fully qualified images as needed.
{{</hint>}}
<!-- vale gitlab.FutureTense = NO --> <!-- vale gitlab.FutureTense = NO -->
Crossplane v2 supports legacy v1-style XRs and MRs. Most users will be able to Crossplane v2 supports legacy v1-style XRs and MRs. Most users will be able to
upgrade from v1.x to Crossplane v2 without breaking changes. upgrade from v1.x to Crossplane v2 without breaking changes.