fix(traefik): set controllerName on GatewayClasses and Traefik providers
ci/woodpecker/pr/pre-commit Pipeline was successful
ci/woodpecker/pr/kubeconform Pipeline failed

GatewayClasses were stuck as Unknown because neither Traefik instance
had controllerName configured, causing both to default to
traefik.io/gateway-controller which matched neither GatewayClass.

Align the GatewayClass controllerName fields with what each Traefik
instance is now explicitly configured to advertise.
This commit is contained in:
2026-05-22 23:31:02 +10:00
parent f53a2dc4f8
commit 45fd0090e5
4 changed files with 4 additions and 2 deletions
@@ -4,4 +4,4 @@ kind: GatewayClass
metadata:
name: traefik-external
spec:
controllerName: traefik.io/gateway-controller
controllerName: traefik.io/gateway-controller-external
@@ -4,4 +4,4 @@ kind: GatewayClass
metadata:
name: traefik-internal
spec:
controllerName: traefik.io/gateway-controller
controllerName: traefik.io/gateway-controller-internal
@@ -28,6 +28,7 @@ providers:
namespaces: []
nativeLBByDefault: false
labelSelector: "traefik.io/instance=external"
controllerName: "traefik.io/gateway-controller-external"
logs:
access:
@@ -28,6 +28,7 @@ providers:
namespaces: []
nativeLBByDefault: false
labelSelector: "traefik.io/instance=internal"
controllerName: "traefik.io/gateway-controller-internal"
logs:
access: