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?
In the current k8s implementation, once the POD is terminated & a new instance is started, the log files associated with the OLD POD get deleted. Is there an existing option to retain the immediate previous POD instance logs under the /var/log/pods?
### Why is this needed?
I coul... | [Query] How to retain the terminated POD logs? | https://api.github.com/repos/kubernetes/kubernetes/issues/105877/comments | 14 | 2021-10-25T10:38:18Z | 2022-04-07T16:06:30Z | https://github.com/kubernetes/kubernetes/issues/105877 | 1,034,967,083 | 105,877 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I have two PVs with same UniqueVolumeName. Two different pods use those PVs assigned to the same node.
The first assigned pod can run well, but the second assigned pod can't be set up correctly.
### What did you expect to happen?
My two pods both can be set up correctly.
### How can we reproduce... | multi PV with same unique volume name mount failed | https://api.github.com/repos/kubernetes/kubernetes/issues/105868/comments | 8 | 2021-10-25T04:05:50Z | 2021-11-02T10:04:59Z | https://github.com/kubernetes/kubernetes/issues/105868 | 1,034,651,549 | 105,868 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
I would like to propose the graduation of the [evictions_number](https://github.com/kubernetes/kubernetes/blame/0d50c969c587c8a6c16e0962118305ac652c5a6b/pkg/controller/nodelifecycle/metrics.go#L67) metric from alpha to stable.
### Why is this needed?
The `evictions_number` metric... | Proposed graduation of evictions_number metric to stable | https://api.github.com/repos/kubernetes/kubernetes/issues/105864/comments | 9 | 2021-10-24T15:37:32Z | 2021-12-13T07:19:59Z | https://github.com/kubernetes/kubernetes/issues/105864 | 1,034,446,107 | 105,864 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I'm trying to push a large .yaml file (over 3 MB, less than 4 MB) with kubectl.
`kubectl apply -f viya4-sasdeployment.yaml -n sasoperator`
In response I've got :
`Error from server (RequestEntityTooLarge): error when creating "viya4-sasdeployment.yaml": Request entity too large: limit is 3145728... | [KUBE-APISERVER] Error from server (RequestEntityTooLarge Request entity too large: limit is 3145728 | https://api.github.com/repos/kubernetes/kubernetes/issues/105863/comments | 9 | 2021-10-24T15:33:18Z | 2023-12-08T13:11:59Z | https://github.com/kubernetes/kubernetes/issues/105863 | 1,034,445,273 | 105,863 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
I would like to propose the graduation of the following apiserver metrics from alpha to stable:
- [apiserver_response_sizes](https://github.com/kubernetes/kubernetes/blob/0d50c969c587c8a6c16e0962118305ac652c5a6b/staging/src/k8s.io/apiserver/pkg/endpoints/metrics/metrics.go#L118)... | Proposed graduation of apiserver metrics from alpha to stable | https://api.github.com/repos/kubernetes/kubernetes/issues/105862/comments | 14 | 2021-10-24T15:28:42Z | 2021-11-08T18:55:20Z | https://github.com/kubernetes/kubernetes/issues/105862 | 1,034,444,310 | 105,862 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
I would like to propose the graduation of the following scheduler metrics from alpha to stable:
- [pending_pods](https://github.com/kubernetes/kubernetes/blob/0d50c969c587c8a6c16e0962118305ac652c5a6b/pkg/scheduler/metrics/metrics.go#L88)
- [preemption_attempts_total](https://gi... | Proposed graduation of scheduler metrics from alpha to stable | https://api.github.com/repos/kubernetes/kubernetes/issues/105861/comments | 15 | 2021-10-24T14:53:39Z | 2021-11-04T17:06:04Z | https://github.com/kubernetes/kubernetes/issues/105861 | 1,034,436,123 | 105,861 |
[
"kubernetes",
"kubernetes"
] | How can this be implemented in RKE yaml config ?
`extra_args` does not seep to accept it.
I tried:
```
kubelet:
image: ""
extra_args:
allowedUnsafeSysctls: '`net.∗`'
```
_Originally posted by @haimari in https://github.com/kubernetes/kubernetes/issues/94249#issuecomment-950279369_ | unsafesysctl - How can this be implemented in RKE yaml config ? | https://api.github.com/repos/kubernetes/kubernetes/issues/105859/comments | 4 | 2021-10-24T08:00:53Z | 2021-10-24T10:35:59Z | https://github.com/kubernetes/kubernetes/issues/105859 | 1,034,351,577 | 105,859 |
[
"kubernetes",
"kubernetes"
] | /sig/networking
### What happened?
Hi,
I have a self managed k8s cluster...
The service type is load balancer , but the load balancer does not get started ,
even after giving
### What did you expect to happen?
Expected aws Load Balancer to start getting created in the self managed cluster
### How ... | aws loadbalancer not started even if Service type is Lodbalancer | https://api.github.com/repos/kubernetes/kubernetes/issues/105856/comments | 7 | 2021-10-23T13:31:12Z | 2022-03-26T22:02:29Z | https://github.com/kubernetes/kubernetes/issues/105856 | 1,034,168,175 | 105,856 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
```
udp 17 119 src=20.170.20.31 dst=10.163.216.84 sport=2123 dport=2123 src=192.168.77.37 dst=192.168.143.64 sport=9323 dport=30219 [ASSURED] mark=0 use=2
```
Worker Node Tunnel Endpoint
```
tunl0: flags=193<UP,RUNNING,NOARP> mtu 1480
inet 192.168.143.64 netmask 255.255.255.... | UDP conntrack shows wrong IP after changing the backend Pod of K8s and reusing same LB IP to different service | https://api.github.com/repos/kubernetes/kubernetes/issues/105848/comments | 7 | 2021-10-22T15:11:23Z | 2021-10-24T17:29:08Z | https://github.com/kubernetes/kubernetes/issues/105848 | 1,033,689,021 | 105,848 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
For a container running as a NonRoot user, debug pod created by `kubectl debug node` cannot access the root of the process. User case [here](https://github.com/kubernetes/enhancements/issues/277#issuecomment-949320689)
### What did you expect to happen?
Privileged debug pod on the node should be a... | kubectl debug node cannot access root of non-root user process | https://api.github.com/repos/kubernetes/kubernetes/issues/105846/comments | 22 | 2021-10-22T14:40:46Z | 2024-05-15T09:14:29Z | https://github.com/kubernetes/kubernetes/issues/105846 | 1,033,657,562 | 105,846 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Limits applied by LimitRanger to a static Pod are not in effect.
### What did you expect to happen?
Either do apply limits or to not show them in yaml/API and document such behavior (if not yet :smiley:)
First is preferable per my opinion.
### How can we reproduce it (as minimally and precisely ... | Allowing mutating webhook to change pod spec for mirror pods is confusing. Consider making it clearer | https://api.github.com/repos/kubernetes/kubernetes/issues/105844/comments | 47 | 2021-10-22T13:53:59Z | 2024-09-24T20:21:30Z | https://github.com/kubernetes/kubernetes/issues/105844 | 1,033,608,861 | 105,844 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When we try to update deployment resource many times where it fails intermittently, status would show incorrect information. Please check steps below for more information.
### What did you expect to happen?
In case of failure, deployment status should show correct information. Please check s... | Incorrect status of kubernetes deployment after updating deployment few times | https://api.github.com/repos/kubernetes/kubernetes/issues/105842/comments | 7 | 2021-10-22T11:23:05Z | 2022-06-05T22:59:18Z | https://github.com/kubernetes/kubernetes/issues/105842 | 1,033,474,978 | 105,842 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
Enhance scheduler logging and address current issues.
1. Migrate the current unstructured logs to structured logging.
- Klog APIs of unstructured logs are found in 2 directories (cmd/kube-scheduler, pkg/scheduler)
- Primarily files in pkg/scheduler/framework and pkg/s... | Migrate scheduler to structured logging | https://api.github.com/repos/kubernetes/kubernetes/issues/105841/comments | 31 | 2021-10-22T10:38:21Z | 2022-03-25T19:36:45Z | https://github.com/kubernetes/kubernetes/issues/105841 | 1,033,435,918 | 105,841 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
service cannot match endpoint event
### What did you expect to happen?
I think service can match pod
### How can we reproduce it (as minimally and precisely as possible)?
```
helm upgrade cilium cilium/cilium --version 1.10.3 --namespace=kube-system \
......
--set prometheus.enable... | service cannot match endpoint | https://api.github.com/repos/kubernetes/kubernetes/issues/105840/comments | 5 | 2021-10-22T08:12:05Z | 2021-10-22T10:45:33Z | https://github.com/kubernetes/kubernetes/issues/105840 | 1,033,302,636 | 105,840 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
1. I deployed a deployment object with 3 replicas.
2. I added the following IP table rule on one of the nodes where a replica is running (after ensuring I am able to SSH after running the following command):
`sudo iptables -P OUTPUT DROP`
The Node goes to NotReady state in about 40 seconds ... | Pod Eviction Timeout not respected | https://api.github.com/repos/kubernetes/kubernetes/issues/105838/comments | 18 | 2021-10-22T03:41:38Z | 2021-11-01T22:19:06Z | https://github.com/kubernetes/kubernetes/issues/105838 | 1,033,145,987 | 105,838 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
According to the pull request https://github.com/kubernetes/kubernetes/pull/98546 in-tree vSphere v6.5 is deprecated and it will be able to be deleted on Kubernetes v1.24.
On the other hand, VMware announced vSphere v6.5 support period is extended from the original November 15, ... | Request for extending vSphere v6.5 support | https://api.github.com/repos/kubernetes/kubernetes/issues/105837/comments | 19 | 2021-10-22T02:54:56Z | 2023-01-06T04:33:49Z | https://github.com/kubernetes/kubernetes/issues/105837 | 1,033,125,837 | 105,837 |
[
"kubernetes",
"kubernetes"
] | ### Issue Details
A security issue was discovered in ingress-nginx where a user that can create or update ingress objects can use the custom snippets feature to obtain all secrets in the cluster.
This issue has been rated **High** ([CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L](https://www.first.org/cvss/calculator... | CVE-2021-25742: Ingress-nginx custom snippets allows retrieval of ingress-nginx serviceaccount token and secrets across all namespaces | https://api.github.com/repos/kubernetes/kubernetes/issues/126811/comments | 63 | 2021-10-21T16:08:21Z | 2024-08-20T13:17:02Z | https://github.com/kubernetes/kubernetes/issues/126811 | 2,475,614,887 | 126,811 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
While watching events, I received an invalid JSON.
I used the following command:
```
curl --cacert $ca_cert --header "Authorization: Bearer $token" "https://$KUBERNETES_SERVICE_HOST/api/v1/namespaces/kube-system/events?resourceVersion=$resource_version&watch=true"
```
And this is the inva... | Invalid JSON received when watching events | https://api.github.com/repos/kubernetes/kubernetes/issues/105821/comments | 9 | 2021-10-21T14:16:23Z | 2022-03-21T15:59:46Z | https://github.com/kubernetes/kubernetes/issues/105821 | 1,032,556,091 | 105,821 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
[Talos Linux](https://github.com/talos-systems/talos) runs `kubelet` in a container. Talos sets OOM score to -450 for the kubelet container and passes `oomScoreAdj: -450` in the kubelet config.
End result is that `kubelet` OOM score adj is -999 though.
```
172.20.0.2: I1020 20:49:51.619550 ... | kubelet resets its OOM score to -999 despite oomScoreAdj configuration value when running in a container | https://api.github.com/repos/kubernetes/kubernetes/issues/105820/comments | 8 | 2021-10-21T13:26:12Z | 2022-02-12T17:07:47Z | https://github.com/kubernetes/kubernetes/issues/105820 | 1,032,498,305 | 105,820 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
I would like the HPA ContainerResource feature to graduated from Alpha to Beta.
https://github.com/kubernetes/enhancements/tree/master/keps/sig-autoscaling/1610-container-resource-autoscaling
### Why is this needed?
This is a way to autoscale on the application alone, ignorin... | Graduate HPA ContainerResource to Beta | https://api.github.com/repos/kubernetes/kubernetes/issues/105818/comments | 7 | 2021-10-21T12:44:28Z | 2022-07-15T16:19:24Z | https://github.com/kubernetes/kubernetes/issues/105818 | 1,032,450,686 | 105,818 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
1. create configmap, like
```
kind: ConfigMap
metadata:
name: test
namespace: default
apiVersion: v1
data:
foo.sh: |
#!/bin/sh
```
2. kube edit configmap test, and make some error and write-save, will see below
```
# configmaps "test" was not valid:
# * <nil>: Invalid... | kubectl edit invalid content will remove command interpreter which begin with `#` | https://api.github.com/repos/kubernetes/kubernetes/issues/105816/comments | 5 | 2021-10-21T11:58:03Z | 2021-11-08T17:15:21Z | https://github.com/kubernetes/kubernetes/issues/105816 | 1,032,405,339 | 105,816 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Looks like there are bugs such as https://github.com/antrea-io/antrea/issues/2701 that you might find in a CNI where certain types of egress fail in various corner cases.
So, for this issue, im proposing adding a new test "should be able to egress into the internal k8s service from a pod [sig-win... | We need a Test for windows pod egress traffic to the kubernetes default service | https://api.github.com/repos/kubernetes/kubernetes/issues/105815/comments | 9 | 2021-10-21T10:48:43Z | 2022-08-13T20:35:23Z | https://github.com/kubernetes/kubernetes/issues/105815 | 1,032,341,926 | 105,815 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
If the `CompletionMode` of a job is `NonIndexed`, then the names of the pods that are generated by the job contain two hyphens. Because the pod name takes the form `$(job-name)-$(index)-$(random-string)`, the index of NonIndexed Job is `-1`, which will generate a pod name like `$(job-name)--1-$(rand... | The pod name of NonIndex Job contains consecutive hyphens | https://api.github.com/repos/kubernetes/kubernetes/issues/105810/comments | 5 | 2021-10-21T07:38:47Z | 2021-10-21T14:20:32Z | https://github.com/kubernetes/kubernetes/issues/105810 | 1,032,161,972 | 105,810 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
kubelet config:
```
/usr/bin/kubelet --bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf --config=/var/lib/kubelet/config.yaml --cgroup-driver=systemd --network-plugin=cni --logtostderr=false --alsologtostderr=true --log-file=/data/log/kubernet... | panic in "cm.(*qosContainerManagerImpl).setCPUCgroupConfig" | https://api.github.com/repos/kubernetes/kubernetes/issues/105806/comments | 10 | 2021-10-21T04:14:59Z | 2021-11-30T08:40:38Z | https://github.com/kubernetes/kubernetes/issues/105806 | 1,032,041,058 | 105,806 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
kubemark-500 scale test fails with apf mutating request estimator enabled.
https://github.com/kubernetes/kubernetes/pull/103539
First red: https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-kubemark-500-gce/1448021022367289344
### What did you expect to happen?
Expected ... | apf: kubemark-500 scale test fails with mutating request estimator enabled | https://api.github.com/repos/kubernetes/kubernetes/issues/105804/comments | 48 | 2021-10-21T02:51:48Z | 2022-01-10T13:22:33Z | https://github.com/kubernetes/kubernetes/issues/105804 | 1,032,001,403 | 105,804 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
Add `coscheduling` plugin from https://github.com/kubernetes-sigs/scheduler-plugins/tree/master/pkg/coscheduling to the default `kube-scheduler`.
### Why is this needed?
1. `coscheduling` plugin is one the [motivations for the scheduling framework](https://github.com/kubern... | Move `coscheduling` plugin from scheduler-plugins to kubernetes/kubernetes | https://api.github.com/repos/kubernetes/kubernetes/issues/105802/comments | 50 | 2021-10-21T01:37:50Z | 2023-01-16T16:13:49Z | https://github.com/kubernetes/kubernetes/issues/105802 | 1,031,969,679 | 105,802 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Kubernetes has promoted Bound Service Account Tokens to beta starting in 1.21.
Bound Service Account Tokens have a backward compatibility feature to allow extended expiration of tokens. However the extended expiration gets applied anytime the extended expiration is enabled and expiration seconds is... | Extended SA token expiration | https://api.github.com/repos/kubernetes/kubernetes/issues/105801/comments | 12 | 2021-10-21T00:47:18Z | 2022-02-01T00:18:10Z | https://github.com/kubernetes/kubernetes/issues/105801 | 1,031,946,228 | 105,801 |
[
"kubernetes",
"kubernetes"
] | ITNOA
I think, it is very useful to add native modern C++ client to interact with Kubernetes. | Please add C++ client for kubernetes | https://api.github.com/repos/kubernetes/kubernetes/issues/105814/comments | 5 | 2021-10-20T19:52:25Z | 2021-10-21T10:32:59Z | https://github.com/kubernetes/kubernetes/issues/105814 | 1,032,322,106 | 105,814 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Altering the kubernetes service targetPort from a numbered port to a named port that is referenced in the deployment causes the following error. Essentially, it is saying that my arbitrary container port (8054) is an HTTP port and it cannot service HTTPS traffic on it. It does not throw this error w... | Switching from numeric port to named port in service causes unexpected behavior in requests | https://api.github.com/repos/kubernetes/kubernetes/issues/105799/comments | 4 | 2021-10-20T18:39:54Z | 2021-10-25T15:28:45Z | https://github.com/kubernetes/kubernetes/issues/105799 | 1,031,719,384 | 105,799 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
The changes to support snapshot tests for Generic Ephemeral Volumes https://github.com/kubernetes/kubernetes/pull/105659 generated some duplicated code in the file `test/e2e/storage/testsuites/snapshottable.go` as commented here: https://github.com/kubernetes/kubernetes/pull/1056... | Reduce code duplication in test/e2e/storage/testsuites/snapshottable.go | https://api.github.com/repos/kubernetes/kubernetes/issues/105798/comments | 20 | 2021-10-20T18:28:39Z | 2022-01-25T22:35:42Z | https://github.com/kubernetes/kubernetes/issues/105798 | 1,031,710,803 | 105,798 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
We have a test that creates a static pod on every node and a daemonset that later deletes the manifests for those files. Sometimes the mirror pod and the containerd pod remain. We've seen this when transient failures communicating with the apiserver caused a failure in calico like:
```
Oct 19 07... | containerd pod and mirror pods sometimes remain after deleting the manifest | https://api.github.com/repos/kubernetes/kubernetes/issues/105790/comments | 15 | 2021-10-20T16:52:22Z | 2023-03-09T23:32:32Z | https://github.com/kubernetes/kubernetes/issues/105790 | 1,031,626,836 | 105,790 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
- gce-cos-master-alpha-features
### Which tests are failing?
- kubetest.Up (ci-kubernetes-e2e-gci-gce-alpha-features)
### Since when has it been failing?
20/10/2021
### Testgrid link
https://testgrid.k8s.io/sig-release-master-blocking#gce-cos-master-alpha-features
### Reason for fail... | [Failing Job] gce-cos-master-alpha-features | https://api.github.com/repos/kubernetes/kubernetes/issues/105789/comments | 9 | 2021-10-20T14:59:31Z | 2021-10-27T14:45:38Z | https://github.com/kubernetes/kubernetes/issues/105789 | 1,031,515,905 | 105,789 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are flaking?
Any Windows Server 2019 job that is not using hcsshim v0.8.21 or newer.
Sample job with failure: https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-e2e-aks-engine-azure-master-windows-containerd-1-22/1449817653236469760
### Which tests are flaking?
This issue affects any... | Windows: "Win32: The device is not ready" random failures | https://api.github.com/repos/kubernetes/kubernetes/issues/105784/comments | 3 | 2021-10-20T11:56:29Z | 2021-10-21T17:33:37Z | https://github.com/kubernetes/kubernetes/issues/105784 | 1,031,319,922 | 105,784 |
[
"kubernetes",
"kubernetes"
] | I am trying out [Topology Aware Scheduler](https://github.com/killianmuldoon/documentation/tree/installguide/install-guides) For that I enabled kubelet memory manager, cpu manager and topology manager.
This is tried on a dual socket NUMA server
`KUBELET_KUBEADM_ARGS="--container-runtime=remote --container-runtime-... | ReservedMemory Configuration for NUMA | https://api.github.com/repos/kubernetes/kubernetes/issues/105783/comments | 13 | 2021-10-20T11:52:08Z | 2022-01-27T14:46:26Z | https://github.com/kubernetes/kubernetes/issues/105783 | 1,031,316,118 | 105,783 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
https://github.com/kubernetes/apimachinery/blob/4a9e16b3571218c2e15b8d0319f0b8e0e3fbacf5/pkg/types/namespacedname.go#L19-L39 should implement [MarshalLog](https://github.com/go-logr/logr/blob/1215c813c1cfed81baa5aa822d98da591001d72b/logr.go#L495).
### Why is this needed?
This ens... | NamespacedName: better structured logging | https://api.github.com/repos/kubernetes/kubernetes/issues/105782/comments | 10 | 2021-10-20T10:04:10Z | 2023-01-24T20:55:55Z | https://github.com/kubernetes/kubernetes/issues/105782 | 1,031,220,421 | 105,782 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
In this PR all probes were disabled during the graceful node termination https://github.com/kubernetes/kubernetes/pull/105215.
This may pose a problem when pods will keep being marked as ready fir the duration of a node termination. Ideally we need to keep readiness probes running
### What d... | Readiness probes should keep running (or pod marked as not ready) during graceful node termination | https://api.github.com/repos/kubernetes/kubernetes/issues/105780/comments | 37 | 2021-10-20T06:57:59Z | 2025-01-17T08:44:13Z | https://github.com/kubernetes/kubernetes/issues/105780 | 1,031,047,886 | 105,780 |
[
"kubernetes",
"kubernetes"
] | IPVS is closing a connection to server without sending FIN packet to the peer on reboot of SPF server and few unknown scenario
2 scenarion we have reproduced it. Do anybody know any other scenario
1. on reboot of IPVS server
2. keepalive > IPVS timeout
We have following setting on the site
[Active:root@dc-x... | IPVS is closing a connection to server without sending FIN packet to the peer on reboot of SPF server and few unknown scenario | https://api.github.com/repos/kubernetes/kubernetes/issues/105779/comments | 7 | 2021-10-20T04:24:30Z | 2021-10-29T06:47:21Z | https://github.com/kubernetes/kubernetes/issues/105779 | 1,030,960,118 | 105,779 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
For some application，start or restart need more resources than running。for exapmle：es/flink。if a node have network jitter，all pods would restart at the same time in this node。When this happens，cpu usage becomes very high in this node。it would increase resource competition in this ... | start pods in batches for per node | https://api.github.com/repos/kubernetes/kubernetes/issues/105778/comments | 7 | 2021-10-20T04:11:34Z | 2022-03-20T11:51:42Z | https://github.com/kubernetes/kubernetes/issues/105778 | 1,030,953,785 | 105,778 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I have 3 cluster. All of them installed by kubeadm. Nodes in two of them had been upgraded to debian 11 and work normally.
But when I upgrade OS of a worker node in last cluster, pods keep on crashing. I compared versions and configuration and found no noticeable difference.
If I stop kubelet se... | Pods keep on crashing after worker node upgrade to debian 11 | https://api.github.com/repos/kubernetes/kubernetes/issues/105762/comments | 5 | 2021-10-19T11:04:22Z | 2021-12-10T18:54:20Z | https://github.com/kubernetes/kubernetes/issues/105762 | 1,030,166,398 | 105,762 |
[
"kubernetes",
"kubernetes"
] | /sig node
### What happened?
I'm trying to use an USB device directly in the pod. The device is connected on the USB 3.0 port and is not available in the pod.
### What did you expect to happen?
The USB devices should be available on the pod.
### How can we reproduce it (as minimally and precisely as poss... | USB devices are not available in Pod | https://api.github.com/repos/kubernetes/kubernetes/issues/105761/comments | 7 | 2021-10-19T08:21:06Z | 2021-10-21T13:58:18Z | https://github.com/kubernetes/kubernetes/issues/105761 | 1,030,003,657 | 105,761 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Apiserver crashed with stacktrace:
```
goroutine 943732 [running]:
runtime.throw
/usr/local/go/src/runtime/panic.go:1117
runtime.mapaccess1_faststr
/usr/local/go/src/runtime/map_faststr.go:21
net/textproto.MIMEHeader.Get
/usr/local/go/src/net/textproto/header.go:34
... | Race condition in apiserver when request times out | https://api.github.com/repos/kubernetes/kubernetes/issues/105759/comments | 7 | 2021-10-19T07:39:01Z | 2021-11-04T15:36:18Z | https://github.com/kubernetes/kubernetes/issues/105759 | 1,029,964,760 | 105,759 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
In a benchmark cluster with the following setup:
* 3x control plane instances
* 3x etcd instances
* 5000x [kubemark](https://github.com/kubernetes/kubernetes/tree/master/pkg/kubemark) nodes
Use [clusterloader](https://github.com/kubernetes/perf-tests/tree/master/clusterloader2) to launch P... | PodTopologySpread performance degrades as more pods are created | https://api.github.com/repos/kubernetes/kubernetes/issues/105750/comments | 13 | 2021-10-19T00:11:27Z | 2022-06-26T08:26:36Z | https://github.com/kubernetes/kubernetes/issues/105750 | 1,029,717,700 | 105,750 |
[
"kubernetes",
"kubernetes"
] | Configure cross-architecture builds of the PodSecurity webhook.
This depends on the initial webhook implementation: #105362
/sig auth | [PodSecurity] Multi-arch builds | https://api.github.com/repos/kubernetes/kubernetes/issues/105747/comments | 5 | 2021-10-18T22:45:35Z | 2022-04-03T16:22:46Z | https://github.com/kubernetes/kubernetes/issues/105747 | 1,029,669,784 | 105,747 |
[
"kubernetes",
"kubernetes"
] | We should automate the webhook image build using cloud build (see https://github.com/kubernetes/k8s.io/tree/main/k8s.gcr.io#enabling-automatic-builds).
This depends on the initial webhook implementation: https://github.com/kubernetes/kubernetes/pull/105362
/sig auth | [PodSecurity] Automated webhook image builds | https://api.github.com/repos/kubernetes/kubernetes/issues/105746/comments | 7 | 2021-10-18T22:44:22Z | 2022-07-08T02:26:14Z | https://github.com/kubernetes/kubernetes/issues/105746 | 1,029,669,142 | 105,746 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
Adding Expression Language validation for CRD.
KEP: <https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/2876-crd-validation-expression-language>
Expression Language validation for CRD is available as alpha feature in 1.23:
- [x] https://github.co... | CRD Validation Expression Language in Alpha | https://api.github.com/repos/kubernetes/kubernetes/issues/105745/comments | 8 | 2021-10-18T22:12:30Z | 2021-11-16T20:19:51Z | https://github.com/kubernetes/kubernetes/issues/105745 | 1,029,649,112 | 105,745 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
Right now the deletion of the below namespaces is prevented by the server
`default`, `kube-public`, `kube-system`
But when trying to delete the
`kube-node-lease` namespace, the server deletes it, and sometimes the namespace removal is stuck at the deleted stage which prevent... | Preventing the kube-node-lease namespace removal | https://api.github.com/repos/kubernetes/kubernetes/issues/105743/comments | 8 | 2021-10-18T19:30:32Z | 2022-07-30T20:34:30Z | https://github.com/kubernetes/kubernetes/issues/105743 | 1,029,512,641 | 105,743 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
We upgraded iptables on one of our hosts, and kube-proxy began logging errors about being unable to acquire the `xtables.lock`. However, we didn't notice this, because kube-proxy's health check (`/healthz`) was still passing (and that's generally what we look at as our sign that something is amiss... | kube-proxy health check doesn't fail when kube-proxy can't acquire iptables lock | https://api.github.com/repos/kubernetes/kubernetes/issues/105742/comments | 20 | 2021-10-18T19:29:55Z | 2022-05-05T13:40:20Z | https://github.com/kubernetes/kubernetes/issues/105742 | 1,029,512,188 | 105,742 |
[
"kubernetes",
"kubernetes"
] | In some cases, issues get more visibility if they are open on other repositories. For instance, after #105518, I learned that issues with `kubectl` should be open in kubernetes/kubectl instead of kubernetes/kubernetes.
According to https://github.com/orgs/kubernetes/repositories?q=issue there is also kubernetes/kube... | Meta: bug report form may suggest other repositories than kubernetes/kubernetes | https://api.github.com/repos/kubernetes/kubernetes/issues/105740/comments | 7 | 2021-10-18T17:21:57Z | 2022-05-14T07:16:29Z | https://github.com/kubernetes/kubernetes/issues/105740 | 1,029,393,870 | 105,740 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When draining a node, using kubectl drain [NODE], the output resembles this:
```text
pod/bar evicted
node/node evicted
```
### What did you expect to happen?
Expected output should indicate that the node was drained, for example:
```text
pod/bar evicted
node/node drained
```
### How c... | kubectl drain output says node deleted/evicted | https://api.github.com/repos/kubernetes/kubernetes/issues/105735/comments | 2 | 2021-10-18T16:01:43Z | 2021-10-27T21:19:11Z | https://github.com/kubernetes/kubernetes/issues/105735 | 1,029,311,736 | 105,735 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I'm working on a task requiring to implement a solution that would allow for horizontal pod autoscaling of a certain service to scale pods based on kafka metric "kafka_consumer_group_ConsumerLagMetrics_Value"
HPA would look something similar to this within that service:
```
consumer-hpa.ya... | Enhancement request for allowing hostnames in endpoints. Currently only IPs are supported | https://api.github.com/repos/kubernetes/kubernetes/issues/105733/comments | 8 | 2021-10-18T15:09:42Z | 2021-11-30T06:16:38Z | https://github.com/kubernetes/kubernetes/issues/105733 | 1,029,252,199 | 105,733 |
[
"kubernetes",
"kubernetes"
] | Problem is that during deployment the oldest-by-date replica set is overwritten instead of oldest-by-revision. Rollback failure will occur according to revisionHistoryLimit value - in our case it was set to 2, so 2 historical revisions plus current one is kept - issue occured during 3rd deployment. Please see details i... | Oldest-by-date repilca set overwrite instead of oldest-by-revision during deployment leads to rollback to inproper version. | https://api.github.com/repos/kubernetes/kubernetes/issues/105732/comments | 4 | 2021-10-18T10:17:06Z | 2021-11-23T00:05:25Z | https://github.com/kubernetes/kubernetes/issues/105732 | 1,028,920,139 | 105,732 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
kubernetes/staging/src/k8s.io/apiserver/pkg/server/options/etcd.go
1. Cancel etcd health check
```
if err := s.addEtcdHealthEndpoint(c); err != nil {
return err
}
```
2. Increase default health check interval
### Why is this needed?
1. To prevent logs fro... | when etcd is abnormal or not heatlth,apiserver's log growing too fast | https://api.github.com/repos/kubernetes/kubernetes/issues/105725/comments | 9 | 2021-10-18T07:01:11Z | 2022-04-23T22:53:10Z | https://github.com/kubernetes/kubernetes/issues/105725 | 1,028,705,023 | 105,725 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
related code is [default_preemption.go#L177-L185](https://github.com/kubernetes/kubernetes/blob/master/pkg/scheduler/framework/plugins/defaultpreemption/default_preemption.go#L177-L185), when selecting nominated node for failed scheduled pods, it only runs `RunFilterPluginsWithNominatedPods` to sel... | In Scheduler Preemption phase, RunFilterPlugins does not consider extender scheduler plugin | https://api.github.com/repos/kubernetes/kubernetes/issues/105720/comments | 5 | 2021-10-17T09:40:43Z | 2021-10-18T10:02:35Z | https://github.com/kubernetes/kubernetes/issues/105720 | 1,028,271,135 | 105,720 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
As per the PRs kubernetes/kubernetes#49579 kubernetes/kubernetes#49586, the defaulting behaviour of the pod exec parameters had been changed however in the code there is a comment where it is mentioned it defaults to True
https://github.com/kubernetes/kubernetes/blob/a53e2eaeaba064309dceca2dc... | Fix Documentation for pod exec default values | https://api.github.com/repos/kubernetes/kubernetes/issues/105717/comments | 7 | 2021-10-16T18:24:38Z | 2021-10-28T16:20:39Z | https://github.com/kubernetes/kubernetes/issues/105717 | 1,028,116,160 | 105,717 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
First of all, my k8s version is v1.18.19 (the same problem also occurs on version 1.16). When I created the pod, I specified nvidia.com/gpu as 0 in the yaml file, but it was running on the pod After getting up, the processes in the pod are still using GPU resources. It seems that I limit nvidia.com/... | k8s does not work on GPU resource limits | https://api.github.com/repos/kubernetes/kubernetes/issues/105715/comments | 8 | 2021-10-16T08:05:13Z | 2022-03-19T18:43:41Z | https://github.com/kubernetes/kubernetes/issues/105715 | 1,027,987,448 | 105,715 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Tried to strip headers, failed with --skip-headers (found in kubectl options):
```
~$ kubectl api-resources --verbs=list --namespaced -o name | xargs -n 1 kubectl get --show-kind --ignore-not-found -l release=istio -A --skip-headers
NAMESPACE NAME DATA AGE
... | kubectl options incorrect --> --skip-headers should be replaced with --no-headers | https://api.github.com/repos/kubernetes/kubernetes/issues/105710/comments | 11 | 2021-10-16T01:05:41Z | 2021-11-05T17:38:23Z | https://github.com/kubernetes/kubernetes/issues/105710 | 1,027,912,677 | 105,710 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
In one AKS cluster, sender service is deployed. In another AKS cluster , receiver service is deployed. The receiver service is exposed by LoadBalancer. The external ip:port is 20.62.218.218:100. When surfing the 20.62.218.218:100 on the website, the receiver service will return "hello world".
I... | Fail to reach another cluster by external ip:port | https://api.github.com/repos/kubernetes/kubernetes/issues/105709/comments | 7 | 2021-10-16T00:57:01Z | 2021-10-28T21:06:38Z | https://github.com/kubernetes/kubernetes/issues/105709 | 1,027,910,562 | 105,709 |
[
"kubernetes",
"kubernetes"
] | <!--
This issue tracker is a best-effort forum for users and customers to suggest features and report bugs.
If you are experiencing a service disruption when creating, upgrading, scaling, or deleting your cluster,
please open a support request with Azure support. Be sure to include your subscription id, resource... | dfadfsdf | https://api.github.com/repos/kubernetes/kubernetes/issues/105708/comments | 2 | 2021-10-16T00:54:34Z | 2021-10-16T06:22:17Z | https://github.com/kubernetes/kubernetes/issues/105708 | 1,027,910,006 | 105,708 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When `--leader-elect=false` is specified to start the scheduler, it's not honored well - the scheduler still tries to acquire leader election obj and it causes the scheduler to fail scheduling pods.
### What did you expect to happen?
The `--leader-elect` flag is always honored, no matter its corre... | sched: `--leader-elect` flag is not honored well | https://api.github.com/repos/kubernetes/kubernetes/issues/105704/comments | 4 | 2021-10-15T18:03:56Z | 2021-11-02T21:28:06Z | https://github.com/kubernetes/kubernetes/issues/105704 | 1,027,676,109 | 105,704 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Hi,
Our backend infrastructure uses Kubernetes pods to perform analysis of data. As the flow of data increases and decreases through the day, the Kubernetes auto scaler scales up and scales down the pods.
The analysis operation on a single workload can take up to six minutes. To enable succe... | Pod looses network connection (connection refused errors) during graceful shutdown period | https://api.github.com/repos/kubernetes/kubernetes/issues/105703/comments | 22 | 2021-10-15T16:48:46Z | 2022-04-19T08:03:53Z | https://github.com/kubernetes/kubernetes/issues/105703 | 1,027,621,468 | 105,703 |
[
"kubernetes",
"kubernetes"
] | With the introduction of https://github.com/kubernetes/kubernetes/pull/97415, we return only exclusively allocated CPUs in the list endpoint of Podresource API.
Though this is useful in meeting the original goal of resource accounting and determining the remaining CPUs on a node, there is no easy way to know the ta... | PodResource API: Provide the client a user friendly way to learn taskset of a container | https://api.github.com/repos/kubernetes/kubernetes/issues/105698/comments | 7 | 2021-10-15T09:31:06Z | 2022-03-14T10:46:46Z | https://github.com/kubernetes/kubernetes/issues/105698 | 1,027,260,265 | 105,698 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Note: I'm using OpenShift. s/oc/kubectl/ below if that's how you roll.
I'm using a command similar to the following to idempotently ensure a label is absent on a Namespace object:
```console
$ oc patch namespace hive -p '{"metadata": {"labels": {"EFRIED": null}}}'
```
If the object's `.metada... | StrategicMerge patching null dict entry on empty dict creates the entry with empty string value | https://api.github.com/repos/kubernetes/kubernetes/issues/105689/comments | 7 | 2021-10-14T23:03:13Z | 2022-02-17T05:19:37Z | https://github.com/kubernetes/kubernetes/issues/105689 | 1,026,897,837 | 105,689 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are flaking?
node-kubelet-serial
### Which tests are flaking?
Kubelet should correctly account for terminated pods after restart
### Since when has it been flaking?
Since test was created, flakes 10-20% of the time. Not entirely clear why, I haven't looked.
### Testgrid link
https://testgrid.k8s.i... | [Flaky test] [sig-node] Kubelet should correctly account for terminated pods after restart | https://api.github.com/repos/kubernetes/kubernetes/issues/105686/comments | 13 | 2021-10-14T20:28:15Z | 2021-11-20T08:05:00Z | https://github.com/kubernetes/kubernetes/issues/105686 | 1,026,792,881 | 105,686 |
[
"kubernetes",
"kubernetes"
] | When editing a kubernetes file in a folder watched by kubelet, editors often create a `foo.yaml~` file.
This file should be ignored by `kubelet`, ideally it would only search for `*.{yml,yaml,json}`
[code](https://github.com/kubernetes/kubernetes/blob/30a32a39a4924c481b1e1c26f3d782f2e02ab014/pkg/kubelet/config/file... | kubelet should not pick up static pods from editor temp/backup files | https://api.github.com/repos/kubernetes/kubernetes/issues/105684/comments | 17 | 2021-10-14T18:59:50Z | 2025-01-22T18:57:21Z | https://github.com/kubernetes/kubernetes/issues/105684 | 1,026,720,454 | 105,684 |
[
"kubernetes",
"kubernetes"
] | Forked from post-merge discussion on https://github.com/kubernetes/kubernetes/pull/103539
Copying the main comments here:
@MikeSpreitzer :
```
I checked the apiserver_flowcontrol_priority_level_request_count_watermarks histogram and it accumulates observations of the fraction (number of executing requests) / (c... | Rethink P&F metrics | https://api.github.com/repos/kubernetes/kubernetes/issues/105683/comments | 13 | 2021-10-14T16:44:06Z | 2022-03-24T21:43:03Z | https://github.com/kubernetes/kubernetes/issues/105683 | 1,026,610,594 | 105,683 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
go 1.17 appears to have significantly increased the amount of memory required on a kubernetes development environment to run `make verify` and in particular, `hack/verify-typecheck.sh` `verify-typecheck-dockerless.sh` and `verify-typecheck-providerless.sh`
With go 1.16.9, these can be run in a ... | OOM when running hack/verify-typecheck.sh with go 1.17 | https://api.github.com/repos/kubernetes/kubernetes/issues/105681/comments | 14 | 2021-10-14T15:33:43Z | 2022-08-17T16:45:02Z | https://github.com/kubernetes/kubernetes/issues/105681 | 1,026,543,464 | 105,681 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Have SYS_NICE capability and privileged: true added to pod. Running C app that calls pthread_create() with a thread priority > 0 fails as non root user. Error is EPERM (https://github.com/kubernetes/kubernetes/issues/84069)
### What did you expect to happen?
With SYS_NICE capability and privileged... | pthread_create EPERM error with SYS_NICE capability added | https://api.github.com/repos/kubernetes/kubernetes/issues/105680/comments | 14 | 2021-10-14T15:21:04Z | 2022-03-27T02:06:29Z | https://github.com/kubernetes/kubernetes/issues/105680 | 1,026,530,107 | 105,680 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
The `test/e2e` tests are full of assertions which compare a boolean against true or false, often without any additional explanation. When those assertions fail, the error message is useless for understanding what went wrong, often just saying:
```
Apr 22 09:03:41.130: Exp... | replace ExpectEqual(someBoolean, ...) | https://api.github.com/repos/kubernetes/kubernetes/issues/105678/comments | 108 | 2021-10-14T14:21:34Z | 2024-08-26T08:27:41Z | https://github.com/kubernetes/kubernetes/issues/105678 | 1,026,462,336 | 105,678 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
ci-kubernetes-e2e-gci-gce-autoscaling-hpa-cm
ci-kubernetes-e2e-gci-gce-autoscaling-migs-hpa
### Which tests are failing?
All Kubernetes e2e suite.[sig-autoscaling] [HPA] Horizontal pod autoscaling (scale resource: Custom Metrics from Stackdriver)
### Since when has it been failing?
La... | HPA Custom metrics tests are failing | https://api.github.com/repos/kubernetes/kubernetes/issues/105677/comments | 7 | 2021-10-14T14:15:18Z | 2022-03-10T07:04:26Z | https://github.com/kubernetes/kubernetes/issues/105677 | 1,026,455,142 | 105,677 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
ci-kubernetes-e2e-autoscaling-hpa-cpu
### Which tests are failing?
All Kubernetes e2e suite.[sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU)
### Since when has it been failing?
Jul 23 18:15:50
### Testgrid link
https://k8s-testgrid.appspot.com/sig-auto... | HPA CPU e2e tests are failing | https://api.github.com/repos/kubernetes/kubernetes/issues/105675/comments | 4 | 2021-10-14T14:07:22Z | 2021-11-09T11:58:25Z | https://github.com/kubernetes/kubernetes/issues/105675 | 1,026,445,742 | 105,675 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
I think it should be more specific that what is the significance for var iterations to be equal to 5.
[https://github.com/kubernetes/kubernetes/blob/master/test/e2e/windows/kubelet_stats.go](url)
### Why is this needed?
It improves readability of the code and it's easier t... | Make iterations a non-magic number | https://api.github.com/repos/kubernetes/kubernetes/issues/105668/comments | 4 | 2021-10-14T07:03:23Z | 2021-10-14T10:59:28Z | https://github.com/kubernetes/kubernetes/issues/105668 | 1,026,036,545 | 105,668 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When we use custom scheduler, e2e node events test failing (as part of 1.20 conformance)
### What did you expect to happen?
You need not to use default scheduler when query events there:
var events *v1.EventList
// Check for scheduler event about the pod.
ginkgo.By("checking for sch... | k8s e2e node events test (test/e2e/node/events.go) is designed only for checking events coming from the default scheduler and fails when custom scheduler is used | https://api.github.com/repos/kubernetes/kubernetes/issues/105664/comments | 10 | 2021-10-14T01:14:15Z | 2022-03-13T23:42:46Z | https://github.com/kubernetes/kubernetes/issues/105664 | 1,025,832,532 | 105,664 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
### Background
When I run the `gosec` static scan against kubernetes master there a lot of findings for a number of rules the scanner provides; e.g.
- `G101 (CWE-798): Potential hardcoded credentials`
- `G601 (CWE-118): Implicit memory aliasing in for loop.`
- `G103 (CWE-242): ... | Run gosec static scan and address findings | https://api.github.com/repos/kubernetes/kubernetes/issues/105662/comments | 17 | 2021-10-13T14:53:09Z | 2022-11-11T22:58:46Z | https://github.com/kubernetes/kubernetes/issues/105662 | 1,025,355,180 | 105,662 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When restarting a rolling deployment, the new pods can end up in imbalanced topologies that violate their specified `MaxSkew`. This is due to interference from the old, `Terminating` pods in the scheduler's topology size calculation. At scheduling time, the constraints are technically satisfied. How... | Topology spreading can become imbalanced during deployment rollout | https://api.github.com/repos/kubernetes/kubernetes/issues/105661/comments | 20 | 2021-10-13T14:44:58Z | 2022-07-30T08:40:44Z | https://github.com/kubernetes/kubernetes/issues/105661 | 1,025,344,471 | 105,661 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I delete an immutable secret and applied it with new values.
Then i deleted the deployment/pods that are using this secret.
After applying the Deployments again, the Pod/Container is having the old secret values
When i use kubectl to get the secret values, i see the new values.
### What did you... | Immutable Secrets are not renewed on recreation of pods | https://api.github.com/repos/kubernetes/kubernetes/issues/105658/comments | 19 | 2021-10-13T12:38:24Z | 2023-08-25T13:38:05Z | https://github.com/kubernetes/kubernetes/issues/105658 | 1,025,197,658 | 105,658 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
On a single node kubernetes cluster, deployed using minikube:
[root@control-plane ~]# kubectl get nodes -o wide
NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER... | Wrong udp conntrack entries are populated after a pod is killed using --force | https://api.github.com/repos/kubernetes/kubernetes/issues/105657/comments | 22 | 2021-10-13T10:34:50Z | 2021-11-08T21:37:30Z | https://github.com/kubernetes/kubernetes/issues/105657 | 1,025,077,322 | 105,657 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Hi Kubernetes,
I'm managing my service pods using HPA, and as the Title implies I have set SelectPolicy of ScaleDown to "Disabled" not to lose any pods.
So basically it's just growing up to .spec.maxReplicas as specific resource metrics I set grow.
However, I realized that HPA recalcul... | The number of pods goes down with ScaleDown: SelectPolicy: Disabled of HPA. | https://api.github.com/repos/kubernetes/kubernetes/issues/105655/comments | 6 | 2021-10-13T10:20:00Z | 2022-03-12T21:34:26Z | https://github.com/kubernetes/kubernetes/issues/105655 | 1,025,062,495 | 105,655 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I'm using AWS EKS 1.21 with service account discovery enabled (it's enabled by default by EKS, I can't change it).
The `.well-known/openid-configuration` endpoint returns:
```
{
"issuer": "https://oidc.eks.eu-west-1.amazonaws.com/id/***",
"jwks_uri": "https://ip-***.eu-west-1.compute.inte... | Wrong “exp” date in projected serviceaccount token | https://api.github.com/repos/kubernetes/kubernetes/issues/105654/comments | 8 | 2021-10-13T10:09:31Z | 2021-10-15T08:32:32Z | https://github.com/kubernetes/kubernetes/issues/105654 | 1,025,051,269 | 105,654 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
running ./legacy-script.sh failed with output `bogus-expected-to-fail: command not found`
### What did you expect to happen?
bogus-expected-to-fail: command not found
### How can we reproduce it (as minimally and precisely as possible)?
master branch and `dadecb2c8932fd28de9dfb94edbc7... | bogus-expected-to-fail: command not found | https://api.github.com/repos/kubernetes/kubernetes/issues/105651/comments | 3 | 2021-10-13T09:01:29Z | 2021-10-13T22:06:03Z | https://github.com/kubernetes/kubernetes/issues/105651 | 1,024,980,311 | 105,651 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
```
/var/log/messages-20211010:Oct 9 16:48:04 iZcr001mb815dp0lyka354Z cloud-init: + kubeadm join --node-name cn-wulan-env212-d01.192.168.155.228 --token o6vnv2.qnbogocntjt8pijx 192.168.153.151:6443 --discovery-token-unsafe-skip-ca-verification
/var/log/messages-20211010:Oct 9 16:48:04 iZcr001mb8... | kubeadm get configmap retry failed | https://api.github.com/repos/kubernetes/kubernetes/issues/105644/comments | 6 | 2021-10-13T03:19:27Z | 2021-11-01T18:02:46Z | https://github.com/kubernetes/kubernetes/issues/105644 | 1,024,726,588 | 105,644 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
We have a situation where we are launching a lot of short-lived pods on a single node on EKS1.20 as a cronjob. Some volumes can take upto 2 hours to reconcile and unmount. Each pod has 3 volumes and 100 subPath
1. EFS volume
2. emptyDir
3. config map
Below logs show this
```
Oct 12 1... | Volume manager re-conciler takes too long to reconcile under high pressure and large number of subpaths | https://api.github.com/repos/kubernetes/kubernetes/issues/105642/comments | 12 | 2021-10-12T22:45:02Z | 2022-07-27T19:35:41Z | https://github.com/kubernetes/kubernetes/issues/105642 | 1,024,545,187 | 105,642 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
Wouldn't it be useful to provide a consistent abbreviation 'policy'?
Examples:
- for deployments it is deploy instead of intuitively 'dep' or 'depl' (that 'loy' is a long way on the keyboard)
- limitranges > limit instead of lr
- networkpolicies > netpol instead of np
- re... | Abbreviations | https://api.github.com/repos/kubernetes/kubernetes/issues/105638/comments | 9 | 2021-10-12T17:27:33Z | 2022-04-22T18:43:51Z | https://github.com/kubernetes/kubernetes/issues/105638 | 1,024,068,132 | 105,638 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
E1009 07:08:48.906004 6 reflector.go:205] github.com/kong/kubernetes-ingress-controller/internal/ingress/controller/store/store.go:150: Failed to list *v1.Service: v1.ServiceList: Items: []v1.Service: v1.Service: ObjectMeta: v1.ObjectMeta: readObjectFieldAsBytes: expect : after object field, b... | Newly created service request not getting capture in kong-ingres-controller | https://api.github.com/repos/kubernetes/kubernetes/issues/105635/comments | 4 | 2021-10-12T14:26:09Z | 2021-10-12T18:37:20Z | https://github.com/kubernetes/kubernetes/issues/105635 | 1,023,890,297 | 105,635 |
[
"kubernetes",
"kubernetes"
] | https://github.com/kubernetes/kubernetes/blob/d9896a23bcec2cdadd398bff0bb967a17ad7893d/pkg/controller/controller_utils.go#L190
when the expectation is fulfilled, why the ReplicaSet controller synchronization is required.
Can someone help me？
/sig k8s-infra | why exp.Fulfilled() return true | https://api.github.com/repos/kubernetes/kubernetes/issues/105634/comments | 2 | 2021-10-12T13:10:02Z | 2021-10-13T01:52:27Z | https://github.com/kubernetes/kubernetes/issues/105634 | 1,023,805,581 | 105,634 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
pull-kubernetes-e2e-gce-ubuntu-containerd
https://prow.k8s.io/pr-history/?org=kubernetes&repo=kubernetes&pr=105380
i retest pull-kubernetes-e2e-gce-ubuntu-containerd ci, it always fail, but get different unit test fail.
i don't know what reason, need some help
### Which tests are... | pull-kubernetes-e2e-gce-ubuntu-containerd: e2e unit test fail | https://api.github.com/repos/kubernetes/kubernetes/issues/105633/comments | 4 | 2021-10-12T12:25:38Z | 2021-10-22T08:09:16Z | https://github.com/kubernetes/kubernetes/issues/105633 | 1,023,761,504 | 105,633 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
feature gate "DisableKubeletCloudCredentialProviders" has been recently added to disable in-tree credential providers. Enabling the feature gate causing unit test failures of aws/gcp credential providers.
https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/105624/pull-kubernetes-unit/1447... | Enabling feature gate "DisableKubeletCloudCredentialProviders" causing unit test failures | https://api.github.com/repos/kubernetes/kubernetes/issues/105629/comments | 14 | 2021-10-12T10:03:49Z | 2022-07-30T12:31:30Z | https://github.com/kubernetes/kubernetes/issues/105629 | 1,023,618,044 | 105,629 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
Right now, our e2e tests and our [external CSI tests](https://github.com/kubernetes/kubernetes/blob/master/test/e2e/storage/external/README.md) allow a test driver to opt-in for RWX testing for both block and filesystem volumes
https://github.com/kubernetes/kubernetes/blob/d9896... | Storage e2e tests should allow RWX for block volumes and RWO for filesystem ones | https://api.github.com/repos/kubernetes/kubernetes/issues/105626/comments | 21 | 2021-10-12T09:32:47Z | 2024-02-15T19:32:37Z | https://github.com/kubernetes/kubernetes/issues/105626 | 1,023,587,426 | 105,626 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
dial tcp 127.0.0.1:10251: connect: connection refused
this is my init
```
kubeadm init \
--apiserver-advertise-address=10.0.1.189 \
--image-repository registry.aliyuncs.com/googl... | NoSchedule | https://api.github.com/repos/kubernetes/kubernetes/issues/105625/comments | 5 | 2021-10-12T09:25:11Z | 2021-10-12T18:34:20Z | https://github.com/kubernetes/kubernetes/issues/105625 | 1,023,579,942 | 105,625 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
The `hack/{update,verify}-vendor.sh` scripts seem to broken. On a fresh checkout of k/k
```
$ go version
go version go1.17.1 linux/amd64
```
```
$ hack/verify-vendor.sh
+++ [1011 16:37:56] logfile at /tmp/update-vendor.bM31/update-vendor.log
+++ [1011 16:37:56] go.mod: update staging ref... | hack/{update,verify}-vendor are broken due to coreos/bbolt rename | https://api.github.com/repos/kubernetes/kubernetes/issues/105618/comments | 8 | 2021-10-11T23:39:53Z | 2021-10-12T00:25:16Z | https://github.com/kubernetes/kubernetes/issues/105618 | 1,023,214,662 | 105,618 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
We've encountered a failure scenario in production where if master nodes hosting etcd, apiserver, controller-manager etc gets network partitioned with worker nodes (say due to apiserver lb outage or a widespread network infra outage), all the pods hosted in that k8s cluster gets [marked as not rea... | NodeLifeCycleController: all pods are marked as not ready making workload services unavailable during network partition b/w master & worker nodes | https://api.github.com/repos/kubernetes/kubernetes/issues/105617/comments | 42 | 2021-10-11T22:16:43Z | 2025-02-20T00:26:17Z | https://github.com/kubernetes/kubernetes/issues/105617 | 1,023,161,969 | 105,617 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
An attempt was made in https://github.com/kubernetes/kubernetes/pull/98089, but conflicted with a lot of deprecation activity at the same time. It looks like in the middle of that, we lost track of the effort to add a unit test.
@kubernetes/sig-storage-bugs
cc @JornShen is thi... | Add unit test for volume operation metrics | https://api.github.com/repos/kubernetes/kubernetes/issues/105616/comments | 9 | 2021-10-11T21:30:52Z | 2022-04-03T02:13:46Z | https://github.com/kubernetes/kubernetes/issues/105616 | 1,023,131,986 | 105,616 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I'm creating a kubernetes cluster on VMs in Hyper-V with dynamic RAM. The kubelet is taking not all available RAM (max ram of the VM) but only the allocated amount at the time of starting. Moreover the available RAM will be not recalculated during the running
### What did you expect to happen?
I'd... | Kubelet's memory capacity and dynamic RAM in Hyper-V | https://api.github.com/repos/kubernetes/kubernetes/issues/105613/comments | 10 | 2021-10-11T19:41:35Z | 2022-08-17T10:07:35Z | https://github.com/kubernetes/kubernetes/issues/105613 | 1,023,054,005 | 105,613 |
[
"kubernetes",
"kubernetes"
] | Service object has a known issue wrt Port and Patch Merge. The issue can be reproduced as the following:
1. Create a Service object as the following:
```yaml
apiVersion: v1
kind: Service
metadata:
name: udp-debug
spec:
type: NodePort
selector:
app: udp-debug
ports:
- name: udp-debug
... | Umbrella Issue: (Known Issue) Service Duplicate Port Numbers + Patch Merge | https://api.github.com/repos/kubernetes/kubernetes/issues/105610/comments | 29 | 2021-10-11T15:43:31Z | 2025-02-27T17:50:26Z | https://github.com/kubernetes/kubernetes/issues/105610 | 1,022,865,402 | 105,610 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I found this issue while validating my arm based `1.19.14` cluster with [sonobuoy](https://github.com/vmware-tanzu/sonobuoy).
[Conformance test Officially supports multiple cpu architectures: amd64, arm, arm64, ppc64le, s390x](https://github.com/kubernetes/kubernetes/tree/master/test/conformanc... | Non-amd64 Conformance test images are built with wrong cpu arch. | https://api.github.com/repos/kubernetes/kubernetes/issues/105607/comments | 4 | 2021-10-11T14:07:10Z | 2021-10-11T14:51:33Z | https://github.com/kubernetes/kubernetes/issues/105607 | 1,022,750,510 | 105,607 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
First I install ```traefik``` with ```hostNetwork:true``` , ```hostPort``` and ```serviceType: NodePort``` then I try to install ```ingress-nginx``` with ```hostNetrowk:true``` , ```hostPort``` mappings and ```serviceType: NodePort```, at that time it gives error that the port 80 is in use. Which ... | Port conflict arises even though port is not in use. | https://api.github.com/repos/kubernetes/kubernetes/issues/105604/comments | 6 | 2021-10-11T10:05:26Z | 2021-10-15T05:38:36Z | https://github.com/kubernetes/kubernetes/issues/105604 | 1,022,508,458 | 105,604 |
[
"kubernetes",
"kubernetes"
] | `ReadWriteOnce` alias `RWO` is an ambiguous [mention](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#access-modes) in access modes, as mention in documentation that the volume can be mounted as read-write by a single node . But `ReadWriteOnce` PV can be accessed from multiple pods when those pods ar... | Modify Access Modes aliases | https://api.github.com/repos/kubernetes/kubernetes/issues/105602/comments | 16 | 2021-10-11T08:26:20Z | 2021-12-09T05:18:17Z | https://github.com/kubernetes/kubernetes/issues/105602 | 1,022,412,891 | 105,602 |
[
"kubernetes",
"kubernetes"
] | This issue is part of the KEP https://github.com/kubernetes/enhancements/issues/2853
When we rename the branch it will retrigger all the open Pull Requests, which will cause a huge queue, some ideas to avoid this
1. before the rename add the `needs-ok-to-test` in all PRs
I did a test in a sample PR and looks l... | Changing default branch name to `main` | https://api.github.com/repos/kubernetes/kubernetes/issues/105601/comments | 12 | 2021-10-11T08:22:37Z | 2022-04-17T14:15:54Z | https://github.com/kubernetes/kubernetes/issues/105601 | 1,022,409,312 | 105,601 |
[
"kubernetes",
"kubernetes"
] | How do Apiserver and Kubelet send commands to listen for pods messages?
Where is this function implemented in the source code? | How do Apiserver and Kubelet send commands to listen for pods messages | https://api.github.com/repos/kubernetes/kubernetes/issues/105597/comments | 10 | 2021-10-11T02:52:59Z | 2022-03-11T15:27:15Z | https://github.com/kubernetes/kubernetes/issues/105597 | 1,022,199,739 | 105,597 |
[
"kubernetes",
"kubernetes"
] | right now due to the inability of only skipping storage test cases, the upgrade testsuite is kept untouched while we [skipped](https://github.com/kubernetes/kubernetes/pull/105052) other tests that will fail upon turning on the `CSIMigrationGCE` feature tag and will fail as a result.
We need to skip only the storage... | Granularly skip storage test cases in upgrade testsuite | https://api.github.com/repos/kubernetes/kubernetes/issues/105595/comments | 8 | 2021-10-11T00:46:40Z | 2022-04-20T05:24:53Z | https://github.com/kubernetes/kubernetes/issues/105595 | 1,022,143,047 | 105,595 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
go: 1.16.9 linux/arm64
k8s: v1.20.9
when in root implement “ go build ./vendor/k8s.io/code-generator/cmd/prerelease-lifecycle-gen/main.go” ，there is error:
vendor/k8s.io/klog/v2/klog_file.go:25:2: //go:build comment without // +build comment
### What did you expect to happen?
go build success
... | Built for aarch64-koji-linux-gnu error | https://api.github.com/repos/kubernetes/kubernetes/issues/105594/comments | 3 | 2021-10-10T11:53:20Z | 2021-10-10T12:45:19Z | https://github.com/kubernetes/kubernetes/issues/105594 | 1,021,962,763 | 105,594 |
Subsets and Splits
Unique Owner-Repo Count
Counts the number of unique owner-repos in the dataset, providing a basic understanding of diverse repositories.