Update CHANGELOG with AKS NAT Gateway support#5663
Open
rahulrai-in wants to merge 1 commit intomasterfrom
Open
Update CHANGELOG with AKS NAT Gateway support#5663rahulrai-in wants to merge 1 commit intomasterfrom
rahulrai-in wants to merge 1 commit intomasterfrom
Conversation
Added support for configuring Standard V2 Azure NAT Gateway as a user-assigned NAT gateway for outbound traffic.
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the repository changelog to document new AKS support for using a Standard V2 Azure NAT Gateway as a user-assigned NAT gateway for outbound traffic.
Changes:
- Adds a new bullet under Behavioral Changes describing Standard V2 Azure NAT Gateway (user-assigned) support.
- Links to the corresponding Microsoft Learn documentation for configuration details.
| * On clusters where ACNS performance is used to enable [eBPF host routing](https://learn.microsoft.com/azure/aks/how-to-enable-ebpf-host-routing), nodes will be labeled with `kubernetes.azure.com/ebpf-host-routing=true`. This is done by a node image upgrade. | ||
| * AKS now supports [configuring Standard V2 Azure NAT Gateway](https://learn.microsoft.com/azure/aks/nat-gateway#create-an-aks-cluster-with-a-user-assigned-nat-gateway) as a user‑assigned NAT gateway for outbound (egress) traffic. | ||
|
|
||
|
|
| - A ValidatingAdmissionPolicy (VAP) restricts creation or updates of ClusterRole and Role objects granting `nodes/proxy`, except for approved system users and groups. | ||
| - An authorization policy denies `nodes/proxy` by default. Approved system users, groups, and kube-system service accounts are exempt. | ||
| * On clusters where ACNS performance is used to enable [eBPF host routing](https://learn.microsoft.com/azure/aks/how-to-enable-ebpf-host-routing), nodes will be labeled with `kubernetes.azure.com/ebpf-host-routing=true`. This is done by a node image upgrade. | ||
| * AKS now supports [configuring Standard V2 Azure NAT Gateway](https://learn.microsoft.com/azure/aks/nat-gateway#create-an-aks-cluster-with-a-user-assigned-nat-gateway) as a user‑assigned NAT gateway for outbound (egress) traffic. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Added support for configuring Standard V2 Azure NAT Gateway as a user-assigned NAT gateway for outbound traffic.