This message was deleted.
# rke2
a
This message was deleted.
n
so like, rke2 won't uninstall traefik when it 'see' existing rke2-traefik helm chart deployed..
b
n
no sorry, ok nice to see that rke2 supports two controllers
h
it does but both cannot listen to 80/443
n
yeah, of course not. Also, type of
ingress-controller:
has been changed to an array?
does anyone know how is this supposed to work? if I set:
Copy code
kubernetesIngressNginx:
   ingressClass: traefik
to make it different to
nginx
, it randomly select some of the nginx classed ingresses and move them to the traefik (the treafik has different publish status address). if I add:
Copy code
controllerClass: "rke2.​cattle.​io/ingress-nginx-migration"
as described, it does not claim any nginx class ingress, however, publishstatusaddress apparently does not work, because it puts IP addresses into status instead of the name from the
publishStatusAddress
option. do I something wrong? My idea is to create a new nginx ingress class (traefik), expose traefik at different IPs and migrate ingresses manually from nginx to traefik. Some of them have unsupported annotations like
whitelist-source-range
, so I cannot move them all just like that.