From 4cf27d8c24c292f4e336c835dec8af04f47b5db1 Mon Sep 17 00:00:00 2001 From: Yury Tsarev Date: Thu, 5 Mar 2026 12:06:55 +0100 Subject: [PATCH] docs: clarify writeConnectionSecretToRef removal is XR-only, not MR-level MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit A common source of confusion when upgrading to v2 is assuming that the removal of native XR connection details also affects managed resources. This is not the case — writeConnectionSecretToRef on MRs is unchanged. Add a tip callout to the upgrade guide's "Composite resource connection details" section and expand the note in the connection details composition guide to explicitly state that only the XR-level aggregation was removed, while MR-level usage continues to work as before. Applied across all v2.x versions and master. Signed-off-by: Yury Tsarev --- content/master/guides/connection-details-composition.md | 4 +++- content/master/guides/upgrade-to-crossplane-v2.md | 7 +++++++ content/master/whats-new/_index.md | 1 + content/v2.0/guides/connection-details-composition.md | 4 +++- content/v2.0/guides/upgrade-to-crossplane-v2.md | 7 +++++++ content/v2.0/whats-new/_index.md | 1 + content/v2.1/guides/connection-details-composition.md | 4 +++- content/v2.1/guides/upgrade-to-crossplane-v2.md | 7 +++++++ content/v2.1/whats-new/_index.md | 1 + content/v2.2/guides/connection-details-composition.md | 4 +++- content/v2.2/guides/upgrade-to-crossplane-v2.md | 7 +++++++ content/v2.2/whats-new/_index.md | 1 + 12 files changed, 44 insertions(+), 4 deletions(-) diff --git a/content/master/guides/connection-details-composition.md b/content/master/guides/connection-details-composition.md index d4eaca673..7b73426ff 100644 --- a/content/master/guides/connection-details-composition.md +++ b/content/master/guides/connection-details-composition.md @@ -17,7 +17,9 @@ resources and exposes them for the XR. {{}} Crossplane v1 included a feature that automatically created connection details -for XRs. +for XRs. Crossplane v2 removes this feature **for XRs only**. Managed Resources (MRs) +aren't affected by this change and still support connection details via their +`writeConnectionSecretToRef` field. To learn more about how to specify XR connection details in Crossplane v1, please see the [v1 connection details]({{}}) docs page. diff --git a/content/master/guides/upgrade-to-crossplane-v2.md b/content/master/guides/upgrade-to-crossplane-v2.md index ad18f3793..85692bf38 100644 --- a/content/master/guides/upgrade-to-crossplane-v2.md +++ b/content/master/guides/upgrade-to-crossplane-v2.md @@ -96,6 +96,13 @@ or [External Secrets Operator](https://external-secrets.io/latest/) before upgra ### Composite resource connection details **Removed**: composite resources no longer have native connection details support. +{{}} +**This only affects XRs, managed resources aren't affected.** + +Managed resources (MRs) still support the `writeConnectionSecretToRef` field on any +MR spec. +{{}} + You can recreate this feature by composing your own connection details `Secret` as described in the [connection details composition guide]({{}}). diff --git a/content/master/whats-new/_index.md b/content/master/whats-new/_index.md index 224c0234a..96309e5ca 100644 --- a/content/master/whats-new/_index.md +++ b/content/master/whats-new/_index.md @@ -283,6 +283,7 @@ remained in alpha for over two years and are now unmaintained. Composite resources no longer have native connection details support. You can recreate this feature by composing your own connection details `Secret` as described in the [connection details composition guide]({{}}). +Connection details for managed resources (MRs) aren't affected. 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 diff --git a/content/v2.0/guides/connection-details-composition.md b/content/v2.0/guides/connection-details-composition.md index d4eaca673..7b73426ff 100644 --- a/content/v2.0/guides/connection-details-composition.md +++ b/content/v2.0/guides/connection-details-composition.md @@ -17,7 +17,9 @@ resources and exposes them for the XR. {{}} Crossplane v1 included a feature that automatically created connection details -for XRs. +for XRs. Crossplane v2 removes this feature **for XRs only**. Managed Resources (MRs) +aren't affected by this change and still support connection details via their +`writeConnectionSecretToRef` field. To learn more about how to specify XR connection details in Crossplane v1, please see the [v1 connection details]({{}}) docs page. diff --git a/content/v2.0/guides/upgrade-to-crossplane-v2.md b/content/v2.0/guides/upgrade-to-crossplane-v2.md index ad18f3793..85692bf38 100644 --- a/content/v2.0/guides/upgrade-to-crossplane-v2.md +++ b/content/v2.0/guides/upgrade-to-crossplane-v2.md @@ -96,6 +96,13 @@ or [External Secrets Operator](https://external-secrets.io/latest/) before upgra ### Composite resource connection details **Removed**: composite resources no longer have native connection details support. +{{}} +**This only affects XRs, managed resources aren't affected.** + +Managed resources (MRs) still support the `writeConnectionSecretToRef` field on any +MR spec. +{{}} + You can recreate this feature by composing your own connection details `Secret` as described in the [connection details composition guide]({{}}). diff --git a/content/v2.0/whats-new/_index.md b/content/v2.0/whats-new/_index.md index 224c0234a..96309e5ca 100644 --- a/content/v2.0/whats-new/_index.md +++ b/content/v2.0/whats-new/_index.md @@ -283,6 +283,7 @@ remained in alpha for over two years and are now unmaintained. Composite resources no longer have native connection details support. You can recreate this feature by composing your own connection details `Secret` as described in the [connection details composition guide]({{}}). +Connection details for managed resources (MRs) aren't affected. 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 diff --git a/content/v2.1/guides/connection-details-composition.md b/content/v2.1/guides/connection-details-composition.md index d4eaca673..7b73426ff 100644 --- a/content/v2.1/guides/connection-details-composition.md +++ b/content/v2.1/guides/connection-details-composition.md @@ -17,7 +17,9 @@ resources and exposes them for the XR. {{}} Crossplane v1 included a feature that automatically created connection details -for XRs. +for XRs. Crossplane v2 removes this feature **for XRs only**. Managed Resources (MRs) +aren't affected by this change and still support connection details via their +`writeConnectionSecretToRef` field. To learn more about how to specify XR connection details in Crossplane v1, please see the [v1 connection details]({{}}) docs page. diff --git a/content/v2.1/guides/upgrade-to-crossplane-v2.md b/content/v2.1/guides/upgrade-to-crossplane-v2.md index ad18f3793..85692bf38 100644 --- a/content/v2.1/guides/upgrade-to-crossplane-v2.md +++ b/content/v2.1/guides/upgrade-to-crossplane-v2.md @@ -96,6 +96,13 @@ or [External Secrets Operator](https://external-secrets.io/latest/) before upgra ### Composite resource connection details **Removed**: composite resources no longer have native connection details support. +{{}} +**This only affects XRs, managed resources aren't affected.** + +Managed resources (MRs) still support the `writeConnectionSecretToRef` field on any +MR spec. +{{}} + You can recreate this feature by composing your own connection details `Secret` as described in the [connection details composition guide]({{}}). diff --git a/content/v2.1/whats-new/_index.md b/content/v2.1/whats-new/_index.md index 224c0234a..96309e5ca 100644 --- a/content/v2.1/whats-new/_index.md +++ b/content/v2.1/whats-new/_index.md @@ -283,6 +283,7 @@ remained in alpha for over two years and are now unmaintained. Composite resources no longer have native connection details support. You can recreate this feature by composing your own connection details `Secret` as described in the [connection details composition guide]({{}}). +Connection details for managed resources (MRs) aren't affected. 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 diff --git a/content/v2.2/guides/connection-details-composition.md b/content/v2.2/guides/connection-details-composition.md index d4eaca673..7b73426ff 100644 --- a/content/v2.2/guides/connection-details-composition.md +++ b/content/v2.2/guides/connection-details-composition.md @@ -17,7 +17,9 @@ resources and exposes them for the XR. {{}} Crossplane v1 included a feature that automatically created connection details -for XRs. +for XRs. Crossplane v2 removes this feature **for XRs only**. Managed Resources (MRs) +aren't affected by this change and still support connection details via their +`writeConnectionSecretToRef` field. To learn more about how to specify XR connection details in Crossplane v1, please see the [v1 connection details]({{}}) docs page. diff --git a/content/v2.2/guides/upgrade-to-crossplane-v2.md b/content/v2.2/guides/upgrade-to-crossplane-v2.md index ad18f3793..85692bf38 100644 --- a/content/v2.2/guides/upgrade-to-crossplane-v2.md +++ b/content/v2.2/guides/upgrade-to-crossplane-v2.md @@ -96,6 +96,13 @@ or [External Secrets Operator](https://external-secrets.io/latest/) before upgra ### Composite resource connection details **Removed**: composite resources no longer have native connection details support. +{{}} +**This only affects XRs, managed resources aren't affected.** + +Managed resources (MRs) still support the `writeConnectionSecretToRef` field on any +MR spec. +{{}} + You can recreate this feature by composing your own connection details `Secret` as described in the [connection details composition guide]({{}}). diff --git a/content/v2.2/whats-new/_index.md b/content/v2.2/whats-new/_index.md index 224c0234a..96309e5ca 100644 --- a/content/v2.2/whats-new/_index.md +++ b/content/v2.2/whats-new/_index.md @@ -283,6 +283,7 @@ remained in alpha for over two years and are now unmaintained. Composite resources no longer have native connection details support. You can recreate this feature by composing your own connection details `Secret` as described in the [connection details composition guide]({{}}). +Connection details for managed resources (MRs) aren't affected. 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