-
Notifications
You must be signed in to change notification settings - Fork 40.1k
Issues: kubernetes/kubernetes
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Pod will be created again and again when we have not enough cpu.
area/app-lifecycle
area/kubectl
area/kubelet
area/pod-lifecycle
Issues or PRs related to Pod lifecycle
area/reliability
area/usability
area/workload-api/deployment
area/workload-api/replicaset
sig/apps
Categorizes an issue or PR as relevant to SIG Apps.
sig/cli
Categorizes an issue or PR as relevant to SIG CLI.
sig/node
Categorizes an issue or PR as relevant to SIG Node.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
#38806
opened Dec 15, 2016 by
aoxn
Add support for custom stop signal to send to containers
area/api
Indicates an issue on api area.
area/kubelet
area/pod-lifecycle
Issues or PRs related to Pod lifecycle
kind/feature
Categorizes issue or PR as related to a new feature.
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
sig/node
Categorizes an issue or PR as relevant to SIG Node.
#30051
opened Aug 4, 2016 by
thockin
Static pod Lifecycle Formalization (was: Decide fate of mirror pods)
area/pod-lifecycle
Issues or PRs related to Pod lifecycle
kind/feature
Categorizes issue or PR as related to a new feature.
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
priority/backlog
Higher priority than priority/awaiting-more-evidence.
sig/node
Categorizes an issue or PR as relevant to SIG Node.
#16627
opened Oct 30, 2015 by
yujuhong
kubelet should treat each pod source independently
area/pod-lifecycle
Issues or PRs related to Pod lifecycle
kind/feature
Categorizes issue or PR as related to a new feature.
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
priority/backlog
Higher priority than priority/awaiting-more-evidence.
sig/node
Categorizes an issue or PR as relevant to SIG Node.
#15195
opened Oct 6, 2015 by
yujuhong
Pod lifecycle checkpointing
area/pod-lifecycle
Issues or PRs related to Pod lifecycle
kind/feature
Categorizes issue or PR as related to a new feature.
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
sig/node
Categorizes an issue or PR as relevant to SIG Node.
triage/needs-information
Indicates an issue needs more information in order to work on it.
#3949
opened Jan 29, 2015 by
bgrant0607
ProTip!
Find all open issues with in progress development work with linked:pr.