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
Re-enable Kubelet Pod Readiness Probes on Termination and Pod probes should be handled by pod worker #110191
Re-enable Kubelet Pod Readiness Probes on Termination and Pod probes should be handled by pod worker #110191
Conversation
5040a2e
to
0d29ef4
Compare
/test pull-kubernetes-node-crio-e2e |
0d29ef4
to
8783744
Compare
cc @aojea |
fdf99b1
to
de7fa7b
Compare
/priority important-soon |
@bobbypage Thank you for the review. I updated the tests to the constants you references and added the gomega.Consistently tweak. I removed the graceperiod optimization since I do not know of any limitations to it. |
Thanks for all the fixes and updates! /lgtm |
/assign @mrunalp |
/assign @aojea and @SergeyKanzhelev |
@rphillips: GitHub didn't allow me to assign the following users: and. Note that only kubernetes members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. In response to this:
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. |
/approve Thank you very much |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aojea, mrunalp, rphillips The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
…1-upstream-release-1.24 Automated cherry pick of #110191: kubelet: Pod probes should be handled by pod worker
…1-upstream-release-1.22 Automated cherry pick of #110191: kubelet: Pod probes should be handled by pod worker
…1-upstream-release-1.23 Automated cherry pick of #110191: kubelet: Pod probes should be handled by pod worker
What type of PR is this?
/kind bug
/kind regression
What this PR does / why we need it:
This PR builds off of @smarterclayton 's #107893 PR to fix
kubelet: Pod probes should be handled by pod worker
. The pod refactor in 2021 disabled all probes on pod deletion. @deads2k also reported to me an issue where Pods were failing to report readiness status on termination. Readiness probes are important for controllers and load balancers to know when to take a pod out of service. Not reporting readiness can cause a load balancer (or controller) to react slower to a terminating pod producing 500s and other ill effects. This PR now reports the correct readiness status during termination.#107893 needed a test case, which this PR adds.
Which issue(s) this PR fixes:
Fixes #110309
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: