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

leader election occasionally fails to reconnect to api server #66

Closed
msau42 opened this issue Nov 3, 2020 · 1 comment · Fixed by #70
Closed

leader election occasionally fails to reconnect to api server #66

msau42 opened this issue Nov 3, 2020 · 1 comment · Fixed by #70
Assignees

Comments

@msau42
Copy link
Collaborator

msau42 commented Nov 3, 2020

Exact root cause is still uncertain, but when apiserver is having problems, the csi sidecars will fail to get the leader election lease with this error:

"error retrieving resource lock kube-system/external-attacher-leader-my-driver: Get https://localhost:443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/external-attacher-leader-my-driver: write tcp [::1]:53540->[::1]:443: write: broken pipe"

Even after apiserver comes back up, this error continues and never recovers. This is apparently intended behavior, and the fix is to enable watchdog so that kubelet can restart the container: https://github.com/kubernetes/client-go/blob/master/tools/leaderelection/healthzadaptor.go#L25

In-tree controllers like kube-controller-manager already set this.

@msau42
Copy link
Collaborator Author

msau42 commented Nov 3, 2020

/assign @verult

@msau42 msau42 changed the title leader election fails to reconnect to api server leader election occasionally fails to reconnect to api server Nov 3, 2020
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

Successfully merging a pull request may close this issue.

2 participants