Skip to content

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.

Sign up for GitHub

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

Clear current search query, filters, and sorts
10 Open 518 Closed
10 Open 518 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Cannot drain node with pod with more than one Pod Disruption Budget area/usability kind/bug Categorizes issue or PR as related to a bug. 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. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/apps Categorizes an issue or PR as relevant to SIG Apps.
#75957 opened Apr 1, 2019 by yaseenhamdulay
2
@mortent
44
StatefulSet numbering offset area/stateful-apps area/usability 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/apps Categorizes an issue or PR as relevant to SIG Apps.
#48466 opened Jul 4, 2017 by CallMeFoxie
10
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
14
kubectl logs should *not* fail while a pod is being started, because it makes for a terrible initial experience area/kubectl area/usability 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/cli Categorizes an issue or PR as relevant to SIG CLI. sig/node Categorizes an issue or PR as relevant to SIG Node.
#28746 opened Jul 11, 2016 by smarterclayton
@mfojtik @avinashupadhya99
30
pod status does not reflect 'Reason' codes for failures that one sees when doing kubectl describe pod <podname> area/kubectl area/reliability area/usability 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/cli Categorizes an issue or PR as relevant to SIG CLI. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling.
#25160 opened May 4, 2016 by buildlackey
10
kubectl should suggest next kubectl commands area/kubectl area/usability 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/cli Categorizes an issue or PR as relevant to SIG CLI.
#19736 opened Jan 16, 2016 by erictune
15
Efficient lookup by label selection, reverse label selection, uid, and IP addresses area/api Indicates an issue on api area. area/usability 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/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/scalability Categorizes an issue or PR as relevant to SIG Scalability.
#4817 opened Feb 25, 2015 by simon3z
20
REST api - 'kind' property not always exists on entities area/api Indicates an issue on api area. area/usability 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/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. triage/accepted Indicates an issue or PR is ready to be actively worked on.
#3030 opened Dec 18, 2014 by abonas
2
@seans3 @Jefftree @leilajal
38
Make deleted objects available from API for some time. area/api Indicates an issue on api area. area/etcd area/usability 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/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/etcd Categorizes an issue or PR as relevant to SIG Etcd.
#1468 opened Sep 26, 2014 by erictune
20
Generic field selectors area/api Indicates an issue on api area. area/usability 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/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery.
#1362 opened Sep 18, 2014 by lavalamp
27
ProTip! Adding no:label will show everything without a label.