Skip to content

Commit 03117e3

Browse files
committed
Add separator between tabbed content
1 parent 03d70f8 commit 03117e3

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

articles/aks/limit-egress-traffic.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -227,6 +227,8 @@ You'll define the outbound type to use the UDR that already exists on the subnet
227227
>
228228
> You can add the AKS feature for [**API server authorized IP ranges**](api-server-authorized-ip-ranges.md) to limit API server access to only the firewall's public endpoint. The authorized IP ranges feature is denoted in the diagram as optional. When enabling the authorized IP range feature to limit API server access, your developer tools must use a jumpbox from the firewall's virtual network, or you must add all developer endpoints to the authorized IP range.
229229
230+
---
231+
230232
### [Create an AKS cluster with system-assigned identities](#tab/aks-with-system-assigned-identities)
231233

232234
> [!NOTE]
@@ -316,6 +318,8 @@ az aks create -g $RG -n $AKSNAME -l $LOC \
316318
--assign-kubelet-identity <kubelet-identity-resource-id>
317319
```
318320

321+
---
322+
319323
## Enable developer access to the API server
320324

321325
If you used authorized IP ranges for your cluster in the previous step, you need to add your developer tooling IP addresses to the AKS cluster list of approved IP ranges so you access the API server from there. You can also configure a jumpbox with the needed tooling inside a separate subnet in the firewall's virtual network.

0 commit comments

Comments
 (0)