-
Notifications
You must be signed in to change notification settings - Fork 146
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
Install stuck in "wait for the first server be ready" with kubevip, cilium and kube proxy disabled #157
Comments
Until I find the reason for this, so I can identify the appropriate conditions for a patch, I have applied a temporary workaround by integrating it into the pre-tasks of my playbook.
|
It's a chicken or the egg scenario. Celium without kube-proxy needs to talk to the kube-api that's being loadbalanced by kube-vip that needs a working cni to contact the kube-api's internal k8s service. As a workaround I set up cilium with: |
Summary
During the initial installation of a cluster using RKE2 version 1.27.1+rke2r1, kubevip, cilium and kube proxy disabled, the first node is stuck in the NOTREADY state preventing the successful completion of the cluster installation process.
The workaround I found :
ip a a 192.0.2.20 dev ens224
systemctl restart rke2-server.service
Not sure why this is happening so far, possibly due to the disabling of kube proxy.
Issue Type
Bug Report
Ansible Version
Ansible 2.14.8
Steps to Reproduce
Deploy RKE2 with the following variables :
Here is the content of rke2-cilium-proxy.yaml :
Expected Results
The first server should at some point be in the READY state, so the installation of the cluster succeed.
Actual Results
The text was updated successfully, but these errors were encountered: