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

Nodecontroller doesn't flip readiness on pods if kubeletVersion < 1.2.0 #30828

Merged
merged 1 commit into from
Aug 18, 2016

Conversation

bprashanth
Copy link
Contributor

@bprashanth bprashanth commented Aug 17, 2016

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 Reviewable

@k8s-github-robot k8s-github-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. release-note-label-needed labels Aug 17, 2016
@lavalamp lavalamp added lgtm "Looks good to me", indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. labels Aug 17, 2016
@lavalamp
Copy link
Member

ought to be cherry-picked into 1.2, are we even still making builds of that?

@bprashanth bprashanth changed the title [wip] Nodecontroller doesn't flip readiness on pods if kubeletVersion < 1.2.0 Nodecontroller doesn't flip readiness on pods if kubeletVersion < 1.2.0 Aug 17, 2016
@bprashanth
Copy link
Contributor Author

bprashanth commented Aug 17, 2016

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.

@k8s-bot
Copy link

k8s-bot commented Aug 17, 2016

GCE e2e build/test passed for commit 15c9826.

@bprashanth bprashanth added this to the v1.3 milestone Aug 17, 2016
@bprashanth bprashanth added cherrypick-candidate priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Aug 17, 2016
@k8s-github-robot
Copy link

@k8s-bot test this [submit-queue is verifying that this PR is safe to merge]

@k8s-bot
Copy link

k8s-bot commented Aug 18, 2016

GCE e2e build/test passed for commit 15c9826.

@k8s-github-robot
Copy link

Automatic merge from submit-queue

@k8s-github-robot k8s-github-robot merged commit 7ceb23c into kubernetes:master Aug 18, 2016
@fabioy fabioy added cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. and removed cherrypick-candidate labels Aug 18, 2016
k8s-github-robot pushed a commit that referenced this pull request Aug 19, 2016
…8770-#30828-upstream-release-1.3

Automatic merge from submit-queue

Automated cherry pick of #28770 #30828

Cherry pick of #28770 #30828 on release-1.3.
shyamjvs pushed a commit to shyamjvs/kubernetes that referenced this pull request Dec 1, 2016
…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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. lgtm "Looks good to me", indicates that a PR is ready to be merged. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants