Open itmwiw opened 3 months ago
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
What happened: I have a Baremetal Host cluster with MetalLB installed in it, a Kubevirt Guest cluster, and I rely on kccm for LBs creation. Everything works fine, and whenever I create a service of type LoadBalancer in the Guest cluster, an equivalent sevice is created in the Host cluster to proxy the incoming requests. However when I create a LoadBlancer service in the Guest cluster and specify the loadBalancerClass property in the spec section, no service in created in the Host cluster and the service in the Guest cluster remains in 'pending' state. Is the loadBalancerClass something kccm is aware of?
What you expected to happen: The service is created in the host cluster with the correct loadBalancerClass.
How to reproduce it (as minimally and precisely as possible): Create a Loadbalancer service type in the Guest Cluster.
Additional context: MetalLb has also implemented the loadBalancerClass concept as described here
Environment:
virtctl version
): N/Akubectl version
): N/Auname -a
): N/A