-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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
Document graceful termination #14713
Comments
/kind feature |
Hello @sftim I will work on this issue and submit the PR for the same |
Perfect timing, there was just a lengthy debate on Twitter on the subject and I was about to file a PR as well. Happy to review if @SupriyaSirbi is already working on it. |
/priority backlog |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle rotten |
Related: issue #22391 |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
/language en |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
Rotten issues close after 30d of inactivity. Send feedback to sig-contributor-experience at kubernetes/community. |
@fejta-bot: 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. |
I think https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#pod-termination covers this. |
This is a Feature Request
What would you like to be added
Add a concept-level guide that explain the motivation and effect of graceful termination in Kubernetes.
https://kubernetes.io/docs/concepts/workloads/pods/pod/#termination-of-pods talks about termination specifically from a Pod perspective, but what about for Endpoints and Services that reference the terminating Pod? The concept of a graceful cleanup covers more than just containers.
Why is this needed
Cluster operators want to provide a smooth experience for their end users and to understand the design elements and trade-offs that are involved in delivering that.
Comments
A couple of external pages that cover this:
The text was updated successfully, but these errors were encountered: