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

LoadBalancer service got stuck with message: Service is ready:Load balancer is being provisioned #5143

Closed
serhiynovos opened this issue Dec 19, 2023 · 3 comments

Comments

@serhiynovos
Copy link

I installed Harvester 1.2.1 and connected Rancher 2.8.0 and then created RKE2 cluster with Cilium CNI.

I created IP pool with a few available IP addresses and Virtual Machine load balancer is working fine. Then I deployed a service which has LoadBalancer service and it got stuck with the next message "Service is ready:Load balancer is being provisioned"

On Harvester side I see LB for this service is created and active but it does not show which IP address is used (but in IP pool I see one more IP address was occupied)

@brandond
Copy link
Member

I don't believe this is the correct place for your issue. Please reopen this issue against harvester, as you are using the harvester load-balancer controller.

@pck
Copy link

pck commented Jan 15, 2024

I had a similar problem, and switching from Cilium to Calico CNI didn't help.
Rancher provisioned RKE2 with 3 × "etcd + control" + 2 × worker nodes and the kube-system/kube-vip daemonset was not running anywhere. (I think because of a NoExecute-taint on nodes with etcd.) Reconfiguring the cluster as 3 × etc + 2 × control + 2 × worker solved my issue.

@serhiynovos
Copy link
Author

@pck
Please refer to this issue harvester/harvester#4891

The issue that kube-vip DeamonSet did have toleration to run on etcd nodes only control plane. This comment solves the problem harvester/harvester#4891 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants