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 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:
If the prior... | Pod with spec.priority configured cannot be created if priority admission controller enabled | https://api.github.com/repos/kubernetes/kubernetes/issues/102724/comments | 6 | 2021-06-09T09:47:53Z | 2021-06-15T01:18:32Z | https://github.com/kubernetes/kubernetes/issues/102724 | 916,008,963 | 102,724 |
[
"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:
As the p.isW... | slow memory leak may be in kubelet podworkers.isWorking | https://api.github.com/repos/kubernetes/kubernetes/issues/102723/comments | 3 | 2021-06-09T09:43:01Z | 2021-06-21T23:27:58Z | https://github.com/kubernetes/kubernetes/issues/102723 | 916,004,587 | 102,723 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
The pod created by replicaset does not include the ownerreference information configured in pod template. In my scenerio, the pod template is automatically generated by my operator.
#### What you expected to happen:
I expect the pod created by relicaset controller would include the ownerreferen... | owner reference configured in pod template would not be added to the pod created by replica set | https://api.github.com/repos/kubernetes/kubernetes/issues/102720/comments | 7 | 2021-06-09T06:23:19Z | 2021-12-05T13:20:11Z | https://github.com/kubernetes/kubernetes/issues/102720 | 915,828,859 | 102,720 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
We use `client-go informerFactory` to handle some pod information,
>informerFactory.Core().V1().Pods().Informer().AddEventHandler(
cache.ResourceEventHandlerFuncs{
AddFunc: addPodToCache,
UpdateFunc: updatePodInCache,
DeleteFunc: deletePodFromCache,
})
> ca... | client-go memory leak | https://api.github.com/repos/kubernetes/kubernetes/issues/102718/comments | 23 | 2021-06-09T03:49:01Z | 2024-11-21T10:21:46Z | https://github.com/kubernetes/kubernetes/issues/102718 | 915,743,051 | 102,718 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
When trying to join a second or sometimes third control plane node, `kubeadm join` fails with:
- something that looks like an etcd hangup ("Initial timeout of 40s passed")
- CrashLoopBackOff for one of the kube-apiserver pods
The k8s [docs](https://kubernetes.io/docs/setup/production-envir... | kubeadm join (control plane) consistently fails with CrashLoopBackOff | https://api.github.com/repos/kubernetes/kubernetes/issues/102715/comments | 11 | 2021-06-09T03:04:21Z | 2021-06-09T18:32:55Z | https://github.com/kubernetes/kubernetes/issues/102715 | 915,724,835 | 102,715 |
[
"kubernetes",
"kubernetes"
] | **What happened:**
kubernetes v1.20.1 sonobuoy e2e test failed for AdmissionWebhook
Plugin: e2e
Status: failed
Passed: 265
Failed: 44
Skipped: 5358
**Failed tests:**
1. [Fail] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] [It] should mutate custom resource with different stored version [Con... | e2e test failed for kubernetes v1.20.1 | https://api.github.com/repos/kubernetes/kubernetes/issues/102712/comments | 9 | 2021-06-09T01:21:10Z | 2021-06-09T04:07:35Z | https://github.com/kubernetes/kubernetes/issues/102712 | 915,683,192 | 102,712 |
[
"kubernetes",
"kubernetes"
] | #### What would you like to be added:
GP3 Storage Class Support for AWS EBS. Currently, `persistentvolume-controller Failed to provision volume with StorageClass "prometheus-gp3": invalid AWS VolumeType "gp3"` via Kubernetes 1.19 on EKS.
May require no more than adding the new type here: https://github.com/kuber... | AWS GP3 Storage Support Missing | https://api.github.com/repos/kubernetes/kubernetes/issues/102707/comments | 11 | 2021-06-08T20:00:09Z | 2021-11-09T20:24:55Z | https://github.com/kubernetes/kubernetes/issues/102707 | 915,426,853 | 102,707 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
I then tried to add a pod that uses an ephemeral volume:
```
kind: Pod
apiVersion: v1
metadata:
name: my-app
spec:
containers:
- name: my-frontend
image: busybox
volumeMounts:
- mountPath: "/scratch"
name: scratch-volume
command: [ "sleep", "1000... | Volume type of ephemeral is not recognized | https://api.github.com/repos/kubernetes/kubernetes/issues/102706/comments | 3 | 2021-06-08T19:48:55Z | 2021-06-08T20:19:00Z | https://github.com/kubernetes/kubernetes/issues/102706 | 915,414,256 | 102,706 |
[
"kubernetes",
"kubernetes"
] | ```
kubeadm init --config /path/to/custom.yaml --log-file out.log --one-output <other-args>
```
will error with
```
can not mix '--config' with arguments [log-file one-output]
```
however it is not apparent in the documentation what the equivalent key entries for these two flags are or if there are equival... | Config file equivalents for --log-file --one-output | https://api.github.com/repos/kubernetes/kubernetes/issues/102699/comments | 5 | 2021-06-08T17:46:08Z | 2021-06-09T01:39:32Z | https://github.com/kubernetes/kubernetes/issues/102699 | 915,296,624 | 102,699 |
[
"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:
Tried to dow... | Controller-manager fails to successfully start when converting a cluster from dual-stack to single-stack | https://api.github.com/repos/kubernetes/kubernetes/issues/102698/comments | 16 | 2021-06-08T16:57:42Z | 2022-06-09T21:25:28Z | https://github.com/kubernetes/kubernetes/issues/102698 | 915,256,062 | 102,698 |
[
"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 want to cr... | Configuring the kube-apiserver advertise address in kubeadm init has incomplete consequences | https://api.github.com/repos/kubernetes/kubernetes/issues/102693/comments | 8 | 2021-06-08T13:41:40Z | 2021-06-10T13:09:45Z | https://github.com/kubernetes/kubernetes/issues/102693 | 915,066,675 | 102,693 |
[
"kubernetes",
"kubernetes"
] | In https://kubernetes.io/docs/setup/production-environment/windows/intro-windows-in-kubernetes/#memory-reservations,
> As you deploy workloads, use resource limits (must set only limits or _**limits must equal requests**_) on containers.
It says limits must equal requests for memory, does it make sense? We are usin... | Memory Reservations on Windows Pod | https://api.github.com/repos/kubernetes/kubernetes/issues/102686/comments | 11 | 2021-06-08T09:34:46Z | 2021-12-20T22:48:56Z | https://github.com/kubernetes/kubernetes/issues/102686 | 914,691,167 | 102,686 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
If I modify a custom endpoint, the kubectl kubectl.kubernetes.io/last-applied-configuration annotation is mirrored to the generated endpoint slice
#### What you expected to happen:
Since the kubect last-applied-configuration tracks the status of the object, it shouldn't be mirrored since it... | Endpoint slice mirroring controller mirrors kubectl kubectl.kubernetes.io/last-applied-configuration | https://api.github.com/repos/kubernetes/kubernetes/issues/102684/comments | 11 | 2021-06-08T08:20:50Z | 2021-06-15T20:41:56Z | https://github.com/kubernetes/kubernetes/issues/102684 | 914,562,297 | 102,684 |
[
"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:
If the pro... | misleading failures info when e2e storage testcase is running locally | https://api.github.com/repos/kubernetes/kubernetes/issues/102680/comments | 4 | 2021-06-08T05:35:19Z | 2021-06-25T01:56:45Z | https://github.com/kubernetes/kubernetes/issues/102680 | 914,378,565 | 102,680 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
Errors like this one
> May 27 06:38:19.960408 ip-10-0-220-230 hyperkube[1448]: E0527 06:38:19.960361 1448 pod_workers.go:190] "Error syncing pod, skipping" err="failed to ensure that the pod: 5ac83c3f-0b16-4cf2-a3cb-f67c19cd0e16 cgroups exist and are correctly applied: failed to create con... | Pod stuck in ContainerCreating: Unit ...slice already exists | https://api.github.com/repos/kubernetes/kubernetes/issues/102676/comments | 45 | 2021-06-08T01:35:32Z | 2021-09-14T08:09:52Z | https://github.com/kubernetes/kubernetes/issues/102676 | 914,139,564 | 102,676 |
[
"kubernetes",
"kubernetes"
] | I'm seeing issues where API servers experience high load when Informers start up. I think I've traced it to this issue https://github.com/kubernetes/client-go/issues/366 where it was intentionally decided that chunking would not be peformed when ResourceVersion="0". That decision dates from 2018 and was made because ... | ResourceVersion="0" causes no chunking, makes starting Informers expensive | https://api.github.com/repos/kubernetes/kubernetes/issues/102672/comments | 26 | 2021-06-07T23:03:45Z | 2022-01-31T20:53:03Z | https://github.com/kubernetes/kubernetes/issues/102672 | 914,025,812 | 102,672 |
[
"kubernetes",
"kubernetes"
] | I have not verified locally yet but I suspect that metric collection from unresponsive NFS mounts will result in leaked goroutine because we are calling `err := unix.Statfs(path, statfs)` on those paths.
cc @kubernetes/sig-storage-bugs
| Metric collection from hard mounted but unresponsive NFS mounts could leak goroutines | https://api.github.com/repos/kubernetes/kubernetes/issues/102664/comments | 5 | 2021-06-07T15:34:24Z | 2021-11-04T16:51:29Z | https://github.com/kubernetes/kubernetes/issues/102664 | 913,683,989 | 102,664 |
[
"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... | Docs about how to bootstrap apiserver | https://api.github.com/repos/kubernetes/kubernetes/issues/102663/comments | 6 | 2021-06-07T15:17:21Z | 2021-06-10T20:17:12Z | https://github.com/kubernetes/kubernetes/issues/102663 | 913,665,816 | 102,663 |
[
"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:
Trying to ru... | kube-controller-manager 1.21.1 crashes with nil pointer (azure_standard.go) | https://api.github.com/repos/kubernetes/kubernetes/issues/102660/comments | 11 | 2021-06-07T15:00:36Z | 2021-06-19T10:11:56Z | https://github.com/kubernetes/kubernetes/issues/102660 | 913,649,738 | 102,660 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
Launching a pod failed with
```
RunPodSandbox from runtime service failed: rpc error: code = Unknown desc = failed to create a sandbox for pod "it-sync-cron-1623075300-hhzbh": operation timeout: context deadline exceeded
Jun 07 14:21:29 ip-10-241-29-119 kubelet[23154]: E0607 14:21:29.850146 2... | kubelet error launching pods, state error on running containers | https://api.github.com/repos/kubernetes/kubernetes/issues/102659/comments | 12 | 2021-06-07T14:33:43Z | 2021-10-05T21:49:49Z | https://github.com/kubernetes/kubernetes/issues/102659 | 913,617,036 | 102,659 |
[
"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:
Tried creati... | Dualstack : Validation issues when creating services | https://api.github.com/repos/kubernetes/kubernetes/issues/102654/comments | 7 | 2021-06-07T08:32:48Z | 2021-07-08T20:37:31Z | https://github.com/kubernetes/kubernetes/issues/102654 | 913,284,367 | 102,654 |
[
"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:
kubelet pani... | kubelet panics on creation of inline ephemeral volume with FSType specified | https://api.github.com/repos/kubernetes/kubernetes/issues/102651/comments | 4 | 2021-06-07T07:31:54Z | 2021-06-09T17:17:27Z | https://github.com/kubernetes/kubernetes/issues/102651 | 913,218,460 | 102,651 |
[
"kubernetes",
"kubernetes"
] | ### Failure cluster [670e16aa8066230be73b](https://go.k8s.io/triage#670e16aa8066230be73b)
exec_test.go:627: wanted sync true, got sync false
exec_test.go:740: wanted sync true, got sync false
exec_test.go:750: wanted sync true, got sync false
exec_test.go:771: informer never changed resource ver... | TestExecPluginRotationViaInformer flake and slow > 2min | https://api.github.com/repos/kubernetes/kubernetes/issues/102650/comments | 5 | 2021-06-07T07:29:40Z | 2021-06-14T14:02:29Z | https://github.com/kubernetes/kubernetes/issues/102650 | 913,216,228 | 102,650 |
[
"kubernetes",
"kubernetes"
] | #### Which jobs are failing:
ci-kubernetes-e2e-gci-gce-coredns
ci-kubernetes-e2e-gci-gce-slow
ci-kubernetes-e2e-gci-gce-ipvs
Basically, all jobs that run the test :)
#### Which test(s) are failing:
[sig-network] Services [Slow] should be able to create and tear down a standard-tier load balancer
###... | [Failing test] [sig-network] Services [Slow] should be able to create and tear down a standard-tier load balancer | https://api.github.com/repos/kubernetes/kubernetes/issues/102649/comments | 5 | 2021-06-07T07:07:01Z | 2021-06-09T20:35:27Z | https://github.com/kubernetes/kubernetes/issues/102649 | 913,193,205 | 102,649 |
[
"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 reviewing... | More concurrency bugs in priority-and-fairness_test.go | https://api.github.com/repos/kubernetes/kubernetes/issues/102648/comments | 10 | 2021-06-07T06:34:07Z | 2023-02-22T01:25:58Z | https://github.com/kubernetes/kubernetes/issues/102648 | 913,160,676 | 102,648 |
[
"kubernetes",
"kubernetes"
] | I have a cluster with two machines (1 master and 1 worker) and have a single pod on worker node which is providing SCTP service. A **ClusterIP** service related to the pod declares **externalIPs**. The value of externalIPs is the public IP (###.###.##.208) of the worker's machine. When pod and service are deployed usin... | SCTP port is not opening to receive traffic from outside of kubernetes cluster | https://api.github.com/repos/kubernetes/kubernetes/issues/102646/comments | 24 | 2021-06-07T05:30:56Z | 2024-04-20T18:05:07Z | https://github.com/kubernetes/kubernetes/issues/102646 | 913,110,830 | 102,646 |
[
"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 try... | owned Custom Resources not garbage collected after CRD API version removal | https://api.github.com/repos/kubernetes/kubernetes/issues/102641/comments | 24 | 2021-06-06T18:54:44Z | 2024-09-17T20:26:18Z | https://github.com/kubernetes/kubernetes/issues/102641 | 912,919,961 | 102,641 |
[
"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 an... | HPA scale up policies are ignored and default algorithm is used | https://api.github.com/repos/kubernetes/kubernetes/issues/102633/comments | 7 | 2021-06-06T17:20:13Z | 2021-09-06T11:37:20Z | https://github.com/kubernetes/kubernetes/issues/102633 | 912,895,594 | 102,633 |
[
"kubernetes",
"kubernetes"
] | Follow up from https://github.com/kubernetes/klog/issues/211
Currently importing `k8s.io/component-base/logs` results both `text` and `json` logging format available by default. As Json format is not yet GAed, it is undesired to force it on component authors that use the library. Instead it should be optional. This ... | JSON logging format should not be registered by default | https://api.github.com/repos/kubernetes/kubernetes/issues/102632/comments | 5 | 2021-06-06T14:55:26Z | 2021-06-26T07:42:57Z | https://github.com/kubernetes/kubernetes/issues/102632 | 912,854,257 | 102,632 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI -->
#### Which jobs are failing:
pull-kubernetes-node-crio-e2e
#### Which test(s) are failing:
The job failed to launch, so no tests were executed.
#### Since when has it been failing:
After ... | pull-kubernetes-node-crio-e2e failing due invalid ssh key format | https://api.github.com/repos/kubernetes/kubernetes/issues/102624/comments | 2 | 2021-06-05T13:37:56Z | 2021-06-05T15:42:39Z | https://github.com/kubernetes/kubernetes/issues/102624 | 912,267,992 | 102,624 |
[
"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:
`flags.Var(c... | string slice flag is not assigned | https://api.github.com/repos/kubernetes/kubernetes/issues/102621/comments | 5 | 2021-06-05T13:15:32Z | 2021-06-30T18:49:29Z | https://github.com/kubernetes/kubernetes/issues/102621 | 912,259,219 | 102,621 |
[
"kubernetes",
"kubernetes"
] |
#### What happened:
when I start kube-apiserver on version v1.22.0-alpha.2 , I got an error blow...
```
[root@node1 ~]# journalctl -xe
Jun 05 19:07:41 node1 systemd[1]: --audit-log-path=/var/lib/audit.log
Jun 05 19:07:41 node1 systemd[1]: --event-ttl=1h
Jun 05 19:07:41 node1 systemd[1]: --allow-privileged=true... | start kube-apiserver failed with parameter "--port=8080 --secure-port=6443" on version 1.22.0-alpha.2 | https://api.github.com/repos/kubernetes/kubernetes/issues/102619/comments | 3 | 2021-06-05T11:18:24Z | 2021-06-05T19:40:01Z | https://github.com/kubernetes/kubernetes/issues/102619 | 912,213,220 | 102,619 |
[
"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:
Devices outs... | kube-proxy/iptables, client continuous to send packets, udp server pod restart cause UDP conntrack entry error | https://api.github.com/repos/kubernetes/kubernetes/issues/102618/comments | 6 | 2021-06-05T10:04:19Z | 2021-06-07T12:21:11Z | https://github.com/kubernetes/kubernetes/issues/102618 | 912,187,203 | 102,618 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI -->
#### Which jobs are failing:
`pull-kubernetes-node-crio-e2e`
#### Which test(s) are failing:
failed to launch the job `pull-kubernetes-node-crio-e2e` itself, so no tests were executed.
###... | pull-kubernetes-node-crio-e2e failing due to lack of gcp permissions | https://api.github.com/repos/kubernetes/kubernetes/issues/102616/comments | 3 | 2021-06-05T09:35:46Z | 2021-06-07T21:10:49Z | https://github.com/kubernetes/kubernetes/issues/102616 | 912,177,237 | 102,616 |
[
"kubernetes",
"kubernetes"
] | #### What would you like to be added:
CRI API methods to execute kubelet TCP and HTTP probes/lifecycle hooks
#### Why is this needed:
Current probes/lifecycle hooks implementation forces the networking model to provide connectivity between the kubelet and the pods, however, this may not be true or easy to achi... | Add TCP/HTTP/network requests to the CRI API | https://api.github.com/repos/kubernetes/kubernetes/issues/102613/comments | 36 | 2021-06-04T23:37:17Z | 2024-06-20T16:23:57Z | https://github.com/kubernetes/kubernetes/issues/102613 | 911,992,077 | 102,613 |
[
"kubernetes",
"kubernetes"
] | This would remove one more reason why pods run as root when they otherwise don't need to. Clearly this is a CRI thing, but perhaps we should require it? | Set sysctl net/ipv4/ip_unprivileged_port_start ? | https://api.github.com/repos/kubernetes/kubernetes/issues/102612/comments | 34 | 2021-06-04T23:16:48Z | 2025-03-10T21:50:51Z | https://github.com/kubernetes/kubernetes/issues/102612 | 911,968,751 | 102,612 |
[
"kubernetes",
"kubernetes"
] | AKA: `make test` should be what `pull-kubernetes-unit` runs.
If we want race detection mode on in CI (`KUBE_RACE=-race`) we should just make that the default.
We should also consider if we want that more than we want caching (we can't use golang caching if we have -race or -count enabled, we have prototypes of ca... | unit test job should reflect trivially runnable local defaults | https://api.github.com/repos/kubernetes/kubernetes/issues/102607/comments | 22 | 2021-06-04T19:48:55Z | 2021-11-03T19:50:31Z | https://github.com/kubernetes/kubernetes/issues/102607 | 911,791,398 | 102,607 |
[
"kubernetes",
"kubernetes"
] | ### Failure cluster [7f9e4d2e1a40224cca34](https://go.k8s.io/triage#7f9e4d2e1a40224cca34)
##### Error text:
```
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/csi_mock_volume.go:584
May 26 08:47:40.013: while cleaning up after test
Unexpected error:
<errors.aggregate ... | [Flaky test] [sig-storage] CSI mock volume CSI Volume expansion should expand volume by restarting pod if attach=on, nodeExpansion=on | https://api.github.com/repos/kubernetes/kubernetes/issues/102605/comments | 5 | 2021-06-04T19:02:58Z | 2021-11-01T20:18:42Z | https://github.com/kubernetes/kubernetes/issues/102605 | 911,764,225 | 102,605 |
[
"kubernetes",
"kubernetes"
] | On a clean Ubuntu dev environment I get the following error when I executed the `make test WHAT=./pkg/volume`
```
+++ [0604 10:05:38] Running tests without code coverage
--- FAIL: TestGetMetricsBlock (0.11s)
metrics_block_test.go:96: Unexpected error when calling GetMetrics: unable to open device "/dev/cdrom": ... | unit tests of the ./pkg/volume are failing | https://api.github.com/repos/kubernetes/kubernetes/issues/102600/comments | 7 | 2021-06-04T14:29:34Z | 2021-06-04T20:58:35Z | https://github.com/kubernetes/kubernetes/issues/102600 | 911,556,168 | 102,600 |
[
"kubernetes",
"kubernetes"
] |
#### What happened:
we have added a prestop hook in one of our microservice "workflow" which uses service bus to consume messages and mongodb to update results , which run the pre-stop.sh script
kubectl rollout restart deployment workflow-v2 -n team3, it should run the prestop hook(which takes all the inprogress ... | SIGPIPE Signal sent during prestop hook execution in pod | https://api.github.com/repos/kubernetes/kubernetes/issues/102589/comments | 6 | 2021-06-04T07:22:44Z | 2021-10-11T16:08:21Z | https://github.com/kubernetes/kubernetes/issues/102589 | 911,206,661 | 102,589 |
[
"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:
Konnectivity S... | Konnectivity Service doesn't tolerate wildcard taints and gets evicted when node gets tainted with NoExecute. | https://api.github.com/repos/kubernetes/kubernetes/issues/102582/comments | 7 | 2021-06-04T05:35:53Z | 2021-09-15T08:40:42Z | https://github.com/kubernetes/kubernetes/issues/102582 | 911,136,017 | 102,582 |
[
"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... | [AutoScaling] Kubernetes Ingress Object Metrics with Community NGINX Ingress Controller | https://api.github.com/repos/kubernetes/kubernetes/issues/102575/comments | 9 | 2021-06-03T21:03:45Z | 2021-06-25T05:00:33Z | https://github.com/kubernetes/kubernetes/issues/102575 | 910,851,379 | 102,575 |
[
"kubernetes",
"kubernetes"
] | When the scheduler fails to find a node to schedule a pod, a message is logged summarizing the reason. It would be helpful if we include the plugin name in the summary message so that it is easier to parse this message by diagnostic tools.
I also wonder if we can utilize structured logging to report an even easier ... | Scheduler: add plugin name to the filter message | https://api.github.com/repos/kubernetes/kubernetes/issues/102573/comments | 23 | 2021-06-03T19:53:14Z | 2022-01-18T00:53:38Z | https://github.com/kubernetes/kubernetes/issues/102573 | 910,807,448 | 102,573 |
[
"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:
Exec-ing ont... | Exec timeout does not kick users out on kubectl client 1.21 | https://api.github.com/repos/kubernetes/kubernetes/issues/102569/comments | 30 | 2021-06-03T17:54:41Z | 2024-08-23T20:52:27Z | https://github.com/kubernetes/kubernetes/issues/102569 | 910,730,557 | 102,569 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
When the block volume is detached ungracefully or by a reboot to compute instance, kubelet re-attaches the volume, but it doesn't mount it. Thus, it is inaccessible to the user.
#### What you expected to happen:
The volume should be mounted after attach automatically.
#### How to reproduce ... | kubelet doesn't observe/get call for remounts. | https://api.github.com/repos/kubernetes/kubernetes/issues/102567/comments | 7 | 2021-06-03T14:25:09Z | 2021-11-11T18:13:40Z | https://github.com/kubernetes/kubernetes/issues/102567 | 910,547,047 | 102,567 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
I'm using velero for backups, for the validation I've opened up a new single machine cluster. I've restored the pv,pvc using velero.
But after I deployed the pod -this is a redis pod-, data volume couldn't be attached to the pod.
#### What you expected to happen:
I expect it mounts
#### H... | PV can't be attached to the pod on aws ec2 single node cluster | https://api.github.com/repos/kubernetes/kubernetes/issues/102566/comments | 10 | 2021-06-03T13:41:02Z | 2021-06-08T08:46:01Z | https://github.com/kubernetes/kubernetes/issues/102566 | 910,506,662 | 102,566 |
[
"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-enha... | Reduce memory usage after deployment or statefulset upgrade | https://api.github.com/repos/kubernetes/kubernetes/issues/102564/comments | 7 | 2021-06-03T11:36:13Z | 2021-10-31T21:08:21Z | https://github.com/kubernetes/kubernetes/issues/102564 | 910,405,707 | 102,564 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
Unable to restart serv er
#### What you expected to happen:
Running node after restart
#### How to reproduce it (as minimally and precisely as possible):
I found that setting [Docker daemon systemd](https://kubernetes.io/docs/setup/production-environment/container-runtimes/#docker)(Ubuntu... | systemd on Ubuntu - Current command vanished from the unit file | https://api.github.com/repos/kubernetes/kubernetes/issues/102563/comments | 9 | 2021-06-03T11:18:56Z | 2021-07-13T13:09:35Z | https://github.com/kubernetes/kubernetes/issues/102563 | 910,392,844 | 102,563 |
[
"kubernetes",
"kubernetes"
] | I'm following this page og official documentation https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#restart-policy
I would like to set the `spec.restartPolicy` of a Pod with the Never value, but Kubernetes in GCP give me this message:
> spec.template.spec.restartpolicy unsupported value Never sup... | Container restart policy - Problem settings Spec in Pod | https://api.github.com/repos/kubernetes/kubernetes/issues/102562/comments | 5 | 2021-06-03T11:04:37Z | 2021-06-17T01:23:45Z | https://github.com/kubernetes/kubernetes/issues/102562 | 910,381,022 | 102,562 |
[
"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:
DaemonSet with p... | Conntrack table not flushed for UDP hostPort on pod restart (DaemonSet) | https://api.github.com/repos/kubernetes/kubernetes/issues/102559/comments | 5 | 2021-06-03T09:13:39Z | 2021-06-07T06:47:11Z | https://github.com/kubernetes/kubernetes/issues/102559 | 910,291,009 | 102,559 |
[
"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... | Provide better guidance for structured logging migration contributors | https://api.github.com/repos/kubernetes/kubernetes/issues/102557/comments | 17 | 2021-06-03T07:56:07Z | 2021-06-22T07:11:59Z | https://github.com/kubernetes/kubernetes/issues/102557 | 910,224,360 | 102,557 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
Control plane is broken. Kubelet is technically running but seems stuck in initialization. I think this is a certificate problem, because it stopped working suddenly with no control-plane, hardware or OS-level change, and the following elements:
- `kubectl get nodes` fails with `unauthorized`
- k... | Unable to renew expired certificate | https://api.github.com/repos/kubernetes/kubernetes/issues/102556/comments | 13 | 2021-06-03T07:55:17Z | 2022-08-06T05:46:57Z | https://github.com/kubernetes/kubernetes/issues/102556 | 910,223,589 | 102,556 |
[
"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:
Kubelet does... | Kubelet does not compress container logs | https://api.github.com/repos/kubernetes/kubernetes/issues/102553/comments | 18 | 2021-06-03T06:46:56Z | 2021-11-22T08:55:02Z | https://github.com/kubernetes/kubernetes/issues/102553 | 910,161,749 | 102,553 |
[
"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 the nod... | when the node restarts, the numa information of the device cannot be obtained from the checkpoint | https://api.github.com/repos/kubernetes/kubernetes/issues/102552/comments | 16 | 2021-06-03T06:42:08Z | 2021-11-25T07:16:23Z | https://github.com/kubernetes/kubernetes/issues/102552 | 910,157,950 | 102,552 |
[
"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:
Deployment... | Deployment rolling update hang during scaling | https://api.github.com/repos/kubernetes/kubernetes/issues/102551/comments | 7 | 2021-06-03T06:18:38Z | 2021-10-31T08:07:23Z | https://github.com/kubernetes/kubernetes/issues/102551 | 910,141,310 | 102,551 |
[
"kubernetes",
"kubernetes"
] | #### What would you like to be added:
E2E / conformance tests that verify names like `kubernetes.default`, `kubernetes.default.svc`, etc. are part of Subject Alternate Name (SAN) list in the Kubernetes API server serving certificate. (The full list of PQDNs and FQDNs that should be validated may need to be determine... | Add conformance tests for required SANs (like kubernetes.default) in apiserver serving certificate | https://api.github.com/repos/kubernetes/kubernetes/issues/102549/comments | 30 | 2021-06-03T02:28:52Z | 2022-10-09T23:25:42Z | https://github.com/kubernetes/kubernetes/issues/102549 | 910,033,452 | 102,549 |
[
"kubernetes",
"kubernetes"
] | Just noticed that we have redundant metrics for watch counts like:
```
# HELP apiserver_longrunning_gauge [ALPHA] Gauge of all active long-running apiserver requests broken out by verb, group, version, resource, scope and component. Not all requests are tracked this way.
# TYPE apiserver_longrunning_gauge gauge
a... | Get rid of duplicate set of metrics for watch counts | https://api.github.com/repos/kubernetes/kubernetes/issues/102545/comments | 19 | 2021-06-02T21:51:28Z | 2022-05-31T19:53:17Z | https://github.com/kubernetes/kubernetes/issues/102545 | 909,915,171 | 102,545 |
[
"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:
Nodelocal DN... | Nodelocal DNS Cache missing auto-populated configuration | https://api.github.com/repos/kubernetes/kubernetes/issues/102543/comments | 3 | 2021-06-02T21:06:37Z | 2021-06-02T21:23:38Z | https://github.com/kubernetes/kubernetes/issues/102543 | 909,884,313 | 102,543 |
[
"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:
Pod that r... | Pod does not go into unready state while terminating | https://api.github.com/repos/kubernetes/kubernetes/issues/102537/comments | 25 | 2021-06-02T16:06:09Z | 2022-09-19T22:08:53Z | https://github.com/kubernetes/kubernetes/issues/102537 | 909,658,949 | 102,537 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
IPv6 network traffic to a pod via a `SingleStack` IPv6 loadbalancer service with `externalTrafficPolicy=Local` have their source IP addresses rewritten to a seemingly random service cluster IPv6 address. This rewriting is reversed for the return traffic, so traffic flows normally, but the pod end... | `externalTrafficPolicy=Local` incorrectly rewrites client IP on traffic coming through SingleStack IPv6 loadbalancer services on a dual-stack cluster | https://api.github.com/repos/kubernetes/kubernetes/issues/102527/comments | 18 | 2021-06-02T12:16:15Z | 2021-06-04T14:51:45Z | https://github.com/kubernetes/kubernetes/issues/102527 | 909,437,604 | 102,527 |
[
"kubernetes",
"kubernetes"
] | ### Failure cluster [ad6b52817bdb4c8f181e](https://go.k8s.io/triage#ad6b52817bdb4c8f181e)
##### Error text:
```
Failed
```
#### Recent failures:
[2021/6/2 上午12:42:44 ci-kubernetes-generate-make-test-count10](https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-generate-make-test-count10/13997680368... | Failure cluster [ad6b5281...] Deleted_Pod_with_migrated_PV failed for data race | https://api.github.com/repos/kubernetes/kubernetes/issues/102522/comments | 3 | 2021-06-02T06:47:30Z | 2021-06-07T09:50:40Z | https://github.com/kubernetes/kubernetes/issues/102522 | 909,174,343 | 102,522 |
[
"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/
-->
/sig node
/area kubelet
#### Wh... | kubelet panic with fatal error: concurrent map writes | https://api.github.com/repos/kubernetes/kubernetes/issues/102517/comments | 14 | 2021-06-02T03:35:19Z | 2022-01-29T09:10:18Z | https://github.com/kubernetes/kubernetes/issues/102517 | 909,051,800 | 102,517 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
I have a private GKE cluster and I have set up docker to use squid proxy for worker nodes. **I can successfully pull images** from the private repo by sshing into the worker node and using `docker pull <REPO/IMAGE:TAG>`.
However, when creating a pod, kubelet fails to download image with followin... | kubelet fails to download image via squid proxy server | https://api.github.com/repos/kubernetes/kubernetes/issues/102505/comments | 3 | 2021-06-01T20:09:43Z | 2021-06-01T20:16:32Z | https://github.com/kubernetes/kubernetes/issues/102505 | 908,649,950 | 102,505 |
[
"kubernetes",
"kubernetes"
] | <!--
-->
#### What happened:
We have our microservices are deployed in azure kubernetes service. In one of the pod, we wanted to implement prestop hook, so that before termination, it should gather all inprogress items and update the mongodb collection and deliver the message back to service bus queue to process... | Not able to connect to mongoDb when pod is in terminating state implementing prestop hook | https://api.github.com/repos/kubernetes/kubernetes/issues/102501/comments | 5 | 2021-06-01T18:57:21Z | 2021-06-24T17:21:18Z | https://github.com/kubernetes/kubernetes/issues/102501 | 908,593,996 | 102,501 |
[
"kubernetes",
"kubernetes"
] | Per last k8s-infra WG, some images are more used than others, most notably kube-proxy. This can be easily explained by the fact that while control plane is restricted to a small set of hosts, all regular clusters needs kube-proxy (unless your CNI does implement it, which is not the case).
kube-proxy image is 118Mb, ... | Umbrella issue: Reduce release image sizes | https://api.github.com/repos/kubernetes/kubernetes/issues/102493/comments | 30 | 2021-06-01T15:37:01Z | 2021-11-29T13:47:50Z | https://github.com/kubernetes/kubernetes/issues/102493 | 908,425,114 | 102,493 |
[
"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:
https://testgrid.k8s.io/sig-windows-signal#aks-engine-windows-containerd-1.21
#### Which test(s) are flaking:
[sig-node] Downward... | Possible networking bug causing sig-node test failures in Windows tests | https://api.github.com/repos/kubernetes/kubernetes/issues/102492/comments | 4 | 2021-06-01T15:33:18Z | 2021-06-01T16:25:33Z | https://github.com/kubernetes/kubernetes/issues/102492 | 908,420,465 | 102,492 |
[
"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... | Migrate conformance image to go-runner built by k/release | https://api.github.com/repos/kubernetes/kubernetes/issues/102490/comments | 7 | 2021-06-01T15:18:07Z | 2021-11-20T04:36:01Z | https://github.com/kubernetes/kubernetes/issues/102490 | 908,406,180 | 102,490 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
We have a StatefulSet pod using a CSI volume.
After rolling restart, the pod got scheduled on the 'same node' as where it was running before.
The `NodeUnstageVolume` was called for the CSI volume and the `umount` operation was running on the node.
Before the `NodeUnstageVolume` returned success,... | NodeStageVolume is called before NodeUnstageVolume returns Success | https://api.github.com/repos/kubernetes/kubernetes/issues/102486/comments | 7 | 2021-06-01T14:26:00Z | 2021-10-29T17:52:43Z | https://github.com/kubernetes/kubernetes/issues/102486 | 908,351,864 | 102,486 |
[
"kubernetes",
"kubernetes"
] | #### Which test(s) are failing:
Snapshots tests
#### Since when has it been failing:
From k8s v20.2
#### Reason for failure:
Some clusters need `v1beta1` resources for [Snapshot resources.](https://github.com/rook/rook/issues/6819#issuecomment-852059116)
Required `v1beta1` snapshot class is provided through f... | Failing snapshot tests due to resource version mismatch | https://api.github.com/repos/kubernetes/kubernetes/issues/102482/comments | 5 | 2021-06-01T13:19:21Z | 2021-09-10T04:53:10Z | https://github.com/kubernetes/kubernetes/issues/102482 | 908,285,729 | 102,482 |
[
"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 saw so... | kubelet SyncLoop hangs at GetCgroupStats due to cadvisor encounter a possible deadlock | https://api.github.com/repos/kubernetes/kubernetes/issues/102481/comments | 11 | 2021-06-01T12:48:26Z | 2021-12-03T02:03:37Z | https://github.com/kubernetes/kubernetes/issues/102481 | 908,256,980 | 102,481 |
[
"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:
Since upgr... | kubelet: Panic on portforward streams | https://api.github.com/repos/kubernetes/kubernetes/issues/102480/comments | 9 | 2021-06-01T10:57:46Z | 2021-06-10T07:15:07Z | https://github.com/kubernetes/kubernetes/issues/102480 | 908,169,119 | 102,480 |
[
"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'm using ... | [Node Lifecycle Controller] kube-controller-manager's log keep showing "Node <node-name> no longer present in nodeLister!" | https://api.github.com/repos/kubernetes/kubernetes/issues/102479/comments | 10 | 2021-06-01T10:20:22Z | 2021-11-22T20:55:27Z | https://github.com/kubernetes/kubernetes/issues/102479 | 908,140,236 | 102,479 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI -->
#### Which jobs are failing:
`pull-kubernetes-unit`
#### Which test(s) are failing:
`Test_ADC_VolumeAttachmentRecovery/Deleted_Pod_with_migrated_PV`
#### Since when has it been failing:
... | Failing tests: [sig-storage] Test_ADC_VolumeAttachmentRecovery/Deleted_Pod_with_migrated_PV | https://api.github.com/repos/kubernetes/kubernetes/issues/102476/comments | 18 | 2021-06-01T09:19:38Z | 2021-11-30T10:32:15Z | https://github.com/kubernetes/kubernetes/issues/102476 | 908,089,048 | 102,476 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
https://github.com/kubernetes/kubernetes/pull/8438 introduced a glob mechanism for [Docker authentication configuration files](https://kubernetes.io/docs/concepts/containers/images/#configuring-nodes-to-authenticate-to-a-private-registry). URL paths are being matched via `strings.HasPrefix`:
h... | Docker credentials passed via CRI (on image pull) match URL paths by prefix | https://api.github.com/repos/kubernetes/kubernetes/issues/102472/comments | 13 | 2021-06-01T07:30:52Z | 2021-11-22T17:19:24Z | https://github.com/kubernetes/kubernetes/issues/102472 | 907,991,413 | 102,472 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
Using the Fabric8 client, which defaults to using WebSockets for Watches, I established a Watch on Service resources. After the timeout (implicit or explicit) rather than the WebSocket seeing a close control frame or even an EOF it continued to be open and fulfill ping/pong requests - but no Ser... | Watch of Service resource with WebSocket does not timeout appropriately | https://api.github.com/repos/kubernetes/kubernetes/issues/102464/comments | 15 | 2021-05-31T23:27:54Z | 2022-04-27T14:07:36Z | https://github.com/kubernetes/kubernetes/issues/102464 | 907,755,601 | 102,464 |
[
"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:
After server... | Kubernetes fails to start after host reboot | https://api.github.com/repos/kubernetes/kubernetes/issues/102460/comments | 7 | 2021-05-31T15:15:49Z | 2021-07-19T19:56:15Z | https://github.com/kubernetes/kubernetes/issues/102460 | 907,555,711 | 102,460 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI -->
#### Which jobs are failing:
gce-master-scale-correctness
#### Which test(s) are failing:
Around ~50 tests with prefix "Kubernetes e2e suite: [sig-storage] CSI Volumes [Driver: csi-hostpat... | Failing tests: [sig-storage] CSI Volumes [Driver: csi-hostpath] * | https://api.github.com/repos/kubernetes/kubernetes/issues/102452/comments | 27 | 2021-05-31T09:18:03Z | 2021-06-14T17:11:57Z | https://github.com/kubernetes/kubernetes/issues/102452 | 907,283,705 | 102,452 |
[
"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:
pkg/controll... | Is the "ReplicaSet has no controller" log level error appropriate? | https://api.github.com/repos/kubernetes/kubernetes/issues/102442/comments | 6 | 2021-05-31T01:44:42Z | 2021-10-28T02:31:15Z | https://github.com/kubernetes/kubernetes/issues/102442 | 906,962,889 | 102,442 |
[
"kubernetes",
"kubernetes"
] | I've read a lot about this issue on google and noticed people saying these logs are expected nothing to worry about, but I often see the same logs in the pods and I am curious about how I can get rid of them. Why are we seeing these logs exactly? Please shed some light on that.
Secret ended with: too old resource ve... | Secret ended with: too old resource version | https://api.github.com/repos/kubernetes/kubernetes/issues/102440/comments | 7 | 2021-05-30T23:12:55Z | 2021-06-01T20:39:00Z | https://github.com/kubernetes/kubernetes/issues/102440 | 906,909,966 | 102,440 |
[
"kubernetes",
"kubernetes"
] | For structured logging migration we have developed a tool to klog invocations [logcheck](https://github.com/kubernetes/klog/tree/master/hack/tools/logcheck)
For a given directory logcheck validates two things:
* directory is fully migrated - check if there are non-structured logging calls like `klog.Infof`
* usage... | Correctness of InfoS usage should be checked on whole codebase | https://api.github.com/repos/kubernetes/kubernetes/issues/102439/comments | 19 | 2021-05-30T13:39:51Z | 2021-10-06T20:20:32Z | https://github.com/kubernetes/kubernetes/issues/102439 | 906,759,656 | 102,439 |
[
"kubernetes",
"kubernetes"
] | To take ssh of node using ssh nodename, password authentication is enabled in etc/ssh/sshd_config file in GKE, cloud shell got disconnected automatically. After connecting to cloud shell again password authentication is disabled again | [auth] SSH to kubernetes node | https://api.github.com/repos/kubernetes/kubernetes/issues/102438/comments | 4 | 2021-05-30T08:19:51Z | 2021-06-17T01:22:26Z | https://github.com/kubernetes/kubernetes/issues/102438 | 906,677,708 | 102,438 |
[
"kubernetes",
"kubernetes"
] | Original discussion https://github.com/kubernetes/kubernetes/pull/99799#discussion_r588252534
Problem is that in golang slice of struct cannot be passed into slice of interfaces they implement. This is due to difference in memory representation of two slices (cant wait for Generics) . For example
[]corev1.Pods{} c... | Propose plural version for klog.KObj | https://api.github.com/repos/kubernetes/kubernetes/issues/102434/comments | 23 | 2021-05-29T19:46:30Z | 2021-12-10T09:33:11Z | https://github.com/kubernetes/kubernetes/issues/102434 | 906,546,513 | 102,434 |
[
"kubernetes",
"kubernetes"
] | With Kubelet logs fully migrated to structured logging we can measure macro performance improvements related to using JSON logging format. We should use this data to motive more cluster administrators to save on resources.
Requirements:
* Test different logging format to compare. Formats --logging-forma=text, --log... | Kubelet JSON logging performance test | https://api.github.com/repos/kubernetes/kubernetes/issues/102430/comments | 25 | 2021-05-29T10:36:52Z | 2022-09-27T08:39:11Z | https://github.com/kubernetes/kubernetes/issues/102430 | 906,439,884 | 102,430 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
While trying to debug https://github.com/rancher/rke2/issues/914 and https://github.com/longhorn/longhorn/issues/2629 , I noticed that the `kubelet` continuously attempts to incorrectly perform a `MountVolume.SetUp` for a volume attached to a pod that is terminating. This is caused by `delete`ing t... | Kubelet on first start attempting to `MountVolume.SetUp` volume for pod that enters terminating state while kubelet was offline | https://api.github.com/repos/kubernetes/kubernetes/issues/102410/comments | 4 | 2021-05-28T15:14:05Z | 2021-06-01T20:00:49Z | https://github.com/kubernetes/kubernetes/issues/102410 | 905,585,699 | 102,410 |
[
"kubernetes",
"kubernetes"
] | /sig storage
#### What happened:
When upgrade to 1.18 kubernetes, the block volume will can not be cleaned and the PV stayed in Released status due to loop device can not be clean. Because the loop device bind to a wrong directory:
```
incorrect:
/dev/loop20: [0006]:512 (/dev/mapper/vg10000-vg10000_pvc--dff1d5... | kubelet can not auto clean loop device using block volume when upgrade to kuberentes 1.18 | https://api.github.com/repos/kubernetes/kubernetes/issues/102408/comments | 5 | 2021-05-28T14:59:05Z | 2021-10-25T16:09:07Z | https://github.com/kubernetes/kubernetes/issues/102408 | 905,561,215 | 102,408 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
All versions are vulnerable to CVE-2020-28852.
#### What you expected to happen:
Vulnerability to be mitigated.
#### How to reproduce it (as minimally and precisely as possible):
```
golang.org/x/text => golang.org/x/text v0.3.4
```
This line needs to be updated in go.mod to v0.3... | CVE-2020-28852: Update golang.org/x/text to v0.3.5 | https://api.github.com/repos/kubernetes/kubernetes/issues/102407/comments | 3 | 2021-05-28T14:44:09Z | 2021-06-03T21:33:34Z | https://github.com/kubernetes/kubernetes/issues/102407 | 905,536,651 | 102,407 |
[
"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 deplo... | HPA desired replicas not respecting minReplicas when set to 1 | https://api.github.com/repos/kubernetes/kubernetes/issues/102405/comments | 20 | 2021-05-28T14:09:28Z | 2021-12-26T18:11:32Z | https://github.com/kubernetes/kubernetes/issues/102405 | 905,478,650 | 102,405 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
After latest update (Im not doing it regularly) Im facing following error when trying to connect to GCP pods:
```
$ kubectl exec --stdin --tty ingress-nginx-controller-pxhr2 -n ingress-nginx -- bash
panic: Invalid standard handle identifier: 4294967286
goroutine 1 [running]:
k8s.io/kuber... | Winterm issue on Windows 8.1 in kubectl exec | https://api.github.com/repos/kubernetes/kubernetes/issues/102404/comments | 7 | 2021-05-28T13:49:59Z | 2021-06-15T05:00:08Z | https://github.com/kubernetes/kubernetes/issues/102404 | 905,446,252 | 102,404 |
[
"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:
Pods using e... | outerVolumeSpecName should not set as innerVolumeSpecName when reconstructing volume | https://api.github.com/repos/kubernetes/kubernetes/issues/102402/comments | 6 | 2021-05-28T10:03:09Z | 2021-10-29T04:51:26Z | https://github.com/kubernetes/kubernetes/issues/102402 | 905,093,721 | 102,402 |
[
"kubernetes",
"kubernetes"
] | ```
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
namespace: sdn-web
name: kong-access
spec:
podSelector:
matchLabels:
ingress:
- from:
- namespaceSelector:
matchLabels:
tkestack.io/namespaceName: cls-sdncontr-sdn-web
- ipBlock:
cidr: 100.... | networkpolicy not work cidr: 0.0.0.0/0 | https://api.github.com/repos/kubernetes/kubernetes/issues/102398/comments | 12 | 2021-05-28T09:02:54Z | 2021-07-22T20:48:11Z | https://github.com/kubernetes/kubernetes/issues/102398 | 904,996,984 | 102,398 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI -->
#### Which jobs are failing:
- `pr-node-kubelet-serial-crio-cgroupv1`
- `pr-node-kubelet-serial-crio-cgroupv2`
#### Which test(s) are failing:
`E2eNode Suite: [sig-node] Node Container Ma... | Node Container Manager [Serial] Validate Node Allocatable fails on systemd cgroup driver | https://api.github.com/repos/kubernetes/kubernetes/issues/102394/comments | 19 | 2021-05-28T08:24:18Z | 2022-12-14T18:22:05Z | https://github.com/kubernetes/kubernetes/issues/102394 | 904,934,697 | 102,394 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
On some nodes in my cluster I had to restart the CRI (in my case `containerd`) for maintenance reasons via:
```
systemctl stop containerd
# maintenance
systemctl daemon-reload
systemctl start containerd
```
As expected the following events where given by `kubectl describe node $NODE_N... | Proxy healthz start failure after node CRI maintenance | https://api.github.com/repos/kubernetes/kubernetes/issues/102392/comments | 15 | 2021-05-28T07:28:59Z | 2021-11-21T19:46:59Z | https://github.com/kubernetes/kubernetes/issues/102392 | 904,848,544 | 102,392 |
[
"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:
Auth Yaml fi... | Deployments/auth.yaml: No such file or directory | https://api.github.com/repos/kubernetes/kubernetes/issues/102391/comments | 6 | 2021-05-28T07:22:05Z | 2021-09-20T16:40:13Z | https://github.com/kubernetes/kubernetes/issues/102391 | 904,838,274 | 102,391 |
[
"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:
Ref: This is... | Pods stuck as failed with "Pod Predicate NodeAffinity failed" | https://api.github.com/repos/kubernetes/kubernetes/issues/102387/comments | 13 | 2021-05-28T03:19:25Z | 2022-05-12T12:35:24Z | https://github.com/kubernetes/kubernetes/issues/102387 | 904,617,167 | 102,387 |
[
"kubernetes",
"kubernetes"
] | Yesterday, I created a issue about K8s Prometheus monitor: https://github.com/google/cadvisor/issues/2880.
After two days of tracking, I found it's not Prometheus's problem (config or monitor exp).
Same prometheus version, and same config files. When add new label to K8s node, In Kubernetes v1.13 `container_memor... | K8s node add new label, Prometheus pull data not inconsistent | https://api.github.com/repos/kubernetes/kubernetes/issues/102385/comments | 12 | 2021-05-28T02:43:24Z | 2021-10-31T15:08:23Z | https://github.com/kubernetes/kubernetes/issues/102385 | 904,578,558 | 102,385 |
[
"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... | [scheduler] deprecates NodeUnschedulable plugin | https://api.github.com/repos/kubernetes/kubernetes/issues/102384/comments | 7 | 2021-05-28T02:15:58Z | 2021-10-31T05:04:23Z | https://github.com/kubernetes/kubernetes/issues/102384 | 904,549,920 | 102,384 |
[
"kubernetes",
"kubernetes"
] |
#### What happened:
On a cluster with a 3-node control plane, had worker nodes each with a number of high priority DaemonSet pods and a single normal priority StatefulSet pod. The nodes had 220m CPU unallocated.
Updated the spec of a high priority DaemonSet with a 700m CPU request (no change to requests), trigg... | Unnecessary preemption during DaemonSet rolling update | https://api.github.com/repos/kubernetes/kubernetes/issues/102382/comments | 19 | 2021-05-28T00:26:45Z | 2022-06-02T19:33:05Z | https://github.com/kubernetes/kubernetes/issues/102382 | 904,428,458 | 102,382 |
[
"kubernetes",
"kubernetes"
] | #### What would you like to be added:
This issue is about the `JSONSchemaProps` type defined in:
- [k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1](https://github.com/kubernetes/apiextensions-apiserver/blob/41c32f2661cc03c04d3c7e48ccf8107e0f8922b4/pkg/apis/apiextensions/v1/types_jsonschema.go)
- [k8s.io/... | JSONSchemaProps should also support YAML encoding/decoding | https://api.github.com/repos/kubernetes/kubernetes/issues/102380/comments | 3 | 2021-05-27T18:10:34Z | 2021-05-27T20:29:21Z | https://github.com/kubernetes/kubernetes/issues/102380 | 904,050,209 | 102,380 |
[
"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 [Kuber... | kubectl get command not consistent with overlapping resources kind not in the same group | https://api.github.com/repos/kubernetes/kubernetes/issues/102378/comments | 17 | 2021-05-27T16:49:55Z | 2022-01-31T21:40:23Z | https://github.com/kubernetes/kubernetes/issues/102378 | 903,984,180 | 102,378 |
[
"kubernetes",
"kubernetes"
] | #### What would you like to be added:
We need an E2E test for HPA [ContainerResource](https://pkg.go.dev/k8s.io/api/autoscaling/v2beta2#ContainerResourceMetricSource) targets.
#### Why is this needed:
HPA v2beta2 is graduating to stable!
KEP: https://github.com/kubernetes/enhancements/tree/master/keps/sig-a... | Create HPA ContainerResource E2E Test | https://api.github.com/repos/kubernetes/kubernetes/issues/102374/comments | 4 | 2021-05-27T14:49:41Z | 2021-08-13T21:17:32Z | https://github.com/kubernetes/kubernetes/issues/102374 | 903,873,378 | 102,374 |
Subsets and Splits
Unique Owner-Repo Count
Counts the number of unique owner-repos in the dataset, providing a basic understanding of diverse repositories.