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.
Remove --providers.kubernetesgateway.controllername which does not exist in
Traefik v3, update GatewayClass controllerName to the standard v3 value, and
use labelSelector on each instance's kubernetesGateway provider to differentiate
internal vs external traffic.
Reviewed-on: #125
deploy traefik for internal and external applications. port forwarding
from the external routers will only occur to the IP of the
traefik-external service.
- traefik-internal and traefik-external added
- each is a different deployment
Reviewed-on: #119
unkinben