make book use v1beta2 API

Signed-off-by: sivchari <shibuuuu5@gmail.com>

Author: sivchari

docs/book/src/developer/core/controllers/machine-pool.md

@@ -108,7 +108,7 @@ Note: Infrastructure providers can support MachinePool Machines by having the In
 Example
 ```yaml
 kind: MyMachinePool
-apiVersion: infrastructure.cluster.x-k8s.io/v1beta1
+apiVersion: infrastructure.cluster.x-k8s.io/v1beta2
 spec:
     providerIDList:
       - cloud:////my-cloud-provider-id-0

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

@@ -140,7 +140,7 @@ You best watch the Kubernetes pods with something like `k9s -A` or `watch kubect
 Let's try our cluster out. We'll make some simple YAML:
 
 ```yaml
-apiVersion: cluster.x-k8s.io/v1beta1
+apiVersion: cluster.x-k8s.io/v1beta2
 kind: Cluster
 metadata:
   name: hello-mailgun
@@ -149,7 +149,7 @@ spec:
     pods:
       cidrBlocks: ["192.168.0.0/16"]
   infrastructureRef:
-    apiVersion: infrastructure.cluster.x-k8s.io/v1alpha1
+    apiGroup: infrastructure.cluster.x-k8s.io/v1beta2
     kind: MailgunCluster
     name: hello-mailgun
 ---

docs/book/src/security/pod-security-standards.md

@@ -12,7 +12,7 @@ By adding the following variables and patches Pod Security Standards can be adde
 ### Adding the variables to a ClusterClass
 
 ```yaml
-apiVersion: cluster.x-k8s.io/v1beta1
+apiVersion: cluster.x-k8s.io/v1beta2
 kind: ClusterClass
 spec:
   variables:
@@ -62,7 +62,7 @@ Use this patch if the following keys **already exist** inside the `KubeadmContro
 - `.spec.template.spec.kubeadmConfigSpec.files`
 
 ```yaml
-apiVersion: cluster.x-k8s.io/v1beta1
+apiVersion: cluster.x-k8s.io/v1beta2
 kind: ClusterClass
 spec:
   ...
@@ -71,7 +71,7 @@ spec:
     description: "Adds an admission configuration for PodSecurity to the kube-apiserver."
     definitions:
     - selector:
-        apiVersion: controlplane.cluster.x-k8s.io/v1beta1
+        apiVersion: controlplane.cluster.x-k8s.io/v1beta2
         kind: KubeadmControlPlaneTemplate
         matchResources:
           controlPlane: true
@@ -128,7 +128,7 @@ Use this patches if the following keys **do not** exist inside the `KubeadmContr
 > **Attention:** Existing values inside the `KubeadmControlPlaneTemplate` at the mentioned keys will be replaced by this patch.
 
 ```yaml
-apiVersion: cluster.x-k8s.io/v1beta1
+apiVersion: cluster.x-k8s.io/v1beta2
 kind: ClusterClass
 spec:
   ...
@@ -137,7 +137,7 @@ spec:
     description: "Adds an admission configuration for PodSecurity to the kube-apiserver."
     definitions:
     - selector:
-        apiVersion: controlplane.cluster.x-k8s.io/v1beta1
+        apiVersion: controlplane.cluster.x-k8s.io/v1beta2
         kind: KubeadmControlPlaneTemplate
         matchResources:
           controlPlane: true
@@ -195,7 +195,7 @@ It is also possible to disable this patch or configure different levels for the
 using variables.
 
 ```yaml
-apiVersion: cluster.x-k8s.io/v1beta1
+apiVersion: cluster.x-k8s.io/v1beta2
 kind: Cluster
 metadata:
   name: "my-cluster"

docs/book/src/tasks/bootstrap/kubeadm-bootstrap/index.md

@@ -17,18 +17,18 @@ infrastructure object.
 
 ```yaml
 kind: DockerCluster
-apiVersion: infrastructure.cluster.x-k8s.io/v1beta1
+apiVersion: infrastructure.cluster.x-k8s.io/v1beta2
 metadata:
   name: my-cluster-docker
 ---
 kind: Cluster
-apiVersion: cluster.x-k8s.io/v1beta1
+apiVersion: cluster.x-k8s.io/v1beta2
 metadata:
   name: my-cluster
 spec:
   infrastructureRef:
     kind: DockerCluster
