Merge pull request #12998 from chrischdi/pr-1-10-1-11-document-crd-rbac

📖 book: document required permissions for GetObjectFromContractVersionedRef

Author: k8s-ci-robot

docs/book/src/developer/providers/migrations/v1.10-to-v1.11.md

@@ -2800,6 +2800,12 @@ As documented in [Suggested changes for providers](#suggested-changes-for-provid
   external.GetObjectFromContractVersionedRef(ctx, r.Client, cluster.Spec.InfrastructureRef, cluster.Namespace)
   ```
 
+  - This functions requires the permissions to `get`, `list` and `watch` objects of the type `customresourcedefinitions` to identify the used contract version.
+
+  ```go
+  // +kubebuilder:rbac:groups=apiextensions.k8s.io,resources=customresourcedefinitions,verbs=get;list;watch
+  ```
+
 - Go clients writing status of core Cluster API objects, should use at least Cluster API v1.9 Go types.
   If that is not possible, avoid updating or patching the entire status field and instead you should patch only individual fields.
   (Cluster API v1.9 introduced `.status.v1beta2` fields that are necessary for lossless v1beta2 => v1beta1 => v1beta2 round trips)
@@ -2854,6 +2860,12 @@ As documented in [Suggested changes for providers](#suggested-changes-for-provid
   external.GetObjectFromContractVersionedRef(ctx, r.Client, cluster.Spec.InfrastructureRef, cluster.Namespace)
   ```
 
+  - This functions requires the permissions to `get`, `list` and `watch` objects of the type `customresourcedefinitions` to identify the used contract version.
+
+  ```go
+  // +kubebuilder:rbac:groups=apiextensions.k8s.io,resources=customresourcedefinitions,verbs=get;list;watch
+  ```
+
 - core Cluster API added the new CRD migrator component in the v1.9 release. For more details, see: https://github.com/kubernetes-sigs/cluster-api/issues/11894
   - CRD migration in clusterctl has been deprecated and will be removed in CAPI v1.13, so it's recommended to
     adopt the CRD migrator in providers instead.