Deploying Traefik with helm is failing. I am getting the error: command traefik error: error while building entryPoint web: error preparing server: error opening listener: listen tcp :80: bind: permission denied directly in the traefik pod. It is creating the service correctly though. Here is my va…

[image] erictg: "--entrypoints.web.address=:80" "--entrypoints.websecure.address=:443" should be 8000 and 8443 respectively

Thanks! I love when the fixes are easy :slight_smile:

Hi I am trying to run a fully manual setup k8s instance on a Digital Ocean VM, and I am trying to expose it using traefik. I think this means I need to bind on ports 80 and 443 using hostNetwork = True. I was able to do this with HAProxy, using this tutorial: Getting Started | HAProxy Ingress - he…

After looking deeper, I attempted to use the pod security policy to allow this, but get the same issue: helm install \ --set hostNetwork=true \ --set podSecurityPolicy.enabled=true \ --set securityContext.runAsNonRoot=false \ --set ports.web.port=80 --set ports.websecure.port=443 \ trae…

[image] franco: have tried various value overrides, the current one that is producing this error is Hi @franco have you understood how to do it? I have the same problem if I use helm, while I can install using the following yaml file: --- apiVersion: v1 kind: Namespace metadata: name: tra…

Solved, explained in my stackoverflow question/answer: [Alessandro Dentella] Permission problem w/ helm3 installation of traefik on port 80 (hostNetwork) kubernetes, kubernetes-helm, traefik, microk8s asked by Alessandro Dentella on 02:01PM - 10 Feb 21 …

Why should it be 8000 and 8443? Cant we set port 443 and port 80 as entrypoints?

hello @anyaddres This is done because of security reasons. The Traefik binary inside a container is running on a non-root user, so that's why ports greater than 1024 are being used.

Traefik v2 unable to bind port 80 in k8s

Traefik Traefik v2

sandroden February 14, 2021, 8:35pm 7

Solved, explained in my stackoverflow question/answer:

Topic		Replies	Views
Issues with installing Traefik Pilot on Kubernetes Traefik v2 kubernetes-crd , kubernetes-ingress	11	3128	September 3, 2020
Helm Chart port bind problems Traefik v2 kubernetes-ingress	0	799	May 13, 2020
Traefik Deployment answering 8443(websecure) but not 8000(web) Traefik v2 kubernetes-crd	0	268	January 18, 2024
Traefik v2.2 on k8s + Helm 3 Chart = CrashLoopBackOff [logs don't point to anything] Traefik v2 kubernetes-ingress	3	1311	May 29, 2020
Traefik serves traffic on port 80 over https Traefik v2 kubernetes-ingress	1	140	June 27, 2024

Traefik v2 unable to bind port 80 in k8s

Related topics