Busyloop when installed alongside MetalLB

[imax9000]

trafficstars

Describe the bug

When using LoadBalancer service type, NGF and MetalLB are constantly updating the same Service objects: MetalLB adds metallb.io/ip-allocated-from-pool annotation and NGF immediately deletes it, MetalLB adds it back and so on.

To Reproduce Steps to reproduce the behavior:

1. Install and configure NGF and MetalLB.
2. Create a Gateway resource.
3. Run kubectl proxy and curl -s "http://127.0.0.1:8001/api/v1/namespaces/${NAMESPACE:-default}/services?watch=1" | jq -c .object.metadata.annotations

{"metallb.io/ip-allocated-from-pool":"extra"}
null
{"metallb.io/ip-allocated-from-pool":"extra"}
null
{"metallb.io/ip-allocated-from-pool":"extra"}
null
{"metallb.io/ip-allocated-from-pool":"extra"}
null
{"metallb.io/ip-allocated-from-pool":"extra"}
null
{"metallb.io/ip-allocated-from-pool":"extra"}
null
{"metallb.io/ip-allocated-from-pool":"extra"}
null

Expected behavior

Peaceful coexistence and proper functioning of both NGF and MetalLB.

Your environment

• nginx-gateway-fabric: 2.1.4
• MetalLB: v0.14.9
• Kubernetes: v1.33.0, on-prem via kubeadm