Skip to content

Commit 362595f

Browse files
authored
docs: fix cluster name in README (#330)
1 parent 741be0b commit 362595f

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

README.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -66,27 +66,27 @@ EOF
6666
To create a cluster, update `clusterConfig` variable and run:
6767

6868
```shell
69-
kubectl apply --server-side -f examples/capi-quick-start/docker-cluster.yaml
69+
kubectl apply --server-side -f examples/capi-quick-start/docker-cluster-calico-helm-addon.yaml
7070
```
7171

7272
Wait until control plane is ready:
7373

7474
```shell
75-
kubectl wait clusters/docker-quick-start --for=condition=ControlPlaneInitialized --timeout=5m
75+
kubectl wait clusters/docker-quick-start-helm-addon-calico --for=condition=ControlPlaneInitialized --timeout=5m
7676
```
7777

7878
To get the kubeconfig for the new cluster, run:
7979

8080
```shell
81-
clusterctl get kubeconfig docker-quick-start > docker-kubeconfig
81+
clusterctl get kubeconfig docker-quick-start-helm-addon-calico > docker-kubeconfig
8282
```
8383

8484
If you are not on Linux, you will also need to fix the generated kubeconfig's `server`, run:
8585

8686
```shell
87-
kubectl config set-cluster docker-quick-start \
87+
kubectl config set-cluster docker-quick-start-helm-addon-calico \
8888
--kubeconfig docker-kubeconfig \
89-
--server=https://$(docker port docker-quick-start-lb 6443/tcp)
89+
--server=https://$(docker port docker-quick-start-helm-addon-calico-lb 6443/tcp)
9090
```
9191

9292
Wait until all nodes are ready (this indicates that CNI has been deployed successfully):
@@ -151,7 +151,7 @@ watch -n 0.5 kubectl --kubeconfig docker-kubeconfig get service/traefik
151151
To delete the workload cluster, run:
152152

153153
```shell
154-
kubectl delete cluster docker-quick-start
154+
kubectl delete cluster docker-quick-start-helm-addon-calico
155155
```
156156

157157
Notice that the traefik service is deleted before the cluster is actually finally deleted.

0 commit comments

Comments
 (0)