-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Nodecontroller doesn't flip readiness on pods if kubeletVersion < 1.2.0 #30828
Conversation
ought to be cherry-picked into 1.2, are we even still making builds of that? |
I tested this with a master running a custom build and 1.1 nodes, pods didn't get marked NotReady on netsplit for > 40s < 5m. Same custom build, same test, nodes running HEAD code, pods marked NotReady then Ready. |
GCE e2e build/test passed for commit 15c9826. |
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
GCE e2e build/test passed for commit 15c9826. |
Automatic merge from submit-queue |
…pick-of-#28770-kubernetes#30828-upstream-release-1.3 Automatic merge from submit-queue Automated cherry pick of kubernetes#28770 kubernetes#30828 Cherry pick of kubernetes#28770 kubernetes#30828 on release-1.3.
Older versions of the kubelet didn't know how to reconcile pod.Status, so the nodecontroller would mark pods NotReady on netsplit, and if the partition recovered in < 5m, the pods would never get marked Ready resulting in NotReady endpoints indefinitely (till kubelet restart/pod recreate etc).
This change is