How We Migrated a Production Cluster from Ingress NGINX to Gateway API
ID: 80167738-cbbd-58a5-9013-746b85385120
STIX ID: report--80167738-cbbd-58a5-9013-746b85385120
Feed Name: Security Boulevard
**Executive summary:** This post documents a real-world migration of a production Kubernetes cluster from ingress-nginx to the Gateway API using kgateway, explaining why Gateway API was chosen, how to translate Ingress objects (including use of an ingress2gateway fork), safe cutover strategies for NLB and ALB, notable behavioral differences (WebSocket upgrades, intermittent 503s after deploys, and rate-limiting semantics), and operational lessons (deployment ordering, controller replica sizing, and cert-manager considerations).
Your team is not currently subscribed to this feed. You must subscribe to it in order to see this post.