Update configuration section in docs (#8087)

Co-authored-by: Saurabh Parekh <[email protected]>

docs/content/en/docs/clustermgmt/cluster-upgrades/airgapped-upgrades.md

@@ -22,7 +22,7 @@ The procedure to upgrade EKS Anywhere clusters in airgapped environments is simi
 
 If the previous steps succeeded, all of the required EKS Anywhere dependencies are now present in your local registry. Before you upgrade your EKS Anywhere cluster, configure `registryMirrorConfiguration` in your EKS Anywhere cluster specification with the information for your local registry. For details see the [Registry Mirror Configuration documentation.]({{< relref "../../getting-started/optional/registrymirror/#registry-mirror-cluster-spec" >}})
 
->**_NOTE:_** If you are running EKS Anywhere on bare metal, you must configure `osImageURL` and `hookImagesURLPath` in your EKS Anywhere cluster specification with the location of the upgraded node operating system image and hook OS image. For details, reference the [bare metal configuration documentation.]({{< relref "../../getting-started/baremetal/bare-spec/#osimageurl" >}})
+>**_NOTE:_** If you are running EKS Anywhere on bare metal, you must configure `osImageURL` and `hookImagesURLPath` in your EKS Anywhere cluster specification with the location of the upgraded node operating system image and hook OS image. For details, reference the [bare metal configuration documentation.]({{< relref "../../getting-started/baremetal/bare-spec/#osimageurl-optional" >}})
 
 ### Next Steps
 - [Build upgraded node operating system images for your cluster]({{< relref "../../osmgmt/artifacts/#building-images-for-a-specific-eks-anywhere-version" >}})

docs/content/en/docs/clustermgmt/cluster-upgrades/baremetal-upgrades.md

@@ -108,7 +108,7 @@ spec:
       ...
 ```
 
->**_NOTE:_** If you have a custom machine image for your nodes in your cluster config yaml or to upgrade a node or group of nodes to a new operating system version (ie. RHEL 8.7 to RHEL 8.8), you may also need to update your [`TinkerbellDatacenterConfig`]({{< relref "../../getting-started/baremetal/bare-spec/#tinkerbelldatacenterconfig-fields" >}}) or [`TinkerbellMachineConfig`]({{< relref "../../getting-started/baremetal/bare-spec/#tinkerbellmachineconfig-fields" >}}) with the new operating system image URL [`osImageURL`]({{< relref "../../getting-started/baremetal/bare-spec/#osimageurl" >}}). 
+>**_NOTE:_** If you have a custom machine image for your nodes in your cluster config yaml or to upgrade a node or group of nodes to a new operating system version (ie. RHEL 8.7 to RHEL 8.8), you may also need to update your [`TinkerbellDatacenterConfig`]({{< relref "../../getting-started/baremetal/bare-spec/#tinkerbelldatacenterconfig-fields" >}}) or [`TinkerbellMachineConfig`]({{< relref "../../getting-started/baremetal/bare-spec/#tinkerbellmachineconfig-fields" >}}) with the new operating system image URL [`osImageURL`]({{< relref "../../getting-started/baremetal/bare-spec/#osimageurl-optional" >}}). 
 
 and then you will run the [upgrade cluster command]({{< relref "baremetal-upgrades/#upgrade-cluster-command" >}}).
 

docs/content/en/docs/getting-started/_configuration/cluster_clusterNetwork.html

@@ -8,29 +8,29 @@
 ### clusterNetwork.cniConfig (required)
 CNI plugin configuration. Supports `cilium`.
 
-### clusterNetwork.cniConfig.cilium.policyEnforcementMode
+### clusterNetwork.cniConfig.cilium.policyEnforcementMode (optional)
 Optionally specify a policyEnforcementMode of `default`, `always` or `never`.
 
-### clusterNetwork.cniConfig.cilium.egressMasqueradeInterfaces
+### clusterNetwork.cniConfig.cilium.egressMasqueradeInterfaces (optional)
 Optionally specify a network interface name or interface prefix used for
 masquerading. See <a href="/docs/getting-started/optional/cni/#egressmasqueradeinterfaces-option-for-cilium-plugin">EgressMasqueradeInterfaces</a>
 option.
 
-### clusterNetwork.cniConfig.cilium.skipUpgrade
+### clusterNetwork.cniConfig.cilium.skipUpgrade (optional)
 When true, skip Cilium maintenance during upgrades. Also see <a href="/docs/getting-started/optional/cni/#use-a-custom-cni">Use a custom
 CNI</a>.
 
-### clusterNetwork.cniConfig.cilium.routingMode
+### clusterNetwork.cniConfig.cilium.routingMode (optional)
 Optionally specify the routing mode. Accepts `default` and `direct`. Also see <a href="/docs/getting-started/optional/cni/#routingmode-option-for-cilium-plugin">RoutingMode</a>
 option.
 
-### clusterNetwork.cniConfig.cilium.ipv4NativeRoutingCIDR
+### clusterNetwork.cniConfig.cilium.ipv4NativeRoutingCIDR (optional)
 Optionally specify the CIDR to use when RoutingMode is set to direct.
 When specified, Cilium assumes networking for this CIDR is preconfigured and
 hands traffic destined for that range to the Linux network stack without
 applying any SNAT.
 
-### clusterNetwork.cniConfig.cilium.ipv6NativeRoutingCIDR
+### clusterNetwork.cniConfig.cilium.ipv6NativeRoutingCIDR (optional)
 Optionally specify the IPv6 CIDR to use when RoutingMode is set to direct.
 When specified, Cilium assumes networking for this CIDR is preconfigured and
 hands traffic destined for that range to the Linux network stack without

docs/content/en/docs/getting-started/airgapped/_index.md

@@ -39,7 +39,7 @@ The process for preparing your airgapped environment for EKS Anywhere is summari
 
 If the previous steps succeeded, all of the required EKS Anywhere dependencies are now present in your local registry. Before you create your EKS Anywhere cluster, configure `registryMirrorConfiguration` in your EKS Anywhere cluster specification with the information for your local registry. For details see the [Registry Mirror Configuration documentation.]({{< relref "../../getting-started/optional/registrymirror/#registry-mirror-cluster-spec" >}})
 
->**_NOTE:_** If you are running EKS Anywhere on bare metal, you must configure `osImageURL` and `hookImagesURLPath` in your EKS Anywhere cluster specification with the location of your node operating system image and the hook OS image. For details, reference the [bare metal configuration documentation.]({{< relref "../baremetal/bare-spec/#osimageurl" >}})
+>**_NOTE:_** If you are running EKS Anywhere on bare metal, you must configure `osImageURL` and `hookImagesURLPath` in your EKS Anywhere cluster specification with the location of your node operating system image and the hook OS image. For details, reference the [bare metal configuration documentation.]({{< relref "../baremetal/bare-spec/#osimageurl-optional" >}})
 
 ### Next Steps
 - Review EKS Anywhere [cluster networking requirements]({{< relref "../ports" >}})