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

clarify that plural names should be used in MRAPs 

Signed-off-by: Jared Watts <jbw976@gmail.com>
This commit is contained in:
Jared Watts 2025-09-03 16:24:30 -07:00
parent 0248bb39c6
commit 622a3c343f
No known key found for this signature in database
GPG Key ID: 0467EEAE3B6EC0D2
2 changed files with 30 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
content/master/managed-resources/managed-resource-activation-policies.md
View File

@ -83,6 +83,13 @@ spec:
- clusters.eks.aws.m.crossplane.io
```
{{<hint "important">}}
Use the **plural** name when using a complete MRD name, aligning with how
Kubernetes expresses the complete names of CRDs.
For example, use `buckets`, as opposed to `bucket`, in `buckets.s3.aws.m.crossplane.io`.
{{</hint>}}
### Wildcard patterns
Use `*` wildcards to match multiple resources:
@ -443,8 +450,9 @@ conflicts. This enables team-based activation strategies and Configuration
package dependencies.
<!-- vale alex.ProfanityUnlikely = NO -->
1. **Start specific, broaden as needed** - Begin with exact resource names,
add wildcards only when beneficial for maintainability
1. **Start specific, broaden as needed** - Begin with exact resource names
(using the plural name for each resource), add wildcards only when beneficial for
maintainability
2. **Plan for provider evolution** - Design wildcard patterns that
accommodate new resources as providers add them (for example,
`*.s3.aws.m.crossplane.io` works for future S3 resources)

12
content/v2.0/managed-resources/managed-resource-activation-policies.md
View File

@ -83,6 +83,13 @@ spec:
- clusters.eks.aws.m.crossplane.io
```
{{<hint "important">}}
Use the **plural** name when using a complete MRD name, aligning with how
Kubernetes expresses the complete names of CRDs.
For example, use `buckets`, as opposed to `bucket`, in `buckets.s3.aws.m.crossplane.io`.
{{</hint>}}
### Wildcard patterns
Use `*` wildcards to match multiple resources:
@ -443,8 +450,9 @@ conflicts. This enables team-based activation strategies and Configuration
package dependencies.
<!-- vale alex.ProfanityUnlikely = NO -->
1. **Start specific, broaden as needed** - Begin with exact resource names,
add wildcards only when beneficial for maintainability
1. **Start specific, broaden as needed** - Begin with exact resource names
(using the plural name for each resource), add wildcards only when beneficial for
maintainability
2. **Plan for provider evolution** - Design wildcard patterns that
accommodate new resources as providers add them (for example,
`*.s3.aws.m.crossplane.io` works for future S3 resources)