# Named "kong-v2", not "kong" — the "kong" GatewayClass already exists on
# this cluster (backs the unrelated tasks/jira/openrouter Gateway) and its
# default parametersRef is load-bearing for that Gateway, which has no
# per-instance override unlike ours. Reusing that name would edit a shared
# cluster-scoped object something else depends on. No parametersRef here:
# every domain's own Gateway sets spec.infrastructure.parametersRef itself
# (see dataplane-template/gateway.yaml), so there's no meaningful default to
# set at the class level.
apiVersion: gateway.networking.k8s.io/v1
kind: GatewayClass
metadata:
  name: kong-v2
spec:
  controllerName: konghq.com/gateway-operator