With Ingress NGINX reaching its end of life this month, many teams might still be relying on it in production environments. I'm curious about the timelines that teams are setting for themselves to migrate to alternatives. In my experience, Ingress NGINX has been the go-to for years, and now that upstream maintenance will cease, organizations are looking at options such as Traefik, HAProxy Ingress, AWS ALB Controller (for EKS), and Gateway API. What's the overall sentiment regarding these alternatives? Are any of them close to being direct replacements for Ingress NGINX? Furthermore, are there teams that might choose to stick with an extended maintenance version instead of quick migration?
5 Answers
I migrated to Envoy Gateway as soon as the EOL was announced. So far, it's been fantastic! The transition was smooth and I’ve been really happy with the performance.
Don't forget that the Nginx controller (nginx-ingress) is actually a solid drop-in alternative! It's the Kubernetes version that’s going away, not the F5 Nginx offering.
I've been working on migrating to Gateway API these past few days, and it seems pretty straightforward. I haven't run into any issues yet, which is promising!
We dropped in Traefik without any problems. There was no real need for us to move to Gateway API just yet since we’re still using Ingress, and everything's working fine.
We just switched to the AWS ALB Controller this week since we use EKS. It wasn’t exactly a drop-in replacement; we had to make quite a few changes to get everything running right.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures