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
Copy file name to clipboardExpand all lines: content/v2.0-preview/whats-new/_index.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -236,8 +236,8 @@ Crossplane v2 drops the `--registry` flag that allowed users to specify a defaul
236
236
registry value and now requires users to always specify a fully qualified URL when
237
237
installing packages, both directly via `spec.package` and indirectly as dependencies.
238
238
Using fully qualified images was already a best practice, but it's now enforced
239
-
to avoid confusion and unexpected behavior, as well as to ensure users are aware
240
-
of the registry used by their packages.
239
+
to avoid confusion and unexpected behavior, to ensure users are aware of the
240
+
registry used by their packages.
241
241
242
242
{{<hint "important">}}
243
243
As long as you're not using these deprecated or alpha features, Crossplane v2 is
@@ -246,9 +246,10 @@ backward compatible with Crossplane v1.x.
246
246
247
247
{{<hint "important">}}
248
248
Before upgrading to Crossplane v2, please ensure all your Packages are using fully
249
-
qualified images that explicitly specify a registry, i.e. `registry.example.com/repo/package:tag`.
249
+
qualified images that explicitly specify a registry (`registry.example.com/repo/package:tag`).
250
250
251
-
Run `kubectl get pkg` to look for any packages that are not fully qualified, then update or rebuild any Packages to use fully qualified images as needed.
251
+
Run `kubectl get pkg` to look for any packages that aren't fully qualified, then
252
+
update or rebuild any Packages to use fully qualified images as needed.
0 commit comments