Скачать или смотреть A  Seamless Path from Ingress-NGINX to

 Users are asking for alternatives to ingress-nginx, since its maintenance mode was announced and there have been security issues lately. They are searching for a practical migration path that is production ready. Emile wrote a blog about it, you can find it in the comments 👇 .

With v3.5, Traefik has an NGINX provider that reads ingress-nginx resources directly:
Same YAML, same annotations (we included the ones we have heard the most about from users, let us know which ones you need).
Just point Traefik to your k8s cluster and it runs.
Lets you move over gradually without changing everything at once.

The biggest burden we hear from users is having numerous annotations in their YAML files, and a full rewrite could be painful. What challenges do you face in moving away from ingress-nginx?

Why we believe Traefik Labs could support those ingress-nginx users looking for their new ingresses:
Cloud-native, dynamic config, no reloads needed, written in Go and fully GitOps compatible.
Go for memory safety, structured parsing and static binaries = security model designed to avoid issues.
Leading Gateway API support for future proofing Kubernetes networking.
Built-in dashboard for visibility, metrics, and quick troubleshooting.
WASM and Go plugins and middleware to extend functionalities.

How are you approaching the move from ingress-nginx?

Let me know if you want to hear more about NGINX provider.