issue_owner_repo listlengths 2 2 | issue_body stringlengths 0 261k ⌀ | issue_title stringlengths 1 925 | issue_comments_url stringlengths 56 81 | issue_comments_count int64 0 2.5k | issue_created_at stringlengths 20 20 | issue_updated_at stringlengths 20 20 | issue_html_url stringlengths 37 62 | issue_github_id int64 387k 2.91B | issue_number int64 1 131k |
|---|---|---|---|---|---|---|---|---|---|
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about flaky tests or jobs (pass or fail with no underlying change in code) in Kubernetes CI -->
#### Which jobs are flaking:
ci-kubernetes-kind-e2e-parallel
#### Which test(s) are flaking:
[sig-network] HostPort validates that there is no conflict betwee... | [Flaky Test] [sig-network] HostPort validates that there is no conflict between pods with same hostPort but different hostIP and protocol [LinuxOnly] [Conformance] | https://api.github.com/repos/kubernetes/kubernetes/issues/100220/comments | 18 | 2021-03-13T23:44:04Z | 2021-05-25T09:29:08Z | https://github.com/kubernetes/kubernetes/issues/100220 | 831,024,490 | 100,220 |
[
"kubernetes",
"kubernetes"
] | From comment https://github.com/kubernetes/kubernetes/issues/100047#issuecomment-796980046
syncPod is waiting for volumes to finish mounting. before calling WaitForAttachAndMount, it checks if the pod is terminated before entering. However, if the pod is terminated after that check, then we are stuck in in WaitForAt... | WaitForAttachAndMount might delay pod terminating. | https://api.github.com/repos/kubernetes/kubernetes/issues/100219/comments | 31 | 2021-03-13T20:42:40Z | 2023-07-05T14:02:44Z | https://github.com/kubernetes/kubernetes/issues/100219 | 830,990,381 | 100,219 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
When adding 2 cidrs to the ipBlock in a network policy, it is accepted as valid when it's clearly not.
#### What you expected to happen:
See an error stating the format is invalid.
#### How to reproduce it (as minimally and precisely as possible):
1. Create a default network policy to block... | Network Policy accepts 2 cidrs in one ipBlock | https://api.github.com/repos/kubernetes/kubernetes/issues/100213/comments | 26 | 2021-03-13T11:33:42Z | 2021-03-31T18:19:30Z | https://github.com/kubernetes/kubernetes/issues/100213 | 830,879,534 | 100,213 |
[
"kubernetes",
"kubernetes"
] | ### issue:
RTSP protocol uses random udp ports to push data every frame.
If I use single port TCP connection it works, but TCP has its own delay. Whenever I try to stream data using UDP in a pod, k8s does not allow udp access.
RTSP-UDP initially connects to 554 TCP port, and gets assigned to an UDP port between ... | Kubernetes blocking UDP requests | https://api.github.com/repos/kubernetes/kubernetes/issues/100212/comments | 26 | 2021-03-13T11:30:43Z | 2024-09-29T17:33:08Z | https://github.com/kubernetes/kubernetes/issues/100212 | 830,879,055 | 100,212 |
[
"kubernetes",
"kubernetes"
] | To CPU Management function in kubelet:
I hope to get all pod’s resource info by “/var/lib/kubelet/pod-resources/kubelet.sock”
in my test:
numa info: one numa node has 0-7 cpus