-    apiVersion: infrastructure.cluster.x-k8s.io/v1beta1
+    apiGroup: infrastructure.cluster.x-k8s.io
     name: my-cluster-docker
 ```
 
@@ -37,20 +37,20 @@ the `KubeadmConfig` bootstrap object.
 
 ```yaml
 kind: KubeadmConfig
-apiVersion: bootstrap.cluster.x-k8s.io/v1beta1
+apiVersion: bootstrap.cluster.x-k8s.io/v1beta2
 metadata:
   name: my-control-plane1-config
 spec:
   initConfiguration:
     nodeRegistration: {} # node registration parameters are automatically injected by CAPD according to the kindest/node image in use.
 ---
 kind: DockerMachine
-apiVersion: infrastructure.cluster.x-k8s.io/v1beta1
+apiVersion: infrastructure.cluster.x-k8s.io/v1beta2
 metadata:
   name: my-control-plane1-docker
 ---
 kind: Machine
-apiVersion: cluster.x-k8s.io/v1beta1
+apiVersion: cluster.x-k8s.io/v1beta2
 metadata:
   name: my-control-plane1
   labels:
@@ -61,11 +61,11 @@ spec:
   bootstrap:
     configRef:
       kind: KubeadmConfig
-      apiVersion: bootstrap.cluster.x-k8s.io/v1beta1
+      apiGroup: bootstrap.cluster.x-k8s.io
       name: my-control-plane1-config
   infrastructureRef:
     kind: DockerMachine
-    apiVersion: infrastructure.cluster.x-k8s.io/v1beta1
+    apiGroup: infrastructure.cluster.x-k8s.io
     name: my-control-plane1-docker
   version: "v1.19.1"
 ```
@@ -107,38 +107,31 @@ Valid combinations of configuration objects are:
 Bootstrap control plane node:
 ```yaml
 kind: KubeadmConfig
-apiVersion: bootstrap.cluster.x-k8s.io/v1beta1
+apiVersion: bootstrap.cluster.x-k8s.io/v1beta2
 metadata:
   name: my-control-plane1-config
 spec:
   initConfiguration:
-    nodeRegistration:
-      nodeRegistration: {} # node registration parameters are automatically injected by CAPD according to the kindest/node image in use.
 ```
 
 Additional control plane nodes:
 ```yaml
 kind: KubeadmConfig
-apiVersion: bootstrap.cluster.x-k8s.io/v1beta1
+apiVersion: bootstrap.cluster.x-k8s.io/v1beta2
 metadata:
   name: my-control-plane2-config
 spec:
   joinConfiguration:
-    nodeRegistration:
-      nodeRegistration: {} # node registration parameters are automatically injected by CAPD according to the kindest/node image in use.
-    controlPlane: {}
 ```
 
 worker nodes:
 ```yaml
 kind: KubeadmConfig
-apiVersion: bootstrap.cluster.x-k8s.io/v1beta1
+apiVersion: bootstrap.cluster.x-k8s.io/v1beta2
 metadata:
   name: my-worker1-config
 spec:
   joinConfiguration:
-    nodeRegistration:
-      nodeRegistration: {} # node registration parameters are automatically injected by CAPD according to the kindest/node image in use.
 ```
 
 ### Bootstrap Orchestration

docs/book/src/tasks/bootstrap/kubeadm-bootstrap/kubelet-config.md

@@ -22,7 +22,7 @@ This method is easy to replace the whole kubelet configuration generated by kube
 ### KubeadmControlPlaneTemplate
 
 ```yaml
-apiVersion: controlplane.cluster.x-k8s.io/v1beta1
+apiVersion: controlplane.cluster.x-k8s.io/v1beta2
 kind: KubeadmControlPlaneTemplate
 metadata:
   name: cloudinit-control-plane
@@ -98,19 +98,21 @@ spec:
             criSocket: unix:///var/run/containerd/containerd.sock
             # Here we configure kubelet to use the KubeletConfiguration file we put on nodes via KubeadmConfigSpec.files
             kubeletExtraArgs:
-              config: "/etc/kubernetes/kubelet/config.yaml"
+              - name: config
+                value: "/etc/kubernetes/kubelet/config.yaml"
         joinConfiguration:
           nodeRegistration:
             criSocket: unix:///var/run/containerd/containerd.sock
             # Here we configure kubelet to use the KubeletConfiguration file we put on nodes via KubeadmConfigSpec.files
             kubeletExtraArgs:
