This message was deleted.

You can disable traefik and deploy your own ingress.

Yes, for sure, it’s just so nice with things working out of the box 😄 I am trying to get my org to use rancher desktop as their laptop k8s solution and it would be very cool if people had to not deploy their own ingress controller for development environments! Happy to open a PR or something to help out if I find the issue

The issue of course is that the traefik version is fixed in the k3s release. So if you run a recent k3s version, you get a recent traefik. If you run an old k3s, you get an older traefik as well.

Would k3s have to be updated in rancher desktop then?

I just checked k3s 1.25.3, and it comes with traefik 2.9.1

That’s the issue, I was on 1.21 😄

Yeah, no worries, but even then the subversion may matter. Were you using 1.21.14?

1.21.14 should include traefik 2.6.1

Thanks, just upgraded but something fishy with my kubeconfig

You upgraded to 1.23.13, right? If you are on Ventura then you cannot currently use 1.24.* or 1.25.* due to some still unidentified issue

No still stuck on Monterey 😄 I did upgrade to

1.25

😬 Should I downgrade? I am not anticipating an upgrade anytime soon due to corp policy

No, 1.25 should work fine on Monterey; the issue is purely on Ventura