{AKS} az aks: add --outbound-type-sku for managed NAT Gateway V2 GA - #34017
Draft
Christine DOSSA (christine33-creator) wants to merge 2 commits into
Draft
{AKS} az aks: add --outbound-type-sku for managed NAT Gateway V2 GA#34017Christine DOSSA (christine33-creator) wants to merge 2 commits into
Christine DOSSA (christine33-creator) wants to merge 2 commits into
Conversation
Ports the aks-preview NAT Gateway V2 GA surface (extension PR Azure#10264) into core az aks now that the 2026-06-01 SDK (azure-mgmt-containerservice 41.6.0) is vendored. az aks create / az aks update: add --outbound-type-sku (Standard|StandardV2) to select the managed NAT gateway SKU with --outbound-type managedNATGateway (the GA shape of NAT Gateway V2), plus the StandardV2-only --nat-gateway-managed-outbound-ipv6-count, --nat-gateway-outbound-ips and --nat-gateway-outbound-ip-prefixes. Create requires an explicit --outbound-type managedNATGateway; update verifies the cluster's existing outbound type before applying. Adds builder + validator unit tests.
…io test (record --live)
|
Azure Pipelines: There may be pipelines that require an authorized user to comment /azp run to run. |
microsoft-github-policy-service
Bot
requested review from
FumingZhang,
elvazhu521,
Julie Zhu (yanzhudd) and
Yong Zhang (yonzhan)
September 2, 2026 02:38
microsoft-github-policy-service
Bot
added
the
customer-reported
Contributor
|
Thank you for your contribution Christine DOSSA (@christine33-creator)! We will review the pull request and get back to you soon. |
microsoft-github-policy-service
Bot
added
Auto-Assign
Member
|
/azp run |
|
Azure Pipelines: Successfully started running 3 pipeline(s). |
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
3 participants
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.
🤖 PR Validation — ❌ Action needed
❌AzureCLI-FullTest
Summary
Ports the NAT Gateway V2 GA surface to core
az aks, now that the2026-06-01API SDK (azure-mgmt-containerservice41.6.0) is vendored (#34011). Mirrors the aks-preview extension PR Azure/azure-cli-extensions#10264 and follows the AKS NAT Gateway V2 GA API proposal.What
az aks create/az aks update:--outbound-type-sku {Standard,StandardV2}— select the managed NAT gateway SKU with--outbound-type managedNATGateway(the GA shape of NAT Gateway V2).--nat-gateway-managed-outbound-ipv6-count— dual-stack IPv6 outbound IPs (StandardV2 only).--nat-gateway-outbound-ips/--nat-gateway-outbound-ip-prefixes— bring-your-own public IPs / prefixes (StandardV2 only).Validation: create requires an explicit
--outbound-type managedNATGateway; update verifies the cluster's existing outbound type before applying the SKU / V2 params.Testing
test_natgateway.pyandtest_validators.py.azdev style acs: pylint + flake8 pass.test_aks_create_and_update_with_managed_nat_gateway_v2is scaffolded but not yet recorded — needs anazdev test ... --liverun against a StandardV2-capable region. This is why the PR is a draft.History Notes
Added an entry under AKS in
src/azure-cli/HISTORY.rst.