Skip to content

Commit d2ea5cf

Browse files
committed
Refinements to doc.
1 parent e8988e4 commit d2ea5cf

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

docs/book/src/development/common.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -29,9 +29,9 @@
2929
export CLOUDSTACK_WORKER_MACHINE_OFFERING="Small Instance"
3030
3131
# Referring to a prerequisite capi-compatible image you've loaded into Apache CloudStack
32-
export CLOUDSTACK_TEMPLATE_NAME=kube-v1.20.10/ubuntu-2004
32+
export CLOUDSTACK_TEMPLATE_NAME=kube-v1.23.3/ubuntu-2004
3333
34-
# The SSH KeyPair to log into the VM (Optional: use flavor *managed-ssh*)
34+
# The SSH KeyPair to log into the VM (Optional: you must use clusterctl --flavor *managed-ssh*)
3535
export CLOUDSTACK_SSH_KEY_NAME=CAPCKeyPair6
3636
```
3737
@@ -50,7 +50,7 @@
5050
kubectl apply -f capc-cluster-spec.yaml
5151
```
5252
53-
4. Check the progress of capc-cluster, and wait for all the components to be ready
53+
4. Check the progress of capc-cluster, and wait for all the components (with the exception of MachineDeployment/capc-cluster-md-0) to be ready. (MachineDeployment/capc-cluster-md-0 will not show ready until the CNI is installed.)
5454
```
5555
clusterctl describe cluster capc-cluster
5656
```
@@ -65,7 +65,7 @@
6565
KUBECONFIG=capc-cluster.kubeconfig kubectl apply -f https://projectcalico.docs.tigera.io/manifests/calico.yaml
6666
```
6767
68-
7. Verify the K8s cluster is fully up
68+
7. Verify the K8s cluster is fully up. (It may take a minute for the nodes status to all reach *ready* state.)
6969
1. Run `KUBECONFIG=capc-cluster.kubeconfig kubectl get nodes`, and observe the following output
7070
```
7171
NAME STATUS ROLES AGE VERSION

0 commit comments

Comments
 (0)