From 2dab2fcaba5167e840b4f6f95620da3e2b43a5bd Mon Sep 17 00:00:00 2001 From: Nic Cope Date: Fri, 28 Mar 2025 20:42:30 -0700 Subject: [PATCH] Add links to backward compatibility heading Signed-off-by: Nic Cope --- content/v2.0-preview/whats-new/_index.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/content/v2.0-preview/whats-new/_index.md b/content/v2.0-preview/whats-new/_index.md index e63da041..be501b9e 100644 --- a/content/v2.0-preview/whats-new/_index.md +++ b/content/v2.0-preview/whats-new/_index.md @@ -44,6 +44,8 @@ claims and provider-kubernetes Objects. {{}} Most users can upgrade to Crossplane v2 without breaking changes. + +Read about Crossplane v2's [backward compatibility](#backward-compatibility). {{}} {{}} @@ -120,6 +122,8 @@ Crossplane v2 is backward compatible with v1-style XRs. When you use v1 of the XRD API `scope` defaults to a special `LegacyCluster` mode. `LegacyCluster` XRs support claims and don't use `spec.crossplane`. + +Read more about Crossplane v2's [backward compatibility](#backward-compatibility). {{}} ## Namespaced managed resources @@ -166,6 +170,8 @@ New provider releases will support both namespaced and cluster scoped MRs. Crossplane v2 considers cluster scoped MRs a legacy feature. Crossplane will deprecate and remove cluster scoped MRs at a future date. + +Read more about Crossplane v2's [backward compatibility](#backward-compatibility). {{}} ## Compose any resource