-
Notifications
You must be signed in to change notification settings - Fork 109
Traefik config doesn't work #1060
Copy link
Copy link
Open
Description
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 traefikis 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
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels