KEP-4960keps/sig-node/4960-container-stop-signals
Container Stop Signals
Container runtimes let you define a STOPSIGNAL to let your container images change which signal is delivered to kill the container. Currently you can only configure this by defining STOPSIGNAL in the container image definition file before you build the image. This becomes difficult to change when you’re using prebuilt images. Kubernetes has no equivalent for… Full summary
Container runtimes let you define a STOPSIGNAL to let your container images change which signal is delivered to kill the container. Currently you can only configure this by defining STOPSIGNAL in the container image definition file before you build the image. This becomes difficult to change when you’re using prebuilt images. Kubernetes has no equivalent for STOPSIGNAL as part of Pod or Container APIs. This KEP proposes to add support to configure custom stop signals for containers from the ContainerSpec.
Facts
- Authors
- @sreeram-venkitesh
- Approvers
- @mrunalp@sergeykanzhelev
- Tracking issue
- #4960(opens GitHub in a new tab) openmilestone v1.38sig/nodestage/betatracked/yeslead-opted-in
- Milestones
- alpha v1.33beta v1.38
- Participating SIGs
- sig-windows
- Feature gates
- ContainerStopSignals
- Created / last updated
- 2025-02-01 / none
Loading decisions and status history