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"
] | This issue is significantly inspired by discussion I had with @smarterclayton an year ago or so. However, given that we're facing more and more issues and concerns related to it, it's probably the highest time to actually get back to it.
The key point that I didn't realize back then (not sure about Clayton) is that ... | Evolve watchcache to optimize LIST calls and support pagination | https://api.github.com/repos/kubernetes/kubernetes/issues/108003/comments | 18 | 2022-02-08T11:03:48Z | 2025-01-30T21:25:43Z | https://github.com/kubernetes/kubernetes/issues/108003 | 1,127,103,949 | 108,003 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are flaking?
`pull-kubernetes-unit`
### Which tests are flaking?
Unit test `TestTimeoutHeaders` in `k8s.io/apiserver/pkg/server/filters` package flakes
```
=== RUN TestTimeoutHeaders
timeout_test.go:247: got res.StatusCode 200; expected 503
--- FAIL: TestTimeoutHeaders (0.00s)
```
... | k8s.io/apiserver/pkg/server/filters.TestTimeoutHeaders flakes | https://api.github.com/repos/kubernetes/kubernetes/issues/107991/comments | 4 | 2022-02-07T15:29:12Z | 2022-02-10T17:43:13Z | https://github.com/kubernetes/kubernetes/issues/107991 | 1,126,145,475 | 107,991 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
The cri-api repository already exposes a bunch of interface definitions there:
https://github.com/kubernetes/cri-api/blob/master/pkg/apis/services.go
The actual implementation of those interfaces, namely `RuntimeService` and `ImageManagerService` are part of the kubelet intern... | Move `pkg/kubelet/cri/remote` to `cri-api` staging | https://api.github.com/repos/kubernetes/kubernetes/issues/107989/comments | 5 | 2022-02-07T12:12:54Z | 2022-05-09T09:47:33Z | https://github.com/kubernetes/kubernetes/issues/107989 | 1,125,906,373 | 107,989 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
We have a cluster on EKS and from 2 days ago we noticed some network issues in our cluster. Imagine a scenario in which we have 2 workers nodes (w1 and w2) and 3 pods with their own services (A, B and C). Pods A and B are located on w1 and pod C are located on w2.
The problem is A cannot reach C ... | Some pod to pod connection fails on EKS | https://api.github.com/repos/kubernetes/kubernetes/issues/107985/comments | 3 | 2022-02-07T10:51:09Z | 2022-02-07T12:05:37Z | https://github.com/kubernetes/kubernetes/issues/107985 | 1,125,820,020 | 107,985 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When diffing an `Endpoints` object with `--server-side=true`, there is no diff produced, but this message is printed:
```
W0207 05:09:34.901634 96076 diff.go:692] Object (/v1, Kind=Endpoints: test-endpoint) keeps changing, diffing without lock
Error from server (Conflict): Apply failed with... | Object (/v1, Kind=Endpoints: test-endpoint) keeps changing, diffing without lock | https://api.github.com/repos/kubernetes/kubernetes/issues/107980/comments | 14 | 2022-02-07T04:21:26Z | 2022-07-29T18:23:57Z | https://github.com/kubernetes/kubernetes/issues/107980 | 1,125,490,337 | 107,980 |
[
"kubernetes",
"kubernetes"
] | https://github.com/kubernetes/kubernetes/blob/9b09612d1b0a6ec441833f928cbb205d936da59c/pkg/controller/volume/attachdetach/statusupdater/node_status_updater.go#L92
UpdateNodeStatuses will exit immediately if updateNodeStatus returns an error.
It does mark the node for which the call failed for later update but all t... | Bug in node_status_updater.go - UpdateNodeStatuses | https://api.github.com/repos/kubernetes/kubernetes/issues/107973/comments | 5 | 2022-02-06T05:42:25Z | 2022-03-01T20:49:54Z | https://github.com/kubernetes/kubernetes/issues/107973 | 1,125,111,531 | 107,973 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Running into an issue with kubeadm init on a raspberry pi cluster
`
I0205 12:29:12.192138 5348 initconfiguration.go:117] detected and using CRI socket: /var/run/dockershim.sock
I0205 12:29:12.196554 5348 interface.go:432] Looking for default routes with IPv4 addresses
I0205 12:29:12.19... | Kubeadm init fails, Kubelet fails to start | https://api.github.com/repos/kubernetes/kubernetes/issues/107969/comments | 6 | 2022-02-05T16:14:26Z | 2022-02-09T15:58:36Z | https://github.com/kubernetes/kubernetes/issues/107969 | 1,124,967,359 | 107,969 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
master-informing[ capg-conformance-v1beta1-ci-artifacts](https://testgrid.k8s.io/sig-release-master-informing)
### Which tests are failing?
- capg-e2e.BeforeSuite
- periodic-cluster-api-provider-gcp-conformance-v1beta1-ci-artifacts.Overall
### Since when has it been failing?
... | [Failing test] capg-conformance-v1beta1-ci-artifacts | https://api.github.com/repos/kubernetes/kubernetes/issues/107966/comments | 9 | 2022-02-05T08:10:28Z | 2022-02-18T08:19:37Z | https://github.com/kubernetes/kubernetes/issues/107966 | 1,124,867,355 | 107,966 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
kube-proxy is running, proxy-mode is iptables, but not found KUBE-SERVICES in iptables nat table .
[root@minion:~]$ iptables -t nat -nL PREROUTING
Chain PREROUTING (policy ACCEPT)
target prot opt source destination
DOCKER all -- 0.0.0.0/0 0.0.0.0/0 ... | chain KUBE-SERVICES cat not see with iptables v1.8.4 (nf_tables) | https://api.github.com/repos/kubernetes/kubernetes/issues/107965/comments | 3 | 2022-02-05T07:04:22Z | 2022-02-07T09:21:37Z | https://github.com/kubernetes/kubernetes/issues/107965 | 1,124,856,110 | 107,965 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
While reviewing the code in queueset.go, I noticed that the block of code that resizes the final work if it is too wide (`if oldestReqFromMinQueue.workEstimate.FinalSeats > uint(qs.dCfg.ConcurrencyLimit) ...`) appears only in `findDispatchQueueLocked` --- not also in the no-queuing code path (`dispa... | APF does not resize final work when not queuing | https://api.github.com/repos/kubernetes/kubernetes/issues/107964/comments | 12 | 2022-02-05T06:40:36Z | 2024-06-18T20:29:10Z | https://github.com/kubernetes/kubernetes/issues/107964 | 1,124,852,150 | 107,964 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
Cleanup work to remove more of the deprecated timeouts, especially throughout the conformance tests. There are newer, configurable timeouts that are available via the framework.Timeouts object.
Some of the deprecated framework timeouts constants are still used: https://github.co... | e2e-framework: Consistent use of configurable timeouts | https://api.github.com/repos/kubernetes/kubernetes/issues/107957/comments | 11 | 2022-02-04T20:05:40Z | 2022-10-15T01:20:37Z | https://github.com/kubernetes/kubernetes/issues/107957 | 1,124,572,965 | 107,957 |
[
"kubernetes",
"kubernetes"
] | ran
```
kubectl version foocluster
```
instead of
```
kubectl version --context foocluster
```
and got no error and then though that was the right version
kubectl should fail for unexpected extra arguments
| kubectl version should fail when given extra arguments | https://api.github.com/repos/kubernetes/kubernetes/issues/107955/comments | 3 | 2022-02-04T19:25:11Z | 2022-03-04T06:26:53Z | https://github.com/kubernetes/kubernetes/issues/107955 | 1,124,540,152 | 107,955 |
[
"kubernetes",
"kubernetes"
] | ### Failure cluster [89c7abe10b4e83db5885](https://go.k8s.io/triage#89c7abe10b4e83db5885)
##### Error text:
```
=== RUN TestRoundTrip
roundtrip.go:136: starting group ""
roundtrip.go:149: finished group ""
roundtrip.go:136: starting group "apiextensions.k8s.io"
roundtrip.go:255: round trippi... | DeepCopy of JSONSchemaProps doesn't deeply copy XValidations. | https://api.github.com/repos/kubernetes/kubernetes/issues/107954/comments | 8 | 2022-02-04T19:22:17Z | 2022-02-10T17:43:20Z | https://github.com/kubernetes/kubernetes/issues/107954 | 1,124,537,905 | 107,954 |
[
"kubernetes",
"kubernetes"
] | Is this supposed to avoid the error message that I removed in https://github.com/kubernetes/kubernetes/pull/107677?
The error that I see in current master is this:
```
$ PATH=third_party/etcd:$PATH make test-integration WHAT=./test/integration/scheduler_perf KUBE_TEST_VMODULE="''" KUBE_TEST_ARGS="-alsologtostderr=... | apiserver logs error "Unable to remove endpoints from kubernetes" at start | https://api.github.com/repos/kubernetes/kubernetes/issues/107953/comments | 7 | 2022-02-04T18:44:03Z | 2022-07-18T00:17:34Z | https://github.com/kubernetes/kubernetes/issues/107953 | 1,124,505,295 | 107,953 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
In kube-proxy's trace log I could see iptables save command which took 3+ mins to execute. Would like to know why and when kube-proxy does iptables save call and does it have any impact on k8's etcd ? kube-proxy running in ipvs mode
I1217 12:04:07.406781 1 node.go:135] Successfully r... | kube-proxy tracelog shows iptable save command output | https://api.github.com/repos/kubernetes/kubernetes/issues/107951/comments | 7 | 2022-02-04T15:11:52Z | 2022-02-07T23:11:18Z | https://github.com/kubernetes/kubernetes/issues/107951 | 1,124,309,552 | 107,951 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I was looking at the metrics exposed by the kube-apiserver and noticed that some of the `apiserver_request_total` metrics had a
status code set to 0 in Kubernetes 1.23. Looking a bit more into the metrics, I noticed that it was affecting the `/healthz` and `/readyz` endpoints as well the streaming... | Kube-apiserver exposes metrics with status code 0 for streaming requests | https://api.github.com/repos/kubernetes/kubernetes/issues/107949/comments | 16 | 2022-02-04T14:13:30Z | 2025-03-04T21:18:10Z | https://github.com/kubernetes/kubernetes/issues/107949 | 1,124,249,712 | 107,949 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I tried to remove namespace in a cluster with 70k CRD objects. The namespace-controller was triggering DELETECOLLECTION call which was failing to make any progress on deletion due to List (part of DeleteCollection) taking more than 34s of timeout hardcoded in the kube-apiserver's code. It was retryi... | namespace-controller fails to delete namespace if there are too many objects of a given type | https://api.github.com/repos/kubernetes/kubernetes/issues/107948/comments | 6 | 2022-02-04T13:09:47Z | 2022-02-04T13:36:55Z | https://github.com/kubernetes/kubernetes/issues/107948 | 1,124,187,992 | 107,948 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
i'm running the newest Kubernetes 1.23.3 on a Ubuntu 20.04 running as a VM on VMware.
Whenever i try to join my cluster from another VM, I'm getting these errors:
I0204 12:49:22.520307 5863 patchnode.go:31] [patchnode] Uploading the CRI Socket information "/var/run/dockershim.sock" to the Nod... | Kubernetes on Ubuntu 20.04 VM, second VM can't join the cluster: nodes "servername" not found, error uploading crisocket | https://api.github.com/repos/kubernetes/kubernetes/issues/107946/comments | 3 | 2022-02-04T12:28:16Z | 2022-02-04T17:00:27Z | https://github.com/kubernetes/kubernetes/issues/107946 | 1,124,149,628 | 107,946 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
My evn: Kubernetes 1.20.7 with runtime: containerd
My problem:
I have a lot of microservices running in kubernetes. To one microservice a large number of calls and logs are written in large numbers.
During the closing of the log and the creation of a new file to continue the logs, one of the logs... | Log rotate for containerd runtime. Splits the log into parts | https://api.github.com/repos/kubernetes/kubernetes/issues/107943/comments | 9 | 2022-02-04T06:57:55Z | 2022-02-10T17:42:02Z | https://github.com/kubernetes/kubernetes/issues/107943 | 1,123,877,473 | 107,943 |
[
"kubernetes",
"kubernetes"
] | # Progress <code>[1/6]</code>
- [x] APISnoop org-flow: [Appsv1ControllerRevisionLifecycleTest.org](https://github.com/apisnoop/ticket-writing/blob/master/Appsv1ControllerRevisionLifecycleTest.org)
- [ ] Test approval issue: [#](https://issues.k8s.io/)
- [ ] Test PR: [!](https://pr.k8s.io/)
- [ ] Two weeks soak st... | Write ControllerRevision Lifecycle Test +7 | https://api.github.com/repos/kubernetes/kubernetes/issues/107939/comments | 3 | 2022-02-03T21:12:41Z | 2022-05-19T01:15:52Z | https://github.com/kubernetes/kubernetes/issues/107939 | 1,123,558,870 | 107,939 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
I understand that in Kubernetes v1.20+, this is not possible and if a cluster-scoped resource specifies a namespaced resource as an owner, it is treated as having an unresolvable owner reference and is not able to be garbage collected.
What is the solution in that case? How can ... | Automatically delete a cluster scoped resource that has a namespaced ownerRef | https://api.github.com/repos/kubernetes/kubernetes/issues/107937/comments | 2 | 2022-02-03T19:18:28Z | 2022-02-06T15:36:25Z | https://github.com/kubernetes/kubernetes/issues/107937 | 1,123,463,051 | 107,937 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
Updating the test framework to ginkgo 2.0 will eventually happen I'm sure and I just wanted to have some notes related to this that people can reference.
### Why is this needed?
Just tracking issues that would be related to any updating of ginkgo from 1.0 to 2.0.
- [ ] Custom re... | Updating the test framework to ginkgo 2.0 | https://api.github.com/repos/kubernetes/kubernetes/issues/107936/comments | 8 | 2022-02-03T17:32:26Z | 2022-07-08T06:57:47Z | https://github.com/kubernetes/kubernetes/issues/107936 | 1,123,368,688 | 107,936 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Here is my controller management profile information
cat > /opt/kubernetes/server/conf/kube-controller-manager.conf << EOF
KUBE_CONTROLLER_MANAGER_OPTS="--logtostderr=false \\
--also... | After upgrading to 1.22.6, controller manager unhealthy | https://api.github.com/repos/kubernetes/kubernetes/issues/107929/comments | 7 | 2022-02-03T12:34:20Z | 2022-02-14T16:06:53Z | https://github.com/kubernetes/kubernetes/issues/107929 | 1,123,033,207 | 107,929 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
POD with sriov nic device attached to it fails to attach correct sriov device up on node is hard rebooted after volumes are attached to it. The node is a VM in openstack cloud provider environment and the PCI address of the sriov VF changes on node hard reboot when additional volumes are attached ... | POD fails to attach correct sriov device on ungraceful node reboot | https://api.github.com/repos/kubernetes/kubernetes/issues/107928/comments | 18 | 2022-02-03T11:50:46Z | 2024-12-12T11:58:49Z | https://github.com/kubernetes/kubernetes/issues/107928 | 1,122,991,743 | 107,928 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
The following appears in EndpointSlice controller logs when a Node specified by `pod.spec.nodeName` is not present in the Node informer cache:
```
Error syncing endpoint slices for service "example/service", retrying: Error: node: "example-123" not found.
```
This is caused by https://githu... | EndpointSlice controller sync fails when Node is not found | https://api.github.com/repos/kubernetes/kubernetes/issues/107927/comments | 37 | 2022-02-03T02:51:11Z | 2022-06-22T17:43:43Z | https://github.com/kubernetes/kubernetes/issues/107927 | 1,122,596,735 | 107,927 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Run `make` in Kubernetes 1.22.x project dir:
```
bash: line 1: hack/make-rules/helpers/cache_go_dirs.sh: Permission denied
```
Golang info:
```bash
GO111MODULE="on"
GOARCH="amd64"
GOBIN="/home/remote/go/bin"
GOCACHE="/home/remote/.cache/go-build"
GOENV="/home/remote/.config/go/env"
... | bash: line 1: hack/make-rules/helpers/cache_go_dirs.sh: Permission denied | https://api.github.com/repos/kubernetes/kubernetes/issues/107926/comments | 3 | 2022-02-02T23:01:58Z | 2022-02-02T23:30:33Z | https://github.com/kubernetes/kubernetes/issues/107926 | 1,122,474,224 | 107,926 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
https://testgrid.k8s.io/sig-node-cos#containerd-e2e-cos-1.4
### Which tests are failing?
kubetest.Up
### Since when has it been failing?
01/24/2022 17:22 PST
### Testgrid link
https://testgrid.k8s.io/sig-node-cos#containerd-e2e-cos-1.4
### Reason for failure (if possible)
```
start... | kubetest.Up of ci-containerd-e2e-cos-gce-1-4 is failing | https://api.github.com/repos/kubernetes/kubernetes/issues/107925/comments | 3 | 2022-02-02T22:39:46Z | 2022-05-10T18:54:10Z | https://github.com/kubernetes/kubernetes/issues/107925 | 1,122,460,032 | 107,925 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Using a `LimitRange`, I'm hoping to have a default request, but _not_ a default limit.
Setting this:
```yaml
apiVersion: v1
kind: LimitRange
metadata:
name: cpu-and-mem-defaults
spec:
limits:
- defaultRequest:
memory: 512Mi
cpu: 100m
type: Container
```... | Setting a defaultRequest on a LimitRange sets an implicit Limit | https://api.github.com/repos/kubernetes/kubernetes/issues/107922/comments | 3 | 2022-02-02T21:02:25Z | 2022-02-02T22:18:04Z | https://github.com/kubernetes/kubernetes/issues/107922 | 1,122,383,963 | 107,922 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
It could make sense to wait for a pod to be terminated before scheduling a new one for the issues mentioned bellow. Even though some issues can be partially mitigated by proper setup of maxUnavailable and maxSurge, it is not applicable for all of them.
I would like to propose a ... | Option for acknowledging terminating Pods in Deployment rolling update | https://api.github.com/repos/kubernetes/kubernetes/issues/107920/comments | 18 | 2022-02-02T19:14:00Z | 2024-05-30T18:43:26Z | https://github.com/kubernetes/kubernetes/issues/107920 | 1,122,294,201 | 107,920 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
When validating update requests, the API server should indicate in returned errors when they are due to a forbidden transition from the old object, rather than inherently invalid content in the new object.
User story 1: If I submit an update request trying to change an immutabl... | API clients should be able to distinguish "invalid transition" validation errors from "invalid content" errors | https://api.github.com/repos/kubernetes/kubernetes/issues/107919/comments | 19 | 2022-02-02T18:41:13Z | 2024-04-11T16:45:24Z | https://github.com/kubernetes/kubernetes/issues/107919 | 1,122,268,031 | 107,919 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
[In-place Pod Vertical Scaling feature](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/1287-in-place-update-pod-resources) allows for resizing of CPU and memory resources of running pods without having to restart the pod and its containers.
This is achieved... | [FG:InPlacePodVerticalScaling] Add support in containerd for returning Resources in ContainerStatus CRI API | https://api.github.com/repos/kubernetes/kubernetes/issues/107911/comments | 17 | 2022-02-02T01:28:10Z | 2022-11-23T17:19:51Z | https://github.com/kubernetes/kubernetes/issues/107911 | 1,121,412,409 | 107,911 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I'm trying to build kubectl `v1.18.20` using the command `./build/run.sh make kubectl KUBE_BUILD_PLATFORMS=darwin/amd64` and the build fails
```
❯ ./build/run.sh make kubectl KUBE_BUILD_PLATFORMS=darwin/amd64
+++ [0201 14:07:48] Verifying Prerequisites....
+++ [0201 14:07:48] Using Docker f... | Cannot produce older builds of Kubectl on Apple Silicon | https://api.github.com/repos/kubernetes/kubernetes/issues/107908/comments | 4 | 2022-02-01T22:14:56Z | 2022-02-02T18:54:55Z | https://github.com/kubernetes/kubernetes/issues/107908 | 1,121,255,711 | 107,908 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When init container does its job it's removed and CPU assigned to it via cpuset returns to the defaultCPUSet pool even though this CPU is in cpuset used by another container. Because of that kubelet seeing drift between **defaultCPUSet** and **exclusive CPUs** assigned to running containers fails... | Exclusive CPU used by init container returns to defaultCPUSet pool causing kubelet go into reboot loop | https://api.github.com/repos/kubernetes/kubernetes/issues/107906/comments | 7 | 2022-02-01T21:15:27Z | 2022-02-02T20:08:10Z | https://github.com/kubernetes/kubernetes/issues/107906 | 1,121,207,695 | 107,906 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I am just reopening https://github.com/kubernetes/kubernetes/issues/52386
`kubectl describe node 10.0.10.132` shows:
```
MemoryPressure True Tue, 01 Feb 2022 09:44:34 +0100 Thu, 20 Jan 2022 04:54:21 +0100 KubeletHasInsufficientMemory kubelet has insufficient memory avail... | Kubelet under MemoryPressure but there are much memory left on the node | https://api.github.com/repos/kubernetes/kubernetes/issues/107899/comments | 11 | 2022-02-01T09:54:29Z | 2024-06-19T02:38:21Z | https://github.com/kubernetes/kubernetes/issues/107899 | 1,120,447,778 | 107,899 |
[
"kubernetes",
"kubernetes"
] | During termination, some pod probes could be stopped before all containers finish. For instance:
* Liveness exec probes can stop when the pod is terminal and when the first failure happens - at that point the container will not be restarted
* Readiness exec probes can stop when the pod is terminal and the first fa... | Pod probes could start earlier depending on type of probe and container status | https://api.github.com/repos/kubernetes/kubernetes/issues/107894/comments | 13 | 2022-02-01T03:12:24Z | 2024-11-14T22:52:51Z | https://github.com/kubernetes/kubernetes/issues/107894 | 1,120,186,204 | 107,894 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I have been running K8s v1.23.3 successfully on Ubuntu 20.04 and Ubuntu 21.04 using the same configurations. It's a single Node cluster running on a Vagrant VM. The cluster is created with kubeadm. When I switch to an Ubuntu 21.10 (impish) VM, and create a new cluster, the control plane Pods immedia... | CrashLoopBackoff for static controlplane Pods on Ubuntu 21.10 | https://api.github.com/repos/kubernetes/kubernetes/issues/107892/comments | 10 | 2022-02-01T01:03:18Z | 2024-08-08T07:05:45Z | https://github.com/kubernetes/kubernetes/issues/107892 | 1,120,113,005 | 107,892 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I wrote a simple job spec where the pod always fails with an exit code of zero (intentionally, by running the 'false' command).
It uses indexed jobs with parallelism=completions=W and backoffLimit=0. I want each pod to run at least once to failure or success, and have the pod objects remain afte... | Indexed Job with completions>1, parallelism>1, backoffLimit=0: failing pods are deleted but shouldn't be | https://api.github.com/repos/kubernetes/kubernetes/issues/107891/comments | 11 | 2022-01-31T23:49:02Z | 2022-02-07T16:26:47Z | https://github.com/kubernetes/kubernetes/issues/107891 | 1,120,059,036 | 107,891 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
```
Cant' scale down a node because there's no place to move its Pods
Pod is blocking scale down because it’s a non-daemonset, non-mirrored, non-pdb-assigned kube-system pod
```
Why are we getting that?
Is this related to account quota exceeded the number of resources such as vCPU?
###... | [Question] Autopilot creation results in two warnings | https://api.github.com/repos/kubernetes/kubernetes/issues/107889/comments | 4 | 2022-01-31T21:04:48Z | 2022-02-01T03:43:34Z | https://github.com/kubernetes/kubernetes/issues/107889 | 1,119,930,218 | 107,889 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I'm trying to deploy 150 stateful sets, each containing a pod with a replica count of 4.
The pod specification specifies both pod affinity (since the four replicas in a namespace share a volume),
as well as they specify pod topology spread with a maxSkew of 4.
These pods are deployed by a helm... | Scheduling issue when both pod affinity and pod topology spread are specified | https://api.github.com/repos/kubernetes/kubernetes/issues/107888/comments | 13 | 2022-01-31T20:57:30Z | 2022-07-11T15:08:22Z | https://github.com/kubernetes/kubernetes/issues/107888 | 1,119,923,526 | 107,888 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
The Kubelet panics when:
1. It's started with the `enable-controller-attach-detach=false` option;
2. When a CSI volume is attached to a Node.
From the Kubelet logs:
```
I0131 20:18:19.990091 100500 reconciler.go:237] "operationExecutor.AttachVolume started for volume \"pvc-5bcf5717-4d8c-... | Kubelet panics when attaching CSI volumes | https://api.github.com/repos/kubernetes/kubernetes/issues/107886/comments | 3 | 2022-01-31T20:20:38Z | 2022-02-11T20:58:07Z | https://github.com/kubernetes/kubernetes/issues/107886 | 1,119,892,620 | 107,886 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
https://github.com/kubernetes/kubernetes/blob/f90267f0629e546d1c5217c19138e2e8f68bfa92/staging/src/k8s.io/client-go/metadata/fake/simple.go#L50-L52
Lines 50 to 52 in f90267f
![Screenshot 2022-01-31 091220](https://user-images.githubusercontent.com/92919173/151735928-774e907c-c3... | Fake metadata: Concurrent map usage because of mutation of scheme | https://api.github.com/repos/kubernetes/kubernetes/issues/107874/comments | 6 | 2022-01-31T03:44:27Z | 2022-02-01T21:23:44Z | https://github.com/kubernetes/kubernetes/issues/107874 | 1,118,930,966 | 107,874 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
Only annotation to specify EIP allocations for an external NLB is available:
// ServiceAnnotationLoadBalancerEIPAllocations is the annotation used on the
// service to specify a comma separated list of EIP allocations to use as
// static IP addresses for the NLB. Only supporte... | Missing annotation to specify private, static IPs (AWS NLB) | https://api.github.com/repos/kubernetes/kubernetes/issues/107873/comments | 4 | 2022-01-31T03:33:38Z | 2022-02-01T04:16:34Z | https://github.com/kubernetes/kubernetes/issues/107873 | 1,118,915,938 | 107,873 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I'm running my Backend on Kubernetes on around 250 pods under 15 deployments , backend in written in NODEJS.
Sometimes after X number of hours (5<X<30) I'm getting ENOTFOUND in one of the PODS , as follows:
```
{
"name": "main",
"hostname": "entrypoint-sdk-54c8788caa-aa3cj",
"pid":... | Kubernetes (K3S) POD gets "ENOTFOUND" after 5-20 hours of airing time | https://api.github.com/repos/kubernetes/kubernetes/issues/107866/comments | 4 | 2022-01-30T15:08:31Z | 2022-01-30T17:13:12Z | https://github.com/kubernetes/kubernetes/issues/107866 | 1,118,575,208 | 107,866 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Within kube-apiserver the `service-account-signing-key` flag is referenced in the help string but this flag does not exist
https://github.com/kubernetes/kubernetes/blob/63e7ee43bb5394abd6dd5010be47ebcb22ec0ef8/pkg/kubeapiserver/options/authentication.go#L316-L321
### What did you expect to hap... | apiserver: Flag docs references service-account-signing-key flag which doesn't exist | https://api.github.com/repos/kubernetes/kubernetes/issues/107862/comments | 2 | 2022-01-30T04:18:01Z | 2022-01-31T07:04:24Z | https://github.com/kubernetes/kubernetes/issues/107862 | 1,118,402,373 | 107,862 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are flaking?
pull-kubernetes-integration
https://testgrid.k8s.io/presubmits-kubernetes-blocking#pull-kubernetes-integration&graph-metrics=test-duration-minutes
### Which tests are flaking?
Unclear, the entire job is regularly failing with a 2 hour timeout
Relevant failures:
* https://prow.k8s.i... | pull-kubernetes-integration timing out | https://api.github.com/repos/kubernetes/kubernetes/issues/107857/comments | 17 | 2022-01-29T15:27:32Z | 2022-04-01T07:15:28Z | https://github.com/kubernetes/kubernetes/issues/107857 | 1,118,248,173 | 107,857 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
$ make test-e2e-node
fails with an error `[7] E0129 22:41:05.743374 624494 test_context.go:496] Unsupported CRI container runtime: "docker"`
because of the docker deprecation. I think we have to fix the default options for helper scripts.
### What did you expect to happen?
$ make te... | make test_e2e_node fails by default with the docker deprecation. | https://api.github.com/repos/kubernetes/kubernetes/issues/107856/comments | 4 | 2022-01-29T13:47:42Z | 2022-02-06T23:32:53Z | https://github.com/kubernetes/kubernetes/issues/107856 | 1,118,221,493 | 107,856 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
Decrease the TCP Retransmission time of AGNHOST Windows image from 3 seconds to 1 second.
Probe timeout can be decreased as well to 2 seconds.
The RTO can be consistent on both Linux and Windows machines, providing a more reliable probing on network policy test suite.
Defau... | Improve network policy tests reliability on Windows nodes | https://api.github.com/repos/kubernetes/kubernetes/issues/107853/comments | 19 | 2022-01-29T11:51:03Z | 2022-07-07T09:16:03Z | https://github.com/kubernetes/kubernetes/issues/107853 | 1,118,195,879 | 107,853 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Volume couldn't be umount successfuly for an intree rbd volume when csi migratation enabled.
With kubelet loglevel=4, can see the csi plugin volume path is unmounted.
```
Jan 29 07:41:36 node-10-200-112-221 kubelet[75663]: I0129 07:41:36.986617 75663 csi_mounter.go:463] kubernetes.io/csi:... | Umount intree volume failed when csiMigrationRBD enabled. | https://api.github.com/repos/kubernetes/kubernetes/issues/107849/comments | 30 | 2022-01-29T04:41:56Z | 2022-02-11T07:29:48Z | https://github.com/kubernetes/kubernetes/issues/107849 | 1,118,028,044 | 107,849 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
If possible, I'd love to see the option for `kubeadm kubeconfig user` to be able to use not only a kubeadm config file for the required `--config` flag, but also a ConfigMap directly from the cluster.
An alternative would be to specify in the Kubernetes docs how to easily find... | Kubeadm/kubeconfig: user should accept a in-cluster kubeadm config | https://api.github.com/repos/kubernetes/kubernetes/issues/107844/comments | 6 | 2022-01-28T22:41:47Z | 2022-01-31T11:28:03Z | https://github.com/kubernetes/kubernetes/issues/107844 | 1,117,911,815 | 107,844 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
```bash
$ cat testpod.yaml
apiVersion: v1
kind: Pod
metadata:
name: test-pod-ubuntu
spec:
containers:
- name: container-ubuntu
image: ubuntu:20.04
imagePullPolicy: IfNotPresent
command: ["/bin/sleep", "30s"]
$ kubectl apply -f testpod.yaml
pod/test-pod-ubuntu... | Pods fail with "restartPolicy: Always" | https://api.github.com/repos/kubernetes/kubernetes/issues/107838/comments | 9 | 2022-01-28T15:38:14Z | 2022-03-18T13:47:28Z | https://github.com/kubernetes/kubernetes/issues/107838 | 1,117,542,701 | 107,838 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
https://testgrid.k8s.io/sig-node-containerd#cos-cgroupv2-containerd-e2e
### Which tests are failing?
majority of tests
### Since when has it been failing?
Since 01-25
### Testgrid link
_No response_
### Reason for failure (if possible)
_No response_
### Anything else we need to kno... | cos-cgroupv2-containerd-e2e failing | https://api.github.com/repos/kubernetes/kubernetes/issues/107830/comments | 12 | 2022-01-28T02:59:11Z | 2022-02-12T01:32:15Z | https://github.com/kubernetes/kubernetes/issues/107830 | 1,116,948,871 | 107,830 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When running a server-side apply with the following query parameters, the result indicates that there is no change when in fact a field is being deleted from the target object.
```
?dryRun=All&fieldManager=kubectl&force=true
```
(parameters taken from `kubectl diff ... -v6` as reproduced below)... | Server-side apply dry-run incorrectly does not report any changes when removing a field from an object | https://api.github.com/repos/kubernetes/kubernetes/issues/107828/comments | 9 | 2022-01-27T22:57:07Z | 2022-02-01T21:23:22Z | https://github.com/kubernetes/kubernetes/issues/107828 | 1,116,822,024 | 107,828 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Cronjobs created in Kubernetes version v1.20 is not honoring `concurrencyPolicy: Forbid` . It always spins up new jobs if the previous job is still running. As per the docs concurrencyPolicy: Forbid should not spin up new Jobs if one is already running. So this looks like a bug. This is working fine... | CronJob not honoring concurrencyPolicy: Forbid v1.20 | https://api.github.com/repos/kubernetes/kubernetes/issues/107827/comments | 3 | 2022-01-27T20:58:03Z | 2022-01-28T03:21:01Z | https://github.com/kubernetes/kubernetes/issues/107827 | 1,116,730,684 | 107,827 |
[
"kubernetes",
"kubernetes"
] | https://github.com/kubernetes/kubernetes/blob/f90267f0629e546d1c5217c19138e2e8f68bfa92/staging/src/k8s.io/client-go/metadata/fake/simple.go#L50-L52
Because of this scheme mutation, this leads to concurrent use of the same scheme to cause the program to panic. It would be ideal to do this in some concurrent safe mann... | metadata fake: mutation of Scheme leads to concurrent map usage | https://api.github.com/repos/kubernetes/kubernetes/issues/107823/comments | 3 | 2022-01-27T16:29:40Z | 2022-02-02T17:20:22Z | https://github.com/kubernetes/kubernetes/issues/107823 | 1,116,487,682 | 107,823 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Only annotation to specify EIP allocations for an **external** NLB is available:
```
// ServiceAnnotationLoadBalancerEIPAllocations is the annotation used on the
// service to specify a comma separated list of EIP allocations to use as
// static IP addresses for the NLB. Only supported on elbv... | Missing annotation to specify private, static IPs for AWS NLB | https://api.github.com/repos/kubernetes/kubernetes/issues/107822/comments | 6 | 2022-01-27T16:11:32Z | 2022-02-02T21:16:42Z | https://github.com/kubernetes/kubernetes/issues/107822 | 1,116,454,935 | 107,822 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Mounting a ssh-key via a secret and subpath where an existing key was present, renders the key unusable of the ssh-clieent
### What did you expect to happen?
Overmount with subpath should work or not work transparently. In this case it seems to work, but not in all cases.
### How can we r... | Over-Mounting an ssh-key using subpath makes the key unusable for the ssh-client | https://api.github.com/repos/kubernetes/kubernetes/issues/107818/comments | 9 | 2022-01-27T12:21:30Z | 2022-06-26T19:31:39Z | https://github.com/kubernetes/kubernetes/issues/107818 | 1,116,145,804 | 107,818 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
We're running Openshift in a enterprise environment and noticed something strange happening to Deployments with all 3 probes (liveness, readiness and startup).
If a new pod is beeing rolled out the container within is booting up without issues. However if for some reason (e.g. application erro... | StartupProbe seem to only restart/trigger with pod restart | https://api.github.com/repos/kubernetes/kubernetes/issues/107817/comments | 9 | 2022-01-27T11:08:27Z | 2022-02-16T18:32:18Z | https://github.com/kubernetes/kubernetes/issues/107817 | 1,116,076,865 | 107,817 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are flaking?
pull-kubernetes-unit
### Which tests are flaking?
k8s.io/kubernetes/pkg/proxy/ipvs.Test_RaceTerminateRSList
### Since when has it been flaking?
~1 day since merging of https://github.com/kubernetes/kubernetes/pull/107748
### Testgrid link
https://testgrid.k8s.io/presubmi... | [flake] Test_RaceTerminateRSList seems to be flaking | https://api.github.com/repos/kubernetes/kubernetes/issues/107811/comments | 4 | 2022-01-27T06:19:05Z | 2022-01-27T11:02:26Z | https://github.com/kubernetes/kubernetes/issues/107811 | 1,115,818,244 | 107,811 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
```
func (c *FakeEndpoints) List(ctx context.Context, opts v1.ListOptions) (result *corev1.EndpointsList, err error) {
obj, err := c.Fake.
Invokes(testing.NewListAction(endpointsResource, endpointsKind, c.ns, opts), &corev1.EndpointsList{})
if obj == nil {
return nil, ... | Fake client list watch support field selector | https://api.github.com/repos/kubernetes/kubernetes/issues/107809/comments | 9 | 2022-01-27T02:16:33Z | 2022-07-16T09:59:26Z | https://github.com/kubernetes/kubernetes/issues/107809 | 1,115,692,198 | 107,809 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are flaking?
https://testgrid.k8s.io/sig-node-cri-o#node-kubelet-serial-crio
### Which tests are flaking?
```
E2eNode Suite.[sig-node] Topology Manager [Serial] [Feature:TopologyManager][NodeFeature:TopologyManager] With kubeconfig updated to static CPU Manager policy run the Topology Manager tests r... | sig-node-cri-o#node-kubelet-serial-crio: failing test Topology Manager [Serial] [Feature:TopologyManager][NodeFeature:TopologyManager] With kubeconfig updated to static CPU Manager policy run the Topology Manager tests run Topology Manager policy test suite | https://api.github.com/repos/kubernetes/kubernetes/issues/107805/comments | 6 | 2022-01-26T21:12:19Z | 2022-02-22T08:53:53Z | https://github.com/kubernetes/kubernetes/issues/107805 | 1,115,506,130 | 107,805 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
sig-node-cri-o#ci-crio-cgroupv1-node-e2e-eviction
### Which tests are failing?
```
E2eNode Suite.[sig-node] PriorityPidEvictionOrdering [Slow] [Serial] [Disruptive][NodeFeature:Eviction] when we run containers that should cause PIDPressure should eventually evict all of the correct pods
... | sig-node-cri-o#ci-crio-cgroupv1-node-e2e-eviction: test fail PriorityPidEvictionOrdering [Slow] [Serial] [Disruptive][NodeFeature:Eviction] when we run containers that should cause PIDPressure should eventually evict all of the correct pods | https://api.github.com/repos/kubernetes/kubernetes/issues/107804/comments | 11 | 2022-01-26T21:08:26Z | 2022-12-19T10:38:14Z | https://github.com/kubernetes/kubernetes/issues/107804 | 1,115,502,927 | 107,804 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
https://testgrid.k8s.io/sig-node-cri-o#ci-crio-cgroupv1-node-e2e-alpha
this job seems to be misconfigured. It suppose to run alpha tests based on the name, but doesn't
### Which tests are failing?
```
E2eNode Suite.[sig-storage] ConfigMap optional updates should be reflected in volume... | sig-node-cri-o#ci-crio-cgroupv1-node-e2e-alpha is running non-alpha tests and failing doing so | https://api.github.com/repos/kubernetes/kubernetes/issues/107803/comments | 6 | 2022-01-26T20:31:28Z | 2022-04-27T18:30:11Z | https://github.com/kubernetes/kubernetes/issues/107803 | 1,115,473,272 | 107,803 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
sig-node-cos#soak-cos-gce
### Which tests are failing?
The test https://testgrid.k8s.io/sig-node-cos#soak-cos-gce exercise interesting behavior. It fails all the time with NPD issue (may be related to https://github.com/kubernetes/kubernetes/issues/107067), but for other tests it runs ... | sig-node-cos#soak-cos-gce is failing quite often | https://api.github.com/repos/kubernetes/kubernetes/issues/107802/comments | 12 | 2022-01-26T20:26:59Z | 2022-06-30T09:06:11Z | https://github.com/kubernetes/kubernetes/issues/107802 | 1,115,468,307 | 107,802 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
- https://testgrid.k8s.io/sig-node-containerd#containerd-node-e2e-features-1.4
- https://testgrid.k8s.io/sig-node-containerd#containerd-node-e2e-features-1.5
- https://testgrid.k8s.io/sig-node-containerd#cos-cgroupv2-containerd-e2e
### Which tests are failing?
most of tests
### Sinc... | Many tests are failing since 1/24 in containerd tab | https://api.github.com/repos/kubernetes/kubernetes/issues/107801/comments | 4 | 2022-01-26T20:14:31Z | 2022-02-02T05:34:55Z | https://github.com/kubernetes/kubernetes/issues/107801 | 1,115,449,309 | 107,801 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
- https://testgrid.k8s.io/sig-node-containerd#containerd-e2e-ubuntu
- https://testgrid.k8s.io/sig-node-containerd#containerd-node-e2e-1.4
- https://testgrid.k8s.io/sig-node-containerd#e2e-cos-device-plugin-gpu
- https://testgrid.k8s.io/sig-node-containerd#e2e-ubuntu
### Which tests ... | A number of containerd tests fail to start | https://api.github.com/repos/kubernetes/kubernetes/issues/107800/comments | 21 | 2022-01-26T20:12:18Z | 2022-02-14T23:29:22Z | https://github.com/kubernetes/kubernetes/issues/107800 | 1,115,445,792 | 107,800 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Occasionally rescheduling deployments that container HostProcessContainers repeatedly experience `ErrImagePull` errors.
It looks like this is most common when `ImagePullPolicy: Always` is specified and setting `ImagePullPolicy: IfNotPresent` in the deployment appears to fix the issue.
This was c... | [Windows] HostProcessContainers sometimes fail repeatedly with ErrImagePull | https://api.github.com/repos/kubernetes/kubernetes/issues/107799/comments | 3 | 2022-01-26T19:46:46Z | 2022-04-07T16:54:13Z | https://github.com/kubernetes/kubernetes/issues/107799 | 1,115,419,906 | 107,799 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
I want to create, monitor and delete pods from one existing pod. The in_cluster_config.py in example/ folder can help me to create and delete pods. However, I did not find any APIs that can help me to monitor the memory and CPU usage just that can be achieve through "kubectl top po... | Get cpu and memory usage through in cluster config. | https://api.github.com/repos/kubernetes/kubernetes/issues/107798/comments | 3 | 2022-01-26T19:04:38Z | 2022-01-26T20:05:34Z | https://github.com/kubernetes/kubernetes/issues/107798 | 1,115,380,476 | 107,798 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Most of the FooApplyConfiguration constructors pre-fill the Kind and APIVersion fields to make using them smooth.
But k8s.io/client-go/applyconfigurations/autoscaling/v1.Scale() is missing this, making patterns like this fail:
```go
_, err = deployments.ApplyScale(
ctx, deploymentName,
s... | client-go: Scale() constructor for ScaleApplyConfiguration missing WithKind, WithAPIVersion | https://api.github.com/repos/kubernetes/kubernetes/issues/107795/comments | 3 | 2022-01-26T18:45:32Z | 2022-02-08T17:59:14Z | https://github.com/kubernetes/kubernetes/issues/107795 | 1,115,364,682 | 107,795 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
The error code of `pods "pod-gvh4t" already exists, the server was not able to generate a unique name for the object` is 409.
Is this an expected behavior? The doc seems to say no:
> If this field is specified and the generated name exists, the server will
NOT return a 409 - instead, it will e... | The error code for GenerateName conflict shouldn't be 409 | https://api.github.com/repos/kubernetes/kubernetes/issues/107790/comments | 9 | 2022-01-26T13:02:50Z | 2022-03-29T09:58:47Z | https://github.com/kubernetes/kubernetes/issues/107790 | 1,114,994,700 | 107,790 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When I removed rancher from my kubernets cluster, some finalizers keep running in background, and report many errors:
```bash
kubectl -n kube-system logs --tail 300 pod/kube-apiserver-ci-k8s-master-1 |grep ^E
```
>E0126 09:48:41.126515 1 crd_finalizer.go:299] projectroletemplatebinding... | useless finalizers keep running in background | https://api.github.com/repos/kubernetes/kubernetes/issues/107788/comments | 6 | 2022-01-26T10:10:58Z | 2022-02-07T12:02:06Z | https://github.com/kubernetes/kubernetes/issues/107788 | 1,114,844,190 | 107,788 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
One of my nodes failed because of DiskPressure. I solved that issue then I've deleted pod which running on that node to bring up that service quickly. I saw "pod deleted" message and replicaset created new pod for that service but old pod haven't disappeared from pods list even new one Running.
W... | Kubernetes shows pod that not actually exist | https://api.github.com/repos/kubernetes/kubernetes/issues/107772/comments | 3 | 2022-01-26T02:32:42Z | 2022-01-26T02:36:15Z | https://github.com/kubernetes/kubernetes/issues/107772 | 1,114,563,336 | 107,772 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are flaking?
https://github.com/kubernetes/kubernetes/issues/107708
### Which tests are flaking?
TestRoundTripSocks5AndNewConnection
### Since when has it been flaking?
Disabled by https://github.com/kubernetes/kubernetes/pull/107758
### Testgrid link
_No response_
### Reason for failure (if poss... | Enable TestRoundTripSocks5AndNewConnection | https://api.github.com/repos/kubernetes/kubernetes/issues/107766/comments | 3 | 2022-01-25T21:39:23Z | 2022-01-29T10:48:01Z | https://github.com/kubernetes/kubernetes/issues/107766 | 1,114,389,065 | 107,766 |
[
"kubernetes",
"kubernetes"
] | > I did a trivial pass on 1.20 -> 1.23 e2e serial runs in openshift ci environments, and while I see the failed mount errors during test pod creation, all of them seemed to be associated with races between the test creating the secret/config map and the pod getting created (i.e. some background controller creates the i... | e2e test should wait for kube-root-ca.crt to be created in the namespace | https://api.github.com/repos/kubernetes/kubernetes/issues/107762/comments | 4 | 2022-01-25T18:12:53Z | 2022-01-26T03:20:46Z | https://github.com/kubernetes/kubernetes/issues/107762 | 1,114,213,496 | 107,762 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I have enabled audit logging on apiserver and capturing all resources
resources: ["persistentvolumeclaims", "persistentvolume", "pods", "events", "deployments", "statefulsets","daemonsets", "secrets", "configmaps"]
i am not getting the audit log for deployments, daemonsets, statefulsets, persi... | audit logs are not getting generated for deployment, statefulset, pvc | https://api.github.com/repos/kubernetes/kubernetes/issues/107759/comments | 5 | 2022-01-25T16:41:33Z | 2022-01-26T10:19:03Z | https://github.com/kubernetes/kubernetes/issues/107759 | 1,114,121,033 | 107,759 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
We run sonobuoy tests on production running clusters whenever we upgrade our clusters. We observe that `should support creating Ingress API operations` fails when we already have nginx-ingress controller running in the cluster.
The newer versions of nginx-ingress controller comes up with a valid... | e2e test for creating Ingress API operations fails when ingress controller is already in place | https://api.github.com/repos/kubernetes/kubernetes/issues/107752/comments | 5 | 2022-01-25T13:41:51Z | 2022-01-26T09:30:25Z | https://github.com/kubernetes/kubernetes/issues/107752 | 1,113,904,489 | 107,752 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I created the relevant yaml manifests using kube-prometheus jsonnet. I was able to use Kustomize to apply everything until I added the images section in Kustomize.
### What did you expect to happen?
I expected Kustomize to work.
### How can we reproduce it (as minimally and precisely as possible)... | Kustomize doesn't work with CRDs when specifying images | https://api.github.com/repos/kubernetes/kubernetes/issues/107751/comments | 6 | 2022-01-25T13:14:58Z | 2022-01-25T13:56:52Z | https://github.com/kubernetes/kubernetes/issues/107751 | 1,113,875,528 | 107,751 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When a Pod is executing TeadDownPod in StopPodsandbox, PLEG will stuck in asynchronously GetPodNetworkStatus. Because they take the same Pod lock.
A potential condition `networkReady` could avoid the unnecessary wait. But `networkReady` cannot become false until the TearDownPod method is fini... | Slow CNI requests, such as TearDownPod would cause PLEG to be unhealthy. | https://api.github.com/repos/kubernetes/kubernetes/issues/107749/comments | 13 | 2022-01-25T13:05:02Z | 2022-07-09T11:45:15Z | https://github.com/kubernetes/kubernetes/issues/107749 | 1,113,865,016 | 107,749 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I have a 3-node cluster (1 master + 2 worker). I am exploring dual-stack capabilities of Kubernetes (version 1.21). I have used kubeadm to initialize this cluster. To begin with, I see IPv4 address of nodes in `kubectl get nodes -o wide` command. Also, I can fetch logs of pods using `kubectl logs` c... | kubectl logs command gives error if worker node has IPv6 address | https://api.github.com/repos/kubernetes/kubernetes/issues/107743/comments | 35 | 2022-01-25T08:27:19Z | 2022-04-05T20:25:56Z | https://github.com/kubernetes/kubernetes/issues/107743 | 1,113,571,955 | 107,743 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Creating an endpoint slice and service in a cluster relying upon kube-dns results in no DNS resolution for either the service name or the hostnames under it. The endpoint slice is not seen by kube-dns.
This impacts Google Kubernetes Engine up to the current rapid version 1.22.3-gke.1500, includ... | Kubernetes DNS Specification does not recognize EndpointSlices, kube-dns & coredns diverge on behavior | https://api.github.com/repos/kubernetes/kubernetes/issues/107742/comments | 25 | 2022-01-25T08:05:09Z | 2022-08-08T01:08:07Z | https://github.com/kubernetes/kubernetes/issues/107742 | 1,113,551,308 | 107,742 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Hi,
We were using Kubernetes 1.16 release, we were using pod preset plugin to inject runtime timezone configuration(so that pods will be in the same time as hosts) to the Kube-system pod and as well other pods in a different namespace.
Now, we are upgrading k8s to 1.21 and could see the pod pr... | podpreset is not working with 1.21 k8s version | https://api.github.com/repos/kubernetes/kubernetes/issues/107741/comments | 7 | 2022-01-25T06:16:11Z | 2022-04-07T21:32:42Z | https://github.com/kubernetes/kubernetes/issues/107741 | 1,113,473,531 | 107,741 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
In AWS EKS a issue was discovered in ipv6 only clusters. When nodes with expanded ipv6 address are created `2600:1f14:1d4:d101:0:0:0:ba3d` the string comparison [here](https://github.com/kubernetes/kubernetes/blob/master/pkg/kubelet/nodestatus/setters.go#L129) ends up comparing `2600:1f14:1d4:d101:0... | Kubelet does not assign node address on expanded ipv6 address | https://api.github.com/repos/kubernetes/kubernetes/issues/107735/comments | 12 | 2022-01-24T20:03:18Z | 2022-01-27T07:07:15Z | https://github.com/kubernetes/kubernetes/issues/107735 | 1,113,083,160 | 107,735 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
In Kubernetes 1.23 we are seeing some static pods fail to start. These static pods failures are on quick remove and adds leaving the static pod not started.
We need to revert kubernetes/kubernetes#104743.
cc @gjkim42
### What did you expect to happen?
All static pods should restart.
### Ho... | Some static pods fail to start on K8S 1.22 and 1.23 | https://api.github.com/repos/kubernetes/kubernetes/issues/107733/comments | 25 | 2022-01-24T19:18:55Z | 2022-03-18T12:35:04Z | https://github.com/kubernetes/kubernetes/issues/107733 | 1,113,043,128 | 107,733 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
After running some Pods and deleting them, sometimes the sandbox containers of the deleted Pods remains until next kubelet restart.
```
# No nginx Pod on the node
$ kubectl get pods -A -o wide --field-selector=spec.nodeName=bm02
NAMESPACE NAME READY STATUS RESTARTS ... | Some Pod sandboxes were not cleaned up until next kubelet restart | https://api.github.com/repos/kubernetes/kubernetes/issues/107730/comments | 14 | 2022-01-24T18:03:33Z | 2022-10-13T18:59:40Z | https://github.com/kubernetes/kubernetes/issues/107730 | 1,112,971,320 | 107,730 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Integration test timed out due to the following error
```
E0120 14:05:02.398256 118058 runtime.go:77] Observed a panic: FieldManager must be installed to run apply
```
The error appeared 748 times in the log. Looks like lots of churning happens during the apf configuration bootstrapping phas... | absence of openapi configuration in integration tests makes server-side apply panic (broke apf controller when it switched to SSA) | https://api.github.com/repos/kubernetes/kubernetes/issues/107727/comments | 47 | 2022-01-24T15:10:34Z | 2022-10-18T16:18:05Z | https://github.com/kubernetes/kubernetes/issues/107727 | 1,112,772,230 | 107,727 |
[
"kubernetes",
"kubernetes"
] | Quite a few contributors do not have access to beefy environments to run `make update` or `make verify`. They are able to use vscode/wsl/codespaces etc to suggest changes, but do get tripped up from our `make verify` scripts as quite a few scenarios we end up with files that needs to be re-generated. Its a high bar for... | Helper CI job that runs `make update` to make it easier for contributors | https://api.github.com/repos/kubernetes/kubernetes/issues/107726/comments | 13 | 2022-01-24T15:10:24Z | 2022-08-28T12:11:36Z | https://github.com/kubernetes/kubernetes/issues/107726 | 1,112,772,014 | 107,726 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Hi everyone!
We need to to start batch job with large input. **The problem is limit for yaml file size**. Current limit is just `3 MB`, but my job is larger, approximately `200 MB` . When trying to start we get the following error:
````
Error from server (RequestEntityTooLarge): error when c... | Can not apply job with large yaml file - RequestEntityTooLarge | https://api.github.com/repos/kubernetes/kubernetes/issues/107723/comments | 4 | 2022-01-24T14:35:54Z | 2022-01-25T21:19:07Z | https://github.com/kubernetes/kubernetes/issues/107723 | 1,112,730,838 | 107,723 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
With the flag **--cpu-manager-policy=static** and other required flags **--kube-reserved** and **--system-reserved**,
similar situation to the issue #103952 happens.
A guaranteed pod that has multiple containers gets the status "CrashLoopBackOff". Detailed description is [here](https://github.c... | The CPU manager does not work correctly for the guaranteed pod with multiple containers and kubelet flag --cpu-manager-policy=static | https://api.github.com/repos/kubernetes/kubernetes/issues/107721/comments | 3 | 2022-01-24T14:18:11Z | 2022-01-24T16:43:14Z | https://github.com/kubernetes/kubernetes/issues/107721 | 1,112,708,966 | 107,721 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
ingress.yaml
``` yaml
apiVersion: networking.k8s.io/v1
kind: IngressClass
metadata:
name: istio
spec:
controller: istio.io/ingress-controller
---
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: rsatest
namespace: default
spec:
ingressClassName: istio
rule... | kubectl describe ingress shows `default-backend:80` when no default backend is present. | https://api.github.com/repos/kubernetes/kubernetes/issues/107720/comments | 7 | 2022-01-24T14:15:21Z | 2022-03-18T17:58:53Z | https://github.com/kubernetes/kubernetes/issues/107720 | 1,112,705,396 | 107,720 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I am implementing a Runtime for Kubernetes using CRI.
When containerStatus.Status.LogPath is empty, Kubelet removes some files that we don't expect to remove, such as /bin symbolic links.
### What did you expect to happen?
I think Kubelet will print an error log telling me that LogPath cannot be ... | when LogPath is empty, Kubelet removes some files that we don't expect to remove | https://api.github.com/repos/kubernetes/kubernetes/issues/107717/comments | 8 | 2022-01-24T13:40:14Z | 2022-02-09T18:29:44Z | https://github.com/kubernetes/kubernetes/issues/107717 | 1,112,664,546 | 107,717 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
kubectl stopped the command, because one of the pods that the label matches is in `Shutdown` state and the logs of the container are not available
```
kubectl logs -f -l app=request-insights
Error from server (BadRequest): container "app" in pod "request-insights-7db45c4d5d-2p4gp" is not availa... | kubectl logs -f .. -l ... fails if one of the matching containers is not ready | https://api.github.com/repos/kubernetes/kubernetes/issues/107714/comments | 4 | 2022-01-24T13:14:05Z | 2022-03-02T17:41:57Z | https://github.com/kubernetes/kubernetes/issues/107714 | 1,112,633,157 | 107,714 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I run service mesh sidecar (in my case Istio) in PODs that are created/controlled by `Jobs`. "Main" container shuts down the istio sidecar via API call to 127.0.0.1 and exits with an actual application code. The issue is when "main" container finishes with error, POD status often displays `Completed... | Inconsistent POD status reporting | https://api.github.com/repos/kubernetes/kubernetes/issues/107713/comments | 24 | 2022-01-24T10:24:57Z | 2024-05-07T10:29:44Z | https://github.com/kubernetes/kubernetes/issues/107713 | 1,112,448,897 | 107,713 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are flaking?
It's not a CI job that is failing, the failures are happening when I run the e2e external storage tests myself with the Ember CSI driver, but I thought this would be the most appropriate kind of issue to open.
### Which tests are flaking?
During e2e External Storage provisioning tests the... | External Storage data source e2e tests failing due to unflushed data. | https://api.github.com/repos/kubernetes/kubernetes/issues/107711/comments | 5 | 2022-01-24T10:01:22Z | 2022-06-23T11:50:04Z | https://github.com/kubernetes/kubernetes/issues/107711 | 1,112,417,812 | 107,711 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
As https://github.com/kubernetes/kubernetes/pull/107703 described, some test utilities like `NewTestQueue()` instantiate an informerFactory and start it. However, the caller instantiates another informerFactory and start it. We should reuse the informer.
https://github.com/kuberne... | Reuse informer instance in tests | https://api.github.com/repos/kubernetes/kubernetes/issues/107710/comments | 5 | 2022-01-24T09:36:05Z | 2022-02-10T01:54:37Z | https://github.com/kubernetes/kubernetes/issues/107710 | 1,112,392,254 | 107,710 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are flaking?
- gce-cos-master-slow
### Which tests are flaking?
- Kubernetes e2e suite. [sig-storage] In-tree Volumes [Driver: gluster] [Testpattern: Pre-provisioned PV (default fs)] volumeIO should write files of various sizes, verify size, validate content [Slow]
- ci-kubernetes-e2e-gci-gce-slow.Ov... | [Flaky test] gce-cos-master-slow | https://api.github.com/repos/kubernetes/kubernetes/issues/107709/comments | 5 | 2022-01-24T05:18:09Z | 2022-01-25T17:27:51Z | https://github.com/kubernetes/kubernetes/issues/107709 | 1,112,186,068 | 107,709 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are flaking?
- ci-kubernetes-unit
### Which tests are flaking?
- ci-kubernetes-unit.Overall
- k8s.io/kubernetes/pkg/kubelet/eviction.TestStart
- k8s.io/kubernetes/vendor/k8s.io/apiserver/pkg/server/filters.TestTimeoutHeaders
- k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/httpst... | [Flaky test] ci-kubernetes-unit | https://api.github.com/repos/kubernetes/kubernetes/issues/107708/comments | 9 | 2022-01-24T04:30:24Z | 2022-01-28T17:32:43Z | https://github.com/kubernetes/kubernetes/issues/107708 | 1,112,160,141 | 107,708 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are flaking?
sig-release-master-blocking
* verify-master
### Which tests are flaking?
* ci-kubernetes-verify-master.Overall
* verify.typecheck
### Since when has it been flaking?
History goes back until January 7
### Testgrid link
https://testgrid.k8s.io/sig-release-master-blockin... | [Flaky test] verify-master, verify-typecheck | https://api.github.com/repos/kubernetes/kubernetes/issues/107702/comments | 13 | 2022-01-22T16:06:49Z | 2022-03-10T04:17:35Z | https://github.com/kubernetes/kubernetes/issues/107702 | 1,111,608,890 | 107,702 |
[
"kubernetes",
"kubernetes"
] | Be cool to see who has the easiest to use and most functional template?? | Pick a template | https://api.github.com/repos/kubernetes/kubernetes/issues/107694/comments | 4 | 2022-01-21T22:30:25Z | 2022-01-24T03:59:23Z | https://github.com/kubernetes/kubernetes/issues/107694 | 1,111,002,363 | 107,694 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I have been working on the issue (https://github.com/kyverno/kyverno/issues/3004) and the problem that we are facing is that, we have `anyPattern` defined in [api/kyverno/v1/policy_types.go](https://github.com/kyverno/kyverno/blob/5ad0d152402f690bd5af2a14ce12d1608ca7d4ca/api/kyverno/v1/policy_types.... | `anyPattern` of type `apiextensions.JSON` breaks for kyverno cluster policy CRD in k8s v1.23 but works for previous k8s versions | https://api.github.com/repos/kubernetes/kubernetes/issues/107690/comments | 4 | 2022-01-21T19:16:43Z | 2022-01-26T02:22:20Z | https://github.com/kubernetes/kubernetes/issues/107690 | 1,110,806,918 | 107,690 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Not really sure how to report this, it seems like an incompatibility with another program's use of the CNI config directory.
podman (like kubernetes) seems ot use CNI for its networking. On systems like RHCoreOS that pre-install podman, podman pre-installs its own CNI plugin and the `87-podman-b... | podman pre-installs its own CNI, interfering with bootstrap of other CNIs | https://api.github.com/repos/kubernetes/kubernetes/issues/107687/comments | 14 | 2022-01-21T15:37:42Z | 2022-06-23T18:50:35Z | https://github.com/kubernetes/kubernetes/issues/107687 | 1,110,603,896 | 107,687 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Upgrading from 1.18.20 to 1.19.16 on ubuntu 20.04 with pakages results on strange behaviour
Upgrading kubeadm to 1.19.16-00 results in having kubelet 1.19.16-00 to be installed which contradicts the documentation that say
- upgrade kubeadm
- do `kubeadm upgrade node`
- upgrade kubelet
As... | kubeadm 1.19.16-00 depends on kubelet>=1.19.0 which might break upgrade | https://api.github.com/repos/kubernetes/kubernetes/issues/107685/comments | 11 | 2022-01-21T14:38:34Z | 2022-07-03T20:50:27Z | https://github.com/kubernetes/kubernetes/issues/107685 | 1,110,542,112 | 107,685 |
Subsets and Splits
Unique Owner-Repo Count
Counts the number of unique owner-repos in the dataset, providing a basic understanding of diverse repositories.