, require cumbersome/unintuitive steps (changing scale) or weird hacks (i.e. issuing an exec followed by a kill command, or in our cas... | Add ability to restart individual pods (i.e., kubectl restart pod <pod> -n <namespace>) | https://api.github.com/repos/kubernetes/kubernetes/issues/100209/comments | 4 | 2021-03-13T04:20:54Z | 2021-03-13T04:31:23Z | https://github.com/kubernetes/kubernetes/issues/100209 | 830,802,158 | 100,209 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
#### What happened:
We've obse... | exec probes that exceed timeout always succeed when using ExecProbeTimeout=false | https://api.github.com/repos/kubernetes/kubernetes/issues/100198/comments | 2 | 2021-03-12T23:13:08Z | 2021-04-11T05:55:59Z | https://github.com/kubernetes/kubernetes/issues/100198 | 830,639,907 | 100,198 |
[
"kubernetes",
"kubernetes"
] | In VMware Tanzu Supervisor Cluster k8s setup, we observed that the AdmissionWebhook tests fail intermittently while updating the namespace with the error: "the object has been modified; please apply your changes to the latest version and try again". This is because the update conflicts with an update being performed by... | namespace update fails in AdmissionWebhook e2e tests | https://api.github.com/repos/kubernetes/kubernetes/issues/100197/comments | 2 | 2021-03-12T23:04:26Z | 2021-03-16T20:29:05Z | https://github.com/kubernetes/kubernetes/issues/100197 | 830,628,712 | 100,197 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about flaky tests or jobs (pass or fail with no underlying change in code) in Kubernetes CI -->
#### Which jobs are flaking:
ci-kubernetes-e2e-ubuntu-gce
#### Which test(s) are flaking:
[sig-storage] Subpath Container restart should verify that container... | [Flaky Test] [sig-storage] Subpath Container restart should verify that container can restart successfully after configmaps modified | https://api.github.com/repos/kubernetes/kubernetes/issues/100194/comments | 9 | 2021-03-12T21:21:26Z | 2021-04-22T04:12:47Z | https://github.com/kubernetes/kubernetes/issues/100194 | 830,481,112 | 100,194 |
[
"kubernetes",
"kubernetes"
] | This is discovered through flaky test issue #100047
The test first create a deployment with 2 replicas using Anghost image. And then the deployment is patched with a different image Pause and replica number changed from 2 to 1. But the following happens
1. the new pod comes up with the new image fails to start s... | Deployment ReadyReplica status does not reflect real state | https://api.github.com/repos/kubernetes/kubernetes/issues/100192/comments | 13 | 2021-03-12T18:51:20Z | 2021-08-21T23:25:52Z | https://github.com/kubernetes/kubernetes/issues/100192 | 830,363,553 | 100,192 |
[
"kubernetes",
"kubernetes"
] | When feature gates are disabled, fields should not be rendered when storing or when returning objects from API.
For this reason, feature gate should control defaulting and the fields should be pointers.
This was missed during api-review for `.spec.suspend` and `.spec.completionMode`
/sig apps | Job suspend and completionMode fields should be left empty when features are disabled | https://api.github.com/repos/kubernetes/kubernetes/issues/100187/comments | 3 | 2021-03-12T15:47:52Z | 2021-03-15T14:35:07Z | https://github.com/kubernetes/kubernetes/issues/100187 | 830,242,486 | 100,187 |
[
"kubernetes",
"kubernetes"
] | Original discussion was here https://github.com/kubernetes/website/pull/26963 but I created this new issue because it has nothing to do with the website/docs.
@bobbypage here is the new issue, thanks for your help!
#### What happened:
Whit GracefulNodeShutdown enabled when I stop a node pods on it get deleted bu... | graceful node shutdown restarts pods during shutdown | https://api.github.com/repos/kubernetes/kubernetes/issues/100184/comments | 5 | 2021-03-12T12:45:35Z | 2021-03-13T13:27:33Z | https://github.com/kubernetes/kubernetes/issues/100184 | 830,084,693 | 100,184 |
[
"kubernetes",
"kubernetes"
] | #### How to reproduce it (as minimally and precisely as possible):
1. Run a pod that uses a CSI volume that supports NodeStage (such as Ceph RBD)
2. Delete the pod
3. The CSI driver times out when processing NodeUnstage call. It is un-staging the volume in the background and eventually succeeds. (Ceph RBD talks to... | NodeStage is not called after NodeUnstage error | https://api.github.com/repos/kubernetes/kubernetes/issues/100182/comments | 5 | 2021-03-12T11:34:51Z | 2021-11-18T09:23:07Z | https://github.com/kubernetes/kubernetes/issues/100182 | 830,031,643 | 100,182 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
#### What happened:
1. Kubelet s... | Kubelet will not work if a nfs volume cannot be accessed | https://api.github.com/repos/kubernetes/kubernetes/issues/100178/comments | 6 | 2021-03-12T09:28:10Z | 2021-06-25T05:12:29Z | https://github.com/kubernetes/kubernetes/issues/100178 | 829,925,165 | 100,178 |
[
"kubernetes",
"kubernetes"
] | <!-- Feature requests are unlikely to make progress as an issue.
Instead, please suggest enhancements by engaging with SIGs on slack and mailing lists.
A proposal that works through the design along with the implications of the change can be opened as a KEP:
https://git.k8s.io/enhancements/keps#kubernetes-enhanc... | Kubedm supports k8s component to customize image name or path to pull images. | https://api.github.com/repos/kubernetes/kubernetes/issues/100174/comments | 15 | 2021-03-12T07:52:03Z | 2021-03-16T02:04:42Z | https://github.com/kubernetes/kubernetes/issues/100174 | 829,851,822 | 100,174 |
[
"kubernetes",
"kubernetes"
] | Because the function `NewSchedulerCommand ` in the path `cmd/kube-scheduler/app/server.go` has no input argument, I can't pass the customized scheduling plugin to it. | How to use Scheduling Framework in v1.15.3? | https://api.github.com/repos/kubernetes/kubernetes/issues/100170/comments | 3 | 2021-03-12T06:49:24Z | 2021-03-15T17:22:21Z | https://github.com/kubernetes/kubernetes/issues/100170 | 829,812,962 | 100,170 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
Nodes are frequently NotReady
#### Environment:
- Kubernetes version (use `kubectl version`): v1.18.1
- OS (e.g: `cat /etc/os-release`): CentOS Linux 7 (Core)
- Kernel (e.g. `uname -a`):Linux njscsjfwzx2 3.10.0-1127.19.1.el7.x86_64 #1 SMP Tue Aug 25 17:23:54 UTC 2020 x86_64 x86_64 x86_64 GNU/... | Nodes are frequently NotReady | https://api.github.com/repos/kubernetes/kubernetes/issues/100166/comments | 7 | 2021-03-12T03:25:47Z | 2023-07-20T10:35:54Z | https://github.com/kubernetes/kubernetes/issues/100166 | 829,722,290 | 100,166 |
[
"kubernetes",
"kubernetes"
] | #### What would you like to be added:
Start multiple kubemark process in one pod.
#### Why is this needed:
As we plan to simulate a cluster with more than 20k nodes, 1:1 hollow-node to pod mapping require us to create 20k pods . By default, there's a 110 pod limit per node, this required more than 180 machines t... | Single hollow-node per Pod setting is not resource efficient | https://api.github.com/repos/kubernetes/kubernetes/issues/100159/comments | 7 | 2021-03-12T01:46:31Z | 2021-08-09T02:35:29Z | https://github.com/kubernetes/kubernetes/issues/100159 | 829,677,529 | 100,159 |
[
"kubernetes",
"kubernetes"
] | #### What would you like to be added:
A kubernetes cluster is normally constructed from a variety of machine templates. Different instance groups may have different CPU, memory capacity. They may be equipped with specialized accelerators, network devices. I think we should have an extensible way for users to custom ... | Expose more node level configurations to customize hollow-node | https://api.github.com/repos/kubernetes/kubernetes/issues/100158/comments | 3 | 2021-03-12T01:43:41Z | 2021-04-09T03:29:13Z | https://github.com/kubernetes/kubernetes/issues/100158 | 829,676,335 | 100,158 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
#### What happened:
When `klog... | [Structured Logging] when klog is passed nil, it causes components to panic while logging | https://api.github.com/repos/kubernetes/kubernetes/issues/100155/comments | 12 | 2021-03-12T00:22:39Z | 2021-03-13T02:01:16Z | https://github.com/kubernetes/kubernetes/issues/100155 | 829,638,280 | 100,155 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/
```
--storage-backend string
--
| The storage backend for persistence. Options: 'etcd3' (default).
```
Although it says in the doc that `etcd3` is the default value of storage-backend flag in apiserver. But... | Show storage-backend default value in kube-apiserver | https://api.github.com/repos/kubernetes/kubernetes/issues/100153/comments | 9 | 2021-03-11T23:19:01Z | 2021-08-16T21:34:26Z | https://github.com/kubernetes/kubernetes/issues/100153 | 829,600,852 | 100,153 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
When starting the Kubelet with ```KUBELET_FLAGS=--logging-format=json hack/local-up-cluster.sh```, the Kubelet begins with unstructured logging and then transitions to structured logging:
```
Flag --chaos-chance has been deprecated, will be removed in a future version.
Flag --cloud-provide... | Kubelet logs start with unstructured logs then transition to structured logs | https://api.github.com/repos/kubernetes/kubernetes/issues/100152/comments | 22 | 2021-03-11T23:14:30Z | 2021-11-18T09:53:02Z | https://github.com/kubernetes/kubernetes/issues/100152 | 829,598,543 | 100,152 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
When trying to update the .spec.updateStrategy.type of a StatefulSet object to "OnDelete" it fails if it was not previously set (so default value _{"type": "RollingUpdate", "rollingUpdate": { "partition": 0} }_ applies).
Following message is printed by the failing kubectl command:
_The Stateful... | Error when trying to update StatefulSet updateStrategy.type to "OnDelete" from default value | https://api.github.com/repos/kubernetes/kubernetes/issues/100151/comments | 14 | 2021-03-11T22:44:11Z | 2021-03-23T21:31:36Z | https://github.com/kubernetes/kubernetes/issues/100151 | 829,581,181 | 100,151 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
the cpumanager e2e tests contain too many assumption about cpu allocation.
TL;DR: cpumanager code *not broken*; tests *not broken*; we should improve to avoid *future possible* false negatives.
The specific case we encountered is: if socket id doesn't match numa cell id, like in this example:... | cpumanager e2e tests contain too many assumption about cpu allocation | https://api.github.com/repos/kubernetes/kubernetes/issues/100145/comments | 22 | 2021-03-11T17:40:01Z | 2025-01-29T16:19:34Z | https://github.com/kubernetes/kubernetes/issues/100145 | 829,373,729 | 100,145 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
#### What happened:
I created a ... | Pods with “hard” podAntiAffinity were scheduled to the same node | https://api.github.com/repos/kubernetes/kubernetes/issues/100140/comments | 11 | 2021-03-11T15:42:18Z | 2021-12-12T04:34:57Z | https://github.com/kubernetes/kubernetes/issues/100140 | 829,272,137 | 100,140 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about flaky tests or jobs (pass or fail with no underlying change in code) in Kubernetes CI -->
#### Which jobs are flaking:
ci-kubernetes-e2e-gci-gce-alpha-features
#### Which test(s) are flaking:
[sig-apps] Daemon set [Serial] should surge pods onto no... | [Flaky Test] [sig-apps] Daemon set [Serial] should surge pods onto nodes when spec was updated and update strategy is RollingUpdate [Feature:DaemonSetUpdateSurge] | https://api.github.com/repos/kubernetes/kubernetes/issues/100138/comments | 14 | 2021-03-11T14:36:59Z | 2021-04-09T20:00:32Z | https://github.com/kubernetes/kubernetes/issues/100138 | 829,212,149 | 100,138 |
[
"kubernetes",
"kubernetes"
] | #### Which jobs are flaking:
ci-kubernetes-e2e-gce-scale-correctness
#### Which test(s) are flaking:
[sig-network] Networking Granular Checks: Services should function for client IP based session affinity: http [LinuxOnly]
#### Testgrid link:
https://testgrid.k8s.io/sig-scalability-gce#gce-master-scale-correct... | [Flaky test] [sig-network] Networking Granular Checks: Services should function for client IP based session affinity: http [LinuxOnly] | https://api.github.com/repos/kubernetes/kubernetes/issues/100135/comments | 3 | 2021-03-11T12:50:11Z | 2021-03-18T23:42:24Z | https://github.com/kubernetes/kubernetes/issues/100135 | 829,121,799 | 100,135 |
[
"kubernetes",
"kubernetes"
] | #### Which jobs are flaking:
ci-kubernetes-e2e-gce-scale-correctness
#### Which test(s) are flaking:
[sig-network] Conntrack should be able to preserve UDP traffic when server pod cycles for a ClusterIP service
#### Testgrid link:
https://testgrid.k8s.io/sig-scalability-gce#gce-master-scale-correctness
####... | [Flaky test] [sig-network] Conntrack should be able to preserve UDP traffic when server pod cycles for a ClusterIP service | https://api.github.com/repos/kubernetes/kubernetes/issues/100134/comments | 7 | 2021-03-11T12:50:04Z | 2021-03-18T23:10:51Z | https://github.com/kubernetes/kubernetes/issues/100134 | 829,121,720 | 100,134 |
[
"kubernetes",
"kubernetes"
] | #### Which jobs are flaking:
ci-kubernetes-e2e-gce-scale-correctness
#### Which test(s) are flaking:
[sig-network] Services should be able to change the type from ExternalName to NodePort [Conformance]
#### Testgrid link:
https://testgrid.k8s.io/sig-scalability-gce#gce-master-scale-correctness
#### Reason f... | [Flaky test] [sig-network] Services should be able to change the type from ExternalName to NodePort [Conformance] | https://api.github.com/repos/kubernetes/kubernetes/issues/100133/comments | 3 | 2021-03-11T12:49:59Z | 2021-05-11T10:25:33Z | https://github.com/kubernetes/kubernetes/issues/100133 | 829,121,649 | 100,133 |
[
"kubernetes",
"kubernetes"
] | #### Which jobs are flaking:
ci-kubernetes-e2e-gce-scale-correctness
#### Which test(s) are flaking:
[sig-network] Services should be able to update service type to NodePort listening on same port number but different protocols
#### Testgrid link:
https://testgrid.k8s.io/sig-scalability-gce#gce-master-scale-co... | [Flaky test] [sig-network] Services should be able to update service type to NodePort listening on same port number but different protocols | https://api.github.com/repos/kubernetes/kubernetes/issues/100132/comments | 6 | 2021-03-11T12:49:53Z | 2021-03-19T00:15:50Z | https://github.com/kubernetes/kubernetes/issues/100132 | 829,121,562 | 100,132 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
#### What happened:
When using t... | kubelet --logging-format flag wrap the description incorrectly | https://api.github.com/repos/kubernetes/kubernetes/issues/100130/comments | 5 | 2021-03-11T12:35:12Z | 2021-03-16T07:05:42Z | https://github.com/kubernetes/kubernetes/issues/100130 | 829,111,032 | 100,130 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI -->
#### Which jobs are failing:
https://prow.k8s.io/job-history/gs/ppc64le-kubernetes/logs/periodic-kubernetes-unit-test-ppc64le
#### Which test(s) are failing:
k8s.io/kubernetes/cmd/genkubedocs
... | Unit Test k8s.io/kubernetes/cmd/genkubedocs fails in ppc64le | https://api.github.com/repos/kubernetes/kubernetes/issues/100127/comments | 17 | 2021-03-11T10:07:04Z | 2021-06-16T07:35:51Z | https://github.com/kubernetes/kubernetes/issues/100127 | 828,997,225 | 100,127 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
#### What happened:
DNS resolu... | DNS resolution failure in Windows Pod | https://api.github.com/repos/kubernetes/kubernetes/issues/100126/comments | 9 | 2021-03-11T09:50:51Z | 2021-03-19T18:02:30Z | https://github.com/kubernetes/kubernetes/issues/100126 | 828,983,230 | 100,126 |
[
"kubernetes",
"kubernetes"
] | Enabling runtime config on E2E node tests #99960 added a new option to the e2e node tests.
However, it seems it wasn't backported and is most likely the reason why `pull-kubernetes-node-e2e` are failing in cherry-picks
> W0311 08:42:07.066] 2021/03/11 08:42:07 process.go:153: Running: go run /go/src/k8s.io/kubern... | pull-kubernetes-node-e2e are failing on release branches | https://api.github.com/repos/kubernetes/kubernetes/issues/100124/comments | 3 | 2021-03-11T09:03:43Z | 2021-03-11T16:39:16Z | https://github.com/kubernetes/kubernetes/issues/100124 | 828,945,498 | 100,124 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
#### What happened:
I restarted ... | CoreDNS is taking 5secs to resolve the name in a POD restart scenario | https://api.github.com/repos/kubernetes/kubernetes/issues/100120/comments | 6 | 2021-03-11T07:52:41Z | 2021-03-15T14:06:07Z | https://github.com/kubernetes/kubernetes/issues/100120 | 828,890,553 | 100,120 |
[
"kubernetes",
"kubernetes"
] | I'm trying to migrate kube-controller-manager to events.k8s.io/v1, but there is a problem...
#### What happened:
I modified node-lifecycle-controller's event recorder using events.k8s.io/v1 version. The following event is generated by node-lifecycle-controller when node '172.11.22.237' is registered.
`Event "172.1... | Events in events.k8s.io/v1 validate failed | https://api.github.com/repos/kubernetes/kubernetes/issues/100119/comments | 11 | 2021-03-11T07:50:46Z | 2022-01-25T14:31:52Z | https://github.com/kubernetes/kubernetes/issues/100119 | 828,888,666 | 100,119 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
#### What happened:
I am running... | Custome Resources are only watched by some of the apiservers | https://api.github.com/repos/kubernetes/kubernetes/issues/100117/comments | 3 | 2021-03-11T07:13:08Z | 2021-03-16T20:29:10Z | https://github.com/kubernetes/kubernetes/issues/100117 | 828,852,379 | 100,117 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about flaky tests or jobs (pass or fail with no underlying change in code) in Kubernetes CI -->
#### Which jobs are flaking:
ci-kubernetes-unit
#### Which test(s) are flaking:
`k8s.io/kubernetes/pkg/registry/core/endpoint/storage.TestWatch`
#### T... | [flaky test] k8s.io/kubernetes/pkg/registry/core/endpoint/storage.TestWatch | https://api.github.com/repos/kubernetes/kubernetes/issues/100112/comments | 13 | 2021-03-11T04:38:16Z | 2021-10-26T13:54:58Z | https://github.com/kubernetes/kubernetes/issues/100112 | 828,719,135 | 100,112 |
[
"kubernetes",
"kubernetes"
] | I am deploying a new cluster based of K8S 1.20.4 and Ubuntu 20.0.4
None of my static pods are getting the default service account mount.
This is for coreDNS but a static pods will not have the mount.
```
{
"Type": "bind",
"Source": "/var/lib/kubelet/pods/3d735801-a925-46f5-81d6... | StaticPod: Missing default serviceaccount mount on Ubuntu 20.0.4 | https://api.github.com/repos/kubernetes/kubernetes/issues/100105/comments | 5 | 2021-03-10T23:11:54Z | 2021-07-08T15:50:31Z | https://github.com/kubernetes/kubernetes/issues/100105 | 828,455,188 | 100,105 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
kube-controller-manager is currently deployed in an active-standby manner. Under this mode, we meet memory issues in large clusters. The problem is it caches many objects which uses too many memories. I am trying to see if it's reasonable to have a native way to split kube-controller-manager into m... | Provides options to shard controllers in kube-controller-manager | https://api.github.com/repos/kubernetes/kubernetes/issues/100102/comments | 2 | 2021-03-10T21:03:32Z | 2021-03-11T01:31:39Z | https://github.com/kubernetes/kubernetes/issues/100102 | 828,331,969 | 100,102 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
#### What happened:
```
$ kubec... | kubectl exec, logs, port-forward command results in 'x509 doesn't contain any IP SANs' error for some nodes | https://api.github.com/repos/kubernetes/kubernetes/issues/100098/comments | 3 | 2021-03-10T19:38:31Z | 2021-03-10T20:30:51Z | https://github.com/kubernetes/kubernetes/issues/100098 | 828,241,910 | 100,098 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about flaky tests or jobs (pass or fail with no underlying change in code) in Kubernetes CI -->
#### Which jobs are flaking:
pull-kubernetes-e2e-azure-file-windows
#### Which test(s) are flaking:
Dynamic Provisioning should create a volume on demand with... | [flaky test]: Dynamic Provisioning should create a volume on demand with useDataPlaneAPI | https://api.github.com/repos/kubernetes/kubernetes/issues/100097/comments | 5 | 2021-03-10T18:52:08Z | 2021-04-06T13:35:21Z | https://github.com/kubernetes/kubernetes/issues/100097 | 828,192,202 | 100,097 |
[
"kubernetes",
"kubernetes"
] | A security issue was discovered in kube-apiserver that could allow node updates to bypass a Validating Admission Webhook. You are only affected by this vulnerability if you run a Validating Admission Webhook for Nodes that denies admission based at least partially on the old state of the Node object.
This issue has ... | CVE-2021-25735: Validating Admission Webhook does not observe some previous fields | https://api.github.com/repos/kubernetes/kubernetes/issues/100096/comments | 6 | 2021-03-10T18:18:01Z | 2021-12-02T22:53:35Z | https://github.com/kubernetes/kubernetes/issues/100096 | 828,149,421 | 100,096 |
[
"kubernetes",
"kubernetes"
] | <!-- Feature requests are unlikely to make progress as an issue.
Instead, please suggest enhancements by engaging with SIGs on slack and mailing lists.
A proposal that works through the design along with the implications of the change can be opened as a KEP:
https://git.k8s.io/enhancements/keps#kubernetes-enhanc... | Add a small random number to PodBackoffDuration | https://api.github.com/repos/kubernetes/kubernetes/issues/100095/comments | 10 | 2021-03-10T18:12:49Z | 2021-08-08T18:35:28Z | https://github.com/kubernetes/kubernetes/issues/100095 | 828,142,653 | 100,095 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
* I got into a situation where the init container image of a pod in a statfulset contains a code that is failing to run successfully.
* I updated the statefulset with an image that should run the init to completion
* The pod is never updated with the new init container. it keeps failing during t... | A pod in a Statefulset is not restarted if its init container is failing | https://api.github.com/repos/kubernetes/kubernetes/issues/100094/comments | 8 | 2021-03-10T17:56:45Z | 2021-08-16T11:22:15Z | https://github.com/kubernetes/kubernetes/issues/100094 | 828,122,194 | 100,094 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
##### Short version
After upgrading our clusters to Kubernetes 1.19, the provisioning of PersistentVolumes started failing with the following Events:
> ProvisioningFailed persistentvolumeclaim/\<namespace-pvc\> Failed to provision volume with StorageClass “\<storage class\>" : quantity 34359738... | Kubernetes fails to allocate PV pretending storage request overflows int64 | https://api.github.com/repos/kubernetes/kubernetes/issues/100091/comments | 6 | 2021-03-10T16:00:11Z | 2021-04-09T00:12:05Z | https://github.com/kubernetes/kubernetes/issues/100091 | 827,961,140 | 100,091 |
[
"kubernetes",
"kubernetes"
] | #### What would you like to be added:
Up to 1.21, that field is immutable. That means in practice, a CSIDriver object has to be deleted and then re-created with a different value instead.
#### Why is this needed:
Mutation via delete/created is unnecessarily complex and as the only consumer of that field (the k... | CSIDriver.StorageCapacity: allow mutating the field | https://api.github.com/repos/kubernetes/kubernetes/issues/100089/comments | 3 | 2021-03-10T15:49:23Z | 2021-08-12T00:05:47Z | https://github.com/kubernetes/kubernetes/issues/100089 | 827,944,458 | 100,089 |
[
"kubernetes",
"kubernetes"
] | _This is probably not a right place to request this, but I didn't find anything on discuss.kubernetes.io or Google._
I have a number of services around kubernetes cluster, that would greatly benefit from original protocol definitions used by kubernetes itself. For example I could have a gRPC handler returning deploy... | Publish kubernetes protocol definitions as .proto files | https://api.github.com/repos/kubernetes/kubernetes/issues/100080/comments | 7 | 2021-03-10T12:27:14Z | 2021-03-10T14:13:04Z | https://github.com/kubernetes/kubernetes/issues/100080 | 827,658,666 | 100,080 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
#### What happened:
#### What ... | A is not grow when B runs. | https://api.github.com/repos/kubernetes/kubernetes/issues/100074/comments | 2 | 2021-03-10T09:37:16Z | 2021-03-10T09:43:15Z | https://github.com/kubernetes/kubernetes/issues/100074 | 827,430,524 | 100,074 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about flaky tests or jobs (pass or fail with no underlying change in code) in Kubernetes CI -->
#### Which jobs are flaking:
- pull-kubernetes-unit
#### Which test(s) are flaking:
- `k8s.io/kubernetes/vendor/k8s.io/apiserver/pkg/admission/plugin/webhook... | [Flaky] k8s.io/apiserver/pkg/admission/plugin/webhook/validating TestValidate | https://api.github.com/repos/kubernetes/kubernetes/issues/100070/comments | 9 | 2021-03-10T09:16:28Z | 2021-03-23T17:46:00Z | https://github.com/kubernetes/kubernetes/issues/100070 | 827,403,462 | 100,070 |
[
"kubernetes",
"kubernetes"
] | <!-- Feature requests are unlikely to make progress as an issue.
Instead, please suggest enhancements by engaging with SIGs on slack and mailing lists.
A proposal that works through the design along with the implications of the change can be opened as a KEP:
https://git.k8s.io/enhancements/keps#kubernetes-enhanc... | Feature: set ignore errors as default for drain,and deprecated flag | https://api.github.com/repos/kubernetes/kubernetes/issues/100052/comments | 9 | 2021-03-10T01:20:47Z | 2021-11-17T06:54:23Z | https://github.com/kubernetes/kubernetes/issues/100052 | 826,903,061 | 100,052 |
[
"kubernetes",
"kubernetes"
] | The following e2e Conformance Tests are showing a similar pattern in the way that they are flaking.
- `should run through the lifecycle of Pods and PodStatus`
- `should test the lifecycle of a ReplicationController`
- `should run the lifecycle of a Deployment`
When the initial pod is scheduled for the test it's... | Pod timeout flakes - "cannot find volume \"kube-api-access-2t44s\" to mount into container" | https://api.github.com/repos/kubernetes/kubernetes/issues/100047/comments | 69 | 2021-03-10T00:36:36Z | 2022-07-21T12:49:54Z | https://github.com/kubernetes/kubernetes/issues/100047 | 826,860,556 | 100,047 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
go-openapi/validate library has a bug that gets exposed with Go 1.16 compiler. Here is the upstream issue: https://github.com/go-openapi/validate/issues/137
k8s master uses the buggy version and our test shows the error with Go 1.16 compiler. The same code works correctly with Go 1.15.8 compiler... | go-openapi/validate bug with Go 1.16 | https://api.github.com/repos/kubernetes/kubernetes/issues/100043/comments | 5 | 2021-03-09T23:27:51Z | 2021-03-16T20:29:16Z | https://github.com/kubernetes/kubernetes/issues/100043 | 826,793,828 | 100,043 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
The controllers can create a second EndpointSlice after an immediate sync if the first EndpointSlice they created is not in the cache yet. Here's what can happen:
1. Controller gets event that triggers sync for Service
2. Controller syncs and creates EndpointSlice
3. Controller gets event that... | EndpointSlice Controllers create duplicate EndpointSlices in certain cases | https://api.github.com/repos/kubernetes/kubernetes/issues/100033/comments | 4 | 2021-03-09T21:34:30Z | 2021-03-11T06:42:56Z | https://github.com/kubernetes/kubernetes/issues/100033 | 826,668,166 | 100,033 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
Using SSA patch to create and manage a couple of resources (specifically [those](https://github.com/openshift/cluster-cloud-controller-manager-operator/tree/fffa7104273622e6d0720c38b72735f9693646ae/pkg/cloud/openstack/assets), the list may change in the future) resulted in endless hot loop, as ea... | SSA triggers update events on apply to resource when it is no-op | https://api.github.com/repos/kubernetes/kubernetes/issues/100024/comments | 29 | 2021-03-09T18:17:12Z | 2022-01-25T17:42:31Z | https://github.com/kubernetes/kubernetes/issues/100024 | 826,409,150 | 100,024 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
We found out race condition could potentially occur in node lifecycle controller when a worker node is terminated and another worker node **with same name** spins up before pod eviction timeout.
Node lifecycle controller keeps monitoring the health report from worker node. [If it didn't get this... | The logic to determine if node is known in node lifecycle controller is overly simple which can potentially lead to werid behavior | https://api.github.com/repos/kubernetes/kubernetes/issues/100022/comments | 8 | 2021-03-09T18:03:45Z | 2021-09-11T07:10:03Z | https://github.com/kubernetes/kubernetes/issues/100022 | 826,387,010 | 100,022 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
#### What happened:
Serializin... | NewSerializerWithOptions yaml for v2beta2 HPA cannot be applied with ValidationError | https://api.github.com/repos/kubernetes/kubernetes/issues/100021/comments | 10 | 2021-03-09T18:01:58Z | 2021-10-29T03:30:52Z | https://github.com/kubernetes/kubernetes/issues/100021 | 826,384,393 | 100,021 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
I ran conformance tests on a cluster that had a controller enabled that syncs a configmap across all clusters. It failed:
```
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
Mar 5 11:07:41.670: Unexpected error:
<*errors.Stat... | newTestResourceQuota causes clusters to fail conformance when they probably shouldn't | https://api.github.com/repos/kubernetes/kubernetes/issues/100016/comments | 3 | 2021-03-09T16:03:45Z | 2021-03-11T08:18:54Z | https://github.com/kubernetes/kubernetes/issues/100016 | 826,157,852 | 100,016 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
Tried to use `kubectl apply` with an old release of kubectl against a new version of an existing built-in type
#### What you expected to happen:
`kubectl apply` (with client-side apply) should honor advertised strategic-merge-patch directives like `patchStrategy=replace` published in the op... | client-side `kubectl apply` does not use strategic merge patch info in openapi for unknown types | https://api.github.com/repos/kubernetes/kubernetes/issues/100012/comments | 10 | 2021-03-09T14:13:27Z | 2022-08-23T23:04:49Z | https://github.com/kubernetes/kubernetes/issues/100012 | 825,993,929 | 100,012 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
#### What happened:
The memory... | The memory manager fails to set cpuset.mems when used with the docker shim | https://api.github.com/repos/kubernetes/kubernetes/issues/100005/comments | 2 | 2021-03-09T12:28:37Z | 2021-03-09T17:19:45Z | https://github.com/kubernetes/kubernetes/issues/100005 | 825,850,288 | 100,005 |
[
"kubernetes",
"kubernetes"
] | Up until now, all issues and PRs have had 5 digits or fewer. We should validate nothing fails when the issue or PR number is 6 digits long. | There are no 6-digit issues or PRs in kubernetes/kubernetes | https://api.github.com/repos/kubernetes/kubernetes/issues/100000/comments | 17 | 2021-03-09T10:39:22Z | 2021-03-10T00:18:22Z | https://github.com/kubernetes/kubernetes/issues/100000 | 825,704,220 | 100,000 |
[
"kubernetes",
"kubernetes"
] | #### What would you like to be added:
Add a way to set CABundle for `ValidatingWebhookConfiguration`s at runtime instead of requiring it on object creation.
#### Why is this needed:
To use helm charts without interfacing with CA bundles we fetch CA certificates automatically and validate them with different ch... | Allow setting ValidatingWebhookConfiguration CA bundle at runtime | https://api.github.com/repos/kubernetes/kubernetes/issues/99993/comments | 6 | 2021-03-09T09:09:49Z | 2021-08-06T23:17:25Z | https://github.com/kubernetes/kubernetes/issues/99993 | 825,578,664 | 99,993 |
[
"kubernetes",
"kubernetes"
] | ## Overview
Currently, the only mechanism to auto-delete failed pods is the [garbage collection](https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#pod-garbage-collection). However, the default threshold is incredibly high - 12500[1]. Therefore it is useless in practice for most of customers.
There... | Auto-delete failed Pods | https://api.github.com/repos/kubernetes/kubernetes/issues/99986/comments | 41 | 2021-03-09T07:11:14Z | 2025-01-09T17:56:04Z | https://github.com/kubernetes/kubernetes/issues/99986 | 825,437,228 | 99,986 |
[
"kubernetes",
"kubernetes"
] | In https://github.com/kubernetes/kubernetes/pull/98243 we deprecated CSIMigrationvSphereComplete flag and we will need to remove it in the 1.22 release for clean up.
/sig storage
/assign @Jiawei0227
/cc @msau42
/triage accepted | Remove CSIMigrationvSphereComplete flag and use InTreePluginvSphereUnregister instead | https://api.github.com/repos/kubernetes/kubernetes/issues/99982/comments | 3 | 2021-03-09T06:09:50Z | 2021-06-07T18:06:18Z | https://github.com/kubernetes/kubernetes/issues/99982 | 825,398,641 | 99,982 |
[
"kubernetes",
"kubernetes"
] | https://github.com/kubernetes/kubernetes/pull/98753 will be used as a preparation for relaxing CSI Node id length limitation, in 1.22, we need to make sure the AllowLongNodeID is set correctly according to the comment https://github.com/kubernetes/kubernetes/pull/98753#discussion_r589441271
/sig storage
/assign @Ji... | Relax CSI Node length limitation in 1.22 | https://api.github.com/repos/kubernetes/kubernetes/issues/99981/comments | 6 | 2021-03-09T06:00:29Z | 2021-08-30T15:17:06Z | https://github.com/kubernetes/kubernetes/issues/99981 | 825,393,155 | 99,981 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about flaky tests or jobs (pass or fail with no underlying change in code) in Kubernetes CI -->
#### Which jobs are flaking:
Seems to be impacting a few KIND jobs on the master branch the most, but also assorted other jobs
https://storage.googleapis.com... | [flaky test]: [sig-node] Probing container should be ready immediately after startupProbe succeeds | https://api.github.com/repos/kubernetes/kubernetes/issues/99979/comments | 43 | 2021-03-09T04:14:36Z | 2021-08-05T21:09:20Z | https://github.com/kubernetes/kubernetes/issues/99979 | 825,283,742 | 99,979 |
[
"kubernetes",
"kubernetes"
] | #### What would you like to be added:
The oversubscribed resources are the resources that requested by Pod but not used when it's running. We'd like to ask kubelet to report those resources, so the scheduler can re-use those resouces for preemptable/best-effort Pods.
#### Why is this needed:
It's hard for the ... | Report oversubscribed resources for schedulers | https://api.github.com/repos/kubernetes/kubernetes/issues/99973/comments | 10 | 2021-03-09T01:49:48Z | 2021-11-26T18:27:09Z | https://github.com/kubernetes/kubernetes/issues/99973 | 825,162,468 | 99,973 |
[
"kubernetes",
"kubernetes"
] | Followup of https://github.com/kubernetes/kubernetes/issues/94009#issuecomment-777557692.
Most unschedulabe pods, in current scheduler implementation, will be re-tried to see if they can be schedulable upon a **Node Add/Update** event. This is reasonable b/c a Node Add/Update usually indicates there is room to place... | sched: requeue optimization upon Node Add/Update | https://api.github.com/repos/kubernetes/kubernetes/issues/99968/comments | 2 | 2021-03-08T23:46:51Z | 2021-04-09T00:11:04Z | https://github.com/kubernetes/kubernetes/issues/99968 | 825,071,545 | 99,968 |
[
"kubernetes",
"kubernetes"
] | Follow-up of https://github.com/kubernetes/kubernetes/pull/98241#discussion_r572468952. Currently we maintain a local registry for looking up the ClusterEvent obj by specifying a cluste event (string). The registry is not that necessary as we can build that ClusterEvent obj on the fly in movePodsToActiveOrBackoffQueue(... | sched: cleanup clusterEventReg from pkg/scheduler/internal/queue/events.go | https://api.github.com/repos/kubernetes/kubernetes/issues/99966/comments | 15 | 2021-03-08T23:34:22Z | 2021-04-24T18:12:57Z | https://github.com/kubernetes/kubernetes/issues/99966 | 825,063,180 | 99,966 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
#### What happened:
#### What ... | [Windows Kube-proxy]LoadBalancer Service type with invalid external loadbalancer IP breaks the datapath | https://api.github.com/repos/kubernetes/kubernetes/issues/99964/comments | 3 | 2021-03-08T22:32:28Z | 2021-03-10T08:35:35Z | https://github.com/kubernetes/kubernetes/issues/99964 | 825,019,048 | 99,964 |
[
"kubernetes",
"kubernetes"
] | CSINode.v1beta1 was deprecated in 1.17 and is slated for removal in 1.22. This will cause many CSI failures in pull-kubernetes-e2e-kind after 1.22 alpha.
https://github.com/kubernetes/kubernetes/pull/99840 is exploring what needs to change when the v1beta1 APIs are automatically removed.
https://prow.k8s.io/view... | csi-hostpath provisioner in e2e runs uses CSINode v1beta1 | https://api.github.com/repos/kubernetes/kubernetes/issues/99957/comments | 12 | 2021-03-08T19:48:45Z | 2021-04-27T03:39:22Z | https://github.com/kubernetes/kubernetes/issues/99957 | 824,893,049 | 99,957 |
[
"kubernetes",
"kubernetes"
] | #### What would you like to be added:
Update AnyVolumeDataSource feature gate to beta
#### Why is this needed:
KEP: https://github.com/kubernetes/enhancements/blob/master/keps/sig-storage/1495-volume-populators/README.md | Update AnyVolumeDataSource feature gate to beta | https://api.github.com/repos/kubernetes/kubernetes/issues/99955/comments | 7 | 2021-03-08T19:28:39Z | 2022-03-30T00:35:25Z | https://github.com/kubernetes/kubernetes/issues/99955 | 824,877,885 | 99,955 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
In PR https://github.com/kubernetes/kubernetes/pull/99462 we migrated the cluster-role-aggregator controller to apply. The controller's unit tests use the client-go fake, which works great for update, but for apply, required adding a custom reactor to handle the apply request because, without any... | client-go fake client difficult to use with apply | https://api.github.com/repos/kubernetes/kubernetes/issues/99953/comments | 28 | 2021-03-08T18:05:51Z | 2025-02-07T19:51:26Z | https://github.com/kubernetes/kubernetes/issues/99953 | 824,816,057 | 99,953 |
[
"kubernetes",
"kubernetes"
] | #### What would you like to be added:
Currently kubernetes (and kubectl) run on a host of platforms. Recently, there has been an uptake in ARM based computing devices, most notably Apple's new M1 and Microsoft's Surface Pro X.
It would be great ik K8S would consider Windows on ARM a primary platform and release t... | Support Windows on ARM | https://api.github.com/repos/kubernetes/kubernetes/issues/99948/comments | 13 | 2021-03-08T16:25:11Z | 2022-02-03T09:01:07Z | https://github.com/kubernetes/kubernetes/issues/99948 | 824,722,437 | 99,948 |
[
"kubernetes",
"kubernetes"
] | #### Which jobs are flaking:
pull-kubernetes-e2e-azure-disk-windows
#### Which test(s) are flaking:
pull-kubernetes-e2e-azure-disk-windows
#### Testgrid link:
https://testgrid.k8s.io/provider-azure-presubmit#pr-k8s-azure-disk-e2e-master-windows
#### Reason for failure:
It seems caused by connection failed:... | flake: AzureDisk CSI Driver End-to-End Tests: Dynamic Provisioning [single-az] should create a statefulset object, write and read to it, delete the pod and write and read to it again [kubernetes.io/azure-disk] [disk.csi.azure.com] [Windows] | https://api.github.com/repos/kubernetes/kubernetes/issues/99947/comments | 9 | 2021-03-08T15:36:46Z | 2021-04-06T00:19:19Z | https://github.com/kubernetes/kubernetes/issues/99947 | 824,678,301 | 99,947 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
#### What happened:
In my enviro... | The output of kubectl top node subcommand is incorrect | https://api.github.com/repos/kubernetes/kubernetes/issues/99945/comments | 7 | 2021-03-08T14:31:19Z | 2021-04-29T17:25:48Z | https://github.com/kubernetes/kubernetes/issues/99945 | 824,622,835 | 99,945 |
[
"kubernetes",
"kubernetes"
] | <!-- Feature requests are unlikely to make progress as an issue.
Instead, please suggest enhancements by engaging with SIGs on slack and mailing lists.
A proposal that works through the design along with the implications of the change can be opened as a KEP:
https://git.k8s.io/enhancements/keps#kubernetes-enhanc... | Use Sort and Filter while doing list of any resources | https://api.github.com/repos/kubernetes/kubernetes/issues/99938/comments | 10 | 2021-03-08T10:53:08Z | 2021-08-08T23:35:28Z | https://github.com/kubernetes/kubernetes/issues/99938 | 824,440,541 | 99,938 |
[
"kubernetes",
"kubernetes"
] | <!-- Feature requests are unlikely to make progress as an issue.
Instead, please suggest enhancements by engaging with SIGs on slack and mailing lists.
A proposal that works through the design along with the implications of the change can be opened as a KEP:
https://git.k8s.io/enhancements/keps#kubernetes-enhanc... | Improve concurrency for hack/verify-structured-logging.sh | https://api.github.com/repos/kubernetes/kubernetes/issues/99934/comments | 8 | 2021-03-08T07:07:03Z | 2021-03-09T11:22:50Z | https://github.com/kubernetes/kubernetes/issues/99934 | 824,250,617 | 99,934 |
[
"kubernetes",
"kubernetes"
] | #### What would you like to be added:
Instead of ignoring invalid PVC data sources, reject them
#### Why is this needed:
KEP 2546 explains the motivation and design. It it not merged yet. See this PR:
https://github.com/kubernetes/enhancements/pull/2552 | Implement Reject Invalid PVC DataSource KEP | https://api.github.com/repos/kubernetes/kubernetes/issues/99931/comments | 3 | 2021-03-08T04:52:02Z | 2021-07-07T19:04:36Z | https://github.com/kubernetes/kubernetes/issues/99931 | 824,161,733 | 99,931 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
#### What happened:
The pod pa... | Race condition between kubelet and scheduler | https://api.github.com/repos/kubernetes/kubernetes/issues/99919/comments | 16 | 2021-03-07T17:16:00Z | 2021-05-25T17:46:43Z | https://github.com/kubernetes/kubernetes/issues/99919 | 823,967,178 | 99,919 |
[
"kubernetes",
"kubernetes"
] | #### What would you like to be added:
To deploy cluster addon that communicates with Kubelet (for example Metrics Server), cluster administrator needs to figure out Kubelet endpoints, certificates and authorization configuration and pass it to Metrics Server. This can lead to errors and user frustration as most app... | Kubelet should publish information about preferred way to connect to it | https://api.github.com/repos/kubernetes/kubernetes/issues/99918/comments | 13 | 2021-03-07T09:28:20Z | 2024-11-04T17:50:46Z | https://github.com/kubernetes/kubernetes/issues/99918 | 823,872,087 | 99,918 |
[
"kubernetes",
"kubernetes"
] | Scheduler throughput drops significantly in http://perf-dash.k8s.io/#/?jobname=scheduler-perf-benchmark&metriccategoryname=Scheduler&metricname=BenchmarkPerfResults&Metric=SchedulingThroughput&Name=BenchmarkPerfScheduling%2FSchedulingBasic%2F500Nodes%2Fnamespace-2:
:
- Deploy K8S cluster (1.20.5) on ... | Guaranteed PODs CPUs are shared by other process running on the same host | https://api.github.com/repos/kubernetes/kubernetes/issues/99895/comments | 10 | 2021-03-06T14:46:12Z | 2022-07-29T03:16:37Z | https://github.com/kubernetes/kubernetes/issues/99895 | 823,666,047 | 99,895 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
#### What happened:
We are usi... | kubectl defaults to its pod's namespace | https://api.github.com/repos/kubernetes/kubernetes/issues/99884/comments | 15 | 2021-03-06T05:51:58Z | 2021-03-07T20:33:34Z | https://github.com/kubernetes/kubernetes/issues/99884 | 823,572,962 | 99,884 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
#### What happened:
- Some of ... | unit tests should not require root | https://api.github.com/repos/kubernetes/kubernetes/issues/99881/comments | 35 | 2021-03-06T02:00:39Z | 2023-01-09T22:00:48Z | https://github.com/kubernetes/kubernetes/issues/99881 | 823,533,544 | 99,881 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
I have a controller which uses the clientSet object returned by `kubernetes.NewForConfig`. This clientSet object is then passed to other objects. These objects are using a `kubernetes.Interface` to receive this object. The main reason for using a `kubernetes.Interface` is to be able to use the `fak... | Cannot use kubernetes.Clientset as kubernetes.Interface value in struct literal: missing method AdmissionregistrationV1 | https://api.github.com/repos/kubernetes/kubernetes/issues/99878/comments | 3 | 2021-03-06T01:10:45Z | 2021-03-16T20:29:22Z | https://github.com/kubernetes/kubernetes/issues/99878 | 823,521,944 | 99,878 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about flaky tests or jobs (pass or fail with no underlying change in code) in Kubernetes CI -->
#### Which jobs are flaking:
pull-kubernetes-unit
#### Which test(s) are flaking:
`k8s.io/kubernetes/pkg/kubelet/volumemanager/reconciler`: `Test_Run_Posi... | [flaky test] Test_Run_Positive_VolumeAttachMountUnmountDetach | https://api.github.com/repos/kubernetes/kubernetes/issues/99877/comments | 9 | 2021-03-06T00:53:05Z | 2022-02-04T18:08:03Z | https://github.com/kubernetes/kubernetes/issues/99877 | 823,517,448 | 99,877 |
[
"kubernetes",
"kubernetes"
] | See: https://github.com/kubernetes/kubernetes/pull/99561#issuecomment-791505243
xref: https://github.com/kubernetes/enhancements/issues/2420
/sig testing
/sig architecture
/area code-organization
/assign | bazel visibility rules need porting to make verify | https://api.github.com/repos/kubernetes/kubernetes/issues/99876/comments | 11 | 2021-03-06T00:41:56Z | 2021-03-26T00:42:59Z | https://github.com/kubernetes/kubernetes/issues/99876 | 823,514,621 | 99,876 |
[
"kubernetes",
"kubernetes"
] | <!-- Feature requests are unlikely to make progress as an issue.
Instead, please suggest enhancements by engaging with SIGs on slack and mailing lists.
A proposal that works through the design along with the implications of the change can be opened as a KEP:
https://git.k8s.io/enhancements/keps#kubernetes-enhanc... | Support 'patch' files with `kubectl apply -f` | https://api.github.com/repos/kubernetes/kubernetes/issues/99867/comments | 11 | 2021-03-05T20:49:23Z | 2022-02-17T14:15:18Z | https://github.com/kubernetes/kubernetes/issues/99867 | 823,401,991 | 99,867 |
[
"kubernetes",
"kubernetes"
] | #### What would you like to be added:
Improve the [etcd data integration test](https://github.com/kubernetes/kubernetes/blob/master/test/integration/etcd/etcd_storage_path_test.go) to ensure that the expected storage version for a resource is one understood by previous releases.
We have API testdata from prior ve... | Improve etcd storage test to ensure storage version is not changed prematurely | https://api.github.com/repos/kubernetes/kubernetes/issues/99863/comments | 2 | 2021-03-05T20:33:46Z | 2021-03-23T12:27:37Z | https://github.com/kubernetes/kubernetes/issues/99863 | 823,393,382 | 99,863 |
[
"kubernetes",
"kubernetes"
] | <!-- Feature requests are unlikely to make progress as an issue.
Instead, please suggest enhancements by engaging with SIGs on slack and mailing lists.
A proposal that works through the design along with the implications of the change can be opened as a KEP:
https://git.k8s.io/enhancements/keps#kubernetes-enhanc... | Definitive end date for ExecProbeTimeout kubelet feature gate | https://api.github.com/repos/kubernetes/kubernetes/issues/99854/comments | 16 | 2021-03-05T18:21:26Z | 2024-04-18T18:23:52Z | https://github.com/kubernetes/kubernetes/issues/99854 | 823,315,634 | 99,854 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
Attempting to use port-forward (e.g. via `kubectl port-forward`) to a pod (e.g. `etcd`) that only listens on IPv6 addresses fails with this error:
```
E0305 17:22:44.391325 669306 portforward.go:400] an error occurred forwarding 5000 -> 2379: error forwarding port
2379 to pod 816046a9fc2... | port-forward fails connecting to pods with IPv6 only listeners | https://api.github.com/repos/kubernetes/kubernetes/issues/99850/comments | 12 | 2021-03-05T17:52:46Z | 2021-03-29T17:01:37Z | https://github.com/kubernetes/kubernetes/issues/99850 | 823,297,514 | 99,850 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
Kuberentes fails to create very large Gluster PVC and the following error is logged:
ProvisioningFailed 35s (x566 over 20h) persistentvolume-controller Failed to provision volume with StorageClass "gluster-heketi": failed to create volume: quantity 134192Gi is too great, overflows int64
... | Kuberentes fails to create large Gluster PVC | https://api.github.com/repos/kubernetes/kubernetes/issues/99846/comments | 10 | 2021-03-05T15:57:10Z | 2021-11-01T15:16:28Z | https://github.com/kubernetes/kubernetes/issues/99846 | 823,214,268 | 99,846 |
[
"kubernetes",
"kubernetes"
] | #### Which jobs are flaking:
pull-kubernetes-unit
#### Which test(s) are flaking:
k8s.io/kubernetes/pkg/kubelet/config: TestWatchFileChanged
https://storage.googleapis.com/k8s-gubernator/triage/index.html?pr=1&text=TestWatchFileChanged
```
--- FAIL: TestWatchFileChanged (0.23s)
file_linux_test.go:3... | k8s.io/kubernetes/pkg/kubelet/config: TestWatchFileChanged data race and flake | https://api.github.com/repos/kubernetes/kubernetes/issues/99845/comments | 4 | 2021-03-05T15:37:16Z | 2021-03-24T17:26:30Z | https://github.com/kubernetes/kubernetes/issues/99845 | 823,198,280 | 99,845 |
[
"kubernetes",
"kubernetes"
] | Hi!
#### What happened:
I am trying to setup a HPA with multiple External metrics on a GKE Kubernetes cluster running v1.17
* External metrics are provided using Datadog Cluster Agent
* The HPA works properly when I use a single external metric. This applies for ANY of the metrics I try to use - the labels ar... | HPA not working with multiple External metrics (v1.17) | https://api.github.com/repos/kubernetes/kubernetes/issues/99832/comments | 6 | 2021-03-05T08:50:29Z | 2021-08-02T10:37:04Z | https://github.com/kubernetes/kubernetes/issues/99832 | 822,883,432 | 99,832 |
Subsets and Splits
Unique Owner-Repo Count
Counts the number of unique owner-repos in the dataset, providing a basic understanding of diverse repositories.