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/aks/limit-egress-traffic.md
+6-2Lines changed: 6 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -180,7 +180,7 @@ This section covers three network rules and an application rule you can use to c
180
180
* The first network rule allows access to port 9000 via TCP.
181
181
* The second network rule allows access to port 1194 and 123 via UDP. If you're deploying to Microsoft Azure operated by 21Vianet, see the [Azure operated by 21Vianet required network rules](./outbound-rules-control-egress.md#microsoft-azure-operated-by-21vianet-required-network-rules). Both these rules will only allow traffic destined to the Azure Region CIDR in this article, which is East US.
182
182
* The third network rule opens port 123 to `ntp.ubuntu.com` FQDN via UDP. Adding an FQDN as a network rule is one of the specific features of Azure Firewall, so you'll need to adapt it when using your own options.
183
-
* The application rule covers all needed FQDNs accessible through TCP port 443 and port 80.
183
+
* The fourth and fifth network rules allows access to pull containers from GitHub Container Registry (ghcr.io) and Docker Hub (docker.io).
184
184
185
185
1. Create the network rules using the [`az network firewall network-rule create`][az-network-firewall-network-rule-create] command.
186
186
@@ -190,6 +190,10 @@ This section covers three network rules and an application rule you can use to c
0 commit comments