-              config: "/etc/kubernetes/kubelet/config.yaml"
+              - name: config
+                value: "/etc/kubernetes/kubelet/config.yaml"
 ```
 
 ### KubeadmConfigTemplate
 
 ```yaml
-apiVersion: bootstrap.cluster.x-k8s.io/v1beta1
+apiVersion: bootstrap.cluster.x-k8s.io/v1beta2
 kind: KubeadmConfigTemplate
 metadata:
   name: cloudinit-default-worker-bootstraptemplate
@@ -185,7 +187,8 @@ spec:
           criSocket: unix:///var/run/containerd/containerd.sock
           # Here we configure kubelet to use the KubeletConfiguration file we put on nodes via KubeadmConfigSpec.files
           kubeletExtraArgs:
-            config: "/etc/kubernetes/kubelet/config.yaml"
+            - name: config
+              value: "/etc/kubernetes/kubelet/config.yaml"
 ```
 
 ## Set kubelet flags via `KubeadmConfigSpec.kubeletExtraArgs`
@@ -197,7 +200,7 @@ This method is useful when you want to set kubelet flags that are not configurab
 ### KubeadmControlPlaneTemplate
 
 ```yaml
-apiVersion: controlplane.cluster.x-k8s.io/v1beta1
+apiVersion: controlplane.cluster.x-k8s.io/v1beta2
 kind: KubeadmControlPlaneTemplate
 metadata:
   name: kubelet-extra-args-control-plane
@@ -211,23 +214,29 @@ spec:
             criSocket: unix:///var/run/containerd/containerd.sock
             # Set kubelet flags via KubeadmConfigSpec.kubeletExtraArgs
             kubeletExtraArgs:
-              kube-reserved: cpu=1,memory=2Gi,ephemeral-storage=1Gi
-              system-reserved: cpu=500m,memory=1Gi,ephemeral-storage=1Gi
-              eviction-hard: memory.available<500Mi,nodefs.available<10%
+              - name: kube-reserved
+                value: "cpu=1,memory=2Gi,ephemeral-storage=1Gi"
+              - name: system-reserved
+                value: "cpu=500m,memory=1Gi,ephemeral-storage=1Gi"
+              - name: eviction-hard
+                value: "memory.available<500Mi,nodefs.available<10%"
         joinConfiguration:
           nodeRegistration:
             criSocket: unix:///var/run/containerd/containerd.sock
             # Set kubelet flags via KubeadmConfigSpec.kubeletExtraArgs
             kubeletExtraArgs:
-              kube-reserved: cpu=1,memory=2Gi,ephemeral-storage=1Gi
-              system-reserved: cpu=500m,memory=1Gi,ephemeral-storage=1Gi
-              eviction-hard: memory.available<500Mi,nodefs.available<10%
+              - name: kube-reserved
+                value: "cpu=1,memory=2Gi,ephemeral-storage=1Gi"
+              - name: system-reserved
+                value: "cpu=500m,memory=1Gi,ephemeral-storage=1Gi"
+              - name: eviction-hard
+                value: "memory.available<500Mi,nodefs.available<10%"
 ```
 
 ### KubeadmConfigTemplate
 
 ```yaml
-apiVersion: bootstrap.cluster.x-k8s.io/v1beta1
+apiVersion: bootstrap.cluster.x-k8s.io/v1beta2
 kind: KubeadmConfigTemplate
 metadata:
   name: kubelet-extra-args-default-worker-bootstraptemplate
@@ -240,9 +249,12 @@ spec:
           criSocket: unix:///var/run/containerd/containerd.sock
           # Set kubelet flags via KubeadmConfigSpec.kubeletExtraArgs
           kubeletExtraArgs:
-            kube-reserved: cpu=1,memory=2Gi,ephemeral-storage=1Gi
-            system-reserved: cpu=500m,memory=1Gi,ephemeral-storage=1Gi
-            eviction-hard: memory.available<500Mi,nodefs.available<10%
+            - name: kube-reserved
+              value: "cpu=1,memory=2Gi,ephemeral-storage=1Gi"
+            - name: system-reserved
+              value: "cpu=500m,memory=1Gi,ephemeral-storage=1Gi"
+            - name: eviction-hard
+              value: "memory.available<500Mi,nodefs.available<10%"
 ```
 
 ## Use kubeadm's `kubeletconfiguration` patch target
@@ -254,7 +266,7 @@ This method is useful when you want to change the kubelet configuration file par
 ### KubeadmControlPlaneTemplate
 
 ```yaml
