Replies: 2 comments 9 replies
-
Don't edit the HelmChart. Packaged components are reverted to their default content every time k3s is restarted. Use a HelmChartConfig to add values as shown in the documentation. https://docs.k3s.io/helm#customizing-packaged-components-with-helmchartconfig |
Beta Was this translation helpful? Give feedback.
-
Problem was not with my config but that the server was configured from the outside to only receive traffic on 80 and 443. |
Beta Was this translation helpful? Give feedback.
-
I struggle hard getting my k3s/traefik v2 setup to work for my seemingly very simple usecase. This is on a Debian 12 bare metal server.
What works:
What doesn't work:
Port 50051 for a grpc server answers on pod and service level but cannot be reached from the outside world. I tried with
nc
andgrpcurl
which work from inside but they cannot connect from outside.In general I struggle hard to have a consistent grip over the k3s config. Sometimes it seems like it ignores or forgets my config changes. E.g. trying to have debug log by adding these lines to valuesContent of traefik has no effect (checking description of the pod).
Even when I force a rollout with:
k3s kubectl rollout restart deployment traefik -n kube-system
When I kill the pod and it is recreated I see only:
time="2025-01-23T13:20:23Z" level=info msg="Configuration loaded from flags."
My endpoints:
My traefik config:
My ingress routes:
My grpc service:
My grpc container:
My traefik pod:
Beta Was this translation helpful? Give feedback.
All reactions