LoadBalancer IP address requirement too strict in Gateway Controller

[mflendrich]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

The kong-proxy service in all-in-one-dbless.yaml is type: LoadBalancer.

On microk8s this blocks Gateway API altogether. The gateway controller refuses to reconcile Gateway because there's no load balancer controller in the cluster that would set the external IP on the service.

The result is that Gateway API entries (e.g. HTTPRoutes) fail to sync to Kong at all.

Another thing is that Gateway API ceasing to work if the load balancer fails is a failure mode that doesn't look appropriate.

Expected Behavior

HTTPRoutes work even if Gateway is exposed on a Service of type LoadBalancer but there's no infra in the cluster to provision the load balancer.

Steps To Reproduce

1. snap install microk8s --channel 1.22/stable --classic
2. install gateway API CRDs
3. kubectl apply -f all-in-one-dbless.yaml (but enable the Gateway feature gate first)
4. kubectl apply -f examples/gateway-httproute.yaml
5. observe that "configuration successfully synced to kong" never occurs in logs; instead, you see repeated reconciliation errors from the Gateway controller complaining that the kong-proxy service is of type LoadBalancer but has no external IP.

Kong Ingress Controller version

2.3.1

Kubernetes version

any

Anything else?

No response