Navigating the ingress-NGINX retirement

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".

1. The Post-March 2026 landscape

⚠ The CatalystAcknowledge the March 2026 retirement of the Kubernetes SIG Network ingress-nginx controller. Staying on this controller introduces severe operational risks, including unpatched CVEs and a complete halt of feature updates and community support.

A common misconception is that Kubernetes Ingress itself is being retired. In reality, the Ingress API remains supported and widely used. What is reaching end of life is the community-maintained ingress-nginx controller, which means organizations must decide whether to adopt another controller or use the opportunity to modernize their networking architecture. 

The Dilemma

Infrastructure teams face a crucial architectural decision to maintain cluster security and routing capabilities.Organizations generally have two primary migration paths.: performing a “lift-and-shift” migration to another Ingress controller like Contour, or using this event as a forcing function to modernize with the Gateway API.

2. Path A: The “lift and shift”

Staying on Ingress API with Contour

How it Works: Operators can keep their existing Ingress YAML resources and simply swap the underlying ingress class to an Envoy-based controller like Contour. This minimizes immediate disruption to standard routing definitions.

Handling Annotations: While the base Ingress resource stays the same, all of the proprietary nginx.ingress.kubernetes.io/* annotations will fail. These must be manually translated to Contour’s equivalent annotations or rebuilt using its CRDs.

Path A Architecture

3. Path B: The architectural …

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen: Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://www.cncf.io/blog/2026/07/09/navigating-the-ingress-nginx-retirement/
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.