-
Notifications
You must be signed in to change notification settings - Fork 38.6k
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
ProbeTerminationGracePeriod promote to GA #114307
ProbeTerminationGracePeriod promote to GA #114307
Conversation
Please note that we're already in Test Freeze for the Fast forwards are scheduled to happen every 6 hours, whereas the most recent run was: Tue Dec 6 09:53:09 UTC 2022. |
/sig node |
ccb7913
to
4258a0e
Compare
pull-kubernetes-node-e2e-containerd seems to be |
/test pull-kubernetes-node-e2e-containerd |
Let's make sure the KEP is approved for 1.27 to go to GA and passed the PRR. Also, is there any tests that we need to promote to conformance with this change? |
Suggestion for changelog entry: Graduate the `ProbeTerminationGracePeriod` feature gate to GA |
2274c69
to
14ed547
Compare
14ed547
to
83d0fc9
Compare
/priority important-soon |
eb0bf92
to
c01612a
Compare
oh, we missed this for 1.27? I thought it is done. Can you also send the update for k/enhancements PR with the milestone update? |
c01612a
to
ae08fe1
Compare
/retest |
KEP is merged. |
LGTM label has been added. Git tree hash: aad7496e760018539ee9b2c2b662b9b2fae1f470
|
@rphillips two things to follow up if needed
Gonna approve this for now, please submit a follow up PRs if needed. /approve |
/assign @thockin (need approvals for some directories that i don't have karma on) |
@liggitt @smarterclayton could you approve for the top level directories? |
/approve for API package updates |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dims, liggitt, 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 |
I guess this may be related to this regression. |
if !utilfeature.DefaultFeatureGate.Enabled(features.ProbeTerminationGracePeriod) && !probeGracePeriodInUse(oldPodSpec) { | ||
if !probeGracePeriodInUse(oldPodSpec) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is the problem.
We should never drop terminationGracePeriodSeconds of a probe.
I'll propose a fix for this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you are correct... this block should have gone away entirely
Changelog suggestion Graduated support for probe-level `terminationGracePeriodSeconds` to general availability. We graduate features; feature gates change as part of this. |
What type of PR is this?
/kind feature
What this PR does / why we need it:
#99375 introduced Probe-level terminationGracePeriodSeconds to provide a timeout for Liveness probes. The feature was initially targeted for GA in 1.25, but was missed.
The PR promotes ProbeTerminationGracePeriod to GA in 1.28 with a removal of the feature gate in 1.29.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: