Skip to content

Automated cherry pick of #110256: kubelet: Mark ready condition as false explicitly for terminal pods#110479

Merged
k8s-ci-robot merged 2 commits into
kubernetes:release-1.24from
bobbypage:automated-cherry-pick-of-#110256-upstream-release-1.24
Jun 10, 2022
Merged

Automated cherry pick of #110256: kubelet: Mark ready condition as false explicitly for terminal pods#110479
k8s-ci-robot merged 2 commits into
kubernetes:release-1.24from
bobbypage:automated-cherry-pick-of-#110256-upstream-release-1.24

Conversation

@bobbypage

@bobbypage bobbypage commented Jun 9, 2022

Copy link
Copy Markdown
Member

Cherry pick of #110256 on release-1.24.

#110256: kubelet: Mark ready condition as false explicitly for terminal pods

For details on the cherry pick process, see the cherry pick requests page.

Fixed a 1.22 regression kubelet issue that could result in invalid pod status updates to be sent to the api-server where pods would be reported in a terminal phase but also report a ready condition of true in some cases.

bobbypage and others added 2 commits June 8, 2022 22:45
Terminal pods may continue to report a ready condition of true because
there is a delay in reconciling the ready condition of the containers
from the runtime with the pod status. It should be invalid for kubelet
to report a terminal phase with a true ready condition. To fix the
issue, explicitly override the ready condition to false for terminal
pods during status updates.

Signed-off-by: David Porter <david@porter.me>
Use a watch to detect invalid pod status updates in graceful node
shutdown node e2e test. By using a watch, all pod updates will be
captured while the previous logic required polling the api-server which
could miss some intermediate updates.

Signed-off-by: David Porter <david@porter.me>
@k8s-ci-robot k8s-ci-robot added this to the v1.24 milestone Jun 9, 2022
@k8s-ci-robot k8s-ci-robot added do-not-merge/cherry-pick-not-approved Indicates that a PR is not yet approved to merge into a release branch. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/needs-kind Indicates a PR lacks a `kind/foo` label and requires one. do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. area/kubelet labels Jun 9, 2022
@k8s-ci-robot k8s-ci-robot added area/test sig/node Categorizes an issue or PR as relevant to SIG Node. sig/testing Categorizes an issue or PR as relevant to SIG Testing. release-note Denotes a PR that will be considered when it comes time to generate release notes. and removed do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Jun 9, 2022
@bobbypage

Copy link
Copy Markdown
Member Author

/kind bug
/assign @mrunalp @rphillips @dchen1107 @thockin

@k8s-ci-robot k8s-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Jun 9, 2022
@k8s-ci-robot k8s-ci-robot removed the do-not-merge/needs-kind Indicates a PR lacks a `kind/foo` label and requires one. label Jun 9, 2022
@bobbypage

Copy link
Copy Markdown
Member Author

/triage accepted

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jun 9, 2022
@bobbypage bobbypage changed the title Automated cherry pick of #110256: kubelet: Mark ready condition as false explicitly for Automated cherry pick of #110256: kubelet: Mark ready condition as false explicitly for terminal pods Jun 9, 2022
@bobbypage

Copy link
Copy Markdown
Member Author

/retest

@rphillips

Copy link
Copy Markdown
Member

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jun 9, 2022
@thockin

thockin commented Jun 9, 2022

Copy link
Copy Markdown
Member

/approve

@k8s-ci-robot

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bobbypage, thockin

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 9, 2022
@bobbypage

Copy link
Copy Markdown
Member Author

ping @kubernetes/release-managers

for cherrypick approvals.

Thank you!

@puerco

puerco commented Jun 9, 2022

Copy link
Copy Markdown
Member

Thanks @bobbypage !
/priority improtant-soon
/lgtm

@k8s-ci-robot

Copy link
Copy Markdown
Contributor

@puerco: The label(s) priority/improtant-soon cannot be applied, because the repository doesn't have them.

Details

In response to this:

Thanks @bobbypage !
/priority improtant-soon
/lgtm

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@puerco puerco added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Jun 9, 2022
@k8s-ci-robot k8s-ci-robot removed the needs-priority Indicates a PR lacks a `priority/foo` label and requires one. label Jun 9, 2022
@puerco puerco added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Jun 9, 2022
@k8s-ci-robot k8s-ci-robot removed the do-not-merge/cherry-pick-not-approved Indicates that a PR is not yet approved to merge into a release branch. label Jun 9, 2022
@puerco

puerco commented Jun 9, 2022

Copy link
Copy Markdown
Member

/test pull-kubernetes-e2e-kind

@k8s-ci-robot k8s-ci-robot merged commit 050f930 into kubernetes:release-1.24 Jun 10, 2022
@liggitt liggitt added the kind/regression Categorizes issue or PR as related to a regression from a prior release. label Jan 30, 2023
@liggitt liggitt removed the kind/regression Categorizes issue or PR as related to a regression from a prior release. label Sep 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. area/kubelet area/test cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/bug Categorizes issue or PR as related to a bug. 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. sig/node Categorizes an issue or PR as relevant to SIG Node. sig/testing Categorizes an issue or PR as relevant to SIG Testing. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants