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?
I have encountered an issue where duplicate tolerations exist within the tolerations array of Kubernetes Deployment YAML. Despite being duplicates, these tolerations are not being ignored as I would have expected, which in my case led to duplicate metric samples produced by the kub... | Duplicate Tolerations | https://api.github.com/repos/kubernetes/kubernetes/issues/124881/comments | 9 | 2024-05-15T06:44:23Z | 2024-11-21T15:09:22Z | https://github.com/kubernetes/kubernetes/issues/124881 | 2,297,001,950 | 124,881 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Linux 6.6 comes with a new job scheduler called EEVDF (Earliest Eligible Virtual Deadline First), replacing the old CFS.
The kubelet/containerd failed to create cgroup
### What did you expect to happen?
Kubelet/containerd is compatible with linux EEVDF scheduler
### How can we reproduc... | Linux 6.6 EEVDF scheduler on Kubernetes: openat2 /sys/fs/cgroup/kubepods.slice/cpu.weight: no such file or directory | https://api.github.com/repos/kubernetes/kubernetes/issues/124879/comments | 3 | 2024-05-15T02:35:10Z | 2024-05-21T12:03:10Z | https://github.com/kubernetes/kubernetes/issues/124879 | 2,296,725,610 | 124,879 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
`EphemeralContainerStatuses` is not normalized in `normalizeStatus()` in the status manager:
https://github.com/kubernetes/kubernetes/blob/cade1dddd81eba338df85de7b5d17324a87243b5/pkg/kubelet/status/status_manager.go#L1026-L1043
This does not seem to cause any user facing problem because `Ephem... | Status manager does not normalize ephemeral container statuses | https://api.github.com/repos/kubernetes/kubernetes/issues/124873/comments | 6 | 2024-05-14T20:51:03Z | 2024-09-14T17:21:14Z | https://github.com/kubernetes/kubernetes/issues/124873 | 2,296,394,943 | 124,873 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I was running some pods on my node as usual.
At some point (23:41:35.127989 in the log), the kubelet crashed and then went into a crash loop.
Log showing the first crash and several thereafter: [kubelet-crash.txt](https://github.com/kubernetes/kubernetes/files/15312195/kubelet-crash.txt)
Th... | kubelet crash loop panic with SIGSEGV | https://api.github.com/repos/kubernetes/kubernetes/issues/124871/comments | 10 | 2024-05-14T18:02:00Z | 2024-12-20T09:30:53Z | https://github.com/kubernetes/kubernetes/issues/124871 | 2,296,059,914 | 124,871 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
when disk fills, it hits the hard eviction threshold, causing node disk pressure in the same moment imagegc spots it should prune something and start acting. this casues node going into disk pressure and evicting pods and not just start imagegc soon enough
### What did you expect to happen?
... | image-gc-high-threshold should be lower than value causing hard eviction nodefs.available or imagefs.available | https://api.github.com/repos/kubernetes/kubernetes/issues/124868/comments | 12 | 2024-05-14T12:46:56Z | 2024-12-20T20:23:14Z | https://github.com/kubernetes/kubernetes/issues/124868 | 2,295,352,453 | 124,868 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Setting the Volume subpath option at deployment with an NFS PV with a mount option (e.g. nosuid) does not mount accordingly. If no SubPath is set and the NFS PV is set to the /nfs_share/directory the mount works with the nosuid.
### What did you expect to happen?
should be mounted with correct mou... | NFS PV mountOptions does not work when Volume SubPath option is set | https://api.github.com/repos/kubernetes/kubernetes/issues/124863/comments | 9 | 2024-05-14T04:39:46Z | 2024-10-04T14:02:35Z | https://github.com/kubernetes/kubernetes/issues/124863 | 2,294,386,487 | 124,863 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
https://testgrid.k8s.io/sig-release-1.30-blocking#gce-cos-k8sbeta-alphafeatures
https://testgrid.k8s.io/sig-release-1.30-blocking#gce-cos-k8sbeta-default
https://testgrid.k8s.io/sig-release-1.30-blocking#gce-cos-k8sbeta-ingress
https://testgrid.k8s.io/sig-release-1.30-blocking#gce-cos-k8... | [Failing Test] multi ci gce-cos-k8sbeta-* | https://api.github.com/repos/kubernetes/kubernetes/issues/124861/comments | 5 | 2024-05-14T02:58:37Z | 2024-05-16T05:37:29Z | https://github.com/kubernetes/kubernetes/issues/124861 | 2,294,253,071 | 124,861 |
[
"kubernetes",
"kubernetes"
] | The LimitRanger admission plugin does not currently handle pod updates, but needs to be updated to account for InPlacePodVerticalScaling:
https://github.com/kubernetes/kubernetes/blob/4f04dffe5b2cd652a20b362eaea30164e3e5ea54/plugin/pkg/admission/limitranger/admission.go#L424-L429
/sig node | [FG:InPlacePodVerticalScaling] Handle in-place pod resource updates in LimitRanger admission plugin | https://api.github.com/repos/kubernetes/kubernetes/issues/124855/comments | 5 | 2024-05-13T23:05:39Z | 2024-11-06T06:59:30Z | https://github.com/kubernetes/kubernetes/issues/124855 | 2,293,991,632 | 124,855 |
[
"kubernetes",
"kubernetes"
] | null | #124608 | https://api.github.com/repos/kubernetes/kubernetes/issues/124853/comments | 4 | 2024-05-13T19:25:20Z | 2024-05-16T05:38:11Z | https://github.com/kubernetes/kubernetes/issues/124853 | 2,293,649,936 | 124,853 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
/sig scheduling
/kind feature
Add a new plugin extension to check nodes. Then modify the scheduling filter logic to prioritize nodes that satisfy preferred check conditions, ensuring that these nodes are placed at the beginning of the node array to ensure that the scheduler p... | Ensure that pods are scheduled to nodes that meet preferred conditions, while satisfying a series of filter plugins for the scheduler. | https://api.github.com/repos/kubernetes/kubernetes/issues/124844/comments | 17 | 2024-05-13T08:53:33Z | 2024-10-20T11:30:00Z | https://github.com/kubernetes/kubernetes/issues/124844 | 2,292,216,643 | 124,844 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
When I create the following pod, and the resources requested by the container are less than 6Mi:
```
apiVersion: v1
kind: Pod
metadata:
name: app
spec:
containers:
- name: nginx
image: nginx
resources:
limits:
cpu: "0.1"
memory: "5Mi... | add warnings when apply container memory resources are less than 6Mi | https://api.github.com/repos/kubernetes/kubernetes/issues/124841/comments | 7 | 2024-05-13T08:10:55Z | 2024-08-15T12:28:34Z | https://github.com/kubernetes/kubernetes/issues/124841 | 2,292,128,025 | 124,841 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When running e2e, the following fatal error can be encountered:
```
30715 I0513 08:25:43.792330 285839 reflector.go:289] Starting reflector *v1.ConfigMap (0s) from object-"flexvolume-445 9"/"kube-root-ca.crt"
30716 I0513 08:25:43.797355 285839 plugins.go:651] "Loaded volume plugin" plugin... | Kubelet crashes on concurrent map iteration and map write | https://api.github.com/repos/kubernetes/kubernetes/issues/124839/comments | 8 | 2024-05-13T07:05:58Z | 2025-01-22T10:47:08Z | https://github.com/kubernetes/kubernetes/issues/124839 | 2,292,002,520 | 124,839 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
looking at kubectl events I see things like "message": "Started container bla" with "userAgent": "kubelet" and "involvedObject" "kind": "Pod"
is there any config option to prevent these events being sent?
### Why is this needed?
etcd can fill up | disable events? | https://api.github.com/repos/kubernetes/kubernetes/issues/124836/comments | 7 | 2024-05-13T01:55:34Z | 2024-05-16T05:39:07Z | https://github.com/kubernetes/kubernetes/issues/124836 | 2,291,647,984 | 124,836 |
[
"kubernetes",
"kubernetes"
] | This is breaking the kind job that monitors the state of a cluster with alpha features enabled
https://testgrid.k8s.io/sig-testing-kind#kind-master-alpha-beta
The kubelet fails to start https://storage.googleapis.com/kubernetes-jenkins/logs/ci-kubernetes-e2e-kind-alpha-beta-features/1789720580090499072/artifacts... | [Failing Test] UserNamespacesSupport feature gate kernel version requirements should not apply generally | https://api.github.com/repos/kubernetes/kubernetes/issues/124834/comments | 4 | 2024-05-12T22:24:31Z | 2024-05-13T08:53:30Z | https://github.com/kubernetes/kubernetes/issues/124834 | 2,291,527,629 | 124,834 |
[
"kubernetes",
"kubernetes"
] | https://github.com/kubernetes/kubernetes/blame/99a8a6fe258a456d51dddd3dec16d168d94e4eb1/test/integration/scheduler_perf/scheduler_perf.go#L759-L760 | kubkit | https://api.github.com/repos/kubernetes/kubernetes/issues/124833/comments | 3 | 2024-05-12T14:06:18Z | 2024-05-13T09:58:55Z | https://github.com/kubernetes/kubernetes/issues/124833 | 2,291,348,528 | 124,833 |
[
"kubernetes",
"kubernetes"
] | /kind feature
/sig scheduling
# what
Allow each test case to specify its timeout. Now, it is specified 30 minutes as hard coding.
https://github.com/kubernetes/kubernetes/blob/99a8a6fe258a456d51dddd3dec16d168d94e4eb1/test/integration/scheduler_perf/scheduler_perf.go#L759-L760
# why
I admit that 30 minutes... | scheduler_perf: Allow each test case to specify its timeout | https://api.github.com/repos/kubernetes/kubernetes/issues/124827/comments | 7 | 2024-05-12T12:37:21Z | 2024-05-15T11:48:26Z | https://github.com/kubernetes/kubernetes/issues/124827 | 2,291,315,183 | 124,827 |
[
"kubernetes",
"kubernetes"
] | Hello,
I know that in case of node resource pressure, the controller prioritizes pods to be evicted, for example in case of node memory pressure, pods using more memory than requested are prioritised for deletion.
But for HPA scale-in I struggle to find if and how pods are sorted to prioritize them for deletion.
Whi... | HPA scale-in: is pod resource usage taken into account to prioritize pods to be deleted ? | https://api.github.com/repos/kubernetes/kubernetes/issues/124821/comments | 10 | 2024-05-11T11:26:41Z | 2025-01-09T17:32:13Z | https://github.com/kubernetes/kubernetes/issues/124821 | 2,290,849,433 | 124,821 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
when apiserver cache is not ready, the List request with resourceVersion=0 fetch data from the apiserver cache, don't directly obtain from etcd.
[staging/src/k8s.io/apiserver/pkg/storage/cacher/cacher.go](https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/... | when apiserver cache is not ready, the List request with resourceVersion=0 fetch data from the apiserver cache | https://api.github.com/repos/kubernetes/kubernetes/issues/124818/comments | 7 | 2024-05-11T09:59:41Z | 2024-07-29T07:15:18Z | https://github.com/kubernetes/kubernetes/issues/124818 | 2,290,815,666 | 124,818 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
We can't make sure app Container always reuses init Container cpuset, which may lead to the waste of CPU(init container has already exited but the cpuset can not be reused by other containers) and `not enough cpus available to satis
fy request` error.
<img width="1421" alt="image" src="https:/... | app Container can't reuse its init Container cpuset in a specific condition | https://api.github.com/repos/kubernetes/kubernetes/issues/124797/comments | 12 | 2024-05-10T14:12:18Z | 2024-08-07T12:22:27Z | https://github.com/kubernetes/kubernetes/issues/124797 | 2,289,816,135 | 124,797 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I created a v1.30.0 k8s cluster with kubeadm and created a drop-in directory for kubelet configuration under `/etc/kubernetes/kubelet.conf.d`. The normal conf file created by kubeadm is in ` /var/lib/kubelet/config.yaml`
According to the [docs](https://kubernetes.io/docs/tasks/administer-clust... | bug: kubelet panic & crash if `--config-dir` is used | https://api.github.com/repos/kubernetes/kubernetes/issues/124796/comments | 18 | 2024-05-10T14:11:26Z | 2024-10-25T16:27:53Z | https://github.com/kubernetes/kubernetes/issues/124796 | 2,289,814,628 | 124,796 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
If you use `kubectl auth can-i` to test whether a user can approve certificate signing requests, you get a response indicating that `approve` is not a valid verb
```bash
kubectl auth can-i approve certificatesigningrequests.certificates.k8s.io
Warning: resource 'certificatesigningrequests' is... | Kubectl auth can-i doesn't know about the `approve` verb | https://api.github.com/repos/kubernetes/kubernetes/issues/124880/comments | 12 | 2024-05-10T10:48:14Z | 2024-05-29T06:33:37Z | https://github.com/kubernetes/kubernetes/issues/124880 | 2,296,921,216 | 124,880 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are flaking?
https://prow.k8s.io/job-history/gs/kubernetes-jenkins/pr-logs/directory/pull-kubernetes-node-e2e-containerd
### Which tests are flaking?
E2eNode Suite: [It] [sig-node] [NodeConformance] Containers Lifecycle when a pod is terminating because its liveness probe fails should execute readines... | [Flaking][sig-node] [NodeConformance] Containers Lifecycle when a pod is terminating because its liveness probe fails should execute readiness probe while in preStop, but not liveness | https://api.github.com/repos/kubernetes/kubernetes/issues/124791/comments | 15 | 2024-05-10T10:28:23Z | 2024-08-22T03:05:38Z | https://github.com/kubernetes/kubernetes/issues/124791 | 2,289,457,502 | 124,791 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
InPlacePodVerticalScaling does not meet the requirement of qosClass being equal to Guaranteed after shrinking the memory
### What did you expect to happen?
InPlacePodVerticalScaling maintains... | InPlacePodVerticalScaling does not meet the requirement of qosClass being equal to Guaranteed after shrinking the memory | https://api.github.com/repos/kubernetes/kubernetes/issues/124786/comments | 27 | 2024-05-10T06:21:41Z | 2025-03-05T14:17:03Z | https://github.com/kubernetes/kubernetes/issues/124786 | 2,289,024,624 | 124,786 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are flaking?
- e2e-kops-aws-cni-cilium-eni
- ci-kubernetes-kind-e2e-parallel-1-29
- pull-kubernetes-e2e-kind
### Which tests are flaking?
Kubernetes e2e suite: [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] read-write-once-pod [MinimumKubeletVersio... | [Flaking Test][sig-storage] should block a second pod from using an in-use ReadWriteOncePod volume on the same node | https://api.github.com/repos/kubernetes/kubernetes/issues/124784/comments | 3 | 2024-05-10T03:43:48Z | 2024-05-15T17:24:27Z | https://github.com/kubernetes/kubernetes/issues/124784 | 2,288,856,820 | 124,784 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I was trying to cp a from a Windows Pod to the Windows localhost. But it failed.
```
kubectl.exe cp --kubeconfig .\kubconfig -n namespace-win pod-20240509-120334-779546rrfsc:C:\\data\\0509-1065.log 0509-1065.log
```
It showed
```
tar: Removing leading drive letter from member names
er... | kubectl cp a file from a Windows Pod to Windows 11 localhost failed | https://api.github.com/repos/kubernetes/kubernetes/issues/124781/comments | 16 | 2024-05-10T01:08:27Z | 2025-01-29T03:00:49Z | https://github.com/kubernetes/kubernetes/issues/124781 | 2,288,705,769 | 124,781 |
[
"kubernetes",
"kubernetes"
] | As discussed in the SIG Network meeting on May 9, we should provide "EndpointSlice helpers" to help people get away from Endpoints (without using EndpointSlices in a naive way that breaks for large services).
In particular, we want something that acts sort of like an `Informer`/`Lister`, but where it deals with merg... | add EndpointSlice consumer helper functions | https://api.github.com/repos/kubernetes/kubernetes/issues/124777/comments | 2 | 2024-05-09T19:24:13Z | 2024-05-12T16:08:36Z | https://github.com/kubernetes/kubernetes/issues/124777 | 2,288,310,673 | 124,777 |
[
"kubernetes",
"kubernetes"
] | /kind feature
/sig scheduling
Discussion with sig-scalability: https://kubernetes.slack.com/archives/C09QZTRH7/p1715262959575039
## What
We have scheduler-perf, and it'd be great if we could have an alert-ish stuff based on the result.
Based on the discussion with sig-scalability, the easiest way is to cha... | scheduler_perf: define thresholds per test case and set up alerts for results | https://api.github.com/repos/kubernetes/kubernetes/issues/124774/comments | 17 | 2024-05-09T14:51:56Z | 2024-09-14T03:27:12Z | https://github.com/kubernetes/kubernetes/issues/124774 | 2,287,859,059 | 124,774 |
[
"kubernetes",
"kubernetes"
] | After https://github.com/kubernetes/kubernetes/pull/124519 and https://github.com/kubernetes/kubernetes/pull/124767 were merged, this repo won't get any update once release 1.30 becomes unsupported.
Related file: https://github.com/kubernetes/kubernetes/blob/master/staging/publishing/rules.yaml#L2291
/assign @dim... | Archive legacy-cloud-providers when 1.30 goes out of support | https://api.github.com/repos/kubernetes/kubernetes/issues/124771/comments | 5 | 2024-05-09T10:38:29Z | 2024-06-19T14:40:44Z | https://github.com/kubernetes/kubernetes/issues/124771 | 2,287,419,413 | 124,771 |
[
"kubernetes",
"kubernetes"
] | Hello
Can we add capability to set `feature.node.kubernetes.io/<feature-name>` by cloud provider?
I believe they was designed for that https://kubernetes.io/docs/reference/labels-annotations-taints/#feature-node-kubernetes-io
And probably `node.cloudprovider.kubernetes.io/`
@mmerkes
Thank you.
https://gi... | Allow labels feature.node.kubernetes.io by cloud provider | https://api.github.com/repos/kubernetes/kubernetes/issues/124769/comments | 2 | 2024-05-09T05:51:00Z | 2024-05-22T16:50:38Z | https://github.com/kubernetes/kubernetes/issues/124769 | 2,286,944,958 | 124,769 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
Etcd defragmentation is the workflow to prevent etcd from running out of disk space.
It is expected that defragmentation will result in timeouts and latency to requests that happen to be connected to the node being defragmented.
There is a proposal to stop traffic sending to b... | Add Etcd client support: stop traffic to in-defragmentation-server | https://api.github.com/repos/kubernetes/kubernetes/issues/124763/comments | 7 | 2024-05-08T23:39:55Z | 2024-10-27T18:21:56Z | https://github.com/kubernetes/kubernetes/issues/124763 | 2,286,646,070 | 124,763 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
For example, we had a pod which had:
```yaml
securityContext:
fsGroup: 1001
runAsGroup: 1001
runAsUser: 1001
```
This — unbeknownst to us for quite some time — led to the pod taking _hours_ to start, with it being otherwise apparently stuck in `Pending`.
Now, _in this parti... | Potentially lengthy I/O by kubelet during pod startup needs to be visible to the user | https://api.github.com/repos/kubernetes/kubernetes/issues/124762/comments | 7 | 2024-05-08T21:59:39Z | 2024-10-19T21:25:01Z | https://github.com/kubernetes/kubernetes/issues/124762 | 2,286,552,924 | 124,762 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Aggregated API backend: Call to `CREATE` endpoint consults `PATCH` field validation properties, even if the resource does not support the `PATCH` verb..
### What did you expect to happen?
Expected `CREATE` to be called with `CREATE` field validation without looking at the `PATCH` endpoint.
### H... | Open API v3 requirement for `PATCH` verb support (introduced PR #115119) | https://api.github.com/repos/kubernetes/kubernetes/issues/124760/comments | 7 | 2024-05-08T18:06:32Z | 2024-10-05T20:39:28Z | https://github.com/kubernetes/kubernetes/issues/124760 | 2,286,157,597 | 124,760 |
[
"kubernetes",
"kubernetes"
] | CVSS Rating: [CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N) - **MEDIUM** (6.5)
A security issue was discovered in azure-file-csi-driver where an actor with access to the driver logs could observe service account tokens. These tok... | CVE-2024-3744: azure-file-csi-driver discloses service account tokens in logs | https://api.github.com/repos/kubernetes/kubernetes/issues/124759/comments | 1 | 2024-05-08T16:02:57Z | 2024-05-15T00:45:12Z | https://github.com/kubernetes/kubernetes/issues/124759 | 2,285,943,659 | 124,759 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
Currently if I define environment variables on container in the following way:
```
env:
- name: SOME_VAR
value: SOME_VALUE
- name: SOME_OTHER_VAR
value: SOME_OTHER_VALUE-$(SOME_VALUE)
envFrom:
- secretRef:
name: some-secret
```
When one of the value... | Support `env` variables in values from `envFrom` | https://api.github.com/repos/kubernetes/kubernetes/issues/124756/comments | 6 | 2024-05-08T14:50:02Z | 2024-10-06T03:39:29Z | https://github.com/kubernetes/kubernetes/issues/124756 | 2,285,799,327 | 124,756 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
There is a use case in the flow test that creates a pod which uses pvc and then waits about 2 minutes and then delete the pod. Later it was discovered that the pv referenced by the pod had been attached on the node and had not been detached.
Combining the csi plugin and k8s component logs, we f... | Volumeattachment deletion in a detach operation should carry the resourceVersion | https://api.github.com/repos/kubernetes/kubernetes/issues/124749/comments | 11 | 2024-05-08T10:58:14Z | 2025-02-26T14:08:57Z | https://github.com/kubernetes/kubernetes/issues/124749 | 2,285,309,624 | 124,749 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
master-informing:
- [gce-cos-master-serial](https://testgrid.k8s.io/sig-release-master-informing#gce-cos-master-serial)
### Which tests are failing?
- Kubernetes e2e suite.[It] [sig-autoscaling] DNS horizontal autoscaling [Serial] [Slow] [KubeUp] kube-dns-autoscaler should scale kube-dns... | [Failing Test] [sig-cloud-provider-gcp] Provider does not support InstanceGroups | https://api.github.com/repos/kubernetes/kubernetes/issues/124748/comments | 14 | 2024-05-08T10:47:38Z | 2024-07-17T14:42:38Z | https://github.com/kubernetes/kubernetes/issues/124748 | 2,285,290,437 | 124,748 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Base on HPA/v2beta2 was removed since Kubernetes 1.26 and current HPA/V2 is not support "unknown field "spec.containerMetrics", unknown field "spec.metrics[0].resource.container". So just want suggestion for implement HPAContainerMetrics on cluster.
<img width="1424" alt="328572042-781024d1-7647-... | HPAContainerMetrics Version V2Beta2 Cannot Implement on Kubernetes 1.30 as "V2Beta2" was remove since Kubernetes 1.26 | https://api.github.com/repos/kubernetes/kubernetes/issues/124745/comments | 7 | 2024-05-08T09:17:16Z | 2024-11-06T16:43:06Z | https://github.com/kubernetes/kubernetes/issues/124745 | 2,285,111,031 | 124,745 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
https://testgrid.k8s.io/sig-release-master-informing#gce-master-scale-correctness
### Which tests are failing?
Network related tests:
* Kubernetes e2e suite.[It] [sig-network] Services GCE [Slow] should be able to create and tear down a standard-tier load balancer [Slow]
* Kubernetes e2... | [FailingTest] [gce-master-scale-correctness] Multiple test failures, mostly networking | https://api.github.com/repos/kubernetes/kubernetes/issues/124744/comments | 7 | 2024-05-08T09:04:12Z | 2024-05-09T21:49:38Z | https://github.com/kubernetes/kubernetes/issues/124744 | 2,285,080,305 | 124,744 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
Multiple, for example:
- [ci-crio-cgroupv1-node-e2e-features](https://testgrid.k8s.io/sig-node-cri-o#ci-crio-cgroupv1-node-e2e-features)
- [ci-crio-cgroupv2-node-e2e-features](https://testgrid.k8s.io/sig-node-cri-o#ci-crio-cgroupv2-node-e2e-features)
### Which tests are failing?
`... | [FailingTest] [sig-node] [NodeFeature:SidecarContainers] Containers Lifecycle should terminate sidecars simultaneously if prestop doesn't exit | https://api.github.com/repos/kubernetes/kubernetes/issues/124743/comments | 7 | 2024-05-08T08:18:57Z | 2024-05-23T17:16:20Z | https://github.com/kubernetes/kubernetes/issues/124743 | 2,284,989,110 | 124,743 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
The CPU utilization metrics from Kubelet summary API [`CPUStats.UsageCoreNanoSeconds`](https://github.com/kubernetes/kubernetes/blob/79470526896f8b6ca744c29109bc3455c1a9d199/staging/src/k8s.io/kubelet/pkg/apis/stats/v1alpha1/types.go#L224C2-L224C22) is not accurate on Windows. The value is only 1/1... | CPUStats.UsageCoreNanoSeconds is inaccurate on windows - 1/10 of the real value. | https://api.github.com/repos/kubernetes/kubernetes/issues/124734/comments | 19 | 2024-05-08T06:16:17Z | 2025-03-09T09:44:04Z | https://github.com/kubernetes/kubernetes/issues/124734 | 2,284,767,071 | 124,734 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I wondered what are the restrictions (if any) that Kubernetes imposes on the names of objects of a kind that gets defined by a CustomResourceDefinition. I am not talking about the name of the CRD itself. I tried to find this in the documentation, and couldn't. I asked on the `sig-api-machinery` chan... | Confusing doc on name of object of kind defined by CRD | https://api.github.com/repos/kubernetes/kubernetes/issues/124733/comments | 4 | 2024-05-08T04:15:56Z | 2024-05-08T04:24:23Z | https://github.com/kubernetes/kubernetes/issues/124733 | 2,284,642,884 | 124,733 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
On RHEL, tried to deploy 1.20.0
But unable to fetch packages
`failed to download metadata for repo 'kubernetes': cannot download repomd.xml: cannot download repodata/repomd.xml: all mirrors were tried`
### What did you expect to happen?
I expected the packages to be deployed. Later I read http... | Unable to deploy 1.20.0 | https://api.github.com/repos/kubernetes/kubernetes/issues/124727/comments | 6 | 2024-05-07T14:04:30Z | 2024-05-09T10:37:18Z | https://github.com/kubernetes/kubernetes/issues/124727 | 2,283,459,170 | 124,727 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When /api/v1/namespaces/sop/events is requested, data is obtained from etcd instead of the apiserver cache. When there are too many events, etcd memory increases.
### What did you expect to happen?
We expect that when /api/v1/namespaces/sop/events is requested, data is also fetched from the apiser... | The event is not obtained from the apiserver cache | https://api.github.com/repos/kubernetes/kubernetes/issues/124724/comments | 5 | 2024-05-07T12:32:39Z | 2024-05-30T16:49:40Z | https://github.com/kubernetes/kubernetes/issues/124724 | 2,283,160,225 | 124,724 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
autoscaling e2e test: Kubernetes e2e suite.[It] [sig-autoscaling] Cluster size autoscaling [Slow] should increase cluster size if pod requesting volume is pending [Feature:ClusterSizeAutoscalingScaleUp]
### Which tests are failing?
Kubernetes e2e suite.[It] [sig-autoscaling] Cluster size ... | Failing test due to pv expecting a "topology.gke.io/zone" label that is not set in OSS kubernetes nodes on GCE | https://api.github.com/repos/kubernetes/kubernetes/issues/124721/comments | 20 | 2024-05-07T11:26:39Z | 2024-10-09T16:19:27Z | https://github.com/kubernetes/kubernetes/issues/124721 | 2,283,017,809 | 124,721 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
集群版本是1.22.5-00版本，我这边将节点kubelet版本升级到1.23.17-00版本，按照官方文档中的说明，kubelet版本不能高与kube-apiserver版本（1.22.5-00），可是我的节点还是正常可以创建pod资源。节点kubelet日志无异常。目前不确定这样问题出在哪儿，哪位大神可以帮我解答一下。
官方文档地址：https://kubernetes.io/z... | 集群升级kubelet版本高于kube-apiserver版本 | https://api.github.com/repos/kubernetes/kubernetes/issues/124720/comments | 7 | 2024-05-07T09:30:06Z | 2024-05-08T10:50:03Z | https://github.com/kubernetes/kubernetes/issues/124720 | 2,282,745,891 | 124,720 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
We found that the kubelet memory kept increasing，and we exported the pprof of the goroutine. The grpc goroutine leaks, causing memory leakage.
We found out that the reason was because one of t... | Kubelet memory leak when a plugin is registered twice | https://api.github.com/repos/kubernetes/kubernetes/issues/124716/comments | 7 | 2024-05-07T03:19:02Z | 2024-05-10T20:48:58Z | https://github.com/kubernetes/kubernetes/issues/124716 | 2,282,186,693 | 124,716 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
It would be really great if `InPlacePodVerticalScaling` could in-place resize cpu on containers that have requests only (no limits).
Currently, `InPlacePodVerticalScaling` cannot successfully resize `cpu` against containers without limits. e.g. given this pod:
```
apiVersi... | [FG:InPlacePodVerticalScaling] Add additional E2E Burstable Pod QoS test cases for pods without resource limits | https://api.github.com/repos/kubernetes/kubernetes/issues/124712/comments | 6 | 2024-05-06T22:51:00Z | 2024-11-30T07:06:42Z | https://github.com/kubernetes/kubernetes/issues/124712 | 2,281,919,588 | 124,712 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
https://github.com/kubernetes/kubernetes/pull/119779 added some map queries and creations that add non-negligible latency.
The pprof reveals the following lines inside `findNodesThatFitPod` as too expensive:
- 22.2% https://github.com/kubernetes/kubernetes/blob/44bd04c0cbddde69aaeb7a90d3bd3de4... | Throughput degradation scheduling daemonset pods | https://api.github.com/repos/kubernetes/kubernetes/issues/124709/comments | 26 | 2024-05-06T17:26:20Z | 2024-10-21T20:05:35Z | https://github.com/kubernetes/kubernetes/issues/124709 | 2,281,369,549 | 124,709 |
[
"kubernetes",
"kubernetes"
] | Currently, `EvaluatedNodes` contains the number of nodes that filtered out by PreFilterResult and Filter plugins.
But, before #119779, actually it only contains Nodes reach Filter plugins, which is actually more useful than the current state.
This issue aims to bring back the previous `EvaluatedNodes`.
ref: http... | Change EvaluatedNodes to count Nodes that reach Filter phase only | https://api.github.com/repos/kubernetes/kubernetes/issues/124705/comments | 3 | 2024-05-06T13:10:09Z | 2024-05-10T05:43:24Z | https://github.com/kubernetes/kubernetes/issues/124705 | 2,280,850,035 | 124,705 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
After #124297, which fixes timestamps set by Evented PLEG, was merged, a pod phase transition is slower especially at deletion when the EventedPLEG is enabled.
EventedPLEG is enabled:
```
$ kubectl create -f simple-pod.yaml; kubectl get pod simple-pod -w & kubectl wait --for=jsonpath='{.status.... | Pod phase transition is slower when EventedPLEG is enabled | https://api.github.com/repos/kubernetes/kubernetes/issues/124704/comments | 14 | 2024-05-06T13:06:01Z | 2025-01-18T15:11:47Z | https://github.com/kubernetes/kubernetes/issues/124704 | 2,280,841,413 | 124,704 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
The logic is as follows:
1. Manually update secret resources.
2. kubelet listens to resources and updates the watch cache.
3. Start the pod and query the volume attached to the secret resource.
but probabilistically, especially at lots of operating pressures. The third step is performed befo... | kubelet should alway get lastest secret/configmap resource in pod add event | https://api.github.com/repos/kubernetes/kubernetes/issues/124701/comments | 19 | 2024-05-06T09:44:21Z | 2024-08-27T16:43:29Z | https://github.com/kubernetes/kubernetes/issues/124701 | 2,280,465,014 | 124,701 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
"kubectl top nodes" reports "unknown" when executing multiple concurrent “kubectl exec” requests against a pod
### What did you expect to happen?
"kubectl top nodes" reports the status of nodes.
### How can we reproduce it (as minimally and precisely as possible)?
1. create an AKS Windows node a... | "kubectl top nodes" reports "unknown" when executing multiple concurrent “kubectl exec” requests against a pod running on a Windows node | https://api.github.com/repos/kubernetes/kubernetes/issues/124700/comments | 15 | 2024-05-06T09:30:58Z | 2024-10-31T07:49:00Z | https://github.com/kubernetes/kubernetes/issues/124700 | 2,280,441,593 | 124,700 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Despite enabling topology-aware routing, I'm still seeing traffic being routed from one AZ to another. This is not the expected behavior, as it should prioritize in-zone traffic.
Current setup:
3 AZ eu-west
3 pods in each AZ
3 endpoints per each AZ
### What did you expect to happ... | Topology Aware Routing not working | https://api.github.com/repos/kubernetes/kubernetes/issues/124699/comments | 9 | 2024-05-05T17:11:16Z | 2024-08-21T11:01:49Z | https://github.com/kubernetes/kubernetes/issues/124699 | 2,279,632,380 | 124,699 |
[
"kubernetes",
"kubernetes"
] | - [ ] [github.com/google/gofuzz](https://github.com/google/gofuzz) (Archived Jan 10, 2024)
- [ ] [github.com/google/shlex](https://github.com/google/shlex) (Archived Dec 29, 2022)
- [ ] [github.com/gregjones/httpcache](https://github.com/gregjones/httpcache) (Archived Apr 20, 2023)
- [ ] [github.com/grpc-ecosystem/g... | Drop archived vendored libraries and switch to active ones | https://api.github.com/repos/kubernetes/kubernetes/issues/124695/comments | 9 | 2024-05-04T23:46:54Z | 2024-06-13T13:54:27Z | https://github.com/kubernetes/kubernetes/issues/124695 | 2,279,240,204 | 124,695 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When creating a MySQL deployment with two replicas also volume mount added, after some time one pod becomes `CrashLoopBackOff` stage and another is running successfully.
<img width="446" alt="Screenshot 2024-05-04 at 14 14 22" src="https://github.com/kubernetes/kubernetes/assets/51718908/c90959... | When creating two replicas in a deployment with volume mount, one pod become Error or CrashLoopBackOff stage. | https://api.github.com/repos/kubernetes/kubernetes/issues/124691/comments | 8 | 2024-05-04T08:56:21Z | 2024-09-22T01:23:40Z | https://github.com/kubernetes/kubernetes/issues/124691 | 2,278,870,356 | 124,691 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
I would like `k8s.io/component-base` to be compatible with the latest version of `go.opentelemetry.io/otel/exporters/prometheus`.
### Why is this needed?
In version `0.48.0` of the `github.com/prometheus/common` library, the `expfmt.FmtText` constant [was made private](https://gi... | Compatibility between `k8s.io/component-base` and latest `go.opentelemetry.io/otel/exporters/prometheus`. | https://api.github.com/repos/kubernetes/kubernetes/issues/124687/comments | 8 | 2024-05-03T13:36:21Z | 2024-05-16T19:25:44Z | https://github.com/kubernetes/kubernetes/issues/124687 | 2,277,701,768 | 124,687 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Kubelet unconditionally adds IPv6 entries to `/etc/hosts` even when system has IPv6 totally disabled. This results in strange errors due to "happy eyeballs" fallback behavior: when clients see both an IPv4 and an IPv6 address for a host, they first try IPv4 and then fall back to IPv6, but if IPv6 is... | Kubelet should not add IPv6 entries to /etc/hosts on systems where IPv6 is disabled | https://api.github.com/repos/kubernetes/kubernetes/issues/124686/comments | 13 | 2024-05-03T13:07:32Z | 2024-10-31T13:18:35Z | https://github.com/kubernetes/kubernetes/issues/124686 | 2,277,648,504 | 124,686 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I was running some load testing related to flux. When creating 10.000 kustomization custom resources (about 1KiB), the k8s apiserver consumes about 1GiB of memory. When checking with 100.000k and 300.00k, the k8s apiserver scales linearly.
When doing the same thing for 1KiB conifgmaps, creating 1... | Watch request for CRs costs about 10-15x more memory in k8s-apiserver than in-tree resource watches | https://api.github.com/repos/kubernetes/kubernetes/issues/124680/comments | 11 | 2024-05-02T17:08:34Z | 2024-08-08T06:49:50Z | https://github.com/kubernetes/kubernetes/issues/124680 | 2,276,047,687 | 124,680 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
When a Kubernetes Pod has a container with a startup script as the entrypoint to do some initialization work before starting the actual main process, only the script host process gets the shutdown signal (`SIGTERM` on Linux; `CTRL_SHUTDOWN_EVENT` on Windows according to the [docs... | Provide an easy way to send graceful shutdown signal to all processes in a Windows container | https://api.github.com/repos/kubernetes/kubernetes/issues/124664/comments | 11 | 2024-05-02T08:46:04Z | 2025-01-01T09:30:19Z | https://github.com/kubernetes/kubernetes/issues/124664 | 2,274,946,777 | 124,664 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
As of go 1.22, for string to bytes conversion, we can replace the usage of `unsafe.Slice(unsafe.StringData(s), len(s))` with type casting `[]bytes(str)`, without the worry of losing performance.
As of go 1.22, string to bytes conversion `[]bytes(str)` is faster than using the ... | As of go 1.22, there's no need to use the unsafe package for string to bytes conversion | https://api.github.com/repos/kubernetes/kubernetes/issues/124656/comments | 7 | 2024-05-01T15:47:09Z | 2025-03-08T20:10:20Z | https://github.com/kubernetes/kubernetes/issues/124656 | 2,273,725,693 | 124,656 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Someone opened #124533 saying
> I expected 1.29 libraries to still be compatible with Kubernetes 1.28 based on the kube-apiserver version skew.
I think that is not what the version skew policy (https://kubernetes.io/releases/version-skew-policy/) is trying to say. I think that the guiding prin... | The Version Skew Policy does not mention aggregated apiservers | https://api.github.com/repos/kubernetes/kubernetes/issues/124655/comments | 7 | 2024-05-01T14:34:52Z | 2024-05-21T19:42:56Z | https://github.com/kubernetes/kubernetes/issues/124655 | 2,273,617,960 | 124,655 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
kubectl describe should use **discoveryv1.EndpointSlice** instead of **v1.Endpoints**.
### Why is this needed?
Almost everything in Kubernetes uses endpoint slices instead of endpoints.
This discussion started from https://github.com/kubernetes/kubernetes/issues/123954. | kubectl describe uses Endpoints instead of EndpointSlices | https://api.github.com/repos/kubernetes/kubernetes/issues/124651/comments | 5 | 2024-05-01T09:49:41Z | 2024-05-04T16:14:51Z | https://github.com/kubernetes/kubernetes/issues/124651 | 2,273,244,977 | 124,651 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
Hot increase cpu/memory/storage so that kubelet can recognize it without restarting
### Why is this needed?
When the node machine is expanded to these three configuration types, the calculation value source of kubelet based on eviction pod still uses old data.
I would li... | Kubelet will only get machine info when it is started. | https://api.github.com/repos/kubernetes/kubernetes/issues/124650/comments | 3 | 2024-05-01T06:11:03Z | 2024-05-01T11:33:06Z | https://github.com/kubernetes/kubernetes/issues/124650 | 2,272,995,822 | 124,650 |
[
"kubernetes",
"kubernetes"
] | null | Mano | https://api.github.com/repos/kubernetes/kubernetes/issues/124649/comments | 4 | 2024-05-01T05:55:03Z | 2024-05-01T13:49:03Z | https://github.com/kubernetes/kubernetes/issues/124649 | 2,272,981,650 | 124,649 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When kubelet evicts a pod, the ready condition doesn’t get `NotReady` during the pod termination even if a `readinessProbe` is configured.
### What did you expect to happen?
A readiness probe works during a pod termination so that the pod gets `NotReady` as early as possible.
### How can we rep... | Readiness probe stops too early at eviction | https://api.github.com/repos/kubernetes/kubernetes/issues/124648/comments | 8 | 2024-04-30T22:55:00Z | 2024-08-28T11:09:10Z | https://github.com/kubernetes/kubernetes/issues/124648 | 2,272,613,226 | 124,648 |
[
"kubernetes",
"kubernetes"
] | The current jittering logic in [kubelet token_manager](https://github.com/kubernetes/kubernetes/blob/dd68c5f2409fec7176e6172d6f9d97bd6447c4da/pkg/kubelet/token/token_manager.go#L42) refreshes the token once it has 20% of its lifetime remaining, with 10 seconds of jitter.
Experimentally, this doesn't seem to be enoug... | Improve the jitter value for kubelet's serviceAccountToken projected volume source | https://api.github.com/repos/kubernetes/kubernetes/issues/124646/comments | 3 | 2024-04-30T21:52:32Z | 2024-09-05T16:12:34Z | https://github.com/kubernetes/kubernetes/issues/124646 | 2,272,514,694 | 124,646 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are flaking?
https://storage.googleapis.com/k8s-triage/index.html?sig=windows&text=should%20not%20exceed%20limit%20by%20%3E%205%25
### Which tests are flaking?
```
Kubernetes e2e suite: [It] [sig-windows] [Feature:Windows] Cpu Resources [Serial] Container limits should not be exceeded after waiti... | Cpu Resources Container limits test is flaky for Windows on containerd 1.7 | https://api.github.com/repos/kubernetes/kubernetes/issues/124643/comments | 8 | 2024-04-30T16:55:07Z | 2024-07-03T04:20:45Z | https://github.com/kubernetes/kubernetes/issues/124643 | 2,272,046,762 | 124,643 |
[
"kubernetes",
"kubernetes"
] | [kubebrain](https://github.com/kubewharf/kubebrain) implements the etcd gRPC API. We need to assert that its RV semantics match that of etcd, meaning that running SVM on either environment would work as expected.
/assign nilekhc
/triage accepted
/sig api-machinery
Links to code searches performed: [[1]](https:... | SVM RV Semantics: assert that kubebrain RV semantics match etcd | https://api.github.com/repos/kubernetes/kubernetes/issues/124641/comments | 1 | 2024-04-30T14:15:45Z | 2024-05-02T04:23:51Z | https://github.com/kubernetes/kubernetes/issues/124641 | 2,271,594,601 | 124,641 |
[
"kubernetes",
"kubernetes"
] | [k8s-dqlite](https://github.com/canonical/k8s-dqlite) implements the etcd gRPC API. We need to assert that its RV semantics match that of etcd, meaning that running SVM on either environment would work as expected.
/assign nilekhc
/triage accepted
/sig api-machinery
Links to code searches performed: [[1]](http... | SVM RV Semantics: assert that k8s-dqlite RV semantics match etcd | https://api.github.com/repos/kubernetes/kubernetes/issues/124640/comments | 0 | 2024-04-30T14:13:56Z | 2024-04-30T14:14:01Z | https://github.com/kubernetes/kubernetes/issues/124640 | 2,271,590,843 | 124,640 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I'm looking at various ways to expose a service directly from a set of hosts in a k8s cluster. [Yes, I know about the caveats here, but this is a service that doesn't play like a traditional http/rest endpoint.]
I can do this with a svc that has a `port` setting and a list of `spec.externalIPs`... | service.spec.externalIPs is unnecessarily limited (enhancement request) | https://api.github.com/repos/kubernetes/kubernetes/issues/124636/comments | 12 | 2024-04-30T10:36:45Z | 2024-08-12T16:26:13Z | https://github.com/kubernetes/kubernetes/issues/124636 | 2,271,108,727 | 124,636 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
In `garbagecollector.GetDeletableResources()` if `discoveryClient.ServerPreferredResources()` fails with a lookup error, we log something like the following due to json.Marshal() refusing to marshal a struct type.
```
garbagecollector.go:835] "failed to discover some groups" groups="<internal erro... | garbagecollector.GetDeletableResources logs json encoding error instead of actual error | https://api.github.com/repos/kubernetes/kubernetes/issues/124628/comments | 2 | 2024-04-29T22:11:58Z | 2024-05-21T19:40:04Z | https://github.com/kubernetes/kubernetes/issues/124628 | 2,270,078,187 | 124,628 |
[
"kubernetes",
"kubernetes"
] | [kine](https://github.com/k3s-io/kine) implements the etcd gRPC API. We need to assert that its RV semantics match that of etcd, meaning that running SVM on either environment would work as expected.
/assign nilekhc
/triage accepted
/sig api-machinery
Links to code searches performed: [[1]](https://github.com/... | SVM RV Semantics: assert that kine RV semantics match etcd | https://api.github.com/repos/kubernetes/kubernetes/issues/124627/comments | 0 | 2024-04-29T21:44:19Z | 2024-04-30T14:12:22Z | https://github.com/kubernetes/kubernetes/issues/124627 | 2,270,042,294 | 124,627 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
The apiserver prints a crd update log every 5 minutes. What does this mean? What is the triggering process?
### Why is this needed?
https://github.com/kubernetes/kubernetes/blob/bac1a0ce1b284aff8db1aeeb571d97fa130078a6/staging/src/k8s.io/apiextensions-apiserver/pkg/cont... | What Is the Meaning of "Updating CRD OpenAPI spec because xxx changed" in the apiserver Log? | https://api.github.com/repos/kubernetes/kubernetes/issues/124611/comments | 6 | 2024-04-29T13:04:42Z | 2024-06-04T01:30:08Z | https://github.com/kubernetes/kubernetes/issues/124611 | 2,268,996,244 | 124,611 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
https://github.com/kubernetes/kubernetes/pull/124323 reminded us that test coverage of checkpointing and the interaction between kubelet and DRA drivers could be improved. We can do error injection and/or add delays by extending https://github.com/kubernetes/kubernetes/blob/4946c... | DRA: add e2e_node tests | https://api.github.com/repos/kubernetes/kubernetes/issues/124608/comments | 4 | 2024-04-29T11:34:45Z | 2024-06-18T08:14:21Z | https://github.com/kubernetes/kubernetes/issues/124608 | 2,268,789,424 | 124,608 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
sudo kubeadm join
when i try to join worker node to master node it's throwing error
/etc/sysconfig/kubelet looks like
KUBELET_EXTRA_ARGS=
/etc/systemd/system/kubelet.service.d/10-kubeadm.conf
Environment="KUBELET_KUBECONFIG_ARGS=--bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kub... | Unable to join worker node to master node | https://api.github.com/repos/kubernetes/kubernetes/issues/124606/comments | 4 | 2024-04-29T10:22:11Z | 2024-04-29T13:15:26Z | https://github.com/kubernetes/kubernetes/issues/124606 | 2,268,652,908 | 124,606 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When continuously re-applying the same object via a controller or kubectl with SSA the resourceVersion increases every time.
### What did you expect to happen?
I expected the resourceVersion to stay the same if the client always sends the same object via SSA, especially if the resulting obj... | Server-side apply bumps resourceVersion when re-applying the same object | https://api.github.com/repos/kubernetes/kubernetes/issues/124605/comments | 14 | 2024-04-29T09:55:59Z | 2024-08-01T13:22:58Z | https://github.com/kubernetes/kubernetes/issues/124605 | 2,268,602,126 | 124,605 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are flaking?
https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-unit/1784375152293711872
### Which tests are flaking?
k8s.io/kubernetes/pkg: scheduler TestSchedulerGuaranteeNonNilNodeInSchedulingCycle
### Since when has it been flaking?
04-28?
### Testgrid link
https://testgrid.k8s.... | [Flaking Test] UT TestSchedulerGuaranteeNonNilNodeInSchedulingCycle | https://api.github.com/repos/kubernetes/kubernetes/issues/124591/comments | 13 | 2024-04-28T10:04:37Z | 2024-10-12T16:30:30Z | https://github.com/kubernetes/kubernetes/issues/124591 | 2,267,467,686 | 124,591 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I have a 4-node (1 control-plane and 3 workers) cluster setup. Each node have two NICs, one for Pod network (inside 192.168.16.0/20), the other one for storage (inside 10.87.87.0/24).
I have a headless service, an operator would dynamically update its endpoints with storage NIC IPs. I cannot acce... | Selector-less service with secondary IPs not working properly on Rocky 8/9 with latest kube-proxy | https://api.github.com/repos/kubernetes/kubernetes/issues/124587/comments | 30 | 2024-04-28T06:24:23Z | 2024-05-09T02:06:56Z | https://github.com/kubernetes/kubernetes/issues/124587 | 2,267,374,962 | 124,587 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Currently, a running pod is being evicted if the assigned node, which does not meet the pod's node affinity requirements anymore, restarts its kubelet.
xref: https://github.com/kubernetes/kubernetes/issues/123980#issuecomment-2071554998
### What did you expect to happen?
https://kubernete... | Restarted kubelet should not evict pods due to the node affinity | https://api.github.com/repos/kubernetes/kubernetes/issues/124586/comments | 19 | 2024-04-28T05:20:49Z | 2024-05-15T17:23:57Z | https://github.com/kubernetes/kubernetes/issues/124586 | 2,267,350,541 | 124,586 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When running a command with `kubectl exec`, the output (data written to stdout) can be truncated without the command returning an error. This results in ambiguity around the command failing or network being torn down with an error (non-zero exit code) versus the command completing successfully and r... | kubectl exec truncates stdout without reporting error | https://api.github.com/repos/kubernetes/kubernetes/issues/124571/comments | 7 | 2024-04-26T17:15:56Z | 2024-08-26T16:11:59Z | https://github.com/kubernetes/kubernetes/issues/124571 | 2,266,189,670 | 124,571 |
[
"kubernetes",
"kubernetes"
] | /kind feature
/assign
/sig scheduling
---
We don't have any observability around event handling (= requeueing) throughput. Adding observability can be a monitor for a degradation around it.
Also, based on the metric we add, we can find how fast event handling should be on a certain large scale, like we have 3... | Scheduler: Observe/Improve event handling throughput | https://api.github.com/repos/kubernetes/kubernetes/issues/124566/comments | 11 | 2024-04-26T13:57:44Z | 2024-11-05T09:30:15Z | https://github.com/kubernetes/kubernetes/issues/124566 | 2,265,848,834 | 124,566 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
It happens when the apiserver goes down and after a few minutes when the apiserver comes back up, some endpoints have notReadyAddresses and do not recover.It's an accidental phenomenon.
The cause is that the endpoint obtained from the Informer is not the latest. In the syncService method of endpoin... | The endpoint is lost when the APIServer is restored. | https://api.github.com/repos/kubernetes/kubernetes/issues/124547/comments | 5 | 2024-04-26T06:32:26Z | 2024-05-30T16:43:19Z | https://github.com/kubernetes/kubernetes/issues/124547 | 2,265,059,043 | 124,547 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Thanks for @benluddy who raised the issue and investigated!
We didn't register the cost estimator for extended library hence the cost calculation is inaccurate for expression including extended library.
### What did you expect to happen?
The cost should reflect the extended library
/... | ValidatingAdmissionPolicy: Cost estimator for extended library was not registered | https://api.github.com/repos/kubernetes/kubernetes/issues/124542/comments | 15 | 2024-04-25T23:23:06Z | 2024-05-14T15:57:24Z | https://github.com/kubernetes/kubernetes/issues/124542 | 2,264,649,466 | 124,542 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
We currently have this function https://github.com/kubernetes/kubernetes/blob/ae02f87bb47cd3e10e702ffe19225ff2dba73578/pkg/api/v1/resource/helpers.go#L50
It is used by both kube-scheduler and kubelet to calculate resource utilization.
It would be useful to have it in a librar... | A library function to calculate Pod resource utilization | https://api.github.com/repos/kubernetes/kubernetes/issues/124537/comments | 13 | 2024-04-25T17:24:59Z | 2024-04-29T12:19:57Z | https://github.com/kubernetes/kubernetes/issues/124537 | 2,264,117,143 | 124,537 |
[
"kubernetes",
"kubernetes"
] | As has been extensively discussed on prior occasions (see https://github.com/kubernetes/kubectl/issues/151), `kubectl get all` is not recommended, has been removed from documentation, and should be removed.
It appears that the primary reason this has not yet been completed is because the issue was filed against the ... | Finish removing `kubectl get all` | https://api.github.com/repos/kubernetes/kubernetes/issues/124538/comments | 15 | 2024-04-25T17:04:40Z | 2025-01-22T02:09:09Z | https://github.com/kubernetes/kubernetes/issues/124538 | 2,264,164,727 | 124,538 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
We bumped an aggregated apiserver library based on the generic apiserver library to 1.29 in https://github.com/kubernetes-sigs/custom-metrics-apiserver/pull/170 and users mentioned that after pulling the new dependencies, the aggregated apiservers started failing on Kubernetes 1.28 clusters with t... | 1.29-apiserver based aggregated APIServer does not work against 1.28 kube-apiserver | https://api.github.com/repos/kubernetes/kubernetes/issues/124533/comments | 15 | 2024-04-25T15:54:57Z | 2025-01-15T16:53:42Z | https://github.com/kubernetes/kubernetes/issues/124533 | 2,263,952,959 | 124,533 |
[
"kubernetes",
"kubernetes"
] | ### Problem statement
Using `code-generator`'s `client-gen` in version 1.30 adds several new fields to generated CRDs:
```diff
imagePullSecrets:
description: |-
ImagePullSecrets is an optional list of references to secrets i... | 1.30 adds tags that break `imagePullSecrets` | https://api.github.com/repos/kubernetes/kubernetes/issues/124540/comments | 14 | 2024-04-25T12:11:37Z | 2024-05-03T22:21:16Z | https://github.com/kubernetes/kubernetes/issues/124540 | 2,264,177,850 | 124,540 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are flaking?
https://prow.ppc64le-cloud.cis.ibm.net/job-history/gs/ppc64le-kubernetes/logs/periodic-kubernetes-unit-test-ppc64le
### Which tests are flaking?
TestStatefulSetControl/CreatePodFailure/Burst/ScaleDownOnly/StatefulSetAutoDeletePVCEnabled of pkg/controller/statefulset/stateful_set_control... | Flaky UT TestStatefulSetControl/CreatePodFailure/Burst/ScaleDownOnly/StatefulSetAutoDeletePVCEnabled | https://api.github.com/repos/kubernetes/kubernetes/issues/124526/comments | 2 | 2024-04-25T10:07:21Z | 2024-05-10T13:49:01Z | https://github.com/kubernetes/kubernetes/issues/124526 | 2,263,196,580 | 124,526 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
On Kubernetes 1.29 with PersistentVolumeLabel admission plugin enabled and no in-tree cloud provider configured in the kube-apiserver, the admission plugins adds label `topology.kubernetes.io/region: ""` to in-tree Azure Disk PVs.
The label is completely wrong - the Azure cloud provider is not ... | PersistentVolumeLabel admission plugin provides wrong Azure region | https://api.github.com/repos/kubernetes/kubernetes/issues/124525/comments | 12 | 2024-04-25T09:22:07Z | 2024-06-04T15:21:04Z | https://github.com/kubernetes/kubernetes/issues/124525 | 2,263,105,276 | 124,525 |
[
"kubernetes",
"kubernetes"
] |
My topic is to implement a certain computing function in a container environment, which may involve dynamic scaling and resource scheduling. Now my supervisor wants me to read some papers, please recommend some papers to me. | Some high-quality literature reading is required | https://api.github.com/repos/kubernetes/kubernetes/issues/124523/comments | 4 | 2024-04-25T08:32:33Z | 2024-04-25T09:24:33Z | https://github.com/kubernetes/kubernetes/issues/124523 | 2,263,006,213 | 124,523 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I think the private container registry had some intermittent errors and did return wrong data for some layers.
The problem I think is that kubelet or containerd is in a state were it assumes that a given OCI image is already downloaded locally, but then some parsing of this layer fails and the ... | kubelet and containerd in endless loop for CreateContainer with unexpected media type octet-stream | https://api.github.com/repos/kubernetes/kubernetes/issues/124515/comments | 7 | 2024-04-24T19:38:45Z | 2024-04-25T12:06:38Z | https://github.com/kubernetes/kubernetes/issues/124515 | 2,262,043,795 | 124,515 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
Hi Folks,
I'm checking the e2e test related to webhook. Notice that that webhook first failed now below. Notice
W0424 17:48:11.860818 1 dispatcher.go:187] Failed calling webhook, failing closed deny-unwanted-configmap-data.k8s.io: failed calling webhook "deny-unwanted-configmap-... | [sig-api-machinery] webhook related test | https://api.github.com/repos/kubernetes/kubernetes/issues/124511/comments | 4 | 2024-04-24T17:56:26Z | 2024-04-25T07:43:29Z | https://github.com/kubernetes/kubernetes/issues/124511 | 2,261,869,630 | 124,511 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
In 1.30, the PersistentVolumeLabel admission plugin blocks creation of in-tree AzureDisk and vSphere PVs:
```
persistentvolumes "pvc-2d9b3999-f60d-4797-923f-210f1f75025d" is forbidden:
error querying AzureDisk volume pvc-2d9b3999-f60d-4797-923f-210f1f75025d:
unable to build Azure cloud provi... | PersistentVolumeLabel admission blocks PVs on Azure + vSphere | https://api.github.com/repos/kubernetes/kubernetes/issues/124504/comments | 3 | 2024-04-24T10:37:22Z | 2024-10-21T21:51:25Z | https://github.com/kubernetes/kubernetes/issues/124504 | 2,260,975,377 | 124,504 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Most services access the APIServer through the service of the ClusterIP type. The relationship between the service and the endpoints is created by the APIServer , and then the iptables routing rule maintained by kube-proxy. When the APIServer is restarted, the routing rule cannot be updated quickl... | The APIServer health check failed. As a result, the APIServer automatically exits and APIServer unavailable. | https://api.github.com/repos/kubernetes/kubernetes/issues/124502/comments | 6 | 2024-04-24T09:48:46Z | 2024-05-16T16:59:34Z | https://github.com/kubernetes/kubernetes/issues/124502 | 2,260,879,529 | 124,502 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I installed nfs provisioner and reported an error
### What did you expect to happen?
How can I solve this problem
### How can we reproduce it (as minimally and precisely as possible)?
k8s v1.28.2
nfs-client-provisioner:latest
### Anything else we need to know?
_No response_
### Kubernetes ve... | K8s error message: unexpected error getting claim reference: selfLink was empty, can't make reference | https://api.github.com/repos/kubernetes/kubernetes/issues/124495/comments | 4 | 2024-04-24T02:30:01Z | 2024-04-24T08:09:48Z | https://github.com/kubernetes/kubernetes/issues/124495 | 2,260,154,559 | 124,495 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
This is just my wishlist. We need all of them, so no specific priority.
- [ ] Regexes for object names, label keys, values, container names, etc. I think this one is already in the works?
- [ ] validate the type metav1.Conditions
- [ ] simple functions to check if conditions... | Wishlist of CEL libraries | https://api.github.com/repos/kubernetes/kubernetes/issues/124490/comments | 21 | 2024-04-23T18:59:08Z | 2024-10-31T14:48:54Z | https://github.com/kubernetes/kubernetes/issues/124490 | 2,259,572,483 | 124,490 |
[
"kubernetes",
"kubernetes"
] | ### Failure cluster [ea6679417165f10786e6](https://go.k8s.io/triage#ea6679417165f10786e6)
##### Error text:
```
error during ./hack/e2e-internal/e2e-up.sh: exit status 1
```
#### Recent failures:
[4/23/2024, 5:00:35 AM ci-kubernetes-e2e-gce-device-plugin-gpu-1-29](https://prow.k8s.io/view/gs/kubernetes-jenkins/... | Failure cluster [ea667941...] `cos-97-lts` AWOL from `cos-cloud` causing a lot of CI jobs to fail since 4/16 | https://api.github.com/repos/kubernetes/kubernetes/issues/124478/comments | 7 | 2024-04-23T13:21:43Z | 2024-04-24T21:25:44Z | https://github.com/kubernetes/kubernetes/issues/124478 | 2,258,874,546 | 124,478 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are flaking?
pull-kubernetes-integration
### Which tests are flaking?
k8s.io/kubernetes/test/integration/controlplane: transformation
### Since when has it been flaking?
April 22nd 2024
### Testgrid link
https://testgrid.k8s.io/presubmits-kubernetes-blocking#pull-kubernetes-integration
### Reaso... | [flaky test] k8s.io/kubernetes/test/integration/controlplane: transformation | https://api.github.com/repos/kubernetes/kubernetes/issues/124476/comments | 2 | 2024-04-23T12:22:28Z | 2024-04-24T00:02:27Z | https://github.com/kubernetes/kubernetes/issues/124476 | 2,258,739,556 | 124,476 |
[
"kubernetes",
"kubernetes"
] | first spotted in publishing-bot run:
https://github.com/kubernetes/kubernetes/issues/56876#issuecomment-2070999174
followed steps in [flaky-tests.md](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-testing/flaky-tests.md) to recreate the problem.
- `go test ./staging/src/k8s.io/client-go... | TestRoundTrip is flaky | https://api.github.com/repos/kubernetes/kubernetes/issues/124475/comments | 9 | 2024-04-23T12:15:02Z | 2024-05-16T16:58:18Z | https://github.com/kubernetes/kubernetes/issues/124475 | 2,258,725,472 | 124,475 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
/sig apps
/assign
Want to get feedback on this proposal. I can proceed to KEP process later, if it looks worthy for it to everyone.
**Feature Summary**
This RFE proposes adding an optional parameter to Kubernetes CronJobs that allows setting a maximum number of successf... | RFE Optional CronJob Parameter: Auto-Suspend Kubernetes CronJob After Specified Number of Successful Executions | https://api.github.com/repos/kubernetes/kubernetes/issues/124473/comments | 13 | 2024-04-23T10:34:17Z | 2024-09-30T16:03:34Z | https://github.com/kubernetes/kubernetes/issues/124473 | 2,258,525,282 | 124,473 |
Subsets and Splits
Unique Owner-Repo Count
Counts the number of unique owner-repos in the dataset, providing a basic understanding of diverse repositories.