Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for loadBlancerClass #325

Open
itmwiw opened this issue Aug 23, 2024 · 2 comments
Open

Support for loadBlancerClass #325

itmwiw opened this issue Aug 23, 2024 · 2 comments
Labels
kind/bug lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@itmwiw
Copy link

itmwiw commented Aug 23, 2024

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:

  • KubeVirt version (use virtctl version): N/A
  • Kubernetes version (use kubectl version): N/A
  • VM or VMI specifications: N/A
  • Cloud provider or hardware configuration: N/A
  • OS (e.g. from /etc/os-release): N/A
  • Kernel (e.g. uname -a): N/A
  • Install tools: N/A
  • Others: N/A
@kubevirt-bot
Copy link
Contributor

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

@kubevirt-bot kubevirt-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 21, 2024
@kubevirt-bot
Copy link
Contributor

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

@kubevirt-bot kubevirt-bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Dec 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

2 participants