From e9d4b1333f15f892982618dae40b49bc00f5d714 Mon Sep 17 00:00:00 2001 From: Tanvir Tatla Date: Thu, 27 Jun 2024 18:54:51 -0700 Subject: [PATCH] Update docs/content/en/docs/getting-started/optional/cni.md Co-authored-by: Chris Doherty --- docs/content/en/docs/getting-started/optional/cni.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/content/en/docs/getting-started/optional/cni.md b/docs/content/en/docs/getting-started/optional/cni.md index c34f157a1dd0..29a0a36cad87 100644 --- a/docs/content/en/docs/getting-started/optional/cni.md +++ b/docs/content/en/docs/getting-started/optional/cni.md @@ -222,8 +222,8 @@ anywhere.eks.amazonaws.com/eksa-cilium: "" ### Node IPs configuration option Starting with release v0.10.0, the `node-cidr-mask-size` [flag](https://kubernetes.io/docs/reference/command-line-tools-reference/kube-controller-manager/#options) -for Kubernetes controller manager (kube-controller-manager) is configurable via the EKS anywhere cluster yaml spec. The `clusterNetwork.nodes` being an optional field, -is not generated in the EKS Anywhere spec using `generate clusterconfig` command. The block for `nodes` will need to be manually added to the cluster yaml spec under the +for Kubernetes controller manager (kube-controller-manager) is configurable via the EKS anywhere cluster YAML spec. The `clusterNetwork.nodes` being an optional field, +is not generated in the EKS Anywhere spec using `generate clusterconfig` command. The block for `nodes` will need to be manually added to the cluster YAML spec under the `clusterNetwork` section: ```yaml