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

Clarify that it's not always m.crossplane.io 

Signed-off-by: Nic Cope <nicc@rk0n.org>
This commit is contained in:
Nic Cope 2025-08-15 13:43:40 -07:00
parent 4220cebe6e
commit 5e5a548113
2 changed files with 34 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
content/master/guides/upgrade-to-crossplane-v2.md
View File

@ -177,17 +177,17 @@ metadata:
spec: spec:
activate: activate:
# Legacy cluster-scoped resources (existing v1 resources) # Legacy cluster-scoped resources (existing v1 resources)
- buckets.s3.aws.crossplane.io - buckets.s3.aws.upbound.io
- instances.ec2.aws.crossplane.io - instances.ec2.aws.upbound.io
# Modern namespaced resources (new v2 resources) # Modern namespaced resources (new v2 resources)
- buckets.s3.aws.m.crossplane.io - buckets.s3.aws.m.upbound.io
- instances.ec2.aws.m.crossplane.io - instances.ec2.aws.m.upbound.io
``` ```
{{<hint "tip">}} {{<hint "tip">}}
Notice the distinction: `s3.aws.crossplane.io` (legacy cluster-scoped) vs Notice the distinction: `s3.aws.upbound.io` (legacy cluster-scoped) vs
`s3.aws.m.crossplane.io` (v2 namespaced). The `.m.` indicates modern `s3.aws.m.upbound.io` (v2 namespaced). The `.m.` indicates modern
namespaced managed resources. namespaced managed resources.
{{</hint>}} {{</hint>}}
@ -246,10 +246,18 @@ For example `provider-aws-s3:v2.0.0` has two `Bucket` MRs:
The `spec.forProvider` and `status.atProvider` fields are schematically The `spec.forProvider` and `status.atProvider` fields are schematically
identical. identical.
{{<hint "note">}} {{<hint "tip">}}
Use `kubectl get mrds` to see available MR API versions. Use `kubectl get mrds` to see available MR API versions.
{{</hint>}} {{</hint>}}
{{<hint "note">}}
Not all providers use `.crossplane.io` domains. For example, `provider-aws-s3`
uses `.upbound.io` domains for historical reasons. The general pattern for
namespaced resources is adding `.m` to the existing domain: `<domain>` becomes
`m.<domain>` (like `upbound.io` → `m.upbound.io` or `crossplane.io` →
`m.crossplane.io`).
{{</hint>}}
**Before (v1 cluster-scoped)**: **Before (v1 cluster-scoped)**:
```yaml ```yaml
apiVersion: apiextensions.crossplane.io/v1 apiVersion: apiextensions.crossplane.io/v1
@ -271,7 +279,7 @@ spec:
source: Inline source: Inline
inline: inline:
template: | template: |
apiVersion: s3.aws.crossplane.io/v1beta2 apiVersion: s3.aws.upbound.io/v1beta2
kind: Bucket kind: Bucket
metadata: metadata:
name: {{ .observed.composite.resource.metadata.name }} name: {{ .observed.composite.resource.metadata.name }}
@ -301,7 +309,7 @@ spec:
source: Inline source: Inline
inline: inline:
template: | template: |
apiVersion: s3.aws.m.crossplane.io/v1beta1 # Added .m, reset to v1beta1 apiVersion: s3.aws.m.upbound.io/v1beta1 # Added .m, reset to v1beta1
kind: Bucket kind: Bucket
metadata: metadata:
name: {{ .observed.composite.resource.metadata.name }} name: {{ .observed.composite.resource.metadata.name }}

26
content/v2.0/guides/upgrade-to-crossplane-v2.md
View File

@ -177,17 +177,17 @@ metadata:
spec: spec:
activate: activate:
# Legacy cluster-scoped resources (existing v1 resources) # Legacy cluster-scoped resources (existing v1 resources)
- buckets.s3.aws.crossplane.io - buckets.s3.aws.upbound.io
- instances.ec2.aws.crossplane.io - instances.ec2.aws.upbound.io
# Modern namespaced resources (new v2 resources) # Modern namespaced resources (new v2 resources)
- buckets.s3.aws.m.crossplane.io - buckets.s3.aws.m.upbound.io
- instances.ec2.aws.m.crossplane.io - instances.ec2.aws.m.upbound.io
``` ```
{{<hint "tip">}} {{<hint "tip">}}
Notice the distinction: `s3.aws.crossplane.io` (legacy cluster-scoped) vs Notice the distinction: `s3.aws.upbound.io` (legacy cluster-scoped) vs
`s3.aws.m.crossplane.io` (v2 namespaced). The `.m.` indicates modern `s3.aws.m.upbound.io` (v2 namespaced). The `.m.` indicates modern
namespaced managed resources. namespaced managed resources.
{{</hint>}} {{</hint>}}
@ -246,10 +246,18 @@ For example `provider-aws-s3:v2.0.0` has two `Bucket` MRs:
The `spec.forProvider` and `status.atProvider` fields are schematically The `spec.forProvider` and `status.atProvider` fields are schematically
identical. identical.
{{<hint "note">}} {{<hint "tip">}}
Use `kubectl get mrds` to see available MR API versions. Use `kubectl get mrds` to see available MR API versions.
{{</hint>}} {{</hint>}}
{{<hint "note">}}
Not all providers use `.crossplane.io` domains. For example, `provider-aws-s3`
uses `.upbound.io` domains for historical reasons. The general pattern for
namespaced resources is adding `.m` to the existing domain: `<domain>` becomes
`m.<domain>` (like `upbound.io` → `m.upbound.io` or `crossplane.io` →
`m.crossplane.io`).
{{</hint>}}
**Before (v1 cluster-scoped)**: **Before (v1 cluster-scoped)**:
```yaml ```yaml
apiVersion: apiextensions.crossplane.io/v1 apiVersion: apiextensions.crossplane.io/v1
@ -271,7 +279,7 @@ spec:
source: Inline source: Inline
inline: inline:
template: | template: |
apiVersion: s3.aws.crossplane.io/v1beta2 apiVersion: s3.aws.upbound.io/v1beta2
kind: Bucket kind: Bucket
metadata: metadata:
name: {{ .observed.composite.resource.metadata.name }} name: {{ .observed.composite.resource.metadata.name }}
@ -301,7 +309,7 @@ spec:
source: Inline source: Inline
inline: inline:
template: | template: |
apiVersion: s3.aws.m.crossplane.io/v1beta1 # Added .m, reset to v1beta1 apiVersion: s3.aws.m.upbound.io/v1beta1 # Added .m, reset to v1beta1
kind: Bucket kind: Bucket
metadata: metadata:
name: {{ .observed.composite.resource.metadata.name }} name: {{ .observed.composite.resource.metadata.name }}