tag: Ingress · 3 items
- Platform/SRE — Plan: ingress-nginx is one of the most widely deployed Kubernetes ingress controllers; its retirement means planning a migration to an alternative (Gateway API, Traefik, Emissary, etc.) before it goes unmaintained. No hard deadline surfaced in signals, so schedule migration evaluation this quarter.
- CI/CD — Skip
- Leader — Plan: Organizations standardized on ingress-nginx will need to choose and adopt a replacement ingress strategy; evaluate Gateway API or alternative controllers and factor the migration into the next infrastructure planning cycle.
- Signals: deprecation mentioned (no explicit date found)
- Platform/SRE — Plan: The Kubernetes Gateway API is the intended successor to the Ingress API, and it’s now GA on AKS — plan a migration evaluation from existing Ingress controllers to the managed Gateway API offering this quarter. No forced deadline exists, but adopting early reduces future migration debt as the Ingress API ages out.
- CI/CD — Skip
- Leader — Learn: Gateway API going GA on AKS signals accelerating industry standardization on the new Kubernetes networking model, worth tracking as context for ingress-tooling decisions if an AKS golden-path review is upcoming.
- Signals: GA announcement
- Platform/SRE — Plan: ingress-nginx is one of the most widely deployed Kubernetes ingress controllers; its retirement means planning a migration to an alternative (e.g., Envoy Gateway, NGINX Gateway Fabric, or another Gateway API-conformant controller). No forced migration date is confirmed yet, so scope the migration project now before community support winds down.
- CI/CD — Skip
- Leader — Plan: If ingress-nginx is part of the org’s Kubernetes golden path or standard stack, its retirement requires evaluating replacement ingress controllers and updating platform standards; begin that toolchain review this planning cycle before the project loses maintainer support.
- Signals: deprecation mentioned (no explicit date found)