-
Couldn't load subscription status.
- Fork 2.8k
Closed
Labels
Good First IssueThis issue would be a good issue for a first time contributor to undertake.This issue would be a good issue for a first time contributor to undertake.kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.kubelocked - please file new issue/PRAssist humans wanting to comment on an old issue or PR with locked comments.Assist humans wanting to comment on an old issue or PR with locked comments.
Description
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.
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.
apiVersion: v1
kind: Pod
metadata:
name: nginx
spec:
containers:
- name: nginx
image: nginx:1.14.2
lifecycle:
stopSignal: SIGUSR1Have 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.
Metadata
Metadata
Assignees
Labels
Good First IssueThis issue would be a good issue for a first time contributor to undertake.This issue would be a good issue for a first time contributor to undertake.kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.kubelocked - please file new issue/PRAssist humans wanting to comment on an old issue or PR with locked comments.Assist humans wanting to comment on an old issue or PR with locked comments.