website
website copied to clipboard
KEP 4960: Container Stop Signals
Description
Docs for KEP 4960: Container Stop Signals.
Related PRs
- Enhancements PR: https://github.com/kubernetes/enhancements/pull/5122
Issue
Closes: nil, part of https://github.com/kubernetes/enhancements/issues/4960
Deploy Preview for kubernetes-io-vnext-staging processing.
| Name | Link |
|---|---|
| Latest commit | ba588e909725f8ce33aa036a377a4f931c0ffe39 |
| Latest deploy log | https://app.netlify.com/sites/kubernetes-io-vnext-staging/deploys/67f46e36e8d4c6000868baa9 |
Pull request preview available for checking
Built without sensitive environment variables
| Name | Link |
|---|---|
| Latest commit | 5ae90290e27b10a0f8ff9b4b459f97718635746b |
| Latest deploy log | https://app.netlify.com/sites/kubernetes-io-main-staging/deploys/67b8c97812e525000814ccb1 |
| Deploy Preview | https://deploy-preview-49857--kubernetes-io-main-staging.netlify.app |
| Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
Pull request preview available for checking
| Name | Link |
|---|---|
| Latest commit | ba588e909725f8ce33aa036a377a4f931c0ffe39 |
| Latest deploy log | https://app.netlify.com/sites/kubernetes-io-main-staging/deploys/67f46e3683db830008800321 |
| Deploy Preview | https://deploy-preview-49857--kubernetes-io-main-staging.netlify.app |
| Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
The route I recommend is (still):
…add a new detail within https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#pod-termination
Mention that even if you don't specify a stop signal within the Pod manifest:
the container runtime attempts to signal graceful termination
the signalling mechanism is OS-dependent
and then, do mention that you can customise the signal for Linux Pods, by adding a
StopSignalentry withinlifecycle:
@sreeram-venkitesh there's pending feedback; would you be willing to revise this PR based on that feedback?
@sftim @lmktfy Please take a look if the changes are in the right direction. The docs itself might need more wordsmithing.
Hello @sreeram-venkitesh , :wave:! I'm reaching out from the Docs team. Just checking in as we approach Docs Freeze on 8th April, 2025 18:00 PDT. This documentation appears to still be under review. To meet the Docs Freeze, this PR must have a technical review as well as lgtm and approve labels applied, without any unaddressed comments or concerns from SIG Docs. The status of this enhancement is marked as at risk for docs freeze. Thank you!
/approve
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: tengqm
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~content/en/docs/OWNERS~~ [tengqm]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
@haircommander This PR could use an lgtm. Thanks!
/lgtm
LGTM label has been added.