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-1.15.3: pod-eviction-timeout is ignored #2
Comments
kskmori
added a commit
that referenced
this issue
Aug 29, 2019
…ion-timeout (fixes #2) NOTE: Taint based Evictions timeout starts since the node status changed to NotReady (or Unreachable) so it would take 40s in total after the time of the actual failure: 40s = node-monitor-grace-period(20s) + default-not-ready-toleration-seconds(20s) as it's equal to pod-eviction-timeout=40s
fixed in 26076cb
|
Another note: the pod status is now shown as "Terminating" instead of "Unknown" in 1.11, but the service availability is same (can not fail over in the event of a node failure).
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
revision: 1d9a9b6 2019-08-29 Update versions to kubernetes 1.15.3 and the latest documents
It takes 5 minutes until the pods are evicted after a node failure regardless of the kubeadm init config below. It has been working as expected in kubeadm-1.11.3.
Diagnosis:
As of 1.13, Taint based Evictions is enabled and needs to be configured for it instead of pod-eviction-timeout.
Ref.
The text was updated successfully, but these errors were encountered: