Skip to content

Commit 7631149

Browse files
committed
update doc for Cluster
Signed-off-by: sivchari <shibuuuu5@gmail.com>
1 parent 3656b49 commit 7631149

File tree

4 files changed

+8
-8
lines changed

4 files changed

+8
-8
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -140,7 +140,7 @@ You best watch the Kubernetes pods with something like `k9s -A` or `watch kubect
140140
Let's try our cluster out. We'll make some simple YAML:
141141

142142
```yaml
143-
apiVersion: cluster.x-k8s.io/v1beta1
143+
apiVersion: cluster.x-k8s.io/v1beta2
144144
kind: Cluster
145145
metadata:
146146
name: hello-mailgun
@@ -149,7 +149,7 @@ spec:
149149
pods:
150150
cidrBlocks: ["192.168.0.0/16"]
151151
infrastructureRef:
152-
apiVersion: infrastructure.cluster.x-k8s.io/v1alpha1
152+
apiGroup: infrastructure.cluster.x-k8s.io
153153
kind: MailgunCluster
154154
name: hello-mailgun
155155
---

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -17,18 +17,18 @@ infrastructure object.
1717

1818
```yaml
1919
kind: DockerCluster
20-
apiVersion: infrastructure.cluster.x-k8s.io/v1beta1
20+
apiVersion: infrastructure.cluster.x-k8s.io/v1beta2
2121
metadata:
2222
name: my-cluster-docker
2323
---
2424
kind: Cluster
25-
apiVersion: cluster.x-k8s.io/v1beta1
25+
apiVersion: cluster.x-k8s.io/v1beta2
2626
metadata:
2727
name: my-cluster
2828
spec:
2929
infrastructureRef:
3030
kind: DockerCluster
31-
apiVersion: infrastructure.cluster.x-k8s.io/v1beta1
31+
apiGroup: infrastructure.cluster.x-k8s.io
3232
name: my-cluster-docker
3333
```
3434

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,11 +13,11 @@ Cluster API bootstrap provider MicroK8s (CABPM) is a component responsible for g
1313
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:
1414

1515
```yaml
16-
apiVersion: cluster.x-k8s.io/v1beta1
16+
apiVersion: cluster.x-k8s.io/v1beta2
1717
kind: Cluster
1818
spec:
1919
controlPlaneRef:
20-
apiVersion: controlplane.cluster.x-k8s.io/v1beta1
20+
apiGroup: controlplane.cluster.x-k8s.io
2121
kind: MicroK8sControlPlane
2222
name: capi-aws-control-plane
2323
```

docs/book/src/tasks/workload-bootstrap-gitops.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ Follow the quickstart setup guide for your provider but ensure that CAAPH is ins
1414
Add the labels `argoCDChart: enabled` and `guestbook: enabled` to your desired workload cluster yaml file in the `Cluster` metadata section, for example:
1515

1616
```yaml
17-
apiVersion: cluster.x-k8s.io/v1beta1
17+
apiVersion: cluster.x-k8s.io/v1beta2
1818
kind: Cluster
1919
metadata:
2020
name: my-cluster

0 commit comments

Comments
 (0)