From 8a5c44c874e5258c6ece47ee23b5eaa6b782e135 Mon Sep 17 00:00:00 2001 From: Darshna Das Date: Sun, 16 Jan 2022 20:47:37 +0530 Subject: [PATCH] Added changes --- .../tools/kubeadm/high-availability.md | 6 +++--- 1 file changed, 3 insertions(+), 3 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 854cd8e5a3..922b01c2ef 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 @@ -170,10 +170,10 @@ option. Your cluster requirements may need a different configuration. [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. - {{}} - You must pick your own CNI plugin and deploy it before you move on to next step. + {{< note >}} + You must pick a network plugin that suits your use case 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. - {{}} + {{< /note >}} 1. Type the following and watch the pods of the control plane components get started: