Repository navigation
Conversation
… API Signed-off-by: Johan Kuylenstierna <johan@agency42.se>
This branch has not been deployed
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.
Fixes Issue
N/A (new blog post)
Changes proposed
content/blog/migrate-ingress-nginx-to-gateway-api-hands-on.md(filename = slug,datePublishedset,draft: false)johan-kuylenstiernaincontent/authors.json(avatar: null, so the default Kubesimplify logo is used)public/img/blog/migrate-ingress-nginx-to-gateway-api-hands-on/canary-scope.pngnpm run blog:redirects(public/_redirects,public/_worker.js,vercel.json)npm run buildpasses locally and the post renders at/blog/migrate-ingress-nginx-to-gateway-api-hands-onScreenshots
The gh CLI can't attach images, so please use the PR preview deploy for a visual check. Locally, the built page shows the title, byline and the canary-scope image.
Note to reviewers
Hi! As promised on #276, this is a fresh article written exclusively for Kubesimplify. It is not a cross-post and hasn't been published anywhere else.
It walks through migrating from ingress-nginx to Gateway API with the official
ingress2gatewaytool. Every step was run on a real kind lab, and the outputs are pasted from the logs. Along the way it covers a canary-scope finding: on ingress-nginx, the canary weight on one Ingress also split traffic for a different hostname that used the same backend Service (23 of 100 requests went to the canary). After conversion, Envoy Gateway kept the weights scoped to that single route, so per-host traffic changes on cutover day.Commands verified on a kind lab cluster on 13 Oct 2026. Drafted with AI assistance, then reviewed and approved by me.
Author: Johan Kuylenstierna, https://www.linkedin.com/in/johankuylenstierna/