[Draft] nat gw2 blog#5738
Conversation
rahulrai-in
requested review from
a team,
ConnieZhuang,
Copilot and
shashankbarsin
There was a problem hiding this comment.
Pull request overview
Adds a new Docusaurus blog post to the AKS engineering blog announcing managed NAT gateway v2 support in AKS, including guidance on enabling, upgrading, and validating egress.
Changes:
- Introduces a new blog post with feature overview, architecture diagrams (Mermaid), and migration guidance.
- Provides Azure CLI examples to create/update clusters using
managedNATGatewayV2. - Adds a basic egress validation workflow and operational considerations.
| If you run workloads with high outbound concurrency, strict outbound IP requirements, or periodic traffic spikes, managed NAT gateway v2 helps you keep egress stable without managing extra network infrastructure by hand. | ||
|
|
||
| <!-- truncate --> | ||
|
|
There was a problem hiding this comment.
The post includes the truncate marker but doesn’t include a hero image afterward. Blog posts in this repo are expected to include a same-directory hero image (for example ./hero-image.png) with descriptive alt text for accessibility and consistent rendering on listing pages.
|  |
| --name "$CLUSTER_NAME" | ||
|
|
||
| kubectl run egress-check \ | ||
| --image=mcr.microsoft.com/cbl-mariner/base/core:2.0 \ |
There was a problem hiding this comment.
The egress validation snippet assumes curl is present inside the container, but the chosen image (mcr.microsoft.com/cbl-mariner/base/core:2.0) isn’t commonly used as a curl test image in this repo. To avoid readers hitting curl: not found, use an image that explicitly includes curl (or install curl as part of the command).
| --image=mcr.microsoft.com/cbl-mariner/base/core:2.0 \ | |
| --image=curlimages/curl:8.12.1 \ |
| date: "2026-04-26" | ||
| description: "AKS now supports managed StandardV2 NAT Gateway for scalable, resilient, and observable egress. Learn how to enable it, migrate safely, and validate outbound traffic." | ||
| authors: | ||
| - <TO_DO> add authors |
There was a problem hiding this comment.
The front matter still contains a placeholder author entry (<TO_DO> add authors). Replace this with one or more valid author keys from website/blog/authors.yml so the blog metadata resolves correctly (and avoids inline author warnings).
| - <TO_DO> add authors | |
| - paul-yu |
| --- | ||
| title: "Introducing Managed StandardV2 NAT Gateway for AKS" | ||
| date: "2026-04-26" | ||
| description: "AKS now supports managed StandardV2 NAT Gateway for scalable, resilient, and observable egress. Learn how to enable it, migrate safely, and validate outbound traffic." |
There was a problem hiding this comment.
The description front matter appears to exceed the 150–160 character SEO guideline used elsewhere in the blog. Consider tightening it to stay within that range so listings/snippets don’t get truncated awkwardly.
| description: "AKS now supports managed StandardV2 NAT Gateway for scalable, resilient, and observable egress. Learn how to enable it, migrate safely, and validate outbound traffic." | |
| description: "AKS now supports managed StandardV2 NAT Gateway for scalable, resilient egress. Learn how to enable it, migrate safely, and validate traffic." |
| If you run workloads with high outbound concurrency, strict outbound IP requirements, or periodic traffic spikes, managed NAT gateway v2 helps you keep egress stable without managing extra network infrastructure by hand. | ||
|
|
||
| <!-- truncate --> | ||
|
|
There was a problem hiding this comment.
Most AKS blog posts include a hero image immediately after <!-- truncate -->. Consider adding a hero image (with descriptive alt text) here to match the blog’s standard layout and improve accessibility/visual scanning on the post page.
|  |
New blog post introducing managed NAT Gateway v2 support in AKS.