Automated cherry pick of #110256: kubelet: Mark ready condition as false explicitly for terminal pods#110480
Conversation
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>
|
Cherrypick was not fully clean - the only manual conflict was on the e2e test update which required updating the go imports. |
|
/triage accepted |
|
/retest |
810338e to
b23c229
Compare
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>
b23c229 to
772494d
Compare
|
/lgtm |
|
Unit tests failed Same as flaky test report - #106663. Fixed in #107443, but it was not cherrypicked to 1.23. /retest |
|
/approve |
|
[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 DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
ping @kubernetes/release-managers for cherrypick approvals. Thank you! |
|
Thanks @bobbypage ! |
Cherry pick of #110256 on release-1.23.
#110256: kubelet: Mark ready condition as false explicitly for terminal pods
For details on the cherry pick process, see the cherry pick requests page.