Add blog post: How to Move to the Gateway API: post ingress-nginx Retirement #16933

dirien · 2026-01-02T15:00:58Z

Summary

This PR adds a new blog post covering the migration from ingress-nginx to Gateway API using kgateway.

Key topics:

The retirement of ingress-nginx in March 2026
Gateway API fundamentals and the role-oriented model (GatewayClass, Gateway, HTTPRoute)
Comparison of Gateway API implementations (NGINX Gateway Fabric, Traefik, Envoy Gateway, kgateway)
Migration strategies from Ingress to Gateway API
Complete Pulumi TypeScript demo deploying kgateway on DigitalOcean Kubernetes

Test plan

Verify blog post renders correctly on staging
Check all external links are valid
Verify code blocks display properly with syntax highlighting
Confirm the get-started shortcode renders correctly

This blog post covers: - The retirement of ingress-nginx in March 2026 - Gateway API fundamentals and the role-oriented model - Comparison of Gateway API implementations (NGINX Gateway Fabric, Traefik, Envoy Gateway, kgateway) - Migration strategies from Ingress to Gateway API - Complete Pulumi TypeScript demo deploying kgateway on DigitalOcean Kubernetes

claude · 2026-01-02T15:02:39Z

Documentation Review

I've reviewed this blog post and found it to be well-written and technically sound overall. Here are a few suggestions for improvement:

Issues Found

1. Blockquote misuse (line 145)

The > [!INFO] syntax is not standard Markdown blockquote usage. According to STYLE-GUIDE.md, blockquotes should only be used for direct quotations. For informational callouts, use the notes shortcode instead.

Current:

