Describe the bug
Doing the config for k3s behind a reverse proxy, creating /var/lib/rancher/k3s/server/manifests/traefik-config.yaml does nothing to which ports traefik was binding to.
I noticed /var/lib/rancher/k3s/server/manifests/traefik.yaml exists, but merging the suggested config into that file also did nothing.
To Reproduce
Steps to reproduce the behaviour:
- Follow instructions for
Using an existing reverse proxy
- Output of
kubectl get svc -n kube-system | grep traefik is still ports 80 & 443
NB: traefik service in that output indicates it hasn't been restarted, the uptime is large, but so is the uptime in the example output.
Expected behaviour
Traefik is reloaded with customised exposed ports
Desktop (please complete the following information):
N/A
Server:
- Device: [e.g. iPhone6]
- OS: OpenSuse Tumbleweed 20250220
Describe the bug
Doing the config for k3s behind a reverse proxy, creating
/var/lib/rancher/k3s/server/manifests/traefik-config.yamldoes nothing to which ports traefik was binding to.I noticed
/var/lib/rancher/k3s/server/manifests/traefik.yamlexists, but merging the suggested config into that file also did nothing.To Reproduce
Steps to reproduce the behaviour:
Using an existing reverse proxykubectl get svc -n kube-system | grep traefikis still ports 80 & 443NB: traefik service in that output indicates it hasn't been restarted, the uptime is large, but so is the uptime in the example output.
Expected behaviour
Traefik is reloaded with customised exposed ports
Desktop (please complete the following information):
N/A
Server: