Merge pull request #11735 from tsuzu/use-labels-for-kustomize

🌱  Use labels for kustomize

Author: k8s-ci-robot

docs/book/src/developer/providers/contracts/bootstrap-config.md

@@ -135,13 +135,14 @@ The value is an underscore-delimited (_) list of versions. Each value MUST point
 The label allows Cluster API controllers to perform automatic conversions for object references, the controllers will pick
 the last available version in the list if multiple versions are found.
 
-To apply the label to CRDs it’s possible to use commonLabels in your `kustomize.yaml` file, usually in `config/crd`:
+To apply the label to CRDs it’s possible to use labels in your `kustomization.yaml` file, usually in `config/crd`:
 
 ```yaml
-commonLabels:
-  cluster.x-k8s.io/v1alpha2: v1alpha1
-  cluster.x-k8s.io/v1alpha3: v1alpha2
-  cluster.x-k8s.io/v1beta1: v1beta1
+labels:
+- pairs:
+    cluster.x-k8s.io/v1alpha2: v1alpha1
+    cluster.x-k8s.io/v1alpha3: v1alpha2
+    cluster.x-k8s.io/v1beta1: v1beta1
 ```
 
 An example of this is in the [Kubeadm Bootstrap provider](https://github.com/kubernetes-sigs/cluster-api/blob/release-1.1/controlplane/kubeadm/config/crd/kustomization.yaml).

docs/book/src/developer/providers/contracts/control-plane.md

@@ -160,13 +160,14 @@ The value is an underscore-delimited (_) list of versions. Each value MUST point
 The label allows Cluster API controllers to perform automatic conversions for object references, the controllers will pick
 the last available version in the list if multiple versions are found.
 
-To apply the label to CRDs it’s possible to use commonLabels in your `kustomize.yaml` file, usually in `config/crd`:
+To apply the label to CRDs it’s possible to use labels in your `kustomization.yaml` file, usually in `config/crd`:
 
 ```yaml
-commonLabels:
-  cluster.x-k8s.io/v1alpha2: v1alpha1
-  cluster.x-k8s.io/v1alpha3: v1alpha2
-  cluster.x-k8s.io/v1beta1: v1beta1
+labels:
+- pairs:
+    cluster.x-k8s.io/v1alpha2: v1alpha1
+    cluster.x-k8s.io/v1alpha3: v1alpha2
+    cluster.x-k8s.io/v1beta1: v1beta1
 ```
 
 An example of this is in the [Kubeadm Bootstrap provider](https://github.com/kubernetes-sigs/cluster-api/blob/release-1.1/controlplane/kubeadm/config/crd/kustomization.yaml).

docs/book/src/developer/providers/contracts/infra-cluster.md

@@ -144,13 +144,14 @@ The value is an underscore-delimited (_) list of versions. Each value MUST point
 The label allows Cluster API controllers to perform automatic conversions for object references, the controllers will pick
 the last available version in the list if multiple versions are found.
 
-To apply the label to CRDs it’s possible to use commonLabels in your `kustomize.yaml` file, usually in `config/crd`:
+To apply the label to CRDs it’s possible to use labels in your `kustomization.yaml` file, usually in `config/crd`:
 
 ```yaml
-commonLabels:
-  cluster.x-k8s.io/v1alpha2: v1alpha1
-  cluster.x-k8s.io/v1alpha3: v1alpha2
-  cluster.x-k8s.io/v1beta1: v1beta1
+labels:
+- pairs:
+    cluster.x-k8s.io/v1alpha2: v1alpha1
+    cluster.x-k8s.io/v1alpha3: v1alpha2
+    cluster.x-k8s.io/v1beta1: v1beta1
 ```
 
 An example of this is in the [Kubeadm Bootstrap provider](https://github.com/kubernetes-sigs/cluster-api/blob/release-1.1/controlplane/kubeadm/config/crd/kustomization.yaml).

docs/book/src/developer/providers/contracts/infra-machine.md

@@ -135,13 +135,14 @@ The value is an underscore-delimited (_) list of versions. Each value MUST point
 The label allows Cluster API controllers to perform automatic conversions for object references, the controllers will pick
 the last available version in the list if multiple versions are found.
 
-To apply the label to CRDs it’s possible to use commonLabels in your `kustomize.yaml` file, usually in `config/crd`:
+To apply the label to CRDs it’s possible to use labels in your `kustomization.yaml` file, usually in `config/crd`:
 
 ```yaml
-commonLabels:
-  cluster.x-k8s.io/v1alpha2: v1alpha1
-  cluster.x-k8s.io/v1alpha3: v1alpha2
-  cluster.x-k8s.io/v1beta1: v1beta1
+labels:
+- pairs:
+    cluster.x-k8s.io/v1alpha2: v1alpha1
+    cluster.x-k8s.io/v1alpha3: v1alpha2
+    cluster.x-k8s.io/v1beta1: v1beta1
 ```
 
 An example of this is in the [Kubeadm Bootstrap provider](https://github.com/kubernetes-sigs/cluster-api/blob/release-1.1/controlplane/kubeadm/config/crd/kustomization.yaml).

docs/book/src/developer/providers/getting-started/building-running-and-testing.md

@@ -59,9 +59,11 @@ Conditions:
 
 In this guide, we are building an _infrastructure provider_. We must tell cluster-api and its developer tooling which type of provider it is. Edit `config/default/kustomization.yaml` and add the following common label. The prefix `infrastructure-` [is used][label_prefix] to detect the provider type.
 
-```sh
-commonLabels:
-  cluster.x-k8s.io/provider: infrastructure-mailgun
+```yaml
+labels:
+- includeSelectors: true
+  pairs:
+    cluster.x-k8s.io/provider: infrastructure-mailgun
 ```
 
 Now you can apply your provider as well: