Skip to content

Commit 12b5b11

Browse files
authored
Merge pull request #18420 from sethmanheim/arcgtwy
Add new section on Arc Gateway
2 parents 10a4c23 + 4295cfc commit 12b5b11

File tree

5 files changed

+54
-7
lines changed

5 files changed

+54
-7
lines changed

.openpublishing.redirection.aks.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1489,6 +1489,11 @@
14891489
"source_path": "AKS-Arc/tutorial-kubernetes-upgrade-cluster.md",
14901490
"redirect_url": "/azure/aks/aksarc/overview",
14911491
"redirect_document_id": false
1492+
},
1493+
{
1494+
"source_path": "AKS-Arc/aks-hci-network-system-requirements.md",
1495+
"redirect_url": "/azure/aks/aksarc/network-system-requirements",
1496+
"redirect_document_id": false
14921497
}
14931498
]
14941499
}

AKS-Arc/TOC.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@
2525
- name: Networking
2626
items:
2727
- name: Networking concepts and requirements
28-
href: aks-hci-network-system-requirements.md
28+
href: network-system-requirements.md
2929
- name: IP address planning
3030
href: aks-hci-ip-address-planning.md
3131
- name: Load balancer

AKS-Arc/arc-gateway-aks-arc.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.reviewer: srikantsarwa
99
ms.lastreviewed: 07/15/2025
1010
---
1111

12-
# Simplify network configuration requirements with AKS Arc Gateway (preview)
12+
# Simplify network configuration requirements with Azure Arc gateway (preview)
1313

1414
If you use enterprise proxies to manage outbound traffic, Azure Arc gateway can help simplify the process of enabling connectivity.
1515

AKS-Arc/aks-hci-network-system-requirements.md renamed to AKS-Arc/network-system-requirements.md

Lines changed: 18 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,11 +2,11 @@
22
title: AKS enabled by Azure Arc network requirements
33
description: Learn about AKS network prerequisites.
44
ms.topic: overview
5-
ms.date: 07/02/2025
5+
ms.date: 07/17/2025
66
author: sethmanheim
77
ms.author: sethm
88
ms.reviewer: srikantsarwa
9-
ms.lastreviewed: 07/10/2025
9+
ms.lastreviewed: 07/17/2025
1010
---
1111

1212
# AKS enabled by Azure Arc network requirements
@@ -86,6 +86,22 @@ When you deploy Azure Local, you allocate a contiguous block of at least [six st
8686
| 55000 | IP addresses in management network | Logical network used for AKS Arc VMs | Cloud Agent gRPC server | If you use separate VLANs, the AKS Arc VMs need to access the IP addresses in management network used for cloud agent IP and cluster IP on this port and vice-versa. |
8787
| 65000 | IP addresses in management network | Logical network used for AKS Arc VMs | Cloud Agent gRPC authentication | If you use separate VLANs, the AKS Arc VMs need to access the IP addresses in management network used for cloud agent IP and cluster IP on this port and vice-versa. |
8888

89+
## Use Azure Arc gateway (preview) with Azure Local
90+
91+
If you use [Arc gateway](/azure/azure-local/deploy/deployment-azure-arc-gateway-overview) to deploy your Azure Local cluster infrastructure, make sure that connectivity between the AKS subnet and the cluster IP is allowed on port **40343**, as follows:
92+
93+
| Destination port | Destination | Source | Description | Bi-directional cross-VLAN networking notes |
94+
|------------------|---------------------------------|---------------------------------|-----------------------------------------------------------------------------|--------------------------------------------|
95+
| **40343** | Cluster IP address | Logical network used for AKS Arc VMs | Required only when the Azure Local cluster is configured with Arc Gateway for outbound connectivity. | If you use separate VLANs or subnets, ensure that the AKS Arc VMs can reach the Azure Local cluster IP address on port **40343**, and vice versa. |
96+
97+
### Retrieve the Azure Local cluster IP address
98+
99+
You can run the following PowerShell commands on the cluster to get the IP address of the Azure Local cluster:
100+
101+
```powershell
102+
Get-ClusterResource -Name "Cluster IP Address" | Get-ClusterParameter -Name Address | Select-Object -Property Value
103+
```
104+
89105
## Next steps
90106

91107
[IP address planning and considerations for Kubernetes clusters and applications](aks-hci-ip-address-planning.md)

AKS-Arc/network-validation-errors.md

Lines changed: 29 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,9 +4,9 @@ description: Learn how to troubleshoot general network validation errors in AKS
44
author: sethmanheim
55
ms.author: sethm
66
ms.topic: troubleshooting
7-
ms.date: 05/07/2025
8-
ms.reviewer: pradwivedi
9-
ms.lastreviewed: 05/06/2025
7+
ms.date: 07/17/2025
8+
ms.reviewer: srikantsarwa
9+
ms.lastreviewed: 07/16/2025
1010

1111
---
1212

@@ -60,6 +60,32 @@ This error indicates that the required URLs are not reachable from the AKS clust
6060

6161
To resolve this error, ensure that the logical network IP addresses have outbound internet access. If there's a firewall, ensure that the [AKS required URLs](aks-hci-network-system-requirements.md#firewall-url-exceptions) are accessible from the Arc VM logical network.
6262

63+
## InternetConnectivityError (in Arc Gateway scenario)
64+
65+
Error: Network validation failed during cluster creation.
66+
67+
### Description
68+
69+
Detailed message: `Not able to connect to https://mcr.microsoft.com. Error returned: action failed after 5 attempts: Get "https://mcr.microsoft.com": proxyconnect tcp: dial tcp 192.168.2.100:40343: connect: connection refused`.
70+
71+
### Causes of failure
72+
73+
- The control plane VM can't reach the Azure Local cluster IP on port **40343**, which is required when Arc Gateway is enabled.
74+
- The firewall or network security rules block traffic between the AKS subnet and the cluster IP.
75+
- Proxy settings are incorrect, or the proxy does not allow connections to `mcr.microsoft.com`.
76+
77+
### Mitigation
78+
79+
To resolve this error, you can take the following steps:
80+
81+
- Ensure that the **AKS subnet has connectivity to the Azure Local Cluster IP on port `40343`**.
82+
- Verify that the Arc Gateway service on the Azure Local Cluster is running and listening on port `40343`.
83+
- Check firewall or NSG rules to ensure that traffic between the AKS VMs and the Cluster IP on `40343` is allowed.
84+
- Confirm that proxy settings (if used) are correct and that the proxy can forward requests to `https://mcr.microsoft.com`.
85+
- Test connectivity to `https://mcr.microsoft.com` from the control plane VM, either directly or via the configured proxy.
86+
87+
For more information, see [Use Azure Arc Gateway with Azure Local](aks-hci-network-system-requirements.md#use-azure-arc-gateway-preview-with-azure-local).
88+
6389
## VMNotReachableError
6490

6591
Error: Network validation failed during cluster creation.

0 commit comments

Comments
 (0)