Skip to content

[release-1.12] 📖 Fix note about CRD contract label in migration doc #13208

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
k8s-ci-robot merged 1 commit into from
Jan 7, 2026
+2 −2
Merged

[release-1.12] 📖 Fix note about CRD contract label in migration doc #13208

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/book/src/developer/providers/migrations/v1.10-to-v1.11.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2914,13 +2914,13 @@ Implementing the new v1beta2 contract for providers is a multistep operation:
please note that it is necessary to set the `omitzero` JSON marker
2. While implementing the changes above, It is also highly recommended to check the implementation of all the other rules
(documentation for contract rules have been improved in recent releases, worth to take a look!).
3. Change the CRD annotation that document which Cluster API contract is implemented by your Provider. e.g.
3. Change the CRD label that documents which Cluster API contract is implemented by your Provider. e.g.

```yaml
apiVersion: apiextensions.k8s.io/v1
kind: CustomResourceDefinition
metadata:
annotations:
labels:
cluster.x-k8s.io/v1beta2: <your API version>
name: <your CRD name>
```
Expand Down