Merge pull request #225396 from JnHs/jh-arcrb-net0123

network requirement updates

Author: Stacyrch140

articles/azure-arc/network-requirements-consolidated.md

@@ -1,7 +1,7 @@
 ---
 title: Azure Arc network requirements
 description: A consolidated list of network requirements for Azure Arc features and Azure Arc-enabled services. Lists endpoints, ports, and protocols.
-ms.date: 03/01/2022
+ms.date: 01/30/2023
 ms.topic: reference
 ---
 

articles/azure-arc/resource-bridge/includes/network-requirements.md

@@ -1,9 +1,6 @@
 ---
-author: MikeRayMSFT
-ms.author: mikeray
-ms.service: azure-arc
 ms.topic: include
-ms.date: 12/13/2022
+ms.date: 01/30/2023
 ---
 
 ### Outbound connectivity
@@ -22,10 +19,7 @@ The firewall and proxy URLs below must be allowlisted in order to enable communi
 |Azure Arc for Kubernetes container image download| 443 | `https://azurearcfork8sdev.azurecr.io`|  Appliance VM IP and Control Plane IP need outbound connection. | Required to pull container images. |
 |ADHS telemetry service | 443 | `adhs.events.data.microsoft.com`| Appliance VM IP and Control Plane IP need outbound connection. | Runs inside the appliance/mariner OS. Used periodically to send Microsoft required diagnostic data from control plane nodes. Used when telemetry is coming off Mariner, which would mean any Kubernetes control plane. |
 |Microsoft events data service | 443 |`v20.events.data.microsoft.com`| Appliance VM IP and Control Plane IP need outbound connection. | Used periodically to send Microsoft required diagnostic data from the Azure Stack HCI or Windows Server host. Used when telemetry is coming off Windows like Windows Server or HCI. |
-
-### SSL proxy configuration
-
-Azure Arc resource bridge must be configured for proxy so that it can connect to the Azure services. This configuration is handled automatically. However, proxy configuration of the management machine isn't configured by the Azure Arc resource bridge.
-
-There are only two certificates that should be relevant when deploying the Arc resource bridge behind an SSL proxy: the SSL certificate for your SSL proxy (so that the host and guest trust your proxy FQDN and can establish an SSL connection to it), and the SSL certificate of the Microsoft download servers. This certificate must be trusted by your proxy server itself, as the proxy is the one establishing the final connection and needs to trust the endpoint. Non-Windows machines may not trust this second certificate by default, so you may need to ensure that it's trusted.
-
+|Log collection for Arc Resource Bridge| 443 | `linuxgeneva-microsoft.azurecr.io`| Appliance VM IP and Control Plane IP need outbound connection. | Push logs for Appliance managed components.|
+|Resource bridge components download| 443 | `kvamanagementoperator.azurecr.io`| Appliance VM IP and Control Plane IP need outbound connection. | Required to pull artifacts for Appliance managed components.|
+|Microsoft Container Registry| 443 | `https://mcr.microsoft.com`| Management machine, Appliance VM IP and Control Plane IP need outbound connection. | Download container images for Arc Resource Bridge.|
+|Custom Locations| 443 | `sts.windows.net`| Appliance VM IP and Control Plane IP need outbound connection. | Required for use by the Custom Locations cluster extension.|

articles/azure-arc/resource-bridge/network-requirements.md

@@ -2,20 +2,64 @@
 title: Azure Arc resource bridge (preview) network requirements
 description: Learn about network requirements for Azure Arc resource bridge (preview) including URLs that must be allowlisted.
 ms.topic: conceptual
-ms.date: 12/06/2022
+ms.date: 01/30/2023
 ---
 
 # Azure Arc resource bridge (preview) network requirements
 
 This article describes the networking requirements for deploying Azure Arc resource bridge (preview) in your enterprise.
 
+## Configuration requirements
+
+### Static Configuration
+
+Static configuration is recommended for Arc resource bridge because the resource bridge needs three static IPs in the same subnet for the control plane, appliance VM, and reserved appliance VM (for upgrade). The control plane corresponds to the `controlplanenedpoint` parameter, the appliance VM IP to `k8snodeippoolstart`, and reserved appliance VM to `k8snodeippoolend` in the `createconfig` command that creates the bridge configuration files. If using DHCP, reserve those IP addresses, ensuring they are outside the DHCP range.
+
+### IP Address Prefix
+
+The subnet of the IP addresses for Arc resource bridge must lie in the IP address prefix that is passed in the `ipaddressprefix` parameter of the `createconfig` command. The IP address prefix is the IP prefix that is exposed by the network to which Arc resource bridge is connected. It is entered as the subnet's IP address range for the virtual network and subnet mask (IP Mask) in CIDR notation, for example `192.168.7.1/24`. Consult your system or network administrator to obtain the IP address prefix in CIDR notation. An IP Subnet CIDR calculator may be used to obtain this value.
+
+### Gateway
+
+The gateway address provided in the `createconfig` command must be in the same subnet specified in the IP address prefix.
+
+### DNS Server
+
+DNS Server must have internal and external endpoint resolution. The appliance VM and control plane need to resolve the management machine and vice versa. All three must be able to reach the required URLs for deployment.
+
+## General network requirements
+
 [!INCLUDE [network-requirement-principles](../includes/network-requirement-principles.md)]
 
 [!INCLUDE [network-requirements](includes/network-requirements.md)]
 
 ## Additional network requirements
 
-In addition, resource bridge (preview) requires [Arc-enabled Kubernetes endpoints](../network-requirements-consolidated.md#azure-arc-enabled-kubernetes-endpoints).
+In addition, resource bridge (preview) requires connectivity to the [Arc-enabled Kubernetes endpoints](../network-requirements-consolidated.md?tabs=azure-cloud).
+
+> [!NOTE]
+> The URLs listed here are required for Arc resource bridge only. Other Arc products (such as Arc-enabled VMware vSphere) may have additional required URLs. For details, see [Azure Arc network requirements](../network-requirements-consolidated.md).
+
+## SSL proxy configuration
+
+Azure Arc resource bridge must be configured for proxy so that it can connect to the Azure services. This configuration is handled automatically. However, proxy configuration of the management machine isn't configured by the Azure Arc resource bridge.
+
+There are only two certificates that should be relevant when deploying the Arc resource bridge behind an SSL proxy: the SSL certificate for your SSL proxy (so that the host and guest trust your proxy FQDN and can establish an SSL connection to it), and the SSL certificate of the Microsoft download servers. This certificate must be trusted by your proxy server itself, as the proxy is the one establishing the final connection and needs to trust the endpoint. Non-Windows machines may not trust this second certificate by default, so you may need to ensure that it's trusted.
+
+## Exclusion list for no proxy
+
+The following table contains the list of addresses that must be excluded by using the `-noProxy` parameter in the `createconfig` command.
+
+|      **IP Address**       |    **Reason for exclusion**    |  
+| ----------------------- | ------------------------------------ |
+| localhost, 127.0.0.1  | Localhost traffic  |
+| .svc | Internal Kubernetes service traffic (.svc) where _.svc_ represents a wildcard name. This is similar to saying \*.svc, but none is used in this schema. |
+| 10.0.0.0/8 | private network address space |
+| 172.16.0.0/12 |Private network address space - Kubernetes Service CIDR |
+| 192.168.0.0/16 | Private network address space - Kubernetes Pod CIDR |
+| .contoso.com | You may want to exempt your enterprise namespace (.contoso.com) from being directed through the proxy. To exclude all addresses in a domain, you must add the domain to the `noProxy` list. Use a leading period rather than a wildcard (\*) character. In the sample, the addresses `.contoso.com` excludes addresses `prefix1.contoso.com`, `prefix2.contoso.com`, and so on. |
+
+The default value for `noProxy` is `localhost,127.0.0.1,.svc,10.0.0.0/8,172.16.0.0/12,192.168.0.0/16`. While these default values will work for many networks, you may need to add more subnet ranges and/or names to the exemption list. For example, you may want to exempt your enterprise namespace (.contoso.com) from being directed through the proxy. You can achieve that by specifying the values in the `noProxy` list.
 
 ## Next steps