Handling of "this cluster does not support `LoadBalancer` services" less graceful than it could be

[mflendrich]

Is there an existing issue for this?

• [X] I have searched the existing issues

Current Behavior

(This is based on my understanding of the issue from 2 years ago and brief verification in the code)

If you run KIC in a cluster that does not support LoadBalancer type services (that means for example homelabs but could also extend well past that - e.g. k8s on edge, embedded, etc), the KIC proxy service that is of type LoadBalancer by default will never get a load balancer IP, and that's okay.

KIC reports this as an error: https://github.com/Kong/kubernetes-ingress-controller/blame/0be255aa3160bdde554ec813922d65174643f877/internal/manager/setup.go#L317C23-L317C23

Expected Behavior

I think that this should be a log.Info reported once and definitely not an error.

Steps To Reproduce

1. Run KIC on microk8s
2. Observe that the proxy service is of type LoadBalancer
3. Observe that the proxy service never gets a public IP
4. See the (undesirable) error spam in KIC's logs

Kong Ingress Controller version

Observed in KIC 2.9 but very likely still relevant.

Kubernetes version

any (that ignores the LoadBalancer service type)

Anything else?

There is an existing ancient PR https://github.com/Kong/kubernetes-ingress-controller/pull/4066 that solves this. I've created this issue to keep track of that idea (so that the stale PR can be closed).