Hello all, with the announcement of the NGINX Ingress retirement -- https://kubernetes.io/blog/2025/11/11/ingress-nginx-retirement/ I'm curious to understand how that will impact the NGINX Ingress versions supported in Rancher.

Rancher itself can be deployed behind any ingress controller, it does not depend on ingress-nginx or anything else specific.

Is there a chance Gateway API or anything else than Traefik will be considered as an option? I have had to move from Traefik to Ngnix in the past because it was more flexible and I fear some regression situations.

Traefik is also a Gateway API controller

But they can't coexist, am I wrong?

What?

I guess that's my problem then. 😁 Thanks.

Hello, I'm joining this thread and would like to clarify a few questions so as not to create additional issues on GitHub. I've been using Rancher since version 2, and I really like the convenience of ingress and web-based configuration of this functionality. I've always used ingress-nginx from the very beginning, but I have a question: 1. Is rancher UI suitable for configuring ingress, traefik, envoy, or any other things other than ingress nginx (I think the answer to my question is yes, but I'm still clarifying it) 2. I'm not familiar with the gateway API, but I also want to clarify: does Rancher support this configuration in the web? For example, we use servicemonitor/podmonitor and write our own manifests for them, since this functionality is configured only via YAML files and doesn't work natively in the UI. Will there be similar issues with gapi, or are you planning to add any related functionality in future releases?

Please start a different thread for questions about gateway API.

sure, can forward this question to a general chat in that case

@creamy-pencil-82913 thanks for the response. I'm more interested around what Rancher will do going forward. We have the "built-in" NGINX Ingress that can be set on a new cluster build.

Following this thread. Really interested to se what happens here.

This is good info, thanks all. Does anyone have a guide on how to enable Traefik in the open source rke2? Is this post all there is to it, aside from editing existing ingresses of course https://github.com/rancher/rke2/issues/5928#issuecomment-2675960786 Tried this and it seemed to work, had to edit existing ingresses to specify ingressClassName as traefik

Nice with the issue tracking on Github. What i understand you can enable traefik when running native RKE2 by changeing the configfile on each host. But when running RKE2 with rancher there is now way to do that. I deployed rancher trough fleet and disabled nginx-ingress in cluster config:

defaultNamespace: kube-system
helm:
  releaseName: traefik
  repo: <https://traefik.github.io/charts>
  chart: traefik
  version: 37.3.0
  values:
    deployment:
      replicas: 3
    providers:
      kubernetesCRD:
        enabled: true
        allowCrossNamespace: false
      kubernetesIngress:
        enabled: true
        publishedService:
          enabled: true
    ingressClass:
      enabled: true
      isDefaultClass: false
    service:
      type: LoadBalancer
      annotations:
        <http://service.antrea.io/external-ip-pool|service.antrea.io/external-ip-pool>: "antrea-ip-pool"
      spec:
        loadBalancerIP: x.x.x.x # <<-- CHANGE THIS
    ports:
      web:
        port: 80
        exposedPort: 80
      websecure:
        port: 443
        exposedPort: 443
        tls:
          enabled: true
    logs:
      general:
        level: INFO
      access:
        enabled: true

Hello, is there way how to enable both ingress controller - nginx as default and traefik as second one?