You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The kubernetes API is getting a field for stop signals added for version 1.33 set to be released in April. This means that the --stop-signal flag can be supported in Kube pod definitions, currently it can only be specified in the CLI or in quadlets.
Feature request description
The kubernetes API is getting a field for stop signals added for version 1.33 set to be released in April. This means that the --stop-signal flag can be supported in Kube pod definitions, currently it can only be specified in the CLI or in quadlets.
kubernetes/enhancements#4960
Suggest potential solution
Being able to pass a stop signal for containers in the same way as in the Kubernetes API, by adding the field in the Lifecycle field of Container.
Have you considered any alternatives?
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: