-
Notifications
You must be signed in to change notification settings - Fork 120
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
kubeadm function failed: unable to create ClusterRoleBinding: client rate limiter Wait returned an error: context deadline exceeded #678
Comments
I saw a similar issue when the connectivity between Kamaji Operaror and Tenant Control Planes was broken. I know it could sound silly but could you check connectivity works as expected with the Furthermore, which version or git SHA commit are you running? |
Hey @prometherion thanks for quick reply I just found that kubernetes api-server seems was stuck. Despite the fact etcd was running, api-server was not working. So it seems Kubernetes API-server issue. |
I just restarted tenant Kubernetes control-plane and everything started working |
My bad, now I can see the same errors. I investigating it right now Kamaji was built from |
UPD: found it! Cluster was working with old hostname. There were correct ingress resource, but Fixed that by removing It seems kamaji should also check kubeconfig files to contain correct hostname as part of #641 improovment |
Yes, you're right, we fixed this with latest releases. If everything's fixed, may I ask you to close this? |
Sure, let's do that |
Just noticed that kamaji stopped processing new clusters, readiness probe reported ok, logs are looping over:
The text was updated successfully, but these errors were encountered: