From c5881a11b8e8eb0252fe3dd3ac13ed51edc77229 Mon Sep 17 00:00:00 2001 From: Darshna Das Date: Thu, 13 Jan 2022 19:56:57 +0530 Subject: [PATCH] Removed weave url --- .../tools/kubeadm/high-availability.md | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/content/en/docs/setup/production-environment/tools/kubeadm/high-availability.md b/content/en/docs/setup/production-environment/tools/kubeadm/high-availability.md index ee4b7a7072..854cd8e5a3 100644 --- a/content/en/docs/setup/production-environment/tools/kubeadm/high-availability.md +++ b/content/en/docs/setup/production-environment/tools/kubeadm/high-availability.md @@ -167,14 +167,13 @@ option. Your cluster requirements may need a different configuration. {{< /caution >}} 1. Apply the CNI plugin of your choice: - [Follow these instructions](/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/#pod-network) + [Follow these instructions](/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/#pod-network) to install the CNI provider. Make sure the configuration corresponds to the Pod CIDR specified in the kubeadm configuration file if applicable. - - In this example we are using Weave Net: - - ```sh - kubectl apply -f "https://cloud.weave.works/k8s/net?k8s-version=$(kubectl version | base64 | tr -d '\n')" - ``` + + {{}} + You must pick your own CNI plugin and deploy it before you move on to next step. + If you don't do this, you will not be able to launch your cluster properly. + {{}} 1. Type the following and watch the pods of the control plane components get started: