-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Add pod-startup liveness-probe holdoff for slow-starting pods #950
Comments
/sig node |
/assign @derekwaynecarr |
/kind api-change |
/milestone v1.15 |
@matthyx: You must be a member of the kubernetes/kubernetes-milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your and have them propose you as an additional delegate for this responsibility. 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. |
/stage alpha |
@kacole2 the feature is implemented in this PR: kubernetes/kubernetes#71449 |
@matthyx Kubernetes 1.15 Enhancement Freeze is 4/30/2019. To be included in the Kubernetes 1.15 milestone, KEPs are required to be in an "Implementable" state with proper test plans and graduation criteria. Please submit any PRs needed to make this KEP adhere to inclusion criteria. If this will slip from the 1.15 milestone, please let us know so we can make appropriate tracking changes. |
Hi Bob! |
@mrbobbytables I haven't heard of them during the night... not sure we'll meet the deadline :-( |
@mrbobbytables I have the support of @thockin for this KEP, can we maintain it in 1.15? |
@matthyx Enhancement Freeze for Kubernetes 1.15 has passed and this unfortunately did not meet the deadline. It's being removed from the 1.15 milestone and the tracking sheet, but it looks like you're already on track to get an Enhancement Exception in. 👍 Thanks for being on point about it :) |
/milestone v1.15 |
Sure. /milestone v1.20 |
Glad to hear this |
@qixiaobo: Reiterating the mentions to trigger a notification: 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. |
Hi @matthyx ! Enhancements Lead here, do you still intend to go GA in 1.20? Thanks! |
I actually did already with this PR: kubernetes/kubernetes#94160 |
@matthyx Perfect thank you for the update! |
Also just as a reminder once this feature totally complete and all of your PRs are merged, please update the kep to have a status of implemented: https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/20190221-livenessprobe-holdoff.md |
sure! |
Hi @matthyx 👋! I'm one of the Enhancement shadows for the 1.20 release cycle. Not exactly relevant to this KEP since it's almost completed, but the Enhancement freeze is on the 6th of Oct. It looks like one of the last things to do is to get the following PR (#1988) merged to move this KEP to Thanks! |
Keeping this open for tracking until we close the milestone :) |
Hello, 1.21 Enhancement lead here. /close |
@annajung: Closing this issue. 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. |
Thanks @annajung ! |
Enhancement Description
initializationFailureThreshold
to probes allowing a greater number of failures during the initial start of the container.The text was updated successfully, but these errors were encountered: