How We Migrated a Production Cluster from Ingress NGINX to Gateway API

Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.

Originaltext der Quelle (nicht übersetzt) – die deutsche Zusammenfassung findest du im Tab „Kurzfassung".

Back in January, we published a post about the retirement of ingress-nginx and laid out what that means for teams still running it. We also gave a CNCF CloudNative Live talk a couple of years ago that walked through the case for Gateway API. This post is what came after: we actually did it with a customer. One migration, on real infrastructure, under real traffic. Here's the plan Stevie Caldwell designed and what I learned executing it. Why Gateway API Gateway API is a Kubernetes-native specification for routing traffic, not an API gateway product, and not a drop-in replacement for any specific ingress controller. Our January post covers the full decision framework. The short version: ingress-nginx has served teams well for years, but its configuration model has real limits. As our CTO Andy Suderman put it in the CNCF talk, when you get into complex routing or rate limiting, configuration gets fragmented across annotations and config maps in ways that are difficult to audit and even harder to hand off to service owners. Gateway API splits responsibility across objects. The cluster admin owns the Gateway. Application teams own the HTTPRoutes. The resources are typed and validated at the API level rather than parsed from string annotations at runtime. When Stevie demoed an annotation typo in the talk (an integer where a string was expected), it failed silently. Gateway API would have rejected that at apply time. That separation also opens up better traffic control. Stevie demoed weighted routing between two backends using only HTTPRoute fields, no service mesh required. …

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen: Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://www.fairwinds.com/blog/migrated-production-cluster-from-ingress-nginx-to-gateway-api
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.