argocd-apps/apps/base/traefik-system/gatewayclass-external.yaml at 2df359c4a9ca5465260381c6e69f8792d33861d9 - argocd-apps - Gitea

unkin/argocd-apps

Files

T

unkinben 2df359c4a9 fix(traefik): set controllerName on GatewayClasses and Traefik providers (#135 )

## Problem

Both GatewayClasses (`traefik-internal`, `traefik-external`) were stuck as `Unknown`. Neither Traefik deployment had `controllerName` set in `kubernetesGateway`, so both defaulted to `traefik.io/gateway-controller` — which matched neither GatewayClass.

## Fix

- `gatewayclass-internal.yaml`: `controllerName: traefik.io/gateway-controller-internal`
- `gatewayclass-external.yaml`: `controllerName: traefik.io/gateway-controller-external`
- `values-internal.yaml`: added `controllerName: traefik.io/gateway-controller-internal`
- `values-external.yaml`: added `controllerName: traefik.io/gateway-controller-external`

## Test plan

- [ ] ArgoCD syncs traefik-system cleanly
- [ ] `kubectl get gatewayclass` shows both as `Accepted: True`

Reviewed-on: #135

2026-05-22 23:44:06 +10:00

8 lines

162 B

YAML

Raw Blame History

 ---
 apiVersion: gateway.networking.k8s.io/v1
 kind: GatewayClass
 metadata:
   name: traefik-external
 spec:
   controllerName: traefik.io/gateway-controller-external