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"
] | 1. When running the below command directly to vm
ubuntu@rajas-test2:~$ kubectl get pods
NAME READY STATUS RESTARTS AGE
nginx-65f88748fd-b8z4g 1/1 Running 0 89m
==========================================================
2. When running the same command using Jenkins execu... | Kubernetes working fine but not able to run using Jenkins. | https://api.github.com/repos/kubernetes/kubernetes/issues/77190/comments | 12 | 2019-04-28T20:06:17Z | 2019-08-28T08:54:23Z | https://github.com/kubernetes/kubernetes/issues/77190 | 438,094,640 | 77,190 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
In Azure disk... | azure data disk list is corrupted after attach/detach disk | https://api.github.com/repos/kubernetes/kubernetes/issues/77186/comments | 0 | 2019-04-28T12:20:11Z | 2019-04-29T06:38:20Z | https://github.com/kubernetes/kubernetes/issues/77186 | 438,050,708 | 77,186 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Initial submission is in k3s repo, but after verification and Darren's reminder, it also exists in kubernetes.
TL;DR https://github.com/rancher/k3s/issues/387
Accessing the "https://k8s-server:6443/logs/" reveals the details of the /var/log directory and the contents of all the files below.
... | Directory traversal (or path traversal)? | https://api.github.com/repos/kubernetes/kubernetes/issues/77182/comments | 13 | 2019-04-28T08:40:35Z | 2022-07-07T13:32:13Z | https://github.com/kubernetes/kubernetes/issues/77182 | 438,031,184 | 77,182 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
Does kubelet have http debug interface?
**Why is this needed**:
When kubelet or dockerd or node is notReady, we want to know the important cache in kubelet, like pod inof, pod status, containers..etc... | kubelet debug interface | https://api.github.com/repos/kubernetes/kubernetes/issues/77177/comments | 5 | 2019-04-28T04:16:08Z | 2019-04-29T03:15:30Z | https://github.com/kubernetes/kubernetes/issues/77177 | 438,011,404 | 77,177 |
[
"kubernetes",
"kubernetes"
] | http://dl.k8s.io Can't visit | dl.k8s.io Can't visit | https://api.github.com/repos/kubernetes/kubernetes/issues/77175/comments | 6 | 2019-04-28T03:02:08Z | 2019-04-29T21:28:14Z | https://github.com/kubernetes/kubernetes/issues/77175 | 438,006,207 | 77,175 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Kubelet startup error
```
E0428 09:37:13.276141 26151 runtime.go:69] Observed a panic: "invalid memory address or nil pointer dereference" (runtime error: invalid memory address or nil pointer dereference)
/workspace/anago-v1.14.1-beta.0.44+b7394102d6ef77/src/k8s.io/kubernetes/_output/docke... | kubelet: Observed a panic: "invalid memory address or nil pointer dereference" | https://api.github.com/repos/kubernetes/kubernetes/issues/77174/comments | 33 | 2019-04-28T02:18:23Z | 2021-10-22T09:48:58Z | https://github.com/kubernetes/kubernetes/issues/77174 | 438,003,371 | 77,174 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
When running `kubeadm init --pod-network-cidr=10.244.0.0/16` on OpenSUSE Kubic for aarch64 (board with amlogic s905w) kubelet spits out the following error and exits.
`kubelet.go:1359] Failed to start ContainerManager failed to initialize top level QOS containers: failed to update top level Burstab... | Permission denied on hugetlb due to wrong filename | https://api.github.com/repos/kubernetes/kubernetes/issues/77169/comments | 10 | 2019-04-27T19:55:14Z | 2019-06-28T23:09:30Z | https://github.com/kubernetes/kubernetes/issues/77169 | 437,978,382 | 77,169 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
Change killing Set to map which holds Ids of Pods which are killed, along with the timestamp killing starts.
On periodic basis, obtain lock, remove Pod Ids whose killing start time is sufficiently old from the killing map.
**Why is this needed**:
Currently we clear Pod Id as s... | Clear Ids for killed Pods in batches in Kubelet#podKiller | https://api.github.com/repos/kubernetes/kubernetes/issues/77168/comments | 5 | 2019-04-27T19:53:28Z | 2019-09-24T20:55:23Z | https://github.com/kubernetes/kubernetes/issues/77168 | 437,978,226 | 77,168 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
Add worker pool which is used to kill Pods.
**Why is this needed**:
Currently in Kubelet#podKiller, when we retrieve PodPair, we spin off goroutine (per PodPair).
By using worker pool which kills Pods, we can limit resource consumption - in case there is surge in pod killing... | Use worker pool for killing Pods | https://api.github.com/repos/kubernetes/kubernetes/issues/77166/comments | 8 | 2019-04-27T18:07:45Z | 2019-09-28T16:25:12Z | https://github.com/kubernetes/kubernetes/issues/77166 | 437,969,366 | 77,166 |
[
"kubernetes",
"kubernetes"
] | As PodPriority has been GA in 1.14, and we've removed FIFO implementation in scheduler.
I think it'd good to remove code related with "checking if features.PodPriority feature gate is enabled or not" - as that's always true now.
/sig scheduling
/kind cleanup | cleanup features.PodPriority | https://api.github.com/repos/kubernetes/kubernetes/issues/77152/comments | 5 | 2019-04-27T00:05:34Z | 2019-06-23T09:45:55Z | https://github.com/kubernetes/kubernetes/issues/77152 | 437,883,585 | 77,152 |
[
"kubernetes",
"kubernetes"
] | Tested on Kubernetes 1.14 (minikube 1.0). To reproduce:
1. deploy pod with a websocket server running:
```bash
kubectl run wsserver --generator=run-pod/v1 --rm -i --tty --image ubuntu:disco -- bash -c \
"apt-get update && apt-get install -y wget && \
wget https://github.com/vi/websocat/rele... | API proxy strips URL query params when proxying websocket connections | https://api.github.com/repos/kubernetes/kubernetes/issues/77142/comments | 56 | 2019-04-26T20:34:22Z | 2025-01-26T15:13:57Z | https://github.com/kubernetes/kubernetes/issues/77142 | 437,835,708 | 77,142 |
[
"kubernetes",
"kubernetes"
] | /sig storage
/kind cleanup
/kind enhancement
This is necessary to make sure that operation generator functions use the correct plugins when being run with migration on/off. Additionally we should check that the metrics generated from the `CompleteFunc` are generated with the correct plugin name | Add unit tests for Migration scenarios for Operation Generator | https://api.github.com/repos/kubernetes/kubernetes/issues/77141/comments | 9 | 2019-04-26T20:28:49Z | 2019-10-18T19:16:20Z | https://github.com/kubernetes/kubernetes/issues/77141 | 437,833,857 | 77,141 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
```
remote_runtime.go:173] ListPodSandbox with filter nil from runtime service failed: rpc error: code = ResourceExhausted desc = grpc: trying to send message larger than max (8398577 vs. 8388608)
kuberuntime_sandbox.go:210] ListPodSandbox failed: rpc error: code = ResourceExhausted desc = grpc:... | Inconsistent message size in Kubelet | https://api.github.com/repos/kubernetes/kubernetes/issues/77138/comments | 3 | 2019-04-26T19:08:35Z | 2019-05-01T03:50:57Z | https://github.com/kubernetes/kubernetes/issues/77138 | 437,807,574 | 77,138 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Delete an object (Service in this case) with a finalizer. Mutate the Service.
**What you expected to happen**:
I expected an error.
**Anything else we need to know?**:
It's debatable whether this should be a blanket ban on mutability. Status seems important to mutate. Metadata too, ... | Finalizing objects are mutable | https://api.github.com/repos/kubernetes/kubernetes/issues/77135/comments | 17 | 2019-04-26T17:38:23Z | 2019-06-12T21:42:57Z | https://github.com/kubernetes/kubernetes/issues/77135 | 437,775,853 | 77,135 |
[
"kubernetes",
"kubernetes"
] | Assume I have an object, e.g. a Service, which has a finalizer. When I delete that object, it correctly waits for the finalizer to be removed. In that intervening period, I can not see any indication that the object is being deleted. It does not show up in `kubectl describe`. It is not an event. If it gets stuck, ... | Finalizing objects not reflected in CLI | https://api.github.com/repos/kubernetes/kubernetes/issues/77134/comments | 5 | 2019-04-26T17:33:08Z | 2024-11-04T17:36:18Z | https://github.com/kubernetes/kubernetes/issues/77134 | 437,773,924 | 77,134 |
[
"kubernetes",
"kubernetes"
] | I have deploying a custom scheduler after following instructions step by step like mentioned in Kubernetes Docs
Here's [a link] (https://kubernetes.io/docs/tasks/administer-cluster/configure-multiple-schedulers/)
Pods I specify should be scheduled using scheduler "my-scheduler" leaves in Pending state while "my-s... | Custom scheduler leaves pod in pending state | https://api.github.com/repos/kubernetes/kubernetes/issues/77131/comments | 11 | 2019-04-26T14:32:37Z | 2019-09-23T18:35:19Z | https://github.com/kubernetes/kubernetes/issues/77131 | 437,702,277 | 77,131 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
kube-proxy is... | iptables-restore fails applying rules if pod run in arm64 | https://api.github.com/repos/kubernetes/kubernetes/issues/77130/comments | 7 | 2019-04-26T13:26:57Z | 2019-10-23T19:22:02Z | https://github.com/kubernetes/kubernetes/issues/77130 | 437,672,750 | 77,130 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
I set up a wi... | "KubeFailed to get node "{hostname}" when trying to set owner ref to the node lease" when specifying cloud provider. | https://api.github.com/repos/kubernetes/kubernetes/issues/77129/comments | 6 | 2019-04-26T13:22:11Z | 2020-01-03T07:10:20Z | https://github.com/kubernetes/kubernetes/issues/77129 | 437,670,772 | 77,129 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
Ran `sudo /... | Kubelet started with `/usr/bin/kubelet --pod-manifest-path=/etc/kubernetes/manifests` panics | https://api.github.com/repos/kubernetes/kubernetes/issues/77128/comments | 4 | 2019-04-26T12:52:01Z | 2019-07-22T17:35:26Z | https://github.com/kubernetes/kubernetes/issues/77128 | 437,658,536 | 77,128 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs -->
**Which jobs are failing**:
gce-scale-performance
**Which test(s) are failing**:
density test
**Since when has it been failing**:
Run 1117699728771911683. 2019-04-15 10:03 CEST
**Testgrid link**:
http... | GCE-5000: apiserver - increased cpu usage | https://api.github.com/repos/kubernetes/kubernetes/issues/77127/comments | 10 | 2019-04-26T11:28:45Z | 2019-06-25T12:15:51Z | https://github.com/kubernetes/kubernetes/issues/77127 | 437,628,788 | 77,127 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs -->
**Which jobs are failing**:
gce-scale-performance
**Which test(s) are failing**:
density test
**Since when has it been failing**:
Run 1120236390706057221. 2019-04-22 10:02 CEST
**Testgrid link**:
http... | [Failing test] GCE-5000: pods startup latency > 5s | https://api.github.com/repos/kubernetes/kubernetes/issues/77126/comments | 15 | 2019-04-26T11:06:49Z | 2019-06-03T12:47:47Z | https://github.com/kubernetes/kubernetes/issues/77126 | 437,621,439 | 77,126 |
[
"kubernetes",
"kubernetes"
] | k8s's version is 1.14.0
The kube-dns service's cluster-ip is 172.21.0.10. I can use` telnet 172.21.0.10 53` to access this cluster-ip, but the pod in this node cannot.
What should I do? | Node can access cluster-ip but pod is not | https://api.github.com/repos/kubernetes/kubernetes/issues/77125/comments | 5 | 2019-04-26T11:04:06Z | 2019-09-23T12:23:50Z | https://github.com/kubernetes/kubernetes/issues/77125 | 437,620,496 | 77,125 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What you did**: We replaced our... | Kubernetes unable to delete Azure managed disks when PVCs are deleted | https://api.github.com/repos/kubernetes/kubernetes/issues/77121/comments | 12 | 2019-04-26T09:40:26Z | 2019-10-05T06:00:17Z | https://github.com/kubernetes/kubernetes/issues/77121 | 437,588,269 | 77,121 |
[
"kubernetes",
"kubernetes"
] | k8s's version is 1.14.0.
I use kubeadm to install k8s, like this:
```
kubeadm init --pod-network-cidr=172.20.0.0/16
kubectl apply -f rbac-kdd.yaml
kubectl apply -f calico.yml
```
Every pod and service are running, but pod cannot resolve hostname from dns. The service kube-dns has a cluster-ip which i... | POD cannot access kube-dns service's cluster-ip | https://api.github.com/repos/kubernetes/kubernetes/issues/77115/comments | 3 | 2019-04-26T08:46:58Z | 2019-05-05T01:45:59Z | https://github.com/kubernetes/kubernetes/issues/77115 | 437,565,390 | 77,115 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
We've see tho... | Thousands TCP connections between master/compute stuck in "ESTABLISHED" status. | https://api.github.com/repos/kubernetes/kubernetes/issues/77114/comments | 4 | 2019-04-26T08:44:13Z | 2019-04-26T15:30:40Z | https://github.com/kubernetes/kubernetes/issues/77114 | 437,564,346 | 77,114 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
hit rate limi... | hit rate limit issue when attach/detach 70 disks at one time | https://api.github.com/repos/kubernetes/kubernetes/issues/77108/comments | 3 | 2019-04-26T06:24:08Z | 2019-09-05T07:23:34Z | https://github.com/kubernetes/kubernetes/issues/77108 | 437,517,037 | 77,108 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
i test in k8s... | cinder-csi-plugin GRPC attach failed that DeadlineExceeded desc = context deadline exceeded | https://api.github.com/repos/kubernetes/kubernetes/issues/77104/comments | 12 | 2019-04-26T01:01:30Z | 2019-11-08T20:29:56Z | https://github.com/kubernetes/kubernetes/issues/77104 | 437,455,741 | 77,104 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
After fixing golint failures under `test/e2e` (now still in progress), we need to put `gomega` for each `Expect()` and `HaveOccurred()`.
Then very common error checking code has become like:
`gomega.Expect(err).NotTo(gomega.HaveOccurred())`
We can replace this code with `framework.ExpectNoE... | Use framework.ExpectNoError() for e2e tests | https://api.github.com/repos/kubernetes/kubernetes/issues/77103/comments | 36 | 2019-04-26T00:05:05Z | 2019-06-06T22:46:21Z | https://github.com/kubernetes/kubernetes/issues/77103 | 437,445,406 | 77,103 |
[
"kubernetes",
"kubernetes"
] | Using GCE PD in-tree volumes with feature flags `CSIMigration=true,CSIMigrationGCE=true` with csi external provisioner `v1.1.0` when pvc is deleted with `RetentionPolicy=delete` the `Delete` call is never triggered on the CSI Driver.
This causes the PD to be leaked and the PV to never go away.
Feature is `Alpha` ... | Volume deletion not triggered when CSI Migration is enabled | https://api.github.com/repos/kubernetes/kubernetes/issues/77102/comments | 4 | 2019-04-25T23:42:48Z | 2019-05-07T22:50:34Z | https://github.com/kubernetes/kubernetes/issues/77102 | 437,440,857 | 77,102 |
[
"kubernetes",
"kubernetes"
] | Rancher 1.6 is using it still. Current Rancher version is 2.2.x per @alena1108. So we could possibly remove it from upstream and let the rancher folks maintain it in their own tree.
We don't need to carry the extra weight as mentioned in https://github.com/kubernetes/kubernetes/issues/76506
Since this is useful o... | Remove Rancher Credential Provider from upstream kubernetes | https://api.github.com/repos/kubernetes/kubernetes/issues/77098/comments | 2 | 2019-04-25T21:30:56Z | 2019-04-26T11:32:39Z | https://github.com/kubernetes/kubernetes/issues/77098 | 437,406,455 | 77,098 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
PATCH `{"spec":{"finalizers":null}}` doesn't clear the finalizers and also doesn't return an error.
**What you expected to happen**: It should return an error (use the /finalize subresource).
**How to reproduce it (as minimally and precisely as possible)**: see #77086
| modifying namespace spec.finalizers via PATCH should return a validation error | https://api.github.com/repos/kubernetes/kubernetes/issues/77097/comments | 12 | 2019-04-25T20:58:52Z | 2024-07-05T18:30:50Z | https://github.com/kubernetes/kubernetes/issues/77097 | 437,394,989 | 77,097 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
There are a lot of methods in `test/e2e/framework/util.go` that can be cleaned up or moved into it's own package for easier consumption/discovery. In https://github.com/kubernetes/kubernetes/issues/76206 there were some discussions for how to break up this file. The proposed packag... | Break up and Refactor test/e2e/framework/util.go | https://api.github.com/repos/kubernetes/kubernetes/issues/77095/comments | 56 | 2019-04-25T19:57:52Z | 2020-08-19T21:07:28Z | https://github.com/kubernetes/kubernetes/issues/77095 | 437,371,830 | 77,095 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
The certifi... | CSR ignores requested extension "Subject Alternative Name" | https://api.github.com/repos/kubernetes/kubernetes/issues/77092/comments | 6 | 2019-04-25T18:08:05Z | 2019-04-26T19:17:50Z | https://github.com/kubernetes/kubernetes/issues/77092 | 437,329,033 | 77,092 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
There is no way to delete Namespaces stuck in Terminating if they have finalizers which will never be run.
**What you expected to happen**:
There is a way to delete Namespaces stuck in Terminating.
**How to reproduce it (as minimally and precisely as possible)**:
Begin with any Kuberne... | There is no way to force delete Namespaces with invalid finalizers | https://api.github.com/repos/kubernetes/kubernetes/issues/77086/comments | 34 | 2019-04-25T17:11:29Z | 2020-09-04T11:44:22Z | https://github.com/kubernetes/kubernetes/issues/77086 | 437,307,775 | 77,086 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
**Why is this needed**:
https://github.com/kubernetes/kubernetes/pull/75434#discussion_r266358665 | Follow up of #75434: remove duplicate constants | https://api.github.com/repos/kubernetes/kubernetes/issues/77085/comments | 1 | 2019-04-25T17:06:59Z | 2019-05-07T05:53:53Z | https://github.com/kubernetes/kubernetes/issues/77085 | 437,306,057 | 77,085 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
**Why is this needed**:
https://github.com/kubernetes/kubernetes/pull/75434#discussion_r266350830 | Follow up of #75434: fix go lint failures | https://api.github.com/repos/kubernetes/kubernetes/issues/77084/comments | 1 | 2019-04-25T17:04:16Z | 2019-05-07T07:24:08Z | https://github.com/kubernetes/kubernetes/issues/77084 | 437,304,967 | 77,084 |
[
"kubernetes",
"kubernetes"
] | FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -oyaml'
error execution phase preflight: unable to fetch the kubeadm-config ConfigMap: failed to get config map: Get https://172.17.0.11:6443/api/v1/namespaces/kube-system/configmaps/kubeadm-config: dial tcp 172.17.0.11:6443: conn... | kubeadm join | https://api.github.com/repos/kubernetes/kubernetes/issues/77083/comments | 6 | 2019-04-25T16:39:04Z | 2019-09-27T20:04:49Z | https://github.com/kubernetes/kubernetes/issues/77083 | 437,295,051 | 77,083 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Continuous `DELETE` requests with propagation policy "foreground deletion" may lead to objects in the system that can only be purged with manual intervention if the object had a finalizer and no owner references.
I created a `ServiceAccount` and added a finalizer `foo.example.com/bar` to it. Then... | Objects with finalizers may get stuck when deleted with foreground deletion | https://api.github.com/repos/kubernetes/kubernetes/issues/77081/comments | 13 | 2019-04-25T16:10:05Z | 2025-02-26T02:05:51Z | https://github.com/kubernetes/kubernetes/issues/77081 | 437,282,587 | 77,081 |
[
"kubernetes",
"kubernetes"
] | It seems there is yet another regression in scalability tests (another one is debuged in https://github.com/kubernetes/kubernetes/issues/76579), this time in density tests. It looks unrelated to this another regression as it started to failing later (at 53b7bc30b).
/sig scalability | [Failing test] GCE-5000: density tests are failing | https://api.github.com/repos/kubernetes/kubernetes/issues/77080/comments | 10 | 2019-04-25T14:56:34Z | 2019-07-04T16:45:26Z | https://github.com/kubernetes/kubernetes/issues/77080 | 437,245,969 | 77,080 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
`kubeadm init... | kubeadm init phase upload-certs reports storing to ConfigMap instead of Secret | https://api.github.com/repos/kubernetes/kubernetes/issues/77079/comments | 0 | 2019-04-25T14:13:35Z | 2019-04-29T21:36:14Z | https://github.com/kubernetes/kubernetes/issues/77079 | 437,222,931 | 77,079 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
I'm using spark-on-kubernetes to submit spark app to kubernetes.
most of the time, it runs smoothly.
but sometimes, the driver pod phase changed from running to pending and starts another container in the pod though the first container exited successfully.
**What you expected to happen**:
... | spark on kubernetes driver pod phase changed from running to pending and starts another container in pod | https://api.github.com/repos/kubernetes/kubernetes/issues/77078/comments | 7 | 2019-04-25T14:03:57Z | 2019-09-22T17:04:50Z | https://github.com/kubernetes/kubernetes/issues/77078 | 437,218,131 | 77,078 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
I have enabled ipvs on Kubernetes 1.12.2 and try to connect kube-apiserver by kubernetes service sometimes and I find with ipvs mode, cannot connect kube-apiserver, but when I restart kube-proxy, I can connect kube-apiserver by kubernetes service.
**What you expected to happen**:
connect kube-a... | kube-proxy IPVS: can't connect kube-apiserver by kubernetes service sometimes. | https://api.github.com/repos/kubernetes/kubernetes/issues/77077/comments | 2 | 2019-04-25T13:41:44Z | 2019-04-25T14:15:18Z | https://github.com/kubernetes/kubernetes/issues/77077 | 437,206,296 | 77,077 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
Log file o... | Audit plugin: log and webhook get different events | https://api.github.com/repos/kubernetes/kubernetes/issues/77076/comments | 8 | 2019-04-25T13:36:35Z | 2019-05-31T02:40:27Z | https://github.com/kubernetes/kubernetes/issues/77076 | 437,203,758 | 77,076 |
[
"kubernetes",
"kubernetes"
] | Hi Team,
I am new to K8s.
Today i have setup K8s cluster. I am able to deploy K8s dashboard, everything working fine except dashboard authentication (using existing Token not able to respond).
Kindly needful.
Thanks in advance. | kubernetes dashboard token not responding. | https://api.github.com/repos/kubernetes/kubernetes/issues/77075/comments | 5 | 2019-04-25T13:34:50Z | 2019-09-22T17:04:49Z | https://github.com/kubernetes/kubernetes/issues/77075 | 437,202,893 | 77,075 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs -->
**Which jobs are failing**:
gci-gce-scalability and all other gce performance tests
**Which test(s) are failing**:
List resource fails.
**Since when has it been failing**:
Run 1121352546590396419. 02:57 P... | gci-gce-scalability - listResource fails | https://api.github.com/repos/kubernetes/kubernetes/issues/77074/comments | 4 | 2019-04-25T13:31:37Z | 2019-04-26T11:32:27Z | https://github.com/kubernetes/kubernetes/issues/77074 | 437,201,317 | 77,074 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
1. After s... | Updating cpu-manager-policy=static causes NVML unknown error | https://api.github.com/repos/kubernetes/kubernetes/issues/77073/comments | 13 | 2019-04-25T13:30:41Z | 2020-04-08T12:29:09Z | https://github.com/kubernetes/kubernetes/issues/77073 | 437,200,865 | 77,073 |
[
"kubernetes",
"kubernetes"
] | I create a single master cluster with kubeadm, according to doc, I did it like this:
```
kubeadm init --pod-network-cidr=172.20.0.0/16
kubectl apply -f rbac-kdd.yaml
kubectl apply -f calico.yml
```
Now, everything is fine, all pods and services are running, but when I test CoreDNS, the problem is arise. I cre... | I create a single master cluster with kubeadm, everything is fine but CoreDNS didn't work | https://api.github.com/repos/kubernetes/kubernetes/issues/77071/comments | 4 | 2019-04-25T12:58:34Z | 2019-04-26T08:15:13Z | https://github.com/kubernetes/kubernetes/issues/77071 | 437,185,539 | 77,071 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
Make sure `kubernetes.io/hostname` always equals to the node name.
**Why is this needed**:
https://github.com/kubernetes/kubernetes/blob/78190f0758a6ccbe11051b33844a886e5c282342/pkg/kubelet/kubel... | Validate `kubernetes.io/hostname` label is same as metadata.name field of node object? | https://api.github.com/repos/kubernetes/kubernetes/issues/77067/comments | 12 | 2019-04-25T11:01:15Z | 2020-01-02T14:54:11Z | https://github.com/kubernetes/kubernetes/issues/77067 | 437,137,924 | 77,067 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
flannel can't... | flannel can't connect kube-apiserver | https://api.github.com/repos/kubernetes/kubernetes/issues/77061/comments | 2 | 2019-04-25T10:29:19Z | 2019-04-25T15:34:46Z | https://github.com/kubernetes/kubernetes/issues/77061 | 437,124,878 | 77,061 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Created a deployment `v1` with some env vars. Applied a new version of the deployment `v2` with some env vars removed. The deployment failed so I then rolled back to `v1`, which brought the env vars back. I then reapplied `v2` with the env vars removed but they were not removed from the deployment.
... | Deployment Rollback Leaves Env Vars Stranded | https://api.github.com/repos/kubernetes/kubernetes/issues/77058/comments | 21 | 2019-04-25T09:52:36Z | 2021-04-16T13:42:09Z | https://github.com/kubernetes/kubernetes/issues/77058 | 437,109,142 | 77,058 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Pod scheduling to each node is uneven.
I have nine pods and three nodes, a node is allocated five pods, the other node is only assigned one pod. as a result, some of the machine's resources will be fully occupied.some nodes have a lot of resources
**What you expected to happen**:
Let's say I ha... | Pod scheduling is uneven | https://api.github.com/repos/kubernetes/kubernetes/issues/77052/comments | 8 | 2019-04-25T06:43:51Z | 2019-08-16T09:21:35Z | https://github.com/kubernetes/kubernetes/issues/77052 | 437,033,187 | 77,052 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
kubectl top di... | kubectl top should mention it requires setrics server not heapster due to deprecation | https://api.github.com/repos/kubernetes/kubernetes/issues/77047/comments | 8 | 2019-04-25T04:37:22Z | 2020-04-03T01:33:56Z | https://github.com/kubernetes/kubernetes/issues/77047 | 437,005,997 | 77,047 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
Currently, there are many `k8s.io/api/core/v1` imports in the project, and we could see two approaches for imports. I used ag to count the pkg imports and found out as below.
```go
$ ag -c "\t\"k8s.io/api/core/v1\"" | wc -l
1215
$ ag -c "\tv1 \"k8s.io/api/core/v1\"" |... | Inconsistency imports of core/v1 package | https://api.github.com/repos/kubernetes/kubernetes/issues/77045/comments | 12 | 2019-04-25T03:37:46Z | 2019-05-16T23:56:26Z | https://github.com/kubernetes/kubernetes/issues/77045 | 436,995,581 | 77,045 |
[
"kubernetes",
"kubernetes"
] | Repro: `bazel test --runs_per_test=10 //pkg/kubelet/cm/devicemanager:go_default_test`
```console
//pkg/kubelet/cm/devicemanager:go_default_test FAILED in 5 out of 10 in 17.8s
```
Errors tend to look something like this:
```console
--- FAIL: TestNewManagerImplStartProbeMode (11.00... | TestNewManagerImplStartProbeMode in (pkg/kubelet/cm/devicemanager) flakes half the time | https://api.github.com/repos/kubernetes/kubernetes/issues/77041/comments | 13 | 2019-04-25T02:46:40Z | 2019-11-15T10:02:52Z | https://github.com/kubernetes/kubernetes/issues/77041 | 436,985,902 | 77,041 |
[
"kubernetes",
"kubernetes"
] | https://prow.k8s.io/view/gcs/kubernetes-jenkins/pr-logs/pull/76924/pull-kubernetes-bazel-test-rbe/1121234523384713218
```
FAIL: //pkg/kubelet/oom:go_default_test (see /bazel-scratch/.cache/bazel/_bazel_root/7989b31489f31aee54f32688da2f0120/execroot/__main__/bazel-out/k8-fastbuild/testlogs/pkg/kubelet/oom/go_default... | /dev/kmsg inaccessible during remote bazel execution | https://api.github.com/repos/kubernetes/kubernetes/issues/77040/comments | 3 | 2019-04-25T02:43:42Z | 2019-04-25T11:35:10Z | https://github.com/kubernetes/kubernetes/issues/77040 | 436,985,291 | 77,040 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
Latency of volume operations like provisioning a volume has been evaluated as following:
1. for in-tree implementation, latency is recorded ONLY for one-retry loop which could be not accurate, i.e., when the first retry actually fails while the following attempt succeeded.
2. via... | Expose end to end latency volume operation metrics via CSI | https://api.github.com/repos/kubernetes/kubernetes/issues/77030/comments | 5 | 2019-04-24T23:45:13Z | 2019-06-01T03:45:14Z | https://github.com/kubernetes/kubernetes/issues/77030 | 436,951,797 | 77,030 |
[
"kubernetes",
"kubernetes"
] | looks like we still pull in `github.com/ghodss/yaml` instead of `sigs.k8s.io/yaml`
```
sigs.k8s.io/kustomize/pkg/target/kusttarget.go: "github.com/ghodss/yaml"
sigs.k8s.io/kustomize/pkg/resmap/resmap.go: "github.com/ghodss/yaml"
github.com/coreos/etcd/embed/config.go: "github.com/ghodss/yaml"
sigs.k8s.io/kustomize... | Remove dependency on ghodss/yaml | https://api.github.com/repos/kubernetes/kubernetes/issues/77024/comments | 18 | 2019-04-24T19:55:56Z | 2020-04-09T03:57:45Z | https://github.com/kubernetes/kubernetes/issues/77024 | 436,878,670 | 77,024 |
[
"kubernetes",
"kubernetes"
] | As a user of a cluster with multiple StorageClasses my application may have specific needs in terms of storage capabilities (ie Snapshots, Resize) for my application. Ideally I would be able to gather this sort of information in an automated fashion using the Kubernetes API.
Additionally, this would be useful for t... | Discuss providing a way to query configured CSIPlugins for available capabilities | https://api.github.com/repos/kubernetes/kubernetes/issues/77020/comments | 5 | 2019-04-24T17:21:37Z | 2019-09-23T21:32:51Z | https://github.com/kubernetes/kubernetes/issues/77020 | 436,815,803 | 77,020 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
When we mod... | AWS cloud provider caches security group tags forever | https://api.github.com/repos/kubernetes/kubernetes/issues/77019/comments | 25 | 2019-04-24T17:14:54Z | 2020-08-13T12:14:20Z | https://github.com/kubernetes/kubernetes/issues/77019 | 436,813,085 | 77,019 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
When I use ... | Kube-Apiserver can not proxy admission-webhook and aggr-apiserver to Headless Service | https://api.github.com/repos/kubernetes/kubernetes/issues/77018/comments | 7 | 2019-04-24T17:03:40Z | 2019-11-24T03:42:45Z | https://github.com/kubernetes/kubernetes/issues/77018 | 436,808,664 | 77,018 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
when deploy m... | how to change limits.cpu on metrics-server pod? | https://api.github.com/repos/kubernetes/kubernetes/issues/77004/comments | 6 | 2019-04-24T10:36:40Z | 2022-10-21T05:42:39Z | https://github.com/kubernetes/kubernetes/issues/77004 | 436,621,953 | 77,004 |
[
"kubernetes",
"kubernetes"
] | kubectl version
Client Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.5", GitCommit:"753b2dbc622f5cc417845f0ff8a77f539a4213ea", GitTreeState:"clean", BuildDate:"2018-12-06T01:33:57Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"11+", GitV... | how to validate client certificate, my application resolves for all digi cert client certificates | https://api.github.com/repos/kubernetes/kubernetes/issues/76998/comments | 3 | 2019-04-24T08:55:11Z | 2019-05-01T18:33:12Z | https://github.com/kubernetes/kubernetes/issues/76998 | 436,575,152 | 76,998 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
On kubernetes 1.10.9, "kubectl describe node" can get allocatable resources as following:
```
Allocated resources:
(Total limits may be over 100 percent, i.e., overcommitted.)
CPU Requests CPU ... | Can kubectl describe nodes add GPU resource summary? | https://api.github.com/repos/kubernetes/kubernetes/issues/76995/comments | 8 | 2019-04-24T08:19:52Z | 2022-06-09T23:16:58Z | https://github.com/kubernetes/kubernetes/issues/76995 | 436,559,662 | 76,995 |
[
"kubernetes",
"kubernetes"
] | @kubernetes/sig-node-bugs
```
FAIL: //pkg/kubelet/pleg:go_default_test (see /usr/local/google/home/fejta/.cache/bazel/_bazel_fejta/631ceaac9e4091781154c1030ef08d3e/execroot/__main__/bazel-out/k8-fastbuild/testlogs/pkg/kubelet/pleg/go_default_test/test_attempts/attempt_1.log)
FLAKY: //pkg/kubelet/pleg:go_default... | //pkg/kubelet/pleg:go_default_test is flaky | https://api.github.com/repos/kubernetes/kubernetes/issues/76989/comments | 6 | 2019-04-24T06:44:42Z | 2019-05-09T00:14:48Z | https://github.com/kubernetes/kubernetes/issues/76989 | 436,523,109 | 76,989 |
[
"kubernetes",
"kubernetes"
] | Frequently (but not always!) I'm getting "i/o timeout" error when retrieving logs:
````
>kubectl logs genghis-c98d79f7d-lv979 --tail=20
Error from server: Get https://192.168.134.21:10250/containerLogs/default/genghis-c98d79f7d-lv979/genghis?tailLines=20: dial tcp 192.168.134.21:10250: i/o timeout
````
After som... | Error "i/o timeout" when getting logs | https://api.github.com/repos/kubernetes/kubernetes/issues/76987/comments | 8 | 2019-04-24T06:21:27Z | 2021-08-12T12:19:46Z | https://github.com/kubernetes/kubernetes/issues/76987 | 436,516,103 | 76,987 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
use an existi... | use an existing azure file share name should be possible in azure file plugin | https://api.github.com/repos/kubernetes/kubernetes/issues/76986/comments | 0 | 2019-04-24T06:19:56Z | 2019-04-24T21:21:09Z | https://github.com/kubernetes/kubernetes/issues/76986 | 436,515,679 | 76,986 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
Enabled Exper... | ExperimentalHostUserNamespaceDefaulting feature flag is obsolete | https://api.github.com/repos/kubernetes/kubernetes/issues/76982/comments | 23 | 2019-04-24T03:07:21Z | 2024-10-25T04:47:24Z | https://github.com/kubernetes/kubernetes/issues/76982 | 436,475,818 | 76,982 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
We have pre... | Inefficient GetCandidateZonesForDynamicVolume impl caused aws api call throttling | https://api.github.com/repos/kubernetes/kubernetes/issues/76975/comments | 1 | 2019-04-24T00:56:57Z | 2019-05-08T21:32:19Z | https://github.com/kubernetes/kubernetes/issues/76975 | 436,450,095 | 76,975 |
[
"kubernetes",
"kubernetes"
] | There is currently no integration test for dry-run sub-resources, which for example led to #76943. We have a test that goes over all the resources, we should probably have one that goes over all sub-resources too and make sure that it works. | Create an integration test suite for dry-run sub-resources | https://api.github.com/repos/kubernetes/kubernetes/issues/76971/comments | 11 | 2019-04-24T00:08:00Z | 2020-07-15T15:45:11Z | https://github.com/kubernetes/kubernetes/issues/76971 | 436,440,861 | 76,971 |
[
"kubernetes",
"kubernetes"
] | runtimeclass: type description indicates alpha - should be beta | https://api.github.com/repos/kubernetes/kubernetes/issues/76970/comments | 1 | 2019-04-24T00:05:18Z | 2019-04-25T01:12:56Z | https://github.com/kubernetes/kubernetes/issues/76970 | 436,440,261 | 76,970 | |
[
"kubernetes",
"kubernetes"
] | **Merged with #62872**
---
Original type information is lost when CRD authors [expand their openapi definitions](https://github.com/ant31/crd-validation/blob/eab5f7e90b2c/pkg/convert_types.go#L81-L89). `openapi-gen`[-based operator code is similarly affected](https://github.com/coreos/prometheus-operator/blob/master/... | Consider $ref in CRDs or recommending authors add a GVK hint in replacements | https://api.github.com/repos/kubernetes/kubernetes/issues/76965/comments | 12 | 2019-04-23T21:50:30Z | 2019-05-05T03:17:33Z | https://github.com/kubernetes/kubernetes/issues/76965 | 436,405,817 | 76,965 |
[
"kubernetes",
"kubernetes"
] | See #76965 | https://api.github.com/repos/kubernetes/kubernetes/issues/76963/comments | 1 | 2019-04-23T20:32:02Z | 2019-04-24T18:47:02Z | https://github.com/kubernetes/kubernetes/issues/76963 | 436,376,840 | 76,963 | |
[
"kubernetes",
"kubernetes"
] | **What happened**:
In the current working directory, I have a `dir` directory, containing a `plop.yml` file.
When typing the following :
```
$ kubectl apply -f di[TAB]
```
the command-line becomes :
```
$ kubectl apply -f dir/ [CURSOR]
```
Please note the space after the trailing slash. This causes a secon... | kubectl zsh completion misbehaves on path containing a directory | https://api.github.com/repos/kubernetes/kubernetes/issues/76957/comments | 21 | 2019-04-23T18:46:48Z | 2020-12-09T09:31:50Z | https://github.com/kubernetes/kubernetes/issues/76957 | 436,336,007 | 76,957 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
The following error messages were found in the Kubernetes API server and controller manager logs:
```
E0423 17:35:58.491576 1 prometheus.go:138] failed to register depth metric admission_quota_controller: duplicate metrics collector registration attempted
E0423 17:35:58.491625 1 p... | duplicate metrics collector registration attempted | https://api.github.com/repos/kubernetes/kubernetes/issues/76956/comments | 22 | 2019-04-23T18:23:26Z | 2020-06-11T10:48:57Z | https://github.com/kubernetes/kubernetes/issues/76956 | 436,326,502 | 76,956 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
I've created ... | User without access to secrets can create pod, mounting secret | https://api.github.com/repos/kubernetes/kubernetes/issues/76954/comments | 3 | 2019-04-23T17:25:38Z | 2019-04-23T21:33:07Z | https://github.com/kubernetes/kubernetes/issues/76954 | 436,303,459 | 76,954 |
[
"kubernetes",
"kubernetes"
] | https://github.com/kubernetes/kubernetes/blob/master/pkg/cloudprovider/providers/vsphere/vclib/fixtures/fixtures.go
Relies on an a very unusual pattern to locate input files. It uses the location of the source file at the compile time. This breaks the test if you try to run the test anywhere else. | providers/vsphere/vclib/fixtures/fixtures.go test using source file location inside the test | https://api.github.com/repos/kubernetes/kubernetes/issues/76952/comments | 6 | 2019-04-23T17:14:20Z | 2019-10-05T06:00:16Z | https://github.com/kubernetes/kubernetes/issues/76952 | 436,299,072 | 76,952 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
For posterity:
```golang
type Probe struct {
InitialDelaySeconds int32
TimeoutSeconds int32
PeriodSeconds int32
...
}
```
Probes today take all their specified timeouts and delays in **... | Allow probes to run on a more granular timer. | https://api.github.com/repos/kubernetes/kubernetes/issues/76951/comments | 32 | 2019-04-23T17:03:58Z | 2023-02-08T07:26:43Z | https://github.com/kubernetes/kubernetes/issues/76951 | 436,295,182 | 76,951 |
[
"kubernetes",
"kubernetes"
] | The OWNERS_ALIASES file in this repo is currently being ignored because it cannot be parsed.
```
error: "error converting YAML to JSON: yaml: line 396: did not find expected key"
msg: "Failed to unmarshal aliases from "/tmp/git119819704/OWNERS_ALIASES". Using empty alias map."
```
I think the problem i... | The OWNERS_ALIASES file cannot be parsed. YAML is invalid. | https://api.github.com/repos/kubernetes/kubernetes/issues/76950/comments | 2 | 2019-04-23T16:23:05Z | 2019-04-24T03:39:27Z | https://github.com/kubernetes/kubernetes/issues/76950 | 436,278,662 | 76,950 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
https://git... | PluginWatcher: if do not close watcher when timeout is expected? | https://api.github.com/repos/kubernetes/kubernetes/issues/76949/comments | 8 | 2019-04-23T16:13:35Z | 2019-05-16T13:46:42Z | https://github.com/kubernetes/kubernetes/issues/76949 | 436,274,506 | 76,949 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
The pods/eviction REST handler does not check options.DryRun, and actually evicts the pod
/sig api-machinery
/assign @apelisse
/priority important-soon
The integration test for dry run skips all subresources. As part of fixing this, we should fix that test to exercise subresources. There ar... | pods/eviction does not honor `dryRun: true`option | https://api.github.com/repos/kubernetes/kubernetes/issues/76943/comments | 0 | 2019-04-23T14:09:26Z | 2019-04-25T04:44:56Z | https://github.com/kubernetes/kubernetes/issues/76943 | 436,209,473 | 76,943 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
I am running ... | undesired number of replica sets are created during deployment update | https://api.github.com/repos/kubernetes/kubernetes/issues/76938/comments | 5 | 2019-04-23T12:46:32Z | 2019-09-20T16:16:58Z | https://github.com/kubernetes/kubernetes/issues/76938 | 436,168,300 | 76,938 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
**TL;DR**: Due to slightly lacking error handling in dockershim, pods can end up with partially setup sandboxes under certain conditions. Specifically, with incorrect dns settings.
We sporadically encounter host-networked pods with the ClusterFirstWithHostNet dnsPolicy fail trying to resolve k8... | kubelet does not setup /etc/resolv.conf correctly for host networked pods | https://api.github.com/repos/kubernetes/kubernetes/issues/76935/comments | 20 | 2019-04-23T10:58:18Z | 2021-01-14T19:27:59Z | https://github.com/kubernetes/kubernetes/issues/76935 | 436,125,608 | 76,935 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
a daemonset p... | do not evict a DaemonSet Pod | https://api.github.com/repos/kubernetes/kubernetes/issues/76930/comments | 3 | 2019-04-23T08:37:04Z | 2019-04-27T17:27:36Z | https://github.com/kubernetes/kubernetes/issues/76930 | 436,064,901 | 76,930 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
Proxy Protocol support for kube-apiserver
**Why is this needed**:
When inspecting audit logs I've noticed load balancer private address is passed to the API - this makes bit harder to inspect API usage. Currently when enabling audit logs and enabling proxy-protocol on AWS ELB r... | proxy protocol support in kube-apiserver | https://api.github.com/repos/kubernetes/kubernetes/issues/76928/comments | 55 | 2019-04-23T07:46:12Z | 2025-02-21T07:03:36Z | https://github.com/kubernetes/kubernetes/issues/76928 | 436,045,249 | 76,928 |
[
"kubernetes",
"kubernetes"
] | **What happened**
Using OpenID Connect as an authentication provider with a client-secret that contains a special character like the `+` sign leads to refresh tokens not working because `kubectl` doesn't URL encode the client-secret before base64-encoding the basic auth header.
**What you expected to happen**
... | Basic auth header isn't URL encoded when making OAuth2 requests | https://api.github.com/repos/kubernetes/kubernetes/issues/76908/comments | 2 | 2019-04-22T21:27:35Z | 2019-04-24T02:08:23Z | https://github.com/kubernetes/kubernetes/issues/76908 | 435,899,878 | 76,908 |
[
"kubernetes",
"kubernetes"
] | https://github.com/kubernetes/kubernetes/pull/76849 added integration testing of admission webhooks, both validating and mutating.
It tests all resources/subresources/verbs found via discovery, with the exception of some resources that require special setup or testing, or which are not sent to admission today.
As... | Complete integration testing for admission webhooks | https://api.github.com/repos/kubernetes/kubernetes/issues/76907/comments | 3 | 2019-04-22T20:53:46Z | 2019-04-24T03:40:41Z | https://github.com/kubernetes/kubernetes/issues/76907 | 435,887,849 | 76,907 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
Currently there are no end-to-end tests to check ephemeral volume support.
**Why is this needed**:
Since https://github.com/kubernetes-csi/csi-driver-host-path/pull/10 introduced support for ephemeral volumes, e2e can be added. | Add CSI e2e tests for inline ephemeral volumes | https://api.github.com/repos/kubernetes/kubernetes/issues/76906/comments | 2 | 2019-04-22T20:38:23Z | 2019-07-22T23:27:43Z | https://github.com/kubernetes/kubernetes/issues/76906 | 435,882,214 | 76,906 |
[
"kubernetes",
"kubernetes"
] | **Which jobs are failing**:
[sig-release-master-upgrade#gce-new-master-upgrade-cluster-new](https://testgrid.k8s.io/sig-release-master-upgrade#gce-new-master-upgrade-cluster-new)
**Which test(s) are failing**:
[SkewTest](https://prow.k8s.io/view/gcs/kubernetes-jenkins/logs/ci-kubernetes-e2e-gce-new-master-upgrade-... | [Failing Test] SkewTest failing in master-upgrade:gce-new-master-upgrade-cluster-new | https://api.github.com/repos/kubernetes/kubernetes/issues/76901/comments | 2 | 2019-04-22T14:20:28Z | 2019-05-13T14:44:00Z | https://github.com/kubernetes/kubernetes/issues/76901 | 435,743,876 | 76,901 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs -->
**Which jobs are failing**:
* `ci-cloud-provider-vsphere-conformance-latest`
* `ci-vsphere-conformance-latest`
**Which test(s) are failing**:
* `Overall` ([spyglass](https://prow.k8s.io/view/gcs/kubernetes-j... | [Failing test] vSphere conformance tests failing in master-informing | https://api.github.com/repos/kubernetes/kubernetes/issues/76899/comments | 7 | 2019-04-22T14:08:26Z | 2019-06-04T14:55:35Z | https://github.com/kubernetes/kubernetes/issues/76899 | 435,739,578 | 76,899 |
[
"kubernetes",
"kubernetes"
] | **Which jobs are failing**:
`ci-kubernetes-e2e-gce-new-master-upgrade-cluster` - `master-upgrade/gce-new-master-upgrade-cluster`
`ci-kubernetes-e2e-gce-new-master-upgrade-cluster-new` - `master-upgrade/gce-new-master-upgrade-cluster-new`
**Which test(s) are failing**:
`[sig-storage] CSI Volumes [Driver: csi-hostp... | [Failing Test] [sig-storage] CSI Volumes [Driver: csi-hostpath-v0] [Testpattern: Dynamic PV (default fs)] subPath should unmount if pod is gracefully deleted while kubelet is down [Disruptive][Slow] | https://api.github.com/repos/kubernetes/kubernetes/issues/76898/comments | 5 | 2019-04-22T14:07:23Z | 2019-05-30T18:14:20Z | https://github.com/kubernetes/kubernetes/issues/76898 | 435,739,239 | 76,898 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
As reported [he... | Master doesn't attempt to attach FlexVolume | https://api.github.com/repos/kubernetes/kubernetes/issues/76897/comments | 2 | 2019-04-22T14:04:26Z | 2019-04-26T22:16:48Z | https://github.com/kubernetes/kubernetes/issues/76897 | 435,738,278 | 76,897 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs -->
**Which jobs are failing**:
`ci-cloud-provider-openstack-acceptance-test-e2e-conformance`
**Which test(s) are failing**:
`Overall` ([spyglass](https://prow.k8s.io/view/gcs/k8s-conformance-openstack/periodic-l... | [Failing Test] openstack conformance is failing in master-informing | https://api.github.com/repos/kubernetes/kubernetes/issues/76896/comments | 7 | 2019-04-22T13:54:38Z | 2019-05-29T02:56:03Z | https://github.com/kubernetes/kubernetes/issues/76896 | 435,734,978 | 76,896 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs -->
**Which jobs are failing**:
* `ci-kubernetes-e2e-gce-master-new-downgrade-cluster`
* `ci-kubernetes-e2e-gce-master-new-downgrade-cluster-parallel`
**Which test(s) are failing**:
* `Up` ([spyglass](https://pr... | [Failing Test] up failing in master-upgrade | https://api.github.com/repos/kubernetes/kubernetes/issues/76895/comments | 14 | 2019-04-22T13:39:02Z | 2019-05-11T23:53:37Z | https://github.com/kubernetes/kubernetes/issues/76895 | 435,730,108 | 76,895 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Set the svc nodeport to 6443 causes the cluster to not work properly. Because port 6443 will be occupied.
i didn't find the same issue so create this issue. i just want to know that if there are some ways to avoid this.
**Environment**:
- Kubernetes version (use `kubectl version`): v1.11.0
- O... | Set the svc nodeport to 6443 causes the cluster to not work properly | https://api.github.com/repos/kubernetes/kubernetes/issues/76892/comments | 6 | 2019-04-22T09:35:23Z | 2019-05-02T21:10:36Z | https://github.com/kubernetes/kubernetes/issues/76892 | 435,666,890 | 76,892 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
I would like scaleUpLimit parameter to be configurable to accommodate various scenarios
**Why is this needed**:
As per current motivation in code comments
```
// Do not upscale too much to prevent... | Allow scaleUpLimit parameter to be configurable | https://api.github.com/repos/kubernetes/kubernetes/issues/76880/comments | 7 | 2019-04-22T00:59:35Z | 2019-09-19T07:45:30Z | https://github.com/kubernetes/kubernetes/issues/76880 | 435,565,276 | 76,880 |
[
"kubernetes",
"kubernetes"
] | Flag deprecate messages e.g. `Flag --resource-container has been deprecated, This feature will be removed in a later release.` are sent only to stderr (I believe), and are not logged to the log-file.
With the move to make the logfiles canonical, and to stop redirect stdout/stderr to log files, we should probably tac... | Flag deprecation messages should be sent to klog | https://api.github.com/repos/kubernetes/kubernetes/issues/76873/comments | 12 | 2019-04-21T04:25:25Z | 2020-10-05T09:16:48Z | https://github.com/kubernetes/kubernetes/issues/76873 | 435,474,074 | 76,873 |
[
"kubernetes",
"kubernetes"
] | ```
version: v1.13.5
```
**What happened**:
```
$ systemctl cat kube-apiserver.service |grep 10.9
--service-cluster-ip-range=10.97.0.0/12 \
$ systemctl cat kube-controller-manager.service | grep -P service-cluster
--service-cluster-ip-range=10.97.0.0/12 \
$ kubectl delete svc kubernetes
service "kuberne... | err svc default/kubernetes's clusterip | https://api.github.com/repos/kubernetes/kubernetes/issues/76864/comments | 5 | 2019-04-20T15:19:07Z | 2019-04-20T17:24:11Z | https://github.com/kubernetes/kubernetes/issues/76864 | 435,410,037 | 76,864 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Our pods are failing to deploy and getting stuck after being successfully deployed. Once pod is stuck you can try deleting it and a new pod would be created (which can also get stuck), the old one would still be there and won't be removed even in 24 hours.
```
kubectl get --sort-by='{.lastTime... | grpc: the connection is unavailable on Google Kubernetes Engine | https://api.github.com/repos/kubernetes/kubernetes/issues/76861/comments | 7 | 2019-04-20T14:09:46Z | 2019-10-06T09:26:46Z | https://github.com/kubernetes/kubernetes/issues/76861 | 435,403,366 | 76,861 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Looks like KEP organization changed and the component-base kep in the readme doesn't link anymore.
**What you expected to happen**:
Link to go to the right document.
**How to reproduce it (as minimally and precisely as possible)**:
click link - https://github.com/kubernetes/component-base/bl... | Component Base KEP Link in readme. | https://api.github.com/repos/kubernetes/kubernetes/issues/76851/comments | 2 | 2019-04-19T22:52:55Z | 2019-05-09T01:50:49Z | https://github.com/kubernetes/kubernetes/issues/76851 | 435,325,476 | 76,851 |
[
"kubernetes",
"kubernetes"
] | This is to track the changes required for the RequestManagement alpha feature, now that it's [KEP](https://github.com/kubernetes/enhancements/blob/master/keps/sig-api-machinery/20190228-priority-and-fairness.md) has been approved. A more verbose version of the work can be found in the below [spreadsheet](https://docs.g... | Umbrella Tracking Issue For WIP Alpha Feature - Priority and Fairness For API Server Requests | https://api.github.com/repos/kubernetes/kubernetes/issues/76846/comments | 23 | 2019-04-19T20:29:27Z | 2020-05-14T12:47:00Z | https://github.com/kubernetes/kubernetes/issues/76846 | 435,295,611 | 76,846 |
Subsets and Splits
Unique Owner-Repo Count
Counts the number of unique owner-repos in the dataset, providing a basic understanding of diverse repositories.