> [!INFO]
> The demo uses [nip.io](https://nip.io), a wildcard DNS service...

Suggested:

{{% notes type="info" %}}
The demo uses [nip.io](https://nip.io), a wildcard DNS service that resolves `*.IP.nip.io` hostnames to the specified IP address. This eliminates the need to configure separate DNS records during testing. Once deployed, the `httpbinUrl` output provides a ready-to-use endpoint for validating the gateway configuration.
{{% /notes %}}

2. Inconsistent heading capitalization (line 447)

The heading "The short-term option: a quick migration to Traefik" uses lowercase after the colon, which is inconsistent. According to STYLE-GUIDE.md, H2+ headings should use sentence case. This should either be split into two sentences or capitalize "A quick migration".

Suggested:

## The short-term option: A quick migration to Traefik

Or better:

## Short-term option: Quick migration to Traefik

3. Navigation instructions (line 31)

The phrase "go to" appears in the text "navigate to". According to STYLE-GUIDE.md, prefer "navigate to" over "go to".

Actually, upon re-reading line 31: "navigate to the source code location" - this is already correct. No issue here.

4. Consider accessibility for meta.png

While the meta image is provided, ensure it includes appropriate text contrast and doesn't rely solely on color to convey information, per BLOGGING.md guidelines. Please verify:

Text is readable against the background
Image is 1200×628 PNG with opaque background
Pulumi branding is present

Style and Content Observations

Strengths:

Clear structure with logical flow from problem to solution
Technical accuracy in explaining Gateway API concepts
Practical Pulumi code example that follows TypeScript best practices
Good use of comparison table for implementations
Appropriate resource links at the end

Minor suggestions:

Line 20: The opening effectively sets context and urgency around the ingress-nginx retirement
Line 145: Consider testing the nip.io approach to ensure it works as described in the demo
Line 447-455: The Traefik section provides a good fallback option for time-constrained teams

Technical Verification

The blog post makes several factual claims that should be verified:

✅ ingress-nginx retirement in March 2026 (confirmed by linked Kubernetes blog)
✅ Gateway API role-oriented model (GatewayClass, Gateway, HTTPRoute)
✅ kgateway was formerly Gloo Gateway and was donated to CNCF in 2025
✅ The Pulumi TypeScript code follows proper dependency ordering

SEO and Front Matter

Front matter looks good:

✅ Title is under 60 characters
✅ Meta description is present and descriptive
✅ Appropriate tags (kubernetes, gateway-api, kgateway, ingress, networking)
✅ Author and date specified
✅ Schema type set to auto

External Links Check

Key links referenced in the post:

https://kubernetes.io/blog/2025/11/11/ingress-nginx-retirement/ (mentioned but should verify it exists)
https://gateway-api.sigs.k8s.io/guides/getting-started/migrating-from-ingress/
https://github.com/kubernetes-sigs/ingress2gateway
https://kgateway.dev/
https://nip.io
Traefik migration guide

Please verify these links are functional before publishing.

Summary: This is a high-quality technical blog post that effectively addresses the ingress-nginx retirement and provides practical migration guidance. The two issues noted above should be fixed before merging. The content is accurate, well-structured, and provides real value to readers facing this migration.

If you'd like me to make these fixes directly or need any additional review, please mention @claude in the PR.

pulumi-bot · 2026-01-02T15:08:13Z

Your site preview for commit 079b038 is ready! 🎉

http://www-testing-pulumi-docs-origin-pr-16933-079b038f.s3-website.us-west-2.amazonaws.com.

Update the short-term option section to reference Chainguard's EmeritOSS fork of ingress-nginx instead of Traefik migration. This provides a more relevant alternative for teams needing continued ingress-nginx support while planning their Gateway API migration.

pulumi-bot · 2026-01-02T15:57:00Z

Your site preview for commit 4e39187 is ready! 🎉

http://www-testing-pulumi-docs-origin-pr-16933-4e39187c.s3-website.us-west-2.amazonaws.com.

dirien · 2026-01-02T17:33:23Z

Related: I've opened an issue to add Kubernetes Gateway API CRDs as first-class citizen resources in the Pulumi Kubernetes provider: pulumi/pulumi-kubernetes#4057

Currently, using Gateway API resources requires the CustomResource approach which lacks type safety and IDE support. Having native support would significantly improve the developer experience showcased in this blog post.

Depending on the timeline, we may want to wait for that implementation before publishing, or publish now and update later once first-class support is available.

asafashirov · 2026-01-05T15:22:11Z

content/blog/ingress-nginx-to-gateway-api-kgateway/index.md

@@ -0,0 +1,488 @@
+---
+title: "From ingress-nginx to Gateway API: A Modern Approach with kgateway"


I would add "Retiring"/"Retirement" to the title considering people tend to search for that sort of stuff in context; e.g. https://pulumi.slack.com/archives/G01HKD9T4M6/p1767624534954149?thread_ts=1766452939.388149&cid=G01HKD9T4M6

Similarly, an H2 with something along the lines of "What should replace ingress-nginx in 2026?", perhaps after the intro if you don't immediately mention Gateway API. I.e. Answer-first stuff works well.

Some LLM-assisted ideas for a title:

Migrating to Gateway API: ingress-nginx Retirement 2026

How to Move to the Gateway API: post ingress-nginx Retirement

Choosing a Gateway API Replacement after ingress-nginx Retirement

content/blog/ingress-nginx-to-gateway-api-kgateway/index.md

adamgordonbell

Great timely issue to cover! LGTM

adamgordonbell · 2026-01-05T18:14:51Z

content/blog/ingress-nginx-to-gateway-api-kgateway/index.md

+
+The shift to the Gateway API is not just about keeping the lights on; it is about building a networking foundation ready for the next decade of infrastructure challenges.
+
+{{< get-started >}}


I wonder if instead of the getting started thing, since we already known the reader is interested in k8s, we guild them towards some K8S Pulumi stuff?

@adamgordonbell make a suggestions please, would help me a lot

Co-authored-by: asaf <[email protected]>

- Replace passive voice with active constructions - Trim wordiness throughout - Remove "not just about" and "more than X—it's Y" patterns - Replace em dashes with parentheses

pulumi-bot · 2026-01-06T22:43:29Z

Your site preview for commit 8cbc94c is ready! 🎉

http://www-testing-pulumi-docs-origin-pr-16933-8cbc94c2.s3-website.us-west-2.amazonaws.com.

dirien temporarily deployed to testing January 2, 2026 15:01 — with GitHub Actions Inactive

dirien requested review from adamgordonbell and asafashirov January 2, 2026 15:11

dirien temporarily deployed to testing January 2, 2026 15:50 — with GitHub Actions Inactive

asafashirov reviewed Jan 5, 2026

View reviewed changes

adamgordonbell approved these changes Jan 5, 2026

View reviewed changes

Update content/blog/ingress-nginx-to-gateway-api-kgateway/index.md

5bc087b

Co-authored-by: asaf <[email protected]>

dirien temporarily deployed to testing January 6, 2026 21:57 — with GitHub Actions Inactive

dirien temporarily deployed to testing January 6, 2026 22:12 — with GitHub Actions Inactive

Improve prose: active voice, conciseness, remove clichés

88d324f

- Replace passive voice with active constructions - Trim wordiness throughout - Remove "not just about" and "more than X—it's Y" patterns - Replace em dashes with parentheses

dirien force-pushed the dirien/ingress-nginx-gateway-api branch from 48a715d to 88d324f Compare January 6, 2026 22:15

dirien temporarily deployed to testing January 6, 2026 22:15 — with GitHub Actions Inactive

pulumi deleted a comment from pulumi-bot Jan 6, 2026

Update blog post title for ingress-nginx Gateway API migration

ebaaa2f

dirien temporarily deployed to testing January 6, 2026 22:20 — with GitHub Actions Inactive

dirien changed the title ~~Add blog post: From ingress-nginx to Gateway API with kgateway~~ Add blog post: How to Move to the Gateway API: post ingress-nginx Retirement Jan 6, 2026

Rewrite intro to improve annotation explanation flow

8cbc94c

dirien temporarily deployed to testing January 6, 2026 22:36 — with GitHub Actions Inactive

pulumi deleted a comment from pulumi-bot Jan 6, 2026

dirien merged commit 967ba19 into master Jan 6, 2026
8 checks passed

dirien deleted the dirien/ingress-nginx-gateway-api branch January 6, 2026 23:43

dirien temporarily deployed to testing January 6, 2026 23:43 — with GitHub Actions Inactive

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Add blog post: How to Move to the Gateway API: post ingress-nginx Retirement #16933

Add blog post: How to Move to the Gateway API: post ingress-nginx Retirement #16933

dirien commented Jan 2, 2026

Uh oh!

claude bot commented Jan 2, 2026

Uh oh!

pulumi-bot commented Jan 2, 2026

Uh oh!

pulumi-bot commented Jan 2, 2026

Uh oh!

dirien commented Jan 2, 2026

Uh oh!

asafashirov Jan 5, 2026

Uh oh!

asafashirov Jan 5, 2026

Uh oh!

asafashirov Jan 6, 2026

Uh oh!

Uh oh!

adamgordonbell left a comment

Uh oh!

adamgordonbell Jan 5, 2026

Uh oh!

dirien Jan 6, 2026

Uh oh!

pulumi-bot commented Jan 6, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

		@@ -0,0 +1,488 @@
		---
		title: "From ingress-nginx to Gateway API: A Modern Approach with kgateway"


		The shift to the Gateway API is not just about keeping the lights on; it is about building a networking foundation ready for the next decade of infrastructure challenges.

		{{< get-started >}}

Add blog post: How to Move to the Gateway API: post ingress-nginx Retirement #16933

Add blog post: How to Move to the Gateway API: post ingress-nginx Retirement #16933

Conversation

dirien commented Jan 2, 2026

Summary

Test plan

Uh oh!

claude bot commented Jan 2, 2026

Documentation Review

Issues Found

1. Blockquote misuse (line 145)

2. Inconsistent heading capitalization (line 447)

3. Navigation instructions (line 31)

4. Consider accessibility for meta.png

Style and Content Observations

Technical Verification

SEO and Front Matter

External Links Check

Uh oh!

pulumi-bot commented Jan 2, 2026

Uh oh!

pulumi-bot commented Jan 2, 2026

Uh oh!

dirien commented Jan 2, 2026

Uh oh!

asafashirov Jan 5, 2026

Choose a reason for hiding this comment

Uh oh!

asafashirov Jan 5, 2026

Choose a reason for hiding this comment

Uh oh!

asafashirov Jan 6, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

adamgordonbell left a comment

Choose a reason for hiding this comment

Uh oh!

adamgordonbell Jan 5, 2026

Choose a reason for hiding this comment

Uh oh!

dirien Jan 6, 2026

Choose a reason for hiding this comment

Uh oh!

pulumi-bot commented Jan 6, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants