Update documentation

kubernetes-sigs · Jul 8, 2020 · b6d22f6 · b6d22f6
1 parent f1c1fa3
commit b6d22f6
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 6 deletions.
diff --git a/docs/book/src/clusterctl/developers.md b/docs/book/src/clusterctl/developers.md
@@ -177,9 +177,7 @@ EOF
 The command for getting the kubeconfig file for connecting to a workload cluster is the following:
 
 ```bash
-kubectl --namespace=default get secret/capi-quickstart-kubeconfig -o jsonpath={.data.value} \
-  | base64 --decode \
-  > ./capi-quickstart.kubeconfig
+clusterctl get kubeconfig capi-quickstart
 ```
 
 When using docker-for-mac MacOS, you will need to do a couple of additional

diff --git a/docs/book/src/user/quick-start.md b/docs/book/src/user/quick-start.md
@@ -560,9 +560,7 @@ The control planes won't be `Ready` until we install a CNI in the next step.
 After the first control plane node is up and running, we can retrieve the [workload cluster] Kubeconfig:
 
 ```bash
-kubectl --namespace=default get secret/capi-quickstart-kubeconfig -o jsonpath={.data.value} \
-  | base64 --decode \
-  > ./capi-quickstart.kubeconfig
+clusterctl get kubeconfig capi-quickstart
 ```
 
 ### Deploy a CNI solution