More details on VFLAG

Author: joemarshallmsft

articles/operator-nexus/concepts-nexus-availability.md

@@ -94,7 +94,7 @@ For another workload, you might choose not to "layer" the multiple levels of red
 
 ### Site Deployment and Connection
 
-Each Nexus site is connected to an Azure region that hosts the in-Azure resources such as Cluster Manager, Nexus Fabric Controller etc.  Ideally, connect each Nexus site to a different Azure region in order to maximize the resilience of the Nexus deployment to any interruption of the Azure regions. Depending on the geography, there is likely to be a trade-off between maximizing the number of distinct Azure regions the deployment is taking a dependency on, and any other restrictions around data residency or sovereignty.
+Each Nexus site is connected to an Azure region that hosts the in-Azure resources such as Cluster Manager, Nexus Fabric Controller etc.  Ideally, connect each Nexus site to a different Azure region in order to maximize the resilience of the Nexus deployment to any interruption of the Azure regions. Depending on the geography, there is likely to be a trade-off between maximizing the number of distinct Azure regions the deployment is taking a dependency on, and any other restrictions around data residency or sovereignty. Note also that the relationship between the on-premise NAKS clusters and Cluster Manager is not necessarily 1:1. A single Cluster Manager can manage clusters in multiple sites.
 
 Virtual machines, including Virtual Network Functions (VNFs) and Nexus Azure Kubernetes Service (AKS), as well as services hosted on-premises within Operator Nexus, are provided with connectivity through highly available links between them and the network fabric. This enhanced connectivity is achieved through the utilization of redundant physical connections, which are seamlessly facilitated by Single Root Input/Output Virtualization (SR-IOV) interfaces employing Virtual Function Link Aggregation (VF-Lag) technology.