Home / server / Questions / 923172
In Process
Paddy
Asked: 2018-07-24 07:33:33 +0800 CST

Traefik doesn't pick TLS certificates secrets from the ingress definition in Kubernetes

  • 772

I have raised this exact query at stackoverflow as well, as, interestingly, "Traefik" and "Kubernetes-Ingress" tags are absent on ServerFault, but present on StackoVerflow.

When I only add the TLS secret to the Ingress, Traefik serves it's default certificate.

kind: Ingress
spec:
  rules:
    ....
  tls:
  - secretName: ingress-mgt-server-keys

Only when I mount the secret and add below parameter, does Traefik start serving the real certificate.

entryPoints.https.tls.certificates

Are TLS secrets to be define in both, Traefik Ingress and Ingress-controller? This forces me to repeat the keys as secrets to all the ingress namespaces as well as the ingress-controller namespace.

reverse-proxy

1 Answers

  1. The TLS Secret isn't needed to be set up in the target (ingress) namespaces.

    Only the ingress controller namespace needs the TLS Secret.

    • 0