Skip to content

Commit 00bb956

Browse files
Merge pull request #222098 from omkark95/main
Added US Gov endpoints for Arc-enabled K8s
2 parents 7f33977 + 6c08be7 commit 00bb956

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/azure-arc/kubernetes/quickstart-connect-cluster.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -133,7 +133,7 @@ For a conceptual look at connecting clusters to Azure Arc, see [Azure Arc-enable
133133
134134
> [!IMPORTANT]
135135
> Azure Arc agents require the following outbound URLs on `https://:443` to function.
136-
> For `*.servicebus.windows.net`, websockets need to be enabled for outbound access on firewall and proxy.
136+
> For `*.servicebus.windows.net` (for Azure Cloud) & `*.servicebus.usgovcloudapi.net` (for Azure US Government), websockets need to be enabled for outbound access on firewall and proxy.
137137
138138
| Endpoint (DNS) | Description |
139139
| ----------------- | ------------- |
@@ -144,12 +144,12 @@ For a conceptual look at connecting clusters to Azure Arc, see [Azure Arc-enable
144144
| `https://gbl.his.arc.azure.com` (for Azure Cloud), `https://gbl.his.arc.azure.us` (for Azure US Government) | Required to get the regional endpoint for pulling system-assigned Managed Identity certificates. |
145145
| `https://*.his.arc.azure.com` (for Azure Cloud), `https://usgv.his.arc.azure.us` (for Azure US Government) | Required to pull system-assigned Managed Identity certificates. |
146146
|`https://k8connecthelm.azureedge.net` | `az connectedk8s connect` uses Helm 3 to deploy Azure Arc agents on the Kubernetes cluster. This endpoint is needed for Helm client download to facilitate deployment of the agent helm chart. |
147-
|`guestnotificationservice.azure.com`, `*.guestnotificationservice.azure.com`, `sts.windows.net`, `https://k8sconnectcsp.azureedge.net` | For [Cluster Connect](cluster-connect.md) and for [Custom Location](custom-locations.md) based scenarios. |
148-
|`*.servicebus.windows.net` | For [Cluster Connect](cluster-connect.md) and for [Custom Location](custom-locations.md) based scenarios. |
147+
|`guestnotificationservice.azure.com`, `*.guestnotificationservice.azure.com`, `sts.windows.net`, `https://k8sconnectcsp.azureedge.net`(for Azure Cloud), `guestnotificationservice.azure.us`, `*.guestnotificationservice.azure.us`, `sts.windows.net`, `https://k8sconnectcsp.azureedge.us` (for Azure US Government) | For [Cluster Connect](cluster-connect.md) and for [Custom Location](custom-locations.md) based scenarios. |
148+
|`*.servicebus.windows.net`(for Azure Cloud), `*.servicebus.usgovcloudapi.net` (for Azure US Government) | For [Cluster Connect](cluster-connect.md) and for [Custom Location](custom-locations.md) based scenarios. |
149149
|`https://graph.microsoft.com/` | Required when [Azure RBAC](azure-rbac.md) is configured |
150150
151151
> [!NOTE]
152-
> To translate the `*.servicebus.windows.net` wildcard into specific endpoints, use the command `\GET https://guestnotificationservice.azure.com/urls/allowlist?api-version=2020-01-01&location=<location>`. Within this command, the region must be specified for the `<location>` placeholder.
152+
> For Azure Cloud to translate the `*.servicebus.windows.net` wildcard into specific endpoints, use the command `\GET https://guestnotificationservice.azure.com/urls/allowlist?api-version=2020-01-01&location=<location>`. For Azure US Government to translate the `*.servicebus.usgovcloudapi.net` wildcard into specific endpoints, use the command `\GET https://guestnotificationservice.azure.us/urls/allowlist?api-version=2020-01-01&location=<location>`. Within these commands, the region must be specified for the `<location>` placeholder.
153153
154154
> [!IMPORTANT]
155155
> To view and manage connected clusters in the Azure portal, be sure that your network allows traffic to `*.arc.azure.net`.
@@ -446,4 +446,4 @@ Remove-AzConnectedKubernetes -ClusterName AzureArcTest1 -ResourceGroupName Azure
446446

447447
Advance to the next article to learn how to deploy configurations to your connected Kubernetes cluster using GitOps.
448448
> [!div class="nextstepaction"]
449-
> [Deploy configurations using GitOps with Flux v2](tutorial-use-gitops-flux2.md)
449+
> [Deploy configurations using GitOps with Flux v2](tutorial-use-gitops-flux2.md)

0 commit comments

Comments
 (0)