I'm curious about the decision to phase out the NGINX Ingress Controller in favor of the API Gateway. Given that many of the annotations we currently rely on are unsupported or incompatible with the Gateway, this switch seems challenging. I'd appreciate more insight into a few key aspects: what are the core technical or strategic reasons for this shift; is there a plan to support the commonly used annotations; how will the migration process work for setups that depend on features presently unavailable; and are there any plans for transitional measures or backward compatibility? I want to ensure that this transition won't disrupt existing workloads. Also, I know the Ingress resource remains, but I'd rather focus on why some are moving to Gateway API, especially considering it doesn't seem fully ready yet.
4 Answers
You're spot on about the confusion out there! Many folks seem to think that the end of ingress-nginx means the Ingress API itself is going away, but that's not true. Ingress is still very much alive in Kubernetes. You can freely switch to other controllers like Traefik and continue using Ingress as before. The Gateway is being promoted for future L7 routing needs, but it doesn't mean you have to transition immediately.
I think a lot of the push to migrate to the Gateway API stems from a desire to future-proof setups, with the belief that it will be the standard moving forward. But for now, if you rely heavily on certain annotations that the Gateway API may not support yet, it might be wiser to consider other controllers instead until features catch up.
The decision to deprecate NGINX Ingress isn't directly aimed at the Gateway API. The original NGINX maintainers who were volunteers decided they no longer wanted to continue their contributions, and after attempts to find new maintainers, nobody stepped up. This isn't about the Gateway itself becoming the norm; there are other options available if you’re not ready to switch just yet.
It’s good to clarify that while ingress-nginx will no longer be maintained, you’re still free to use Ingress with other controllers. The Gateway API is suggested for its improvements, but you’re not being compelled to change over right away. Just update your controller when you're ready to avoid any issues.
Related Questions
How to Build a Custom GPT Journalist That Posts Directly to WordPress
Cloudflare Origin SSL Certificate Setup Guide
How To Effectively Monetize A Site With Ads