This message was deleted.

You might try the Traefik slack or forums. We package Traefik but I don’t think you’re going to find any Traefik experts here.

yes, i’ll probably do that as well - though i fear being sent around “because your using k3s own helm charts - who knows what they set up”

our charts are their charts. We just split the CRDs out to make upgrades smoother. They’re pretty familiar with k3s users since we’re one of the few distros that packages Traefik instead of ingress-nginx.

thanks

I had a similar problem. For me the issue was that Traefik by default doesn't allow using resources across namespaces. I ended up creating a single wildcard cert and putting in kube-system where Traefik is, then setting it as the default TLS cert