-apiVersion: controlplane.cluster.x-k8s.io/v1beta1
+apiVersion: controlplane.cluster.x-k8s.io/v1beta2
 kind: KubeadmControlPlaneTemplate
 metadata:
   name: kubeadm-config-template-control-plane
@@ -306,7 +318,7 @@ spec:
 ### KubeadmConfigTemplate
 
 ```yaml
-apiVersion: bootstrap.cluster.x-k8s.io/v1beta1
+apiVersion: bootstrap.cluster.x-k8s.io/v1beta2
 kind: KubeadmConfigTemplate
 metadata:
   name: kubeadm-config-template-default-worker-bootstraptemplate
@@ -346,4 +358,4 @@ spec:
         # Here we specify the directory that contains the patch files
         patches:
           directory: /etc/kubernetes/patches
-```
+```

docs/book/src/tasks/bootstrap/microk8s-bootstrap.md

@@ -13,19 +13,19 @@ Cluster API bootstrap provider MicroK8s (CABPM) is a component responsible for g
 MicroK8s defines a `MicroK8sControlPlane` definition as well as the `MachineDeployment` to configure the control plane and worker nodes respectively. The `MicroK8sControlPlane` is linked in the cluster definition as shown in the following example:
 
 ```yaml
-apiVersion: cluster.x-k8s.io/v1beta1
+apiVersion: cluster.x-k8s.io/v1beta2
 kind: Cluster
 spec:
   controlPlaneRef:
-    apiVersion: controlplane.cluster.x-k8s.io/v1beta1
+    apiGroup: controlplane.cluster.x-k8s.io
     kind: MicroK8sControlPlane
     name: capi-aws-control-plane
 ```
 
 A control plane manifest section includes the Kubernetes version, the replica number as well as the `MicroK8sConfig`:
 
 ```yaml
-apiVersion: controlplane.cluster.x-k8s.io/v1beta1
+apiVersion: controlplane.cluster.x-k8s.io/v1beta2
 kind: MicroK8sControlPlane
 spec:
   controlPlaneConfig:
@@ -41,7 +41,7 @@ spec:
 The worker nodes are configured through the `MachineDeployment` object:
 
 ```yaml
-apiVersion: cluster.x-k8s.io/v1beta1
+apiVersion: cluster.x-k8s.io/v1beta2
 kind: MachineDeployment
 metadata:
   name: capi-aws-md-0
@@ -57,7 +57,7 @@ spec:
       version: v1.23.0     
       bootstrap:
         configRef:
-          apiVersion: bootstrap.cluster.x-k8s.io/v1beta1
+          apiGroup: bootstrap.cluster.x-k8s.io
           kind: MicroK8sConfigTemplate
           name: capi-aws-md-0
 ......

docs/book/src/tasks/certs/auto-rotate-certificates-in-kcp.md

@@ -10,7 +10,7 @@ To configure a rollout on the KCP machines you need to set `.rolloutBefore.certi
 
 Example: 
 ```yaml
-apiVersion: controlplane.cluster.x-k8s.io/v1beta1
+apiVersion: controlplane.cluster.x-k8s.io/v1beta2
 kind: KubeadmControlPlane
 metadata:
   name: example-control-plane
@@ -64,4 +64,4 @@ KubeadmConfig corresponding to the current machine.
 </aside>
 
 <!-- links -->
-[RFC3339]: https://www.ietf.org/rfc/rfc3339.txt
+[RFC3339]: https://www.ietf.org/rfc/rfc3339.txt

docs/book/src/tasks/cluster-resource-set.md

@@ -19,7 +19,7 @@ This can be accomplished by labeling the clusters with the specific cloud (e.g.
 For example, you could have the following for OpenStack:
 
 ```yaml
-apiVersion: addons.cluster.x-k8s.io/v1beta1
+apiVersion: addons.cluster.x-k8s.io/v1beta2
 kind: ClusterResourceSet
 metadata:
   name: cloud-provider-openstack