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
22 Open 405 Closed
22 Open 405 Closed
Author
Filter by author
Label
Filter by label
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Milestones
Filter by milestone
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

In place pod resizing should be designed into the kubelet config state loop, not alongside it kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/node Categorizes an issue or PR as relevant to SIG Node.
#116971 opened Mar 28, 2023 by smarterclayton
@vinaykul
10
Components in the kubelet are incorrectly pulling state from "desired" instead of the pod worker's "actual" kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/node Categorizes an issue or PR as relevant to SIG Node.
#116970 opened Mar 28, 2023 by smarterclayton
@smarterclayton
6
Pod status updates take longer to propagate to the API than necessary kind/bug Categorizes issue or PR as related to a bug. 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. sig/scalability Categorizes an issue or PR as relevant to SIG Scalability.
#116617 opened Mar 14, 2023 by smarterclayton
9
Static pods that are rejected by admission should be periodically retried / preempt non-static pods kind/feature Categorizes issue or PR as related to a new feature. 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.
#116484 opened Mar 10, 2023 by smarterclayton
@smarterclayton
4
A restart Never static pod does not recreate mirror pod when it is deleted kind/bug Categorizes issue or PR as related to a bug. kind/documentation Categorizes issue or PR as related to documentation. 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.
#116483 opened Mar 10, 2023 by smarterclayton
@smarterclayton
6
Kubelet should react more quickly to pod lifecycle transitions 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.
#113606 opened Nov 3, 2022 by smarterclayton
1
@smarterclayton
7
kubelet does not restart static pods when apiserver is down kind/bug Categorizes issue or PR as related to a bug. 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/backlog Higher priority than priority/awaiting-more-evidence. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. sig/node Categorizes an issue or PR as relevant to SIG Node.
#105543 opened Oct 7, 2021 by smarterclayton
1
@smarterclayton
18
Pods that are terminating but force deleted must still be accounted for in admission kind/bug Categorizes issue or PR as related to a bug. 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.
#104824 opened Sep 7, 2021 by smarterclayton
@smarterclayton
13
Steady state kubelet CPU usage is high due to excessive allocation in prometheus scraping of cadvisor kind/bug Categorizes issue or PR as related to a bug. 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/backlog Higher priority than priority/awaiting-more-evidence. sig/node Categorizes an issue or PR as relevant to SIG Node.
#104459 opened Aug 19, 2021 by smarterclayton
1
@ehashman
40
Kubelet has no rate controls after a pod was evicted kind/bug Categorizes issue or PR as related to a bug. 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. triage/accepted Indicates an issue or PR is ready to be actively worked on.
#89068 opened Mar 11, 2020 by smarterclayton
7
Stateful set controller does not appear to backoff when pods are evicted kind/bug Categorizes issue or PR as related to a bug. 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/apps Categorizes an issue or PR as relevant to SIG Apps.
#89067 opened Mar 11, 2020 by smarterclayton
1
@gongguan @kow3ns
13
Forbidden error returned from dynamic client is not typed correctly area/client-libraries help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery.
#68785 opened Sep 18, 2018 by smarterclayton
1
@sttts @roycaihw
@deads2k @sxllwx
7
VMWare library dependency contributes roughly ~22M to total hyperkube binary size area/code-organization Issues or PRs related to kubernetes code organization area/provider/vmware Issues or PRs related to vmware provider 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-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider.
#66321 opened Jul 18, 2018 by smarterclayton
@dougm
38
Kubernetes is vulnerable to stale reads, violating critical pod safety guarantees kind/bug Categorizes issue or PR as related to a bug. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/apps Categorizes an issue or PR as relevant to SIG Apps. sig/scalability Categorizes an issue or PR as relevant to SIG Scalability.
#59848 opened Feb 14, 2018 by smarterclayton
@jpbetz
89
All etcd3 watches close after 10m or so kind/bug Categorizes issue or PR as related to a bug. 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/scalability Categorizes an issue or PR as relevant to SIG Scalability.
#54974 opened Nov 2, 2017 by smarterclayton
19
406 unacceptable error for POSTing without a content type to the LIST endpoint is wrong lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery.
#46895 opened Jun 3, 2017 by smarterclayton
@smarterclayton
8
Remove client side validation in kubectl lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/cli Categorizes an issue or PR as relevant to SIG CLI.
#39434 opened Jan 4, 2017 by smarterclayton
26
Proposal: Establish guidelines for where commands should go area/code-organization Issues or PRs related to kubernetes code organization area/kubectl 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/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. sig/cli Categorizes an issue or PR as relevant to SIG CLI.
#35226 opened Oct 20, 2016 by smarterclayton
@monopole
20
openapi static init is 50% of startup time for binary that links to it area/apiserver lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery.
#32726 opened Sep 14, 2016 by smarterclayton
9
kubeconfig lock files change behavior of KUBECONFIG area/kubectl lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery.
#32606 opened Sep 13, 2016 by smarterclayton v1.4-nonblocking
1
9
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
Proposal: Long term evolution of runtime.Scheme / conversion.Scheme area/api Indicates an issue on api area. area/apiserver 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/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery.
#7111 opened Apr 21, 2015 by smarterclayton next-candidate
@smarterclayton
41
ProTip! Add no:assignee to see everything that’s not assigned.