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"
] | ### What would you like to be added?
Based on load tests and production data gathered from thousands of production k8s clusters, we have observed that gzip compression in k8s API isn't optimal today. Here's the [full doc with details](https://docs.google.com/document/d/1rMlYKOVyujboAEG2epxSYdx7eyevC7dypkD_kUlBxn4) a... | Revisit response compression in k8s API | https://api.github.com/repos/kubernetes/kubernetes/issues/112296/comments | 17 | 2022-09-07T19:55:30Z | 2023-01-03T18:07:52Z | https://github.com/kubernetes/kubernetes/issues/112296 | 1,365,118,282 | 112,296 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
We're having a Kubernetes installation installed (1.24.4 - using Kubespray)
In our case, we are using a master node with very limited disk space (purposefully), so the default DiskPressure values in Kubernetes need to be adjusted.
I've tried several paths:
1- Tried adding the following to... | KubeletHasDiskPressure on a very limited server | https://api.github.com/repos/kubernetes/kubernetes/issues/112293/comments | 11 | 2022-09-07T18:59:11Z | 2023-02-11T21:19:47Z | https://github.com/kubernetes/kubernetes/issues/112293 | 1,365,069,392 | 112,293 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
After updating my on-premis cluster to 1.23.10 I noticed that services stopped working.
After some investigation I noticed this error recurring in kube-proxy logs:
```
proxier.go:1484] "Failed to execute iptables-restore" err="exit status 1 (iptables-restore: line 1193 failed\n)"
```
### What ... | Failed to execute iptables-restore" err="exit status 1 | https://api.github.com/repos/kubernetes/kubernetes/issues/112292/comments | 9 | 2022-09-07T18:17:15Z | 2022-09-08T20:28:19Z | https://github.com/kubernetes/kubernetes/issues/112292 | 1,365,024,450 | 112,292 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
Make Kubernetes validate correctly the CSI volumes capacity allocated.
### Why is this needed?
## Reproduce
- Create a resourcequota as
```yaml
apiVersion: v1
kind: ResourceQuota
metadata:
name: default-quota
namespace: default
spec:
hard:
... | PVCs capacity can exceed request.storage resource quota | https://api.github.com/repos/kubernetes/kubernetes/issues/112281/comments | 22 | 2022-09-07T12:29:51Z | 2024-01-20T03:10:59Z | https://github.com/kubernetes/kubernetes/issues/112281 | 1,364,591,733 | 112,281 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When I execute the command 'kubectl apply hpa.yaml' toHPA objects using object metrics with Utilization,the console reports an error: 'The HorizontalPodAutoscaler "hpa-cf0e7df160fe42dc8eddf84a58c2622a" is invalid: spec.metrics[2].object.target.averageValue: Required value: must set either a targe... | Cannot create HPA objects using object metrics with Utilization | https://api.github.com/repos/kubernetes/kubernetes/issues/112279/comments | 4 | 2022-09-07T10:19:32Z | 2022-09-29T08:50:06Z | https://github.com/kubernetes/kubernetes/issues/112279 | 1,364,434,387 | 112,279 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
kube-scheduler: do not preempting orphan Pod
### Why is this needed?
Currently, kube-scheduler preempts a Pod by deleting it:
https://github.com/kubernetes/kubernetes/blob/1ab40212a4e6cb10b3ae88c2e6c912a9fc1b1605/pkg/scheduler/framework/preemption/preemption.go#L362-L365... | kube-scheduler: do not preempting orphan Pod | https://api.github.com/repos/kubernetes/kubernetes/issues/112273/comments | 19 | 2022-09-07T04:04:26Z | 2023-01-03T18:27:40Z | https://github.com/kubernetes/kubernetes/issues/112273 | 1,364,057,914 | 112,273 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When there are more than one controller set to true within ownerRef, the validation would return err msg like this:
```
Err: Only one reference can have Controller set to true. Found \"true\" in references for foo and foo"
```
It is confusing to see two same 'foo' controller name.
### Wha... | Confusing to see two same controller name in ownerRef validation | https://api.github.com/repos/kubernetes/kubernetes/issues/112271/comments | 2 | 2022-09-07T03:46:02Z | 2022-11-07T19:20:20Z | https://github.com/kubernetes/kubernetes/issues/112271 | 1,364,048,135 | 112,271 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Based on warnings for pending `kubectl version` output changes, I tried the recommend style with a typo.
`-short` instead of `--short`.
Figured it out, but took a moment due to the odd err shown.
```
$ kubectl version -short
WARNING: This version information is deprecated and will be repl... | Invalid version flag displays DNS error | https://api.github.com/repos/kubernetes/kubernetes/issues/112265/comments | 4 | 2022-09-06T18:15:40Z | 2022-09-07T04:56:14Z | https://github.com/kubernetes/kubernetes/issues/112265 | 1,363,650,211 | 112,265 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
This is really a bug.
Running pod resize E2E tests full scope in GKE 1-master 1-worker setup takes significantly longer (869s vs 2988s to run all 34 E2E tests) Initial investigation shows the the issue is NOT in containerd response to ContainerStatus() CRI API that is called w... | [FG:InPlacePodVerticalScaling] Pod Resize - long delay in updating `apiPodStatus.Resources` | https://api.github.com/repos/kubernetes/kubernetes/issues/112264/comments | 20 | 2022-09-06T16:42:25Z | 2024-11-04T18:31:11Z | https://github.com/kubernetes/kubernetes/issues/112264 | 1,363,554,018 | 112,264 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
client-go uses `KUBERNETES_SERVICE_HOST` to discover the API service address:
https://github.com/kubernetes/kubernetes/blob/67bde9a1023d1805e33d698b28aa6fad991dfb39/staging/src/k8s.io/client-go/rest/config.go#L507-L541
This at odds with the documentation at https://kubernetes.io/docs/tasks/... | client-go's InClusterConfig does not implement documented API discovery heuristics | https://api.github.com/repos/kubernetes/kubernetes/issues/112263/comments | 6 | 2022-09-06T15:34:22Z | 2023-01-18T12:18:36Z | https://github.com/kubernetes/kubernetes/issues/112263 | 1,363,473,075 | 112,263 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
After moving to EKS 1.22.11* (I don't think is related to the distro) port-forwarding on intellij started to be interrupted shortly after start to send data.
I do revert it and problem is gone, I saw some patch in the version that change proxy config can the be related?
### What did you expect t... | port-forward remote debug broken | https://api.github.com/repos/kubernetes/kubernetes/issues/112250/comments | 4 | 2022-09-05T16:47:45Z | 2022-09-07T08:50:41Z | https://github.com/kubernetes/kubernetes/issues/112250 | 1,362,282,943 | 112,250 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When using Dynamic Admission Controllers such as a Mutating or a Validating Webhook configuration pointing to an in-cluster Service backed by multiple endpoints I noticed a reproducible distribution in the request load for a given amount of requests.
### What did you expect to happen?
When u... | kube-apiserver: ResolveEndpoint function is deterministic | https://api.github.com/repos/kubernetes/kubernetes/issues/112246/comments | 9 | 2022-09-05T16:01:00Z | 2022-09-08T09:05:55Z | https://github.com/kubernetes/kubernetes/issues/112246 | 1,362,225,710 | 112,246 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
A node with:
```
$ sudo grep ^topolo /var/lib/kubelet/config.yaml
topologyManager: true
topologyManagerPolicy: single-numa-node
```
fails a pod that uses device plugin resources (empty but non-nil `TopologyHints`) :
```
...
Sep 05 00:35:14 node kubelet[1468778]: I0905 00:35:14.935079... | TopologyManager fails a Pod with AffinityError | https://api.github.com/repos/kubernetes/kubernetes/issues/112234/comments | 10 | 2022-09-05T08:49:58Z | 2022-09-14T14:17:02Z | https://github.com/kubernetes/kubernetes/issues/112234 | 1,361,611,597 | 112,234 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
when set internalTrafficPolicy: true, service of ClusterIP that has no endpoints, iptables rule "--reject-with icmp-port-unreachable" is added.
```
-A KUBE-SERVICES -d 123.123.22.76/32 -p tcp -m comment --comment "default/kubia-local has no endpoints" -m tcp --dport 80 -j REJECT --reject-with icmp... | why service of ClusterIP that has no endpoints is different from service of NodePort that has no endpoints | https://api.github.com/repos/kubernetes/kubernetes/issues/112233/comments | 6 | 2022-09-05T08:35:49Z | 2022-09-15T16:27:00Z | https://github.com/kubernetes/kubernetes/issues/112233 | 1,361,593,754 | 112,233 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
The static CPU manager can reserves full CPU cores for (Guaranteed, integer CPU) pods' init containers.
It supports re-using those reserved CPU cores for main containers, but doesn't enforce (or even favour) their re-use, which can lead to CPU core(s) being left reserved to an init-container wh... | Static CPU Manager can fail with UnexpectedAdmissionError with init-containers requesting integer CPUs | https://api.github.com/repos/kubernetes/kubernetes/issues/112228/comments | 16 | 2022-09-04T18:58:33Z | 2025-02-19T08:54:14Z | https://github.com/kubernetes/kubernetes/issues/112228 | 1,361,226,861 | 112,228 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
To add a `--diff` flag to `kubectl get xxx -w -oyaml` to see the diff lines, like this:
```
kubectl get xxx -w -oyaml | json --diff
```
With this `--diff` flag, we can see the diff lines more clearly, to facilitate resource watching.
Also see the https://github.com/kubernete... | Add `--diff` flag to `kubectl get xxx -w -oyaml` to see the diff lines | https://api.github.com/repos/kubernetes/kubernetes/issues/112224/comments | 8 | 2022-09-04T03:52:50Z | 2023-05-03T11:02:56Z | https://github.com/kubernetes/kubernetes/issues/112224 | 1,361,030,038 | 112,224 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Hi!
I can see my pods are getting killed post probe failure.
Firstly, I can see these two odd logs in my syslog:
```
networkd-dispatcher[781]: WARNING:Unknown index 56 seen, reloading interface list
systemd-udevd[455717]: ethtool: autonegotiation is unset or enabled, the speed and duplex are ... | Pods getting killed after startup probe failure | https://api.github.com/repos/kubernetes/kubernetes/issues/112221/comments | 17 | 2022-09-03T11:18:29Z | 2022-10-13T15:47:57Z | https://github.com/kubernetes/kubernetes/issues/112221 | 1,360,829,559 | 112,221 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
After setting up the master node, worker node couldn't able to join the master. I get the error message - " couldn't validate the identity of the API Server: Get "https://{apiserver-ip}/api/v1/namespaces/kube-public/configmaps/cluster-info?timeout=10s": **dial tcp {kubeapi-ip}:6443: connect: proto... | Kubernetes: couldn't validate the identity of the API Server : protocol not available | https://api.github.com/repos/kubernetes/kubernetes/issues/112210/comments | 5 | 2022-09-02T21:29:12Z | 2022-09-03T07:48:45Z | https://github.com/kubernetes/kubernetes/issues/112210 | 1,360,625,667 | 112,210 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When using many PVCs on a single node (in our case, >200), `kubelet` on INFO level logs many instances of the following and the equivalent call for PVs:
```
Waited for 192.977736ms due to client-side throttling, not priority and fairness, request: GET:https://KUBE_API:443/api/v1/namespaces/NAM... | kubelet: Massive delays for volume reconciliation (including Pod starts) due to client-side throttling of PV/PVC | https://api.github.com/repos/kubernetes/kubernetes/issues/112209/comments | 15 | 2022-09-02T18:26:28Z | 2025-01-18T19:31:15Z | https://github.com/kubernetes/kubernetes/issues/112209 | 1,360,495,414 | 112,209 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
as discussed in https://github.com/kubernetes-sigs/logtools/issues/2 and https://github.com/kubernetes/kubernetes/pull/111708, we should add verbosity Zero Check in logtools
### Why is this needed?
because with V(0) and without V(0) semantically equivalent and V(0) add some (smal... | update logtools to support verbosity Zero Check | https://api.github.com/repos/kubernetes/kubernetes/issues/112206/comments | 7 | 2022-09-02T14:55:06Z | 2023-01-30T13:32:47Z | https://github.com/kubernetes/kubernetes/issues/112206 | 1,360,305,292 | 112,206 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I run k8s v1.24.0 in minikube v1.26.1, When I use my cloud provider to deploy a service in it , it comes out this error:
```console
W0902 07:21:51.180586 1 controllermanager.go:103] detected a cluster without a ClusterID. A ClusterID will be required in the future. Please tag your cluste... | unable to get token for service account: timed out waiting for the condition | https://api.github.com/repos/kubernetes/kubernetes/issues/112201/comments | 6 | 2022-09-02T07:47:44Z | 2022-09-26T14:40:33Z | https://github.com/kubernetes/kubernetes/issues/112201 | 1,359,830,136 | 112,201 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When running on the hardware where the title is located, the following error will occur:
-bash: ./keadm: cannot execute binary file: Exec format error
I tried to compile the arm version myself, but I encountered the following error:
go: github.com/kubeedge/kubeedge@v1.11.1 requires
githu... | The arm release cannot run on ARM chips (raspberry Pi, Kunpeng 920) | https://api.github.com/repos/kubernetes/kubernetes/issues/112196/comments | 6 | 2022-09-02T01:46:07Z | 2022-09-07T12:05:47Z | https://github.com/kubernetes/kubernetes/issues/112196 | 1,359,606,416 | 112,196 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
In GCE cluster startup, kubelet-start (which puts the cluster DNS server into the containerized mounter resolv.conf when the containerized mounter is enabled) race with prepare-mounter-rootfs (which copies the instance resolve.conf into the containerized mounter fs).
This causes domain resolution... | Race between kubelet startup and mounter prepare | https://api.github.com/repos/kubernetes/kubernetes/issues/112194/comments | 2 | 2022-09-01T23:39:52Z | 2022-09-02T02:04:18Z | https://github.com/kubernetes/kubernetes/issues/112194 | 1,359,541,582 | 112,194 |
[
"kubernetes",
"kubernetes"
] | A security issue was discovered in Kubernetes that could allow Windows workloads to run as `ContainerAdministrator` even when those workloads set the `runAsNonRoot` option to `true`.
This issue has been rated low and assigned CVE-2021-25749
### Am I vulnerable?
All Kubernetes clusters with following versions,... | CVE-2021-25749: `runAsNonRoot` logic bypass for Windows containers | https://api.github.com/repos/kubernetes/kubernetes/issues/112192/comments | 3 | 2022-09-01T21:02:01Z | 2022-09-16T07:08:20Z | https://github.com/kubernetes/kubernetes/issues/112192 | 1,359,404,405 | 112,192 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I have a `v1.24.1` based Single Node cluster running (Control Plane taking the workload as well). And the `kube-proxy` is running in IPVS mode.
I am noticing a very odd behavior in terms of the entries under the `ipvsadm` that I am not able to point to a failure point. This behavior is causing... | kube-proxy IPVS - Uncertain behavior on NodePort Entries | https://api.github.com/repos/kubernetes/kubernetes/issues/112185/comments | 25 | 2022-09-01T19:21:06Z | 2024-12-12T06:38:43Z | https://github.com/kubernetes/kubernetes/issues/112185 | 1,359,301,642 | 112,185 |
[
"kubernetes",
"kubernetes"
] | Hi,
My pod deployments are going to pending state when I have multiple profiles(default and custom). Also it's in pending state forever. I don't see any events or logs for this.
I have copied the yaml files below. Please help me with the following:
Why there no logs when there is pending issue?
Why there are ... | Pod Deployment going to pending state when there are multiple profiles | https://api.github.com/repos/kubernetes/kubernetes/issues/112180/comments | 7 | 2022-09-01T16:02:35Z | 2023-02-05T05:50:25Z | https://github.com/kubernetes/kubernetes/issues/112180 | 1,359,080,631 | 112,180 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Running containers in privileged mode is not recommended as privileged containers run with all [linux capabilities](https://man7.org/linux/man-pages/man7/capabilities.7.html) enabled and can access the host's resources. Running containers in privileged mode opens number of security threads such as b... | Document and test minimum privileges to needed run kube-proxy | https://api.github.com/repos/kubernetes/kubernetes/issues/112171/comments | 14 | 2022-09-01T06:19:43Z | 2023-10-25T19:28:49Z | https://github.com/kubernetes/kubernetes/issues/112171 | 1,358,314,085 | 112,171 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
Now when kubelet enable `rotate-certificates` and `bootstrap-kubeconfig`, it will request CSR in background
Consider the following scenario:
1. Hundreds of nodes have been scaled out, these kubelet will request CSR in background and register themself.
2. The kube-controller-ma... | When kubelet enable rotate-certificates and bootstrap, request CSR in foreground | https://api.github.com/repos/kubernetes/kubernetes/issues/112170/comments | 15 | 2022-09-01T04:03:41Z | 2024-11-22T15:02:16Z | https://github.com/kubernetes/kubernetes/issues/112170 | 1,358,215,220 | 112,170 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Running a load test on K8s 1.23.5, and I got some messages like this:
```
\"Inconceivable!\" err=\"dispatch before arrival\" QS=\"system\" queue=0 dispatchR=\"6570.26436833ss\" request=... flowDistinguisher:system:node:[redacted] fsName:system-nodes ... workEstimate:{WorkEstimate:{InitialSeats... | Inconceivable: dispatch before arrival - apparent APF error | https://api.github.com/repos/kubernetes/kubernetes/issues/112169/comments | 25 | 2022-09-01T03:56:51Z | 2024-08-14T05:42:39Z | https://github.com/kubernetes/kubernetes/issues/112169 | 1,358,210,468 | 112,169 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
fake client eviction does not behave as expected in 1.25 release
### What did you expect to happen?
if I Evict a naked pod and then do a List, I expect the pod to not be returned.
### How can we reproduce it (as minimally and precisely as possible)?
The code below will not work on 1.25... | fake client policy/v1 eviction not reflected | https://api.github.com/repos/kubernetes/kubernetes/issues/112168/comments | 16 | 2022-09-01T03:52:06Z | 2024-08-22T20:21:38Z | https://github.com/kubernetes/kubernetes/issues/112168 | 1,358,208,282 | 112,168 |
[
"kubernetes",
"kubernetes"
] | when i run
`kubeadm init --pod-network-cidr=10.244.0.0/16,2001:db8:42:0::/56 --service-cidr=10.96.0.0/16,2001:db8:42:1::/112
`
it worked.but when I setup flannel and run
`kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml`
the kube-flannel's status is always "... | dual-stack | https://api.github.com/repos/kubernetes/kubernetes/issues/112167/comments | 4 | 2022-09-01T03:31:56Z | 2022-09-01T06:08:54Z | https://github.com/kubernetes/kubernetes/issues/112167 | 1,358,198,175 | 112,167 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Running the following command to generate .proto file leads to an error
$ go-to-protobuf -h hack/boilerplate.go.txt --only-idl -p +k8s.io/sample-controller/pkg/apis/samplecontroller/v1alpha1 -o _output/proto
2022/08/31 16:49:02 Unrecognized package: k8s.io/apimachinery/pkg/apis/testapigroup/v1
... | go-to-protobuf not working | https://api.github.com/repos/kubernetes/kubernetes/issues/112164/comments | 6 | 2022-08-31T23:53:55Z | 2022-10-19T14:45:11Z | https://github.com/kubernetes/kubernetes/issues/112164 | 1,358,052,888 | 112,164 |
[
"kubernetes",
"kubernetes"
] | It is possible today to configure multiple kms providers with same name and different config (UDS, cache size, etc.). This does not provide any real value and would be a bug.
**Open questions**
Should we enforce a strict check to not allow this behavior? Any changes to this could be a breaking change.
/kind b... | [KMS] Disallow configuring multiple kms providers with the same name | https://api.github.com/repos/kubernetes/kubernetes/issues/112160/comments | 2 | 2022-08-31T20:23:59Z | 2022-11-08T00:02:08Z | https://github.com/kubernetes/kubernetes/issues/112160 | 1,357,829,835 | 112,160 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Etcdserver exposes a myriad of error codes, see - https://github.com/kubernetes/kubernetes/blob/87721fb71075582a1ee1e89b6a3391813e411a1c/vendor/go.etcd.io/etcd/server/v3/etcdserver/errors.go#L23-L47
While some of those may be non-retriable errors for the k8s client, such as:
```
ErrRequestT... | Apiserver should map etcd errors to proper response status | https://api.github.com/repos/kubernetes/kubernetes/issues/112152/comments | 39 | 2022-08-31T16:04:39Z | 2025-02-12T20:07:03Z | https://github.com/kubernetes/kubernetes/issues/112152 | 1,357,554,576 | 112,152 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When a pod exits, there is some problem in the cgroup cleanup. The containerd cgroup within the kubelet cgroup does not get deleted, and then the kubelet keeps trying to delete the kubelet cgroup, which fails because of the child cgroup. The kubelet continues to try to delete the cgroup every 1 se... | Each time a pod exits, kubelet cpu usage increases with cgroups v2 | https://api.github.com/repos/kubernetes/kubernetes/issues/112151/comments | 24 | 2022-08-31T16:02:11Z | 2023-01-18T14:01:34Z | https://github.com/kubernetes/kubernetes/issues/112151 | 1,357,550,489 | 112,151 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I'm trying to add a control node to my local k8s cluster, but it fails on pulling k8s.gcr.io/coredns:v1.9.3.
```
$ kubeadm join --token <token> <api-endpoint> --discovery-token-ca-cert-hash sha256:<certhash> --control-plane --certificate-key <certkey> -v=3
...snip...
I0831 15:46:08.140872 ... | [kubeadm] cannot pull k8s.gcr.io/coredns:v1.9.3 | https://api.github.com/repos/kubernetes/kubernetes/issues/112148/comments | 5 | 2022-08-31T13:54:54Z | 2022-09-01T08:21:05Z | https://github.com/kubernetes/kubernetes/issues/112148 | 1,357,377,006 | 112,148 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
Allow marking the RootCAConfigMap (kube-root-ca.crt) configmap added to every namesace as immutable to reduce required kubelet watches on a relatively static resource.
https://kubernetes.io/docs/concepts/configuration/configmap/#configmap-immutable
### Why is this needed?
The Ro... | mark RootCAConfigMap kube-root-ca.crt immutable | https://api.github.com/repos/kubernetes/kubernetes/issues/112147/comments | 13 | 2022-08-31T13:26:00Z | 2024-06-17T17:58:53Z | https://github.com/kubernetes/kubernetes/issues/112147 | 1,357,338,001 | 112,147 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
1. create a service without selector, and manual create endpoints for this service
2. endpointslicemirroring controller will create an endpointslice for this service.
3. after endpoint slice created, and kube-controller-manager restart.
4. after kube-controller-manager restart, someone delete thi... | endpointslicemirroring controller not create endpointslice | https://api.github.com/repos/kubernetes/kubernetes/issues/112143/comments | 15 | 2022-08-31T08:41:58Z | 2024-06-18T01:05:56Z | https://github.com/kubernetes/kubernetes/issues/112143 | 1,357,005,623 | 112,143 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
This one involves systemd, DNS, musl, and Kubelet v1.25 😬 👷🏻 🔥
Starting in v1.25.0, pods running on Kubelets on certain nodes with a FQDN hostname (more on that later) will not be able to resolve DNS queries if they're using musl (e.g. alpine:3.16.2, busybox, etc).
```
# OK
kubectl ru... | musl-based DNS resolution will break on v1.25.0 in certain configurations | https://api.github.com/repos/kubernetes/kubernetes/issues/112135/comments | 10 | 2022-08-31T00:23:02Z | 2022-09-12T07:57:49Z | https://github.com/kubernetes/kubernetes/issues/112135 | 1,356,515,650 | 112,135 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
From a fresh installation (clean)
```
echo "Remove all overlays"
umount -R /var/lib/containers/storage/overlay
rm -rf /var/lib/containers
mkdir -p /var/lib/containers/storage/overlay-images
echo "Remove old cluster information"
rm -rf /etc/kubernetes /var/lib/calico /var/lib/kubelet /va... | kubeadm 1.25.0 deployment over yaml pull error coredns:v1.93 | https://api.github.com/repos/kubernetes/kubernetes/issues/112131/comments | 12 | 2022-08-30T20:27:58Z | 2022-12-09T10:06:13Z | https://github.com/kubernetes/kubernetes/issues/112131 | 1,356,266,911 | 112,131 |
[
"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**:
One of our th... | kubectl does not retry after TLS handshake timeout | https://api.github.com/repos/kubernetes/kubernetes/issues/119448/comments | 25 | 2022-08-30T16:56:33Z | 2024-07-30T17:32:49Z | https://github.com/kubernetes/kubernetes/issues/119448 | 1,812,400,263 | 119,448 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
ci-kubernetes-csi-canary-test-on-kubernetes-master, [example](https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-csi-canary-test-on-kubernetes-master/1564570330624692224)
### Which tests are failing?
[It] [sig-storage] CSI mock volume CSI Volume Snapshots [Feature:Vol... | Canary CSI snapshot tests are failing | https://api.github.com/repos/kubernetes/kubernetes/issues/112126/comments | 13 | 2022-08-30T15:08:10Z | 2022-09-12T15:07:26Z | https://github.com/kubernetes/kubernetes/issues/112126 | 1,355,917,967 | 112,126 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I found some grammatical mistakes
In place of :
``` Kubernetes, also known as K8s, is an open source system for managing containerized applications across multiple hosts. It provides basic mechanisms for deployment, maintenance, and scaling of applications. ```
```To use Kubernetes code as a ... | some grammatical mistakes in README.md file | https://api.github.com/repos/kubernetes/kubernetes/issues/112125/comments | 10 | 2022-08-30T13:30:08Z | 2023-05-13T23:07:58Z | https://github.com/kubernetes/kubernetes/issues/112125 | 1,355,777,729 | 112,125 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
After we updated two of our clusters from 1.22 to v1.24.4 we noticed a huge amount of logs (tens of entries per second) in kubelet:
```
kubelet_getters.go:300] "Path does not exist" path="/var/lib/kubelet/pods/86cba354-348c-4826-9837-df9c616a8862/volumes"
```
Neither does the `volumes` subdi... | Huge amount of logs: kubelet_getters.go:300] "Path does not exist" path="/var/lib/kubelet/pods/86cba354-348c-4826-9837-df9c616a8862/volumes" | https://api.github.com/repos/kubernetes/kubernetes/issues/112124/comments | 37 | 2022-08-30T13:28:41Z | 2023-06-28T12:47:57Z | https://github.com/kubernetes/kubernetes/issues/112124 | 1,355,775,628 | 112,124 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
when kubelet restarts, if access /pods api before podStorage's apiserverSource gets ready, the pod list returned is not full，pods from apiserver source are not shown in result.
the code https://github.com/kubernetes/kubernetes/blob/master/pkg/kubelet/server/server.go#L721 returns pods from pod... | kubelet http api /pods returned data not consistent with data from etcd | https://api.github.com/repos/kubernetes/kubernetes/issues/112119/comments | 17 | 2022-08-30T08:01:57Z | 2023-08-09T15:18:38Z | https://github.com/kubernetes/kubernetes/issues/112119 | 1,355,341,428 | 112,119 |
[
"kubernetes",
"kubernetes"
] | Events collect traces of attacks that are not recorded in default audit logs, such as creating cronjobs for attack persistence.
Attackers may delete events to erase the traces of attacks and make it harder to trace, as featured in the [Threat matrix for Kubernetes](https://www.microsoft.com/security/blog/2021/03/23/... | Add recording of Events in audit log for security reasons | https://api.github.com/repos/kubernetes/kubernetes/issues/112117/comments | 6 | 2022-08-30T07:20:54Z | 2023-01-27T09:17:00Z | https://github.com/kubernetes/kubernetes/issues/112117 | 1,355,289,073 | 112,117 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When setting "--container-log-max-files=5" and "--container-log-max-size=9Mi", we only can find two log files for the test container and the file size of one log file exceeds the max size.
```
C:\var\log\pods\default_win-logs-vtlfq_b8fec92f-bedd-42ad-8d3f-ee0718e71581\win-logs
Mode ... | `--container-log-max-files` and `--container-log-max-size` do not work as expected on Windows | https://api.github.com/repos/kubernetes/kubernetes/issues/112114/comments | 6 | 2022-08-30T03:21:17Z | 2022-12-14T01:10:26Z | https://github.com/kubernetes/kubernetes/issues/112114 | 1,355,110,294 | 112,114 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
kubelet calculates memory usage in a different way:
`memUsage = "WorkingSet - Private" / TotalPhysicalMemory`
'WorkingSet - Private" is physical memory used by all the processes, it does not include "cached" memory used by FileSystem.
### What did you expect to happen?
kubelet takes account ... | kubelet reports wrong memory usage on Windows | https://api.github.com/repos/kubernetes/kubernetes/issues/112111/comments | 23 | 2022-08-29T23:31:12Z | 2025-03-03T07:55:07Z | https://github.com/kubernetes/kubernetes/issues/112111 | 1,354,978,832 | 112,111 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I want to get a pod shell to check the file inside the pod, but I can't get a normal terminal to run any command line. I tried in UI tool Lens and my local terminal, and I got the same error. I compared it to my colleague's terminal setting (bashrc), we have the same setting, but I get the wrong pod... | kubectl exec -it get messed up terminal | https://api.github.com/repos/kubernetes/kubernetes/issues/112109/comments | 5 | 2022-08-29T21:36:12Z | 2022-08-30T21:48:02Z | https://github.com/kubernetes/kubernetes/issues/112109 | 1,354,899,323 | 112,109 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
We are getting the below error while mount the pvc volume for the minio. This pvc has 1.7TB and 900GB of data. it not mounting to the pod and container is failed to start with below error.
```
Normal Pulled 47m (x77 over 3h35m) kubelet Container image "minio/minio:RELEASE.2021-10-06T23-36-31Z"... | Error: Kubelet may be retrying requests that are timing out in CRI-O due to system load context deadline exceeded: error reserving ctr name | https://api.github.com/repos/kubernetes/kubernetes/issues/112105/comments | 6 | 2022-08-29T20:28:39Z | 2022-09-15T07:01:09Z | https://github.com/kubernetes/kubernetes/issues/112105 | 1,354,836,476 | 112,105 |
[
"kubernetes",
"kubernetes"
] | Hi All,
My workloads are running in Azure AKS 1.22.11 cluster with No AZs. To ensure high availability across zones, I am planning to move the workload to a new node pool which is of Multi AZ.
The question here is, about Azure AKS Control Plane components. How it will behave in case of zone failures, anyhow workl... | Azure AKS - 1.22.11 Cluster with No AZ's | https://api.github.com/repos/kubernetes/kubernetes/issues/112100/comments | 4 | 2022-08-29T13:41:42Z | 2022-08-30T08:42:54Z | https://github.com/kubernetes/kubernetes/issues/112100 | 1,354,325,836 | 112,100 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
Currently we have `ParseError` here https://github.com/kubernetes/kubernetes/blob/891cbede96ab4b64c48edf25f8bbd331d8731622/pkg/scheduler/framework/types.go#L121-L128
And we'll validate the error like this: https://github.com/kubernetes/kubernetes/blob/891cbede96ab4b64c48edf25f8b... | Extract ParseError from PodInfo | https://api.github.com/repos/kubernetes/kubernetes/issues/112096/comments | 26 | 2022-08-29T09:23:14Z | 2022-10-12T23:45:04Z | https://github.com/kubernetes/kubernetes/issues/112096 | 1,353,971,132 | 112,096 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When upgrading our extended API-Server (https://github.com/onmetal/onmetal-api) to `v1.25.0`, our tests failed with a `panic` in a new branch of the `FieldManager`, the `IgnoreManagedFieldsTimestampsTransformer`.
This part makes checks whether an API object semantically changed using `avoidTimest... | `IgnoreManagedFieldsTimestampsTransformer` causes extended API types with non-default equals to panic | https://api.github.com/repos/kubernetes/kubernetes/issues/112094/comments | 3 | 2022-08-29T08:42:10Z | 2022-09-28T14:56:36Z | https://github.com/kubernetes/kubernetes/issues/112094 | 1,353,919,082 | 112,094 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
sometimes， the jobs will stop create and Perform after when I update the cronjob, such as update the image.
### What did you expect to happen?
I think the update about cronjob resource will not affect the job.
### How can we reproduce it (as minimally and precisely as possible)?
This is an o... | Cronjob v2 controller bugs：jobs will be pending after when update cronjob | https://api.github.com/repos/kubernetes/kubernetes/issues/112092/comments | 17 | 2022-08-29T07:00:07Z | 2024-06-26T08:00:40Z | https://github.com/kubernetes/kubernetes/issues/112092 | 1,353,802,863 | 112,092 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I have 3 `EC2` instances on AWS, (`1 Master`, `2 Workers`)
I went through the [official docs](https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/install-kubeadm/)
My steps:
1) Create 1 Ubuntu Control Plane machine (`t2.medium`)
2) Create 2 Ubuntu Worker machines (`t2.l... | Api Server pod automaticaaly restart | https://api.github.com/repos/kubernetes/kubernetes/issues/112082/comments | 4 | 2022-08-27T08:20:44Z | 2022-08-27T08:49:26Z | https://github.com/kubernetes/kubernetes/issues/112082 | 1,352,982,180 | 112,082 |
[
"kubernetes",
"kubernetes"
] | See #107329
OpenShift found issues rendering updated ConfigMaps to pods. When ConfigMaps get updated within the API, they do not get rendered to the resulting pod's filesystem by the Kubelet with the following error:
```
Aug 26 20:22:30 test1-lkz4t-master-1 kubenswrapper[1474]: E0826 20:22:30.751336 1474 nest... | when updated ConfigMaps to pods，pod's filesystem by the Kubelet get errors | https://api.github.com/repos/kubernetes/kubernetes/issues/112081/comments | 11 | 2022-08-27T04:32:28Z | 2023-07-24T10:03:55Z | https://github.com/kubernetes/kubernetes/issues/112081 | 1,352,939,071 | 112,081 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I've just noticed that [minReadySeconds](https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#minimum-ready-seconds) does not work in statefulset with [parallel podManagementPolicy](https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#parallel-pod-management).
... | MinReadySeconds in statefulset does not work with parallel podManagementPolicy | https://api.github.com/repos/kubernetes/kubernetes/issues/112066/comments | 10 | 2022-08-26T13:13:31Z | 2024-01-23T14:20:13Z | https://github.com/kubernetes/kubernetes/issues/112066 | 1,352,252,204 | 112,066 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When enable apiserver tracing, the webhook request spans only show spanName as `GET`/`POST`, mostly because `opentelemetry-go v0.20.0` use http request operations as default span name, https://github.com/open-telemetry/opentelemetry-go-contrib/blob/v0.20.0/instrumentation/net/http/otelhttp/handler.... | Tracing: precise spanName of apiserver webhook requests | https://api.github.com/repos/kubernetes/kubernetes/issues/112059/comments | 14 | 2022-08-26T10:05:08Z | 2024-04-18T08:03:02Z | https://github.com/kubernetes/kubernetes/issues/112059 | 1,352,049,738 | 112,059 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
The default values of kubelet hard eviction's parameters are:
```
memory.available: "100Mi"
nodefs.available: "10%"
nodefs.inodesFree: "5%"
imagefs.available: "15%
```
We changed it's one of the parameters from their default value as:
`memory.available: "500Mi"`
Then, on checking the conf... | Default values of Kubelet's EvictionHard aren't inherited if one of its parameters was changed | https://api.github.com/repos/kubernetes/kubernetes/issues/112057/comments | 9 | 2022-08-26T09:45:37Z | 2022-09-14T01:58:16Z | https://github.com/kubernetes/kubernetes/issues/112057 | 1,352,027,227 | 112,057 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
We ran some tests on Burst downloading images on the cluster and came to the conclusion that the kubelet rules not being followed (possibly qps is as well). It appears that the kubelet will just send the requests to the cri on the node without checking the status of what's downloading when in .
`... | QPS and Burst in kubelet are not being followed | https://api.github.com/repos/kubernetes/kubernetes/issues/112044/comments | 15 | 2022-08-25T20:21:29Z | 2024-10-23T17:45:11Z | https://github.com/kubernetes/kubernetes/issues/112044 | 1,351,406,464 | 112,044 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
The apiserver etcd3 metrics `etcd_request_duration_seconds` and `etcd_bookmark_counts` treat all CustomResourceDefinitions as `*unstructured.Unstructured` instead of as individual group-resources. This makes it impossible to distinguish these metrics per CRD type.
### What did you expect to happen?... | apiserver etcd3 metrics groups all CRDs as *unstructured.Unstructured | https://api.github.com/repos/kubernetes/kubernetes/issues/112041/comments | 2 | 2022-08-25T18:39:59Z | 2022-08-30T20:21:07Z | https://github.com/kubernetes/kubernetes/issues/112041 | 1,351,299,189 | 112,041 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I am using the below nodeSelector and topologySpreadConstraints in my deployment
```
spec:
replicas: 4
spec:
nodeSelector:
product: v1
topologySpreadConstraints:
- maxSkew: 1
topologyKey: product
whenUnsatisfiable: DoNotSchedule
... | topologySpreadConstraints not working as expected with nodeSelector | https://api.github.com/repos/kubernetes/kubernetes/issues/112040/comments | 7 | 2022-08-25T18:37:27Z | 2022-08-31T06:39:55Z | https://github.com/kubernetes/kubernetes/issues/112040 | 1,351,296,778 | 112,040 |
[
"kubernetes",
"kubernetes"
] | Seen in all gce jobs like
https://storage.googleapis.com/kubernetes-jenkins/pr-logs/pull/110470/pull-kubernetes-e2e-gce-ubuntu-containerd/1562786578244308992/artifacts/e2e-92b275a2f4-a7d53-master/kube-apiserver.log
https://storage.googleapis.com/kubernetes-jenkins/pr-logs/pull/batch/pull-kubernetes-e2e-gce-ubunt... | [CI] pull-kubernetes-e2e-gce jobs using "Unavailble Services" | https://api.github.com/repos/kubernetes/kubernetes/issues/112036/comments | 5 | 2022-08-25T14:38:45Z | 2022-11-18T14:34:13Z | https://github.com/kubernetes/kubernetes/issues/112036 | 1,351,008,009 | 112,036 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
The metric `scheduler_goroutines` is not called in some instances where we initiate routines, like when we call Parallelize
### What did you expect to happen?
We increase the counter every time we create a routine.
### How can we reproduce it (as minimally and precisely as possible)?
N/A
### An... | Some scheduler goroutines are not tracked in the metric | https://api.github.com/repos/kubernetes/kubernetes/issues/112034/comments | 12 | 2022-08-25T13:30:06Z | 2023-05-03T01:39:47Z | https://github.com/kubernetes/kubernetes/issues/112034 | 1,350,905,245 | 112,034 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When installing stacked HA cluster on Ubuntu:
```
LOAD_BALANCER_DNS_LOAD_BALANCER_PORT=192.170.1.165:6443
sudo kubeadm init --v=9 --control-plane-endpoint "$LOAD_BALANCER_DNS_LOAD_BALANCER_PORT" --upload-certs
```
```
nc -v 192.170.1.165 6443
Connection to 192.170.1.165 6443 port [t... | kubeadm init - unable to create ConfigMap | https://api.github.com/repos/kubernetes/kubernetes/issues/112033/comments | 3 | 2022-08-25T12:37:57Z | 2022-08-25T14:48:31Z | https://github.com/kubernetes/kubernetes/issues/112033 | 1,350,832,146 | 112,033 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
The port forwarding client leaks memory when a port forwarding session is reused over time.
### What did you expect to happen?
The port forwarder client should not leak memory.
### How can we reproduce it (as minimally and precisely as possible)?
1. Start forwarding a port with kubectl.
2. Crea... | Memory leak in port forwarding client | https://api.github.com/repos/kubernetes/kubernetes/issues/112032/comments | 3 | 2022-08-25T12:21:38Z | 2022-09-15T13:47:26Z | https://github.com/kubernetes/kubernetes/issues/112032 | 1,350,812,272 | 112,032 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
There are cases when selected by HPAs Pod sets overlap due to misconfiguration:
**Example 1:**
_Deployment A_ (with controlling _HPA A_) has selector:
```
...
spec:
selector:
matchLabels:
pod: a
...
```
_Deployment B_ (with controlling _HPA B_) has selector:
```
...
... | Undefined behaviour when selected pods overlap in HPA | https://api.github.com/repos/kubernetes/kubernetes/issues/112027/comments | 3 | 2022-08-25T07:44:41Z | 2023-11-01T03:31:10Z | https://github.com/kubernetes/kubernetes/issues/112027 | 1,350,469,344 | 112,027 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
The lock acquired by tryAcquireOrRenew is released when the leader ends leadership. However, due to the cancellation of the context, the lock may be set as an empty lock, so the Update cannot be run normally, resulting in a failure to release the lock.
### What did you expect to happen?
The lock c... | [client-go] sometimes the leader could not release his lock properly in leaderelection | https://api.github.com/repos/kubernetes/kubernetes/issues/112023/comments | 6 | 2022-08-25T04:08:29Z | 2022-09-07T15:52:38Z | https://github.com/kubernetes/kubernetes/issues/112023 | 1,350,291,899 | 112,023 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
crio-e2e tests
### Which tests are failing?
The following tests fail when run on a node with SELinux enabled:
```
30174:{"msg":"FAILED [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should provide basic identity","completed":98,"skipped":1006,"failed":1,"fail... | StatefulSet Basic StatefulSet functionality tests fail due to incorrect selinux labels | https://api.github.com/repos/kubernetes/kubernetes/issues/112020/comments | 3 | 2022-08-25T00:40:25Z | 2022-12-23T20:35:29Z | https://github.com/kubernetes/kubernetes/issues/112020 | 1,350,166,036 | 112,020 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When I use the command
`kubectl rollout restart deployment --selector "label=value"`
I get this error: unknown flag: --selector
Even though the flag is clearly indicated in the examples of the rollout command in the reference docs
### What did you expect to happen?
A restart of all deploymen... | The --selector flag in kubectl rollout restart not recognized | https://api.github.com/repos/kubernetes/kubernetes/issues/112018/comments | 5 | 2022-08-24T20:23:59Z | 2022-08-29T08:54:29Z | https://github.com/kubernetes/kubernetes/issues/112018 | 1,349,983,475 | 112,018 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
1. Create a deployment with N replicas and AzureDisk Volume (for example).
2. Shutdown the Node in which Pods resident.
3. Wait until the Node goes into `NotReady` state and Pods go into `Terminating` state( it can't be really deleted since Node is down ) and new Pods are generated automatically... | Pod with volume attached to a node can't failover when the node goes down | https://api.github.com/repos/kubernetes/kubernetes/issues/112016/comments | 17 | 2022-08-24T16:53:07Z | 2023-07-20T02:53:24Z | https://github.com/kubernetes/kubernetes/issues/112016 | 1,349,756,796 | 112,016 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I applied a new configuration to a series of statefulsets that changed a configMap volume into a projected volume. Some, but not all, of the statefulsets merged the volume definition so that the volume had two types, and later when the pods were replaced, they failed because `Forbidden: may not spec... | Kubectl apply sometimes merges different volume types | https://api.github.com/repos/kubernetes/kubernetes/issues/112014/comments | 13 | 2022-08-24T16:08:00Z | 2024-06-21T13:59:39Z | https://github.com/kubernetes/kubernetes/issues/112014 | 1,349,694,671 | 112,014 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When we limited the number of pods for the namespace (let's say 2), then after we deployed the StatefulSet with 5 replicas. Only 2 pods were launched. This is expected behavior but when we see the status of StatefulSet it shows only 1 pod under the `Ready` column. It should show 2 pods in the column... | Statefuleset/DaemonSet reports invalid status due to ResourceQuota. | https://api.github.com/repos/kubernetes/kubernetes/issues/112010/comments | 36 | 2022-08-24T11:52:59Z | 2023-01-12T16:46:47Z | https://github.com/kubernetes/kubernetes/issues/112010 | 1,349,320,508 | 112,010 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Using helm, I upgraded a deployment and the k8s started replacing the pods and while it replaced all the pods successfully, some of the pods that were replaced got stuck in ```ContainerCreating``` status:
```
NAME READY STATUS.
demo-... | Some pods get stuck in ContainerCreating status after being replaced by another pod | https://api.github.com/repos/kubernetes/kubernetes/issues/112009/comments | 19 | 2022-08-24T10:15:54Z | 2025-01-22T18:45:41Z | https://github.com/kubernetes/kubernetes/issues/112009 | 1,349,200,552 | 112,009 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
While testing Encryption at rest feature https://kubernetes.io/docs/tasks/administer-cluster/encrypt-data/
Normally encrypted secret is prefixed with the name of the key that encrypted it.
When I randomly deleted some kube-apiserver pods and job that runs this script [1].
I got a secret... | randomly killing kube-apiserver pods can make secret without the encryption key prefix | https://api.github.com/repos/kubernetes/kubernetes/issues/112001/comments | 19 | 2022-08-24T09:19:26Z | 2022-10-18T15:52:23Z | https://github.com/kubernetes/kubernetes/issues/112001 | 1,349,129,242 | 112,001 |
[
"kubernetes",
"kubernetes"
] | test | test | https://api.github.com/repos/kubernetes/kubernetes/issues/111996/comments | 2 | 2022-08-24T06:56:24Z | 2022-08-24T06:57:53Z | https://github.com/kubernetes/kubernetes/issues/111996 | 1,348,959,143 | 111,996 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
containerd github.com/containerd/containerd v1.6.8 9cd3357b7fd7218e4aec3eae239db1f68a5a6ec6
running 1.25.0
```
Aug 24 14:27:54 docker-test4 containerd[8211]: time="2022-08-24T14:27:54.157014109+08:00" level=error msg="RunPodSandbox for &PodSandboxMetadata{Name:etcd-docker-test4,Uid:f46d0... | can't running kubernetes 1.25.0 in containerd 1.6.8 | https://api.github.com/repos/kubernetes/kubernetes/issues/111995/comments | 8 | 2022-08-24T06:45:50Z | 2022-09-10T22:21:19Z | https://github.com/kubernetes/kubernetes/issues/111995 | 1,348,949,618 | 111,995 |
[
"kubernetes",
"kubernetes"
] | Broken Blogs and docs Links for [Change log](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.25.md#changelog-since-v1240)
| Broken Links on Release note CHANGELOG 1.25 | https://api.github.com/repos/kubernetes/kubernetes/issues/111989/comments | 8 | 2022-08-24T06:12:45Z | 2023-01-22T23:34:22Z | https://github.com/kubernetes/kubernetes/issues/111989 | 1,348,919,486 | 111,989 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
https://github.com/kubernetes/kubernetes/blob/5fa65e989bbc949c3cb4fb3a155d39bf49d8b9b1/staging/src/k8s.io/kubectl/pkg/describe/describe.go#L1974
The above `scheme.Scheme.ConvertFieldLabel` can only process `metadata.name` and `metadata.namespace` field, because the `fieldLabelConversionFuncs` m... | The scheme used by kubectl has no registered FieldLabelConversionFunc | https://api.github.com/repos/kubernetes/kubernetes/issues/111987/comments | 12 | 2022-08-24T04:39:29Z | 2024-10-13T18:36:31Z | https://github.com/kubernetes/kubernetes/issues/111987 | 1,348,853,338 | 111,987 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
In v1.25.0, invoking the DeleteCollection API with a non-empty request body fails with HTTP 500 - the error message is `no kind "DeleteOptions" is registered for version "meta.k8s.io/v1" in scheme "pkg/api/legacyscheme/scheme.go:30"`
All DeleteCollection APIs are specced (in the OpenAPI spec, e... | DeleteCollection API fails if request body is non-empty | https://api.github.com/repos/kubernetes/kubernetes/issues/111985/comments | 13 | 2022-08-24T03:21:55Z | 2023-01-31T16:31:16Z | https://github.com/kubernetes/kubernetes/issues/111985 | 1,348,792,353 | 111,985 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
The following code is slightly wrong:
```
f := framework.NewDefaultFramework("foo")
AfterEach(func() {
// do something with f.ClientSet
})
```
It's wrong because f.AfterEach runs first and clear f.ClientSet.
We can make such code work as intended by switching t... | e2e: use DeferCleanup for Framework instance | https://api.github.com/repos/kubernetes/kubernetes/issues/111979/comments | 2 | 2022-08-23T20:35:18Z | 2022-09-09T23:17:24Z | https://github.com/kubernetes/kubernetes/issues/111979 | 1,348,515,429 | 111,979 |
[
"kubernetes",
"kubernetes"
] | ref: https://github.com/kubernetes/enhancements/tree/master/keps/sig-auth/3299-kms-v2-improvements
/sig auth | [KMSv2] Allow encryption for all resources */* | https://api.github.com/repos/kubernetes/kubernetes/issues/111977/comments | 10 | 2022-08-23T17:20:51Z | 2023-03-09T21:07:11Z | https://github.com/kubernetes/kubernetes/issues/111977 | 1,348,284,632 | 111,977 |
[
"kubernetes",
"kubernetes"
] | Hi Team,
one of Kafka node becomes unresponsive on Strimzi Kafka cluster which running on kubernetes cluster with below error on that specific node.
kubelet_node_status.go:402] Error updating node status, will retry: error getting node "node11.dc02.its.myorgcorp.net": an error on the server ("") has prevented the... | Authorization error (user=kube-apiserver-kubelet-client, verb=get, resource=nodes, subresource=metrics) | https://api.github.com/repos/kubernetes/kubernetes/issues/111976/comments | 4 | 2022-08-23T15:27:01Z | 2022-08-29T08:50:14Z | https://github.com/kubernetes/kubernetes/issues/111976 | 1,348,138,211 | 111,976 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
once the we hit a beta release, we can reset the default value for strict handling to false to prep for 1.26.
/kind cleanup
/priority important-soon
/milestone v1.26
/assign
/cc @deads2k | reset deleted_kinds strictRemovedHandlingInAlpha to false after beta | https://api.github.com/repos/kubernetes/kubernetes/issues/111972/comments | 6 | 2022-08-23T13:07:01Z | 2022-11-16T06:59:38Z | https://github.com/kubernetes/kubernetes/issues/111972 | 1,347,930,282 | 111,972 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
The Kubelet reports in the Node Status an aggregate for Ephemeral storage space in Allocatable and Capacity. The drawback to this is when a different partition - not the root partition - is mounted to `/var/lib/kubelet` or `/var/lib/containers`. The Ephemeral storage values reported do not reflect t... | Kubelet Ephemeral Storage by Disk | https://api.github.com/repos/kubernetes/kubernetes/issues/111965/comments | 7 | 2022-08-22T17:30:18Z | 2022-09-14T19:11:02Z | https://github.com/kubernetes/kubernetes/issues/111965 | 1,346,759,929 | 111,965 |
[
"kubernetes",
"kubernetes"
] | - [x] Create a new project for sig-auth
- We're using the classic board today: https://github.com/orgs/kubernetes/projects/54 and want to migrate to use the new board
- [x] Use github actions to automate board sync
- xref: https://github.com/kubernetes-sigs/sig-windows-tools/blob/master/hack/sync-project-board... | [sig-auth] New project board and use github actions for board sync | https://api.github.com/repos/kubernetes/kubernetes/issues/111963/comments | 6 | 2022-08-22T16:30:16Z | 2023-05-18T21:53:29Z | https://github.com/kubernetes/kubernetes/issues/111963 | 1,346,686,284 | 111,963 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
In https://github.com/cilium/cilium/issues/20981, cilium agent fall back to `/proc/timer_list` to get kernel HZ when OS distribution like Ubuntu 22.04 does not have `/proc/config.gz` or `/boot/config-release` to get kernel HZ. but cilium agent does not run in privilege mode, so cil... | Move /proc/timer_list from defaultMaskedPaths to defaultReadonlyPaths | https://api.github.com/repos/kubernetes/kubernetes/issues/111962/comments | 5 | 2022-08-22T15:04:10Z | 2022-09-25T19:37:23Z | https://github.com/kubernetes/kubernetes/issues/111962 | 1,346,564,776 | 111,962 |
[
"kubernetes",
"kubernetes"
] | # Progress <code>[6/6]</code>
- [X] APISnoop org-flow: [CoreV1ResourceQuotaStatusTest.org](https://github.com/apisnoop/ticket-writing/blob/master/CoreV1ResourceQuotaStatusTest.org)
- [X] Test approval issue: #111956
- [X] Test PR: #111957
- [x] Two weeks soak start date: [testgrid-link](https://testgrid.k... | Write e2e test for ResourceQuota status +3 Endpoints | https://api.github.com/repos/kubernetes/kubernetes/issues/111956/comments | 3 | 2022-08-22T12:09:45Z | 2022-11-02T02:59:38Z | https://github.com/kubernetes/kubernetes/issues/111956 | 1,346,299,160 | 111,956 |
[
"kubernetes",
"kubernetes"
] | As part of the LFX mentorship, I try to integrate the Pod Security Admission with Kyverno to provide native admission enforcement for finer-grained controls. I presented a demo at [the sig-auth meeting](https://www.youtube.com/watch?v=etGq-IKxZRk&list=PL69nYSiGNLP0VMOZ-V7-5AchXTHAQFzJw&index=2). For design specificatio... | Formalized `CheckResult` | https://api.github.com/repos/kubernetes/kubernetes/issues/111958/comments | 14 | 2022-08-22T07:51:55Z | 2024-03-26T09:18:36Z | https://github.com/kubernetes/kubernetes/issues/111958 | 1,346,339,864 | 111,958 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When a job is started with `activeDeadlineSeconds` param the duration currently is considered as soon as the job controller reports the job as running but it may not be the case that pods are running. In our case, All pods associated with the job are in the `Pending` phase.
### What did you expect... | Support active deadline in jobs since the time the pod started | https://api.github.com/repos/kubernetes/kubernetes/issues/111948/comments | 28 | 2022-08-21T13:16:50Z | 2024-10-18T10:14:59Z | https://github.com/kubernetes/kubernetes/issues/111948 | 1,345,485,450 | 111,948 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
If a user starts an [inotify](https://man7.org/linux/man-pages/man7/inotify.7.html) watch for a file on a mounted `Secret` volume, updating the Secret resource (changing the contents of the watched file) causes an inotify event [**`IN_DELETE_SELF`**](https://man7.org/linux/man-pages/man7/inotify... | kubelet: Updating files from Secret volumes causes DELETE_SELF inotify event on user-visible symlink | https://api.github.com/repos/kubernetes/kubernetes/issues/111947/comments | 4 | 2022-08-21T03:18:44Z | 2022-08-21T06:58:49Z | https://github.com/kubernetes/kubernetes/issues/111947 | 1,345,372,725 | 111,947 |
[
"kubernetes",
"kubernetes"
] | GinkgoV1 doesn't support to run Serial and Parallel tests in the same suite, this caused us to set up different jobs for Serial tests.
@onsi implemented this long standing request in V2 , so users can run Serial tests at the same time, Ginkgo will do the magic
> Serial allows the user to mark specs and containers... | E2E run serial tests in parallel suite | https://api.github.com/repos/kubernetes/kubernetes/issues/111944/comments | 20 | 2022-08-20T09:35:44Z | 2024-10-24T20:59:54Z | https://github.com/kubernetes/kubernetes/issues/111944 | 1,345,107,901 | 111,944 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
apiserver panic by some requests, and finally it will crash to restart ,and this situation will replay after one day
```bash
2022-08-17T23:23:26.190411273+08:00 stderr F E0817 15:23:26.190027 1 wrap.go:39] apiserver panic'd on GET /api/v1/namespaces/kube-system/pods?continue=eyJ2IjoibWV... | 1.18: kube-apiserver: fatal error: concurrent map writes | https://api.github.com/repos/kubernetes/kubernetes/issues/111943/comments | 11 | 2022-08-20T09:05:39Z | 2024-03-05T23:52:16Z | https://github.com/kubernetes/kubernetes/issues/111943 | 1,345,101,065 | 111,943 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
control-plane stays in the status `NotReady`.
```bash
# kubectl get nodes
NAME STATUS ROLES AGE VERSION
tomoyafujita NotReady control-plane 20s v1.24.4
```
### What did you expect to happen?
control-plane becomes `Ready` state.
### How can we reproduce i... | control-plane is stuck with status `NotReady` | https://api.github.com/repos/kubernetes/kubernetes/issues/111940/comments | 6 | 2022-08-19T23:33:53Z | 2022-08-21T12:01:48Z | https://github.com/kubernetes/kubernetes/issues/111940 | 1,344,978,609 | 111,940 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When there are conflicting pdbs the api server errors on the conflict but doesn't name the podisruption budgets in question.
### What did you expect to happen?
Include the names of at least 2 of the pdbs in the error message otherwise this leads to confusion especially if the cluster operator doi... | Better user error for confliciting pdbs | https://api.github.com/repos/kubernetes/kubernetes/issues/111939/comments | 7 | 2022-08-19T22:33:48Z | 2023-02-25T16:56:23Z | https://github.com/kubernetes/kubernetes/issues/111939 | 1,344,947,108 | 111,939 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Been having issues on this new cluster I've built with k8s
pod1
`MountVolume.SetUp failed for volume "kube-api-access-2qx96" : object "app"/"kube-root-ca.crt" not registered
`
pod2
```
MountVolume.SetUp failed for volume "kube-api-access-8x9l6" : object "app"/"kube-root-ca.crt" not registere... | Core certificate not being created within startup | https://api.github.com/repos/kubernetes/kubernetes/issues/111938/comments | 4 | 2022-08-19T19:31:22Z | 2022-09-25T22:01:28Z | https://github.com/kubernetes/kubernetes/issues/111938 | 1,344,825,888 | 111,938 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Hi - a user reported an issue were server-side apply (ssa) stopped working.
ref: https://github.com/knative/operator/issues/1184
tl;dr as we update our CRD schema we drop versions. Prior to dropping versions we run migration jobs so that only the latest storage version is present in the CRD ... | managedField entry for a removed API version prevent further resource updates | https://api.github.com/repos/kubernetes/kubernetes/issues/111937/comments | 23 | 2022-08-19T16:07:56Z | 2025-03-03T12:57:31Z | https://github.com/kubernetes/kubernetes/issues/111937 | 1,344,634,327 | 111,937 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
1. Create a Deployment or SS that uses a vsphere CSI volumes (for example).
2. Shutdown the node while pod was running.
3. Wait for node to go `NotReady` and pod to switch to `Terminating` state.
4. Bring back the node up.
5. If the pod migrates to different node (or pod gets deleted), then fil... | CSI volumes left overs are not cleaned up if CSI plugin is attachable | https://api.github.com/repos/kubernetes/kubernetes/issues/111933/comments | 9 | 2022-08-19T13:24:26Z | 2023-04-11T22:35:43Z | https://github.com/kubernetes/kubernetes/issues/111933 | 1,344,441,382 | 111,933 |
[
"kubernetes",
"kubernetes"
] | I have looked through the code but can't seem to find a way to monitor for graceful and ungrateful pod termination i.e pods that terminate gracefully (respecting the grace-period set) and pods that do not and the corresponding events.
Can someone point me in the right direction?
/sig <cluster-lifecycle> | Inability to monitor for graceful and ungraceful pod termination | https://api.github.com/repos/kubernetes/kubernetes/issues/111931/comments | 7 | 2022-08-19T12:12:31Z | 2023-01-19T12:50:25Z | https://github.com/kubernetes/kubernetes/issues/111931 | 1,344,359,500 | 111,931 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Hi All,
I am trying to follow the instruction for using [Endpoints ](https://kubernetes.io/docs/concepts/services-networking/service/) objects to ask a Service object to distribute the load between Pods with specific IP addresses instead of any Pod with a matching label/selector.
However, Endpo... | Endpoints objects fail to affect Service objects that previously had Selectors | https://api.github.com/repos/kubernetes/kubernetes/issues/111929/comments | 13 | 2022-08-19T10:57:00Z | 2022-10-13T16:04:11Z | https://github.com/kubernetes/kubernetes/issues/111929 | 1,344,283,020 | 111,929 |
Subsets and Splits
Unique Owner-Repo Count
Counts the number of unique owner-repos in the dataset, providing a basic understanding of diverse repositories.