You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-arc/resource-bridge/includes/network-requirements.md
+14-4Lines changed: 14 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,9 @@
1
1
---
2
2
ms.topic: include
3
-
ms.date: 03/19/2024
3
+
ms.date: 05/22/2024
4
4
---
5
5
6
-
### Outbound connectivity
6
+
### Outbound connectivity requirements
7
7
8
8
The firewall and proxy URLs below must be allowlisted in order to enable communication from the management machine, Appliance VM, and Control Plane IP to the required Arc resource bridge URLs.
9
9
@@ -42,6 +42,16 @@ The firewall and proxy URLs below must be allowlisted in order to enable communi
42
42
|Azure Arc Agent| 443 |`*.dp.kubernetesconfiguration.azure.com`| Management machine needs outbound connection. | Dataplane used for Arc agent.|
|SSH| 22 |`Arc resource bridge appliance VM IPs`| Management machine needs outbound connection. | Used for troubleshooting the appliance VM.|
46
-
|Kubernetes API server| 6443 |`Arc resource bridge appliance VM IPs`| Management machine needs outbound connection. | Management of appliance VM.|
47
45
46
+
## Inbound connectivity requirements
47
+
48
+
The following ports must be allowlisted in your firewall/proxy to enable communication between the management machine, Appliance VM IPs, and Control Plane IPs. Ensure these ports are open to facilitate the deployment and maintenance of the Azure Arc Resource Bridge.
- communication over port 443 to the private cloud management console (ex: VMware vCenter machine)
70
70
71
-
- Internal and external DNS resolution. The DNS server must resolve internal names, such as the vCenter endpoint for vSphere or cloud agent service endpoint for Azure Stack HCI. The DNS server must also be able to resolve external addresses that are [required URLs](network-requirements.md#outbound-connectivity) for deployment.
71
+
- Internal and external DNS resolution. The DNS server must resolve internal names, such as the vCenter endpoint for vSphere or cloud agent service endpoint for Azure Stack HCI. The DNS server must also be able to resolve external addresses that are [required URLs](network-requirements.md#outbound-connectivity-requirements) for deployment.
72
72
- Internet access
73
73
74
74
## Appliance VM IP address requirements
@@ -81,7 +81,7 @@ Appliance VM IP address requirements:
81
81
82
82
- Communcation with the private cloud management endpoint via Port 443 (such as VMware vCenter).
83
83
84
-
- Internet connectivity to [required URLs](network-requirements.md#outbound-connectivity) enabled in proxy/firewall.
84
+
- Internet connectivity to [required URLs](network-requirements.md#outbound-connectivity-requirements) enabled in proxy/firewall.
85
85
- Static IP assigned and within the IP address prefix.
86
86
87
87
- Internal and external DNS resolution.
@@ -97,7 +97,7 @@ Reserved appliance VM IP requirements:
97
97
98
98
- Communcation with the private cloud management endpoint via Port 443 (such as VMware vCenter).
99
99
100
-
- Internet connectivity to [required URLs](network-requirements.md#outbound-connectivity) enabled in proxy/firewall.
100
+
- Internet connectivity to [required URLs](network-requirements.md#outbound-connectivity-requirements) enabled in proxy/firewall.
101
101
102
102
- Static IP assigned and within the IP address prefix.
103
103
@@ -107,7 +107,7 @@ Reserved appliance VM IP requirements:
107
107
108
108
## Control plane IP requirements
109
109
110
-
The appliance VM hosts a management Kubernetes cluster with a control plane that requires a single, static IP address. This IP is assigned from the `controlplaneendpoint` parameter in the `createconfig` command or equivalent configuration files creation command.
110
+
The appliance VM hosts a management Kubernetes cluster with a control plane that requires a single, static IP address. This IP is assigned from the `controlplaneendpoint` parameter in the `createconfig` command or equivalent configuration files creation command.
0 commit comments