-
Notifications
You must be signed in to change notification settings - Fork 9
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
Fix kubeadm race #4
Labels
Comments
We have kubeadm.service run After=etcd-member.service, which makes it start after etcd gets started the first time. etcd might fail though for various reasons (e.g SRV record not updated yet) on the first 1-2 starts which leads kubeadm to fail. Since it's Type=oneshot it can't be restarted by systemd. Here is the log from a rolling upgrade showing the problem:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Sometimes kubeadm fails, probably when it comes up before etcd reached quorum and fails (but can be restarted).
The text was updated successfully, but these errors were encountered: