Using Kubernetes Gateway API with Cert Manager continuously reloads controller
Author: asardaesCreated Jan 19, 2026Updated Sep 15, 2026
Labelskind/bug/possiblearea/provider/k8s
Welcome!
- Yes, I've searched similar issues on GitHub and didn't find any.
- Yes, I've searched similar issues on the Traefik community forum and didn't find any.
What did you do?
I have 2 Traefik controllers in Kubernetes, same Helm chart but different values. In both of them I enabled the Kubernetes Gateway API and configured a TLS secret that is created and managed by Cert Manager (each one gets a different secret for a different host name).
What did you see instead?
Based on the logs, it seems to me that each Traefik controller receives updates for both TLS secrets and reloads everything periodically. See the attached logs below.
What version of Traefik are you using?
v3.6.7
What is your environment & configuration?
Kubernetes with Helm chart v38.0.2 Values from 1 of the installations:
providers:
kubernetesCRD:
enabled: true
allowCrossNamespace: true
ingressClass: mbcon
labelSelector: app.kubernetes.io/instance=mbcon-ingress
kubernetesIngress:
enabled: false
allowEmptyServices: false
ingressClass: mbcon
kubernetesGateway:
enabled: true
gatewayClass:
enabled: true
name: mbcon
gateway:
enabled: true
name: mbcon
listeners:
web:
port: 8000
protocol: HTTP
hostname: svc.domain.com
namespacePolicy:
from: Same
websecure:
port: 8443
protocol: HTTPS
mode: Terminate
hostname: svc.domain.com
namespacePolicy:
from: All
certificateRefs:
- kind: Secret
name: mbcon-cert-secret
group: ""
If applicable, please paste the log output in DEBUG level
Source: traefik/traefik