I'm using two instances of traefik 2.10.5 on a kubernetes cluster (1.28.2) with nodes in two network zones
One instance is dedicated to LAN pods, one instance is dedicated to DMZ pods.
I use two IngressClass. The first "traefik-lan" and the second "traefik-dmz".
Each traefik instance has its own dahboard interface, service account and has been deployed with helm.
When I publish an Ingress, I associate it with either the IngressClass "traefik-dmz" or the IngressClass "traefik-lan".
kubectl get Ingress --all-namespaces
NAMESPACE NAME CLASS HOSTS ADDRESS PORTS AGE
dev-demonginxdatastore-dmz ingress-http-https-dev-demonginxdatastore-dmz traefik-dmz dev-demok8sdatastore-dmz.demo.com 80, 443 6h52m
dev-demonginxnfs-lan ingress-http-https-dev-demonginxnfs-lan traefik-lan dev-demok8snfs.demo.com 80, 443 28h
rec-demonginxdatastore-lan ingress-http-https-rec-demonginxdatastore-lan traefik-lan rec-demok8sdatastore.demo.com 80, 443 27h
rec-demonginxnfs-lan ingress-http-https-rec-demonginxnfs-lan traefik-lan rec-demok8snfs.demo.com 80, 443 38m
I don't understand why when I connect to the dashboard of the lan traefik instance, I see all the LAN and DMZ Ingress...conversely, when I connect to the dashboard of the dmz traefik instance, I see all the DMZ and lan Ingress.
Shouldn't I only see the Ingress that correspond to the IngressClass of the network zone instance where the dashboard is located ?
Note that I don't have this problem when I use "IngressRoute" objects from Traefik CRDs.
Thank for your help