Hey, I had some issues when trying to add the pilot token to our Traefik. It mostly crashed or didn't do anything, and upon checking the traefik cli from the pod itself by running: traefik --experimental.pilot.token=, I got the following error: INFO[0000] Configuration loaded from flags. 2020/08/…

I have those already setup, and I still get the same error. I'm going to link the values file of our deployment: # Default values for Traefik image: name: traefik tag: v2.3.0-rc4 # # Configure the deployment # deployment: enabled: true # Number of pods of the deployment replicas: 1 # Ad…

[image] PeterOrliczki1: I have those already setup, and I still get the same error. If you get the same error, is it possible you set it up incorrectly? The error indicates that it still tries to bind to port 80. Look at the kubernetes manifests and check if the values for entrypoints are c…

I dont think there should be any problem with that, as I can see that it tries to run on the above ports. (I tried to test pilot on traefik-private) [Screenshot 2020-09-02 at 11.51.11]

Hey, can you look at the kubernetes manifests and check if the values for entrypoints are correct? Note entrypoint as per notsureifkevin's link, not endpoints.

Sorry, my bad. However, the generated manifest still has the correct entrypoints and ports. [Screenshot 2020-09-02 at 12.02.20]

Actually, I just re-read your top post more carefully, and realised that you are getting this error from CLI. I missed that on the first reading, apologies. So this then makes sense, you are trying to start second instance of traefik inside the pod and it cannot bind.

We run two traefik deployments yes, however, they are in different pods, and even on different helm deployments, so if I understood you correctly, then there shouldnt be a case where these 2 traefik installations are in the same pod.

[image] PeterOrliczki1: upon checking the traefik cli from the pod itself by running: traefik --experimental.pilot.token=, I got the following error: INFO[0000] Configuration loaded from flags. 2020/08/27 08:36:42 traefik.go:76: command traefik error: error while building entryPoint http: err…

It was true, upon checking again, I managed to make it work, here's the yaml in case anyone is interested: # Default values for Traefik image: name: traefik tag: v2.3.0-rc4 # # Configure the deployment # deployment: enabled: true # Number of pods of the deployment replicas: 1 # Additio…

Issues with installing Traefik Pilot on Kubernetes

Traefik Traefik v2

notsureifkevin August 31, 2020, 11:38am 2

Traefik cannot bind directly to port 80/443 because of security limitations on the cluster.

Please see this post for additional configuration details. Traefik v2 unable to bind port 80 in k8s

Topic		Replies	Views
Traefik v2 unable to bind port 80 in k8s Traefik v2 kubernetes-ingress	8	19275	November 9, 2021
Basic example for an instance running with admin interface enabled Traefik v2 kubernetes-crd , kubernetes-ingress	7	2684	October 16, 2019
Cannot access Traefik Dashboard on k3s Traefik v3 (latest) rancher , kubernetes-crd , kubernetes-ingress , dashboard-api	1	2113	September 15, 2024
Install And Configure Traefik with Helm Blog	15	5598	April 8, 2024
Deploy multiple Traefik in k8s Traefik v2 kubernetes-ingress	0	324	December 15, 2021

Issues with installing Traefik Pilot on Kubernetes

Related topics