ingress-nginx Retirement
#10486
Replies: 1 comment 4 replies
-
|
Hello, I've started using rancher products for a few month (sorry for the noob question and my english). I'm disabled nginx-ingress by defaut and using traefik-ingress since the beginning using the Apps Charts (with yml customs values). How the migration to my treafik-ingress from apps Charts to the rke2 core integration will impact my cluster ? And how to do it (if somethings have to be done) ? Thank you, |
Beta Was this translation helpful? Give feedback.
-
|
You don't have to migrate. You can disable the Traefik controller coming with RKE2 and use the traefik-ingress from the App Charts instead. Same procedure as when you disabled ingress-nginx. |
Beta Was this translation helpful? Give feedback.
-
|
Ok thanks, It seems logic. |
Beta Was this translation helpful? Give feedback.
-
|
If my understanding is correct, you are consuming Traefik from https://github.com/rancher/partner-charts/tree/main-source/charts/traefik/traefik, right? The content from the Partner Helm Chart Catalog is 100% maintained by the partners. I think Traefik will keep doing it :) |
Beta Was this translation helpful? Give feedback.
-
|
Yes that 's it ! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
As many of you may have noted with our most recent releases, Traefik is the new default ingress in RKE2. Read ahead for more details.
ingress-nginx was retired upstream as of March 2026; Traefik is now the default for new clusters starting in v1.36 (existing clusters will keep their current ingress upon upgrade to avoid breakage). This transition brings the following structural changes:
Please let us know here if you have any comments, questions, or feedback for us, we would be happy to receive it :)
Beta Was this translation helpful? Give feedback.
All reactions