Merge pull request #80773 from dfitzmau/OCPBUGS-38800

OCPBUGS-38800: Added link to About the Kubernetes NMState Operator fo…

Author: Srivaralakshmi

networking/k8s_nmstate/k8s-nmstate-about-the-k8s-nmstate-operator.adoc

@@ -20,7 +20,7 @@ Before you can use NMState with {product-title}, you must install the Kubernetes
 ====
 The Kubernetes NMState Operator updates the network configuration of a secondary NIC. The Operator cannot update the network configuration of the primary NIC, or update the `br-ex` bridge on most on-premise networks.
 
-On a bare-metal platform, using the Kubernetes NMState Operator to update the `br-ex` bridge network configuration is only supported if you set the `br-ex` bridge as the interface in a machine config manifest file. To update the `br-ex` bridge as a postinstallation task, you must set the `br-ex` bridge as the interface in the NMState configuration of the `NodeNetworkConfigurationPolicy` custom resource (CR) for your cluster.
+On a bare-metal platform, using the Kubernetes NMState Operator to update the `br-ex` bridge network configuration is only supported if you set the `br-ex` bridge as the interface in a machine config manifest file. To update the `br-ex` bridge as a postinstallation task, you must set the `br-ex` bridge as the interface in the NMState configuration of the `NodeNetworkConfigurationPolicy` custom resource (CR) for your cluster. For more information, see xref:../../installing/installing_bare_metal_ipi/ipi-install-post-installation-configuration.adoc#creating-manifest-file-customized-br-ex-bridge_ipi-install-post-installation-configuration[Creating a manifest object that includes a customized br-ex bridge] in _Postinstallation configuration_.
 ====
 
 {product-title} uses link:https://nmstate.github.io/[`nmstate`] to report on and configure the state of the node network. This makes it possible to modify the network policy configuration, such as by creating a Linux bridge on all nodes, by applying a single configuration manifest to the cluster.