From e1f11eb4b800bcb31a6995d178edea991bd13794 Mon Sep 17 00:00:00 2001 From: Ivy Ostosh Date: Wed, 16 Nov 2022 13:44:52 -0600 Subject: [PATCH] Fix blank line (#4112) --- .../getting-started/production-environment/vsphere-getstarted.md | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/content/en/docs/getting-started/production-environment/vsphere-getstarted.md b/docs/content/en/docs/getting-started/production-environment/vsphere-getstarted.md index 23a26f9db0c3..8441049795eb 100644 --- a/docs/content/en/docs/getting-started/production-environment/vsphere-getstarted.md +++ b/docs/content/en/docs/getting-started/production-environment/vsphere-getstarted.md @@ -189,7 +189,6 @@ Follow these steps if you want to use your initial cluster to create and manage -f eksa-w01-cluster.yaml \ # --install-packages packages.yaml \ # uncomment to install curated packages at cluster creation --kubeconfig mgmt/mgmt-eks-a-cluster.kubeconfig - ``` As noted earlier, adding the `--kubeconfig` option tells `eksctl` to use the management cluster identified by that kubeconfig file to create a different workload cluster.