Using Traefik version 2.0.0.-beta1 running in Kubernetes version 1.15.1, when I configure an IngressRoute resource with its "spec.tls.secretName" populated with the name of a Kubernetes Secret in the same namespace, Traefik does create a route to the backend pods, but it serves it using the default …

No, I think it's settled well enough for now. In summary, an IngressRoute can suggest a certificate to use for serving it over TLS, but it will only be used if a client's request includes an SNI hint that's covered by that certificate's SANs, and even then only if no other IngressRoute has a competi…

IngressRoute with "secretName" field still serves with default certificate

Traefik Traefik v2

daniel.tomcej July 23, 2019, 8:49pm 12

Is there anything you still need assistance with on this topic?

Traefik - Custom TLS certificate

Topic		Replies	Views
Traefik's default TLS certificate instead of one from secret Traefik v3 (latest) kubernetes-ingress	1	664	June 27, 2024
IngressRoute without "secretName" field yields 404 response Traefik v2 kubernetes-crd	4	2117	July 24, 2019
TLS secret associated with Ingress resource in K8s isn't used Traefik v2 kubernetes-ingress	1	476	October 14, 2022
CA certificate from secret is not served Traefik v2 kubernetes-ingress	7	1662	June 20, 2022
TLS via secretName Kubernetes Traefik v2 kubernetes-crd	7	4946	October 22, 2019

IngressRoute with "secretName" field still serves with default certificate

Related topics