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"
] | <!-- 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 deployed ... | Pods scheduled on Windows node show as "running" even when the Windows node is shut down | https://api.github.com/repos/kubernetes/kubernetes/issues/93842/comments | 12 | 2020-08-10T05:30:09Z | 2021-02-10T14:58:12Z | https://github.com/kubernetes/kubernetes/issues/93842 | 675,873,825 | 93,842 |
[
"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 is no... | kubeadm deploy failed when using non-default etcd port | https://api.github.com/repos/kubernetes/kubernetes/issues/93840/comments | 5 | 2020-08-10T03:01:28Z | 2020-08-10T14:42:46Z | https://github.com/kubernetes/kubernetes/issues/93840 | 675,833,792 | 93,840 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
There are a lot of `_PILLAR_` variables (i.e. around the DNS area) which need to probably be removed over time, as I think were not coupled to salt anymore.
**What you expected to happen**:
Salt variable semantics wouldn't be coupled into the codebase.
**How to reproduce it (as minimally... | Salt / _PILLAR_ references in DNS parts of the codebase - what's the plan to remove? | https://api.github.com/repos/kubernetes/kubernetes/issues/93835/comments | 6 | 2020-08-09T16:06:13Z | 2020-08-16T12:53:03Z | https://github.com/kubernetes/kubernetes/issues/93835 | 675,725,392 | 93,835 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
Right now we poll one node at a time for intra-pod tests. We ultimately fail a test if any one node is unreachable.
If we instead polled all nodes, multiple times, and collected the number of times a node was unreachable, this would
- tell us what % of nodes on the cluster ... | Breadth first polling in intra-pod networking Conformance verification | https://api.github.com/repos/kubernetes/kubernetes/issues/93833/comments | 5 | 2020-08-09T13:49:31Z | 2020-09-22T19:22:51Z | https://github.com/kubernetes/kubernetes/issues/93833 | 675,703,292 | 93,833 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
(modified this from my original description, where I linked to node IP metadata, probably not a good example)
convenience methods for detecting wether or not a cluster supports different networking modes,
- IPv6 services supported
- IPv6 pods supported
- DualStack supported
... | Should/Can we have a utils function for making decisions based on dualstack support ? | https://api.github.com/repos/kubernetes/kubernetes/issues/93832/comments | 7 | 2020-08-09T13:02:48Z | 2020-08-14T12:39:54Z | https://github.com/kubernetes/kubernetes/issues/93832 | 675,696,286 | 93,832 |
[
"kubernetes",
"kubernetes"
] | This is a bug found in https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/93555/pull-kubernetes-integration/1292393344655167493.
The scheduler fails to schedule the pod `pv-w-prebound` on the first try due to PV is out of sync.
```
I0809 10:06:11.676940 121717 scheduler_binder.go:349] AssumePodVolumes ... | Scheduler should forget the pod when the reverse plugins fail | https://api.github.com/repos/kubernetes/kubernetes/issues/93830/comments | 2 | 2020-08-09T12:24:28Z | 2020-08-11T19:36:18Z | https://github.com/kubernetes/kubernetes/issues/93830 | 675,691,137 | 93,830 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
`TaintToleration` is a plugin that checks if a pod tolerates a node's taints
`NodeUnschedulable` is plugin which check if the pod tolerates one specific taint `node.kubernetes.io/unschedulable` and the i... | merge `NodeUnschedulable` with `TaintToleration` filter plugin together | https://api.github.com/repos/kubernetes/kubernetes/issues/93828/comments | 7 | 2020-08-09T10:03:24Z | 2020-08-11T01:47:45Z | https://github.com/kubernetes/kubernetes/issues/93828 | 675,672,445 | 93,828 |
[
"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**:
Back-off rest... | Back-off restarting failed container | https://api.github.com/repos/kubernetes/kubernetes/issues/93826/comments | 2 | 2020-08-09T07:15:57Z | 2020-08-09T14:50:14Z | https://github.com/kubernetes/kubernetes/issues/93826 | 675,651,511 | 93,826 |
[
"kubernetes",
"kubernetes"
] | /open
_Originally posted by @chiducaf in https://github.com/kubernetes/kops/issues/964#issuecomment-671016315_ | /open | https://api.github.com/repos/kubernetes/kubernetes/issues/93825/comments | 2 | 2020-08-09T07:06:16Z | 2020-08-09T07:07:33Z | https://github.com/kubernetes/kubernetes/issues/93825 | 675,650,472 | 93,825 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
- The service DNS name of `${service-name}.${namespace}.svc.cluster.local` is not Kube DNS optimized, do provide the recommendation/best practices documentation
**Why is this needed**:
Refers to thi... | Recommendation of service DNS name best practise | https://api.github.com/repos/kubernetes/kubernetes/issues/93824/comments | 24 | 2020-08-09T03:59:33Z | 2022-07-30T04:16:17Z | https://github.com/kubernetes/kubernetes/issues/93824 | 675,631,240 | 93,824 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about flaky tests or jobs (pass or fail with no underlying change in code) in Kubernetes CI -->
**Which jobs are flaking**:
`pull-kubernetes-verify`
**Which test(s) are flaking**:
`verify.govet`
**Testgrid link**:
https://testgrid.k8s.io/presub... | [Flaky Test] verify.govet passes entire source tree resulting in high memory usage | https://api.github.com/repos/kubernetes/kubernetes/issues/93822/comments | 12 | 2020-08-09T02:06:52Z | 2021-02-18T23:13:26Z | https://github.com/kubernetes/kubernetes/issues/93822 | 675,620,724 | 93,822 |
[
"kubernetes",
"kubernetes"
] | ### Flaky Job: pr:pull-kubernetes-e2e-gce-100-performance
Flakes in the past week: **18**
Consistency: **93.60%**
#### Flakiest tests by flake count:
| Test | Flake Count |
| --- | --- |
| ClusterLoaderV2 | 12 |
| Timeout | 9 |
| TearDown | 4 |
| testing/density/config.yaml | 4 |
#### Previously closed issues for t... | pr:pull-kubernetes-e2e-gce-100-performance flaked 18 times in the past week | https://api.github.com/repos/kubernetes/kubernetes/issues/93820/comments | 5 | 2020-08-08T22:43:48Z | 2020-08-17T08:45:40Z | https://github.com/kubernetes/kubernetes/issues/93820 | 675,599,572 | 93,820 |
[
"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**:
Running `kube... | Log streaming disconnects after a while | https://api.github.com/repos/kubernetes/kubernetes/issues/93819/comments | 12 | 2020-08-08T22:09:26Z | 2021-01-08T17:05:38Z | https://github.com/kubernetes/kubernetes/issues/93819 | 675,595,842 | 93,819 |
[
"kubernetes",
"kubernetes"
] | **Usecase:** We want a file to be exported to S3 if the container running in pod gets restarted due to OOM error, so we are passing a script in pre stop hook to achieve it, But we are unable to achieve it since pre stop hook is not being triggered.
**What happened**:
_**Scenario 1:**_ when a pod is deleted manually... | Prestop hook are not being triggered when container in the pod gets restarted | https://api.github.com/repos/kubernetes/kubernetes/issues/93818/comments | 14 | 2020-08-08T19:23:27Z | 2022-09-14T16:19:18Z | https://github.com/kubernetes/kubernetes/issues/93818 | 675,575,512 | 93,818 |
[
"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://githu... | SMB mount issue | https://api.github.com/repos/kubernetes/kubernetes/issues/93805/comments | 0 | 2020-08-08T02:42:39Z | 2020-08-15T02:40:19Z | https://github.com/kubernetes/kubernetes/issues/93805 | 675,409,636 | 93,805 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Based on the below references, I am concerned about the implications of including fsGroup in a pod that mounts shared file system volumes. Many companies have multiple workflows that utilize the same shared file system whether onprem, in the cloud, or in containers and if someone mounts a pod that ... | If Kubelet Tries To Chown Files Any Time It Sees fsGroup Then That Can Catastrophically Impact Shared File Systems | https://api.github.com/repos/kubernetes/kubernetes/issues/93802/comments | 12 | 2020-08-07T20:56:16Z | 2021-11-24T15:37:31Z | https://github.com/kubernetes/kubernetes/issues/93802 | 675,282,105 | 93,802 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
When trying to access a port that is forwarded with NodePort, large packet loss is being seen (upwards of 80% packet loss).
This is occurring on a freshly installed Kubernetes cluster running on baremetal and using kube-router as the networking interface. This occurs both locally on the node itsel... | Packet loss with NodePort port forwarding, no SYN-ACK being sent by worker node | https://api.github.com/repos/kubernetes/kubernetes/issues/93801/comments | 15 | 2020-08-07T19:38:39Z | 2021-01-16T05:00:16Z | https://github.com/kubernetes/kubernetes/issues/93801 | 675,234,148 | 93,801 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Kubelet is logging error messages every 10 seconds indicating failed vmss calls because of rate limiting. These calls prevent the subscription from recovering from whatever was the original cause of the rate limiting by making these API calls continuously.
**What you expected to happen**:
Kube... | Kubelet on Azure is making vmss calls even when useInstanceMetadata is set to true | https://api.github.com/repos/kubernetes/kubernetes/issues/93796/comments | 20 | 2020-08-07T19:22:04Z | 2020-08-21T03:52:32Z | https://github.com/kubernetes/kubernetes/issues/93796 | 675,226,064 | 93,796 |
[
"kubernetes",
"kubernetes"
] | Note: this issue should be viewed in the context of #93252.
**What would you like to be added**: When parsing the performance-config.yaml file, make sure each testCase and workload has a unique name. This can also be implemented by changing the yaml file's structure into maps instead of arrays (as suggested by @alcu... | test/integration/scheduler_perf: make sure each testCase and workload has a unique name | https://api.github.com/repos/kubernetes/kubernetes/issues/93795/comments | 17 | 2020-08-07T19:18:25Z | 2021-04-11T02:03:31Z | https://github.com/kubernetes/kubernetes/issues/93795 | 675,224,265 | 93,795 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**: `CleanupNodes` currently enlists all nodes and deletes *all* of them. This is unintuitive as each node preparer should probably only cleanup the nodes it created.
/sig scheduling
/sig testing
/assign | test/integration/framework/perf_utils.go: refactor CleanupNodes to only delete nodes created by itself | https://api.github.com/repos/kubernetes/kubernetes/issues/93794/comments | 25 | 2020-08-07T19:14:26Z | 2023-01-18T06:29:23Z | https://github.com/kubernetes/kubernetes/issues/93794 | 675,222,341 | 93,794 |
[
"kubernetes",
"kubernetes"
] | Note: this issue should be viewed in the context of #93252.
**What would you like to be added**: Currently we support three types of ops: `CreateNodes`, `CreatePods`, `Barrier`. This issue proposes adding a `Sleep` op that would simulate user action by causing the main thread to sleep. Note: I don't have a use-case ... | new scheduler_perf framework: add a sleep timer op | https://api.github.com/repos/kubernetes/kubernetes/issues/93793/comments | 19 | 2020-08-07T19:10:24Z | 2022-05-04T00:17:11Z | https://github.com/kubernetes/kubernetes/issues/93793 | 675,220,185 | 93,793 |
[
"kubernetes",
"kubernetes"
] | Note: this issue should be viewed in the context of https://github.com/kubernetes/kubernetes/pull/93252.
**What would you like to be added**: Each workload currently requires the user to specify the node/pod specs explicitly. While this is sometimes useful in certain workloads, for around half the workloads, all ben... | new scheduler_perf framework: allow users to specify default pod and node specs | https://api.github.com/repos/kubernetes/kubernetes/issues/93792/comments | 27 | 2020-08-07T19:05:24Z | 2022-06-29T18:44:07Z | https://github.com/kubernetes/kubernetes/issues/93792 | 675,217,619 | 93,792 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Udp service is not working with 1 node. (3 others are ok)
**What you expected to happen**:
Udp K8s service is working in my 4th node
**How to reproduce it (as minimally and precisely as possible)**:
**Anything else we need to know?**:
I have build a 3 nodes cluster about 6 months and I ha... | Udp service not working on 1 node | https://api.github.com/repos/kubernetes/kubernetes/issues/93791/comments | 11 | 2020-08-07T17:13:39Z | 2020-12-07T19:37:05Z | https://github.com/kubernetes/kubernetes/issues/93791 | 675,156,494 | 93,791 |
[
"kubernetes",
"kubernetes"
] | Using scheduler like `scheduler --help` or `scheduler --version`, it always get unwanted output like:
```
[root@masterdemo amd64]# ./kube-scheduler --version
I0808 00:08:38.914277 30987 registry.go:173] Registering SelectorSpread plugin
I0808 00:08:38.914519 30987 registry.go:173] Registering SelectorSpread plu... | Scheduler registering info shows in --version flag | https://api.github.com/repos/kubernetes/kubernetes/issues/93788/comments | 3 | 2020-08-07T16:15:39Z | 2020-08-27T23:07:29Z | https://github.com/kubernetes/kubernetes/issues/93788 | 675,121,334 | 93,788 |
[
"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'm trying to... | Kubernetes Worker Node Error -- error uploading crisocket | https://api.github.com/repos/kubernetes/kubernetes/issues/93786/comments | 4 | 2020-08-07T15:51:36Z | 2020-08-10T14:49:42Z | https://github.com/kubernetes/kubernetes/issues/93786 | 675,104,061 | 93,786 |
[
"kubernetes",
"kubernetes"
] | Running :
```
kubectl drain node/XXX --force=true --delete-local-data=true --ignore-daemonsets
```
cpu usage goes to 2 cores @ 100%
**What you expected to happen**:
Way lower cpu usage.
**Environment**:
- Kubernetes version (use `kubectl version`):
```
Client Version: version.Info{Major:"1", Minor:"18... | kubectl drain uses 200% cpu. | https://api.github.com/repos/kubernetes/kubernetes/issues/93784/comments | 16 | 2020-08-07T14:45:56Z | 2020-10-19T14:52:14Z | https://github.com/kubernetes/kubernetes/issues/93784 | 675,064,496 | 93,784 |
[
"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 misbehaving... | Inability to create pods creates a snowball effect in Kubernetes cronjobs | https://api.github.com/repos/kubernetes/kubernetes/issues/93783/comments | 9 | 2020-08-07T14:24:26Z | 2021-01-07T18:43:38Z | https://github.com/kubernetes/kubernetes/issues/93783 | 675,050,986 | 93,783 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about flaky tests or jobs (pass or fail with no underlying change in code) in Kubernetes CI -->
**Which jobs are flaking**:
`kind-ipv6-master-parallel (ci-kubernetes-kind-ipv6-e2e-parallel)`
**Which test(s) are flaking**:
`[sig-scheduling] LimitRange... | [Flaky Test] [sig-scheduling] LimitRange should create a LimitRange with defaults and ensure pod has those defaults applied. [Conformance] | https://api.github.com/repos/kubernetes/kubernetes/issues/93782/comments | 9 | 2020-08-07T14:12:21Z | 2021-01-28T03:31:38Z | https://github.com/kubernetes/kubernetes/issues/93782 | 675,043,445 | 93,782 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about flaky tests or jobs (pass or fail with no underlying change in code) in Kubernetes CI -->
**Which jobs are flaking**:
`integration-master (ci-kubernetes-integration-master)`
**Which test(s) are flaking**:
`TestVolumeBinding`
**Testgrid link*... | [Flaky Test] [sig-storage] TestVolumeBinding experiencing pod scheduling timeout (ci-kubernetes-integration-master) | https://api.github.com/repos/kubernetes/kubernetes/issues/93780/comments | 7 | 2020-08-07T13:50:46Z | 2020-08-13T20:28:46Z | https://github.com/kubernetes/kubernetes/issues/93780 | 675,030,015 | 93,780 |
[
"kubernetes",
"kubernetes"
] | The statement "returns [...], or nil" cannot be true since the return type is a struct:
https://github.com/kubernetes/kubernetes/blob/97c5f1f7632f2d349303515830be76f6c1084b19/staging/src/k8s.io/apimachinery/pkg/runtime/schema/interfaces.go#L26-L28
https://github.com/kubernetes/kubernetes/blob/97c5f1f7632f2d349303... | Incorrect comment in runtime ObjectKind interface | https://api.github.com/repos/kubernetes/kubernetes/issues/93775/comments | 3 | 2020-08-07T11:21:13Z | 2020-09-10T16:33:46Z | https://github.com/kubernetes/kubernetes/issues/93775 | 674,949,196 | 93,775 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Windows kubelet panic occasionally on nodes which have high volume of pods run and delete.
```
fatal error: concurrent map writes
goroutine 13660836 [running]:
runtime.throw(0x40932d0, 0x15)
/usr/local/go/src/runtime/panic.go:774 +0x79 fp=0xc00274b7c0 sp=0xc00274b790 pc=0x4334a9
runtime.map... | kubelet panic with fatal error: concurrent map writes | https://api.github.com/repos/kubernetes/kubernetes/issues/93771/comments | 9 | 2020-08-07T08:21:38Z | 2020-09-02T01:47:01Z | https://github.com/kubernetes/kubernetes/issues/93771 | 674,850,089 | 93,771 |
[
"kubernetes",
"kubernetes"
] | I am trying to configure the kubelet using kubelet --log-dir="xxxx", the new path, but it gives an error and doesn't run. I want to change the log directory from /var/logs/messages, since the last time I spinned the cluster up, it occupied all the space and as a result there was Diskpressure: True. So now I changed the... | Changing the log directory from /var/logs/messages | https://api.github.com/repos/kubernetes/kubernetes/issues/93761/comments | 5 | 2020-08-06T19:30:01Z | 2021-03-08T21:15:21Z | https://github.com/kubernetes/kubernetes/issues/93761 | 674,550,639 | 93,761 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**: `scheduling_perf_test.go` only supports one node labelling strategy currently. However, I don't see any reason why multiple node labelling strategies cannot be supported at the same time. Solving overlapping labels from different strategies would be an interesting problem to solve; ... | scheduler_perf: support multiple node labelling strategies | https://api.github.com/repos/kubernetes/kubernetes/issues/93760/comments | 11 | 2020-08-06T19:18:34Z | 2021-07-04T09:51:55Z | https://github.com/kubernetes/kubernetes/issues/93760 | 674,544,415 | 93,760 |
[
"kubernetes",
"kubernetes"
] | As a workaround solution for issue, https://github.com/golang/go/issues/39786, I used powershell command "(Get-Item -Path %s ).Target" to get the target symlink. However, it does not work under following situation.
1. PD disk attached to Windows node, partitioned and formatted
2. create a symlink /var/lib/kubelet/plu... | Use powershell command Get-item. target to get target symlink issue | https://api.github.com/repos/kubernetes/kubernetes/issues/93759/comments | 4 | 2020-08-06T18:32:00Z | 2021-01-03T22:14:03Z | https://github.com/kubernetes/kubernetes/issues/93759 | 674,518,811 | 93,759 |
[
"kubernetes",
"kubernetes"
] |
## Priority and Fairness End-to-End Tests
## Basic CRUD
Should we create tests around the creation, modification and deletion of the `flowcontrol.apiserver.k8s.io` objects ? For example, adding an invalid FlowSchema with a misconfigured PriorityLevelConfiguration and verifying that the Status appropriately re... | Discussion of Priority and Fairness End-to-End Tests for Beta | https://api.github.com/repos/kubernetes/kubernetes/issues/93757/comments | 12 | 2020-08-06T16:09:30Z | 2020-11-18T20:45:38Z | https://github.com/kubernetes/kubernetes/issues/93757 | 674,429,986 | 93,757 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
Add a skeleton admission webhook that performs a simple admission operation and that can be used as a starting point for developers that need to build their own admission webhooks.
**Why is this need... | Add admission webhook example | https://api.github.com/repos/kubernetes/kubernetes/issues/93756/comments | 7 | 2020-08-06T16:08:06Z | 2021-01-08T18:06:34Z | https://github.com/kubernetes/kubernetes/issues/93756 | 674,429,133 | 93,756 |
[
"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**:
master $ kube... | output of kubectl certificate deny command says approved instead of denied | https://api.github.com/repos/kubernetes/kubernetes/issues/93755/comments | 3 | 2020-08-06T16:01:55Z | 2020-08-06T16:05:10Z | https://github.com/kubernetes/kubernetes/issues/93755 | 674,424,944 | 93,755 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Attempting to run hack/local-up-cluster.sh deploys a cluster locally, but the scheduler terminated unexpectedly. This results in pods not getting scheduled to the kubelet.
**What you expected to happen**:
Scheduler doesn't fail and pods are run as expected.
**How to reproduce it (as minimall... | local-up-cluster.sh scheduler terminated unexpectedly | https://api.github.com/repos/kubernetes/kubernetes/issues/93753/comments | 10 | 2020-08-06T14:40:24Z | 2020-09-04T13:00:30Z | https://github.com/kubernetes/kubernetes/issues/93753 | 674,366,805 | 93,753 |
[
"kubernetes",
"kubernetes"
] | I'm running a K8s cluster on rasberry pi(Ubuntu 20.04) . When I try to deploy the following K8s deployment, the labels 'rel' and 'env' weren't created on pods.
K8s Versions:
Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.7", GitCommit:"8fca2ec50a6133511b771a11559e24191b1aa2b4", GitTreeState... | Pod's labels weren't created after K8s Deployment | https://api.github.com/repos/kubernetes/kubernetes/issues/93752/comments | 5 | 2020-08-06T13:10:10Z | 2020-08-06T17:37:34Z | https://github.com/kubernetes/kubernetes/issues/93752 | 674,301,811 | 93,752 |
[
"kubernetes",
"kubernetes"
] | I created a Kubernetes cluster on Ubuntu 20.04 (Master) having worker node (k8s-wn02) on Debian.
The command "kubectl get nodes" shows both the nodes are Ready. Howerver, the command "kubectl describe k8s-wn02" gives the following error, same goes for the describe of master node:
"the server doesn't have a resou... | the server doesn't have a resource type "NodeName" | https://api.github.com/repos/kubernetes/kubernetes/issues/93751/comments | 2 | 2020-08-06T13:06:30Z | 2020-08-07T01:55:05Z | https://github.com/kubernetes/kubernetes/issues/93751 | 674,299,217 | 93,751 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Pods keep spawning indefinitely with OutOfcpu error
**What you expected to happen**:
A single error returned
**How to reproduce it (as minimally and precisely as possible)**:
Add limitrange:
```
apiVersion: v1
kind: LimitRange
metadata:
name: default-limit-range
namespace: "{{ m... | Limitrange request causes indefinite amount of pods spawned | https://api.github.com/repos/kubernetes/kubernetes/issues/93750/comments | 8 | 2020-08-06T12:44:21Z | 2020-08-06T18:19:57Z | https://github.com/kubernetes/kubernetes/issues/93750 | 674,284,755 | 93,750 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about flaky tests or jobs (pass or fail with no underlying change in code) in Kubernetes CI -->
**Which jobs are flaking**:
`gce-ubuntu-master-containerd (ci-kubernetes-e2e-ubuntu-gce-containerd)`
**Which test(s) are flaking**:
`[sig-storage] CSI moc... | [Flaky Test] [sig-storage] CSI mock volume CSI attach test using mock driver should not require VolumeAttach for drivers without attachment | https://api.github.com/repos/kubernetes/kubernetes/issues/93749/comments | 7 | 2020-08-06T12:41:07Z | 2020-08-13T00:00:30Z | https://github.com/kubernetes/kubernetes/issues/93749 | 674,282,786 | 93,749 |
[
"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-Schedule... | Kube-Scheduler metrics misleading error message if not authenticated | https://api.github.com/repos/kubernetes/kubernetes/issues/93748/comments | 3 | 2020-08-06T11:40:04Z | 2020-08-27T11:49:27Z | https://github.com/kubernetes/kubernetes/issues/93748 | 674,247,538 | 93,748 |
[
"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**:
systemctl r... | Node changes to NotReady after restarting kubelet | https://api.github.com/repos/kubernetes/kubernetes/issues/93747/comments | 8 | 2020-08-06T09:51:06Z | 2022-04-22T07:38:12Z | https://github.com/kubernetes/kubernetes/issues/93747 | 674,183,803 | 93,747 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
HTTP healtz check entrypoints (for kube-scheduler pod http://127.0.0.1:10251/healthz and for kube-controller pod http://127.0.0.1:10252/healthz ) disappear in 1.16.13 version. This led to kubernetes 1.16.13 containers deployed by kubespray fails due to liveness check.
**What you expected to hap... | HTTP healtz check entrypoints disappear | https://api.github.com/repos/kubernetes/kubernetes/issues/93746/comments | 4 | 2020-08-06T09:43:24Z | 2020-08-06T12:43:42Z | https://github.com/kubernetes/kubernetes/issues/93746 | 674,179,013 | 93,746 |
[
"kubernetes",
"kubernetes"
] |
When I learned more about the entire kubernetes scheduler frame from the source code.
I noticed that this is the getContainerPort function of nodeport plugins in the PreFilter stage.
This is the original code as following as bellowing.It is seems to me that the naming and use of for loops is not very good ... | scheduler PreFilter NodePorts plugins clean up getContainerPorts Loop naming | https://api.github.com/repos/kubernetes/kubernetes/issues/93744/comments | 5 | 2020-08-06T09:13:44Z | 2020-08-12T02:40:54Z | https://github.com/kubernetes/kubernetes/issues/93744 | 674,160,042 | 93,744 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
Refs #66603
>> I'd like to be able to tweak attachdetach controller timer options, especially ReconcilerMaxWaitForUnmountDuration(which 6 minutes by default).
| Add attachdetach timer config parameters to kube-controller-manager options | https://api.github.com/repos/kubernetes/kubernetes/issues/93742/comments | 5 | 2020-08-06T07:12:27Z | 2021-01-03T09:00:59Z | https://github.com/kubernetes/kubernetes/issues/93742 | 674,078,477 | 93,742 |
[
"kubernetes",
"kubernetes"
] | Hi,
To support dual stack. Add one env in the pod.
- name: POD_IPs
valueFrom: { fieldRef: { fieldPath: status.podIPs } }
created pod on the cluster with kubernetes API server 1.16. met the following error. another cluster with 1.17 work well.
Warning FailedCreate 84s (x19 over 23m) s... | error converting fieldPath: field label not supported: status.podIPs. | https://api.github.com/repos/kubernetes/kubernetes/issues/93741/comments | 4 | 2020-08-06T06:36:07Z | 2020-08-09T22:17:53Z | https://github.com/kubernetes/kubernetes/issues/93741 | 674,057,459 | 93,741 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about flaky tests or jobs (pass or fail with no underlying change in code) in Kubernetes CI -->
**Which jobs are flaking**:
`gci-gce-ingress (ci-kubernetes-e2e-gci-gce-ingress)`
**Which test(s) are flaking**:
`[sig-network] Loadbalancing: L7 GCE [Slow] [... | [Flaky Test][sig-network] Loadbalancing: L7 GCE [Slow] [Feature:Ingress] should conform to Ingress spec | https://api.github.com/repos/kubernetes/kubernetes/issues/93740/comments | 55 | 2020-08-06T03:13:06Z | 2022-01-15T18:32:47Z | https://github.com/kubernetes/kubernetes/issues/93740 | 673,980,826 | 93,740 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
Ability to specify more than one container image (container registry) per container in a pod.
**Why is this needed**:
This has probably come up a few times and there are some solutions that improv... | Add ability to specify multiple container images for one container for redundancy | https://api.github.com/repos/kubernetes/kubernetes/issues/93736/comments | 13 | 2020-08-05T21:36:36Z | 2024-01-04T19:25:17Z | https://github.com/kubernetes/kubernetes/issues/93736 | 673,862,641 | 93,736 |
[
"kubernetes",
"kubernetes"
] | I'm trying to add a monitor for "api cannot talk to etcd" and the only thing I found was monitoring the metrics etcd emits, which does not cover any network interruptions. Are there metrics for this ? ... if not, are they easy to add ? | Api server should report metrics about etcd requests | https://api.github.com/repos/kubernetes/kubernetes/issues/93734/comments | 16 | 2020-08-05T21:22:43Z | 2021-01-05T03:43:02Z | https://github.com/kubernetes/kubernetes/issues/93734 | 673,855,960 | 93,734 |
[
"kubernetes",
"kubernetes"
] | Why do Kubeadm and Kubelet Debian packages depend on Kubernetes-cni Debian Package?
For my use case, I do not need a CNI, as my pods do not communicate with each other. I hope to save as much disk space as possible. Do some essential functions of the Kubelet or Kubeadm depend on Kubernetes-cni even though I don't n... | Kubeadm, Kubelet Debian package dependency on Kubernetes-cni | https://api.github.com/repos/kubernetes/kubernetes/issues/93731/comments | 4 | 2020-08-05T20:21:18Z | 2020-08-06T11:27:54Z | https://github.com/kubernetes/kubernetes/issues/93731 | 673,822,778 | 93,731 |
[
"kubernetes",
"kubernetes"
] | **What happened**: The `BenchmarkPerfScheduling/MixedSchedulingBasePod` performance benchmark does not finish even after 10 minutes of waiting. This is because the nodes do not have a `failure-domain.beta.kubernetes.io/zone` label set but the pod affinity rules in the benchmark's pod spec expects one:
https://github... | scheduler_perf: MixedSchedulingBasePod does not finish | https://api.github.com/repos/kubernetes/kubernetes/issues/93729/comments | 1 | 2020-08-05T19:38:29Z | 2020-08-13T02:14:15Z | https://github.com/kubernetes/kubernetes/issues/93729 | 673,798,307 | 93,729 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
When the CSI migration is enabled, Kubernetes is sending a request to expand the volume to CSI even when the in-tree plugin is not supporting the volume resize.
**What you expected to happen**:
When the migration is enabled, Kubernetes should not send a request to expand the volume to CSI when i... | Volume expansion request should not reach to CSI driver, if in-tree plugin is not capable of expanding volume | https://api.github.com/repos/kubernetes/kubernetes/issues/93727/comments | 11 | 2020-08-05T19:01:45Z | 2020-08-07T15:02:30Z | https://github.com/kubernetes/kubernetes/issues/93727 | 673,776,601 | 93,727 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
*UPDATE*
For newer k8s versions I think this test is fixed, but I think still we should rename and maybe comment what its purpose is a little bit better.
*ORIGINAL POST*
This is still true for some versions of k 1.16, so might wanna back port, but probably low priority.
By default, this te... | The test TCP CLOSE_WAIT test needs to be documented and verified on different environments | https://api.github.com/repos/kubernetes/kubernetes/issues/93724/comments | 6 | 2020-08-05T16:58:48Z | 2020-08-06T19:11:30Z | https://github.com/kubernetes/kubernetes/issues/93724 | 673,703,785 | 93,724 |
[
"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**:
Created a c... | Volumes accept anything as volume type without complaining, and defaults to emptyDir | https://api.github.com/repos/kubernetes/kubernetes/issues/93719/comments | 8 | 2020-08-05T14:39:50Z | 2021-04-23T07:26:22Z | https://github.com/kubernetes/kubernetes/issues/93719 | 673,592,662 | 93,719 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
When setting a non-default component config (especially custom profiles/plugin configurations), the scheduler should at least log what plugins have been enabled at startup.
**Why is this needed**:
Debugging the scheduler almost always requires knowing what plugins are enabled. ... | Scheduler should log processed component config | https://api.github.com/repos/kubernetes/kubernetes/issues/93718/comments | 11 | 2020-08-05T14:18:35Z | 2020-11-13T00:03:01Z | https://github.com/kubernetes/kubernetes/issues/93718 | 673,577,206 | 93,718 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about flaky tests or jobs (pass or fail with no underlying change in code) in Kubernetes CI -->
**Which jobs are flaking**:
`gce-cos-master-scalability-100 (ci-kubernetes-e2e-gci-gce-scalability)`
**Which test(s) are flaking**:
`testing/density/confi... | [Flaky Test] [sig-scalability] there should be no high-latency requests (ci-kubernetes-e2e-gci-gce-scalability) | https://api.github.com/repos/kubernetes/kubernetes/issues/93716/comments | 7 | 2020-08-05T13:55:16Z | 2020-10-28T12:21:45Z | https://github.com/kubernetes/kubernetes/issues/93716 | 673,560,176 | 93,716 |
[
"kubernetes",
"kubernetes"
] | ERROR: type should be string, got "https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/93605/pull-kubernetes-bazel-test/1290329488629960704\r\n```\r\n=== RUN TestUpdateNodeStatusWithLease\r\nI0803 17:08:37.155082 23 plugin_manager.go:114] Starting Kubelet Plugin Manager\r\n==================\r\nWARNING: DATA RACE\r\nRead at 0x00c00066d938 by goroutine 106:\r\n k8s.io/kubernetes/pkg/kubelet/cadvisor.CapacityFromMachineInfo()\r\n pkg/kubelet/cadvisor/util.go:44 +0x1d5\r\n k8s.io/kubernetes/pkg/kubelet/nodestatus.MachineInfo.func1()\r\n pkg/kubelet/nodestatus/setters.go:287 +0x19dc\r\n k8s.io/kubernetes/pkg/kubelet.(*Kubelet).setNodeStatus()\r\n pkg/kubelet/kubelet_node_status.go:559 +0x154\r\n k8s.io/kubernetes/pkg/kubelet.(*Kubelet).initialNode()\r\n pkg/kubelet/kubelet_node_status.go:409 +0xdcf\r\n k8s.io/kubernetes/pkg/kubelet.(*Kubelet).GetNode()\r\n pkg/kubelet/kubelet_getters.go:236 +0x14a\r\n k8s.io/kubernetes/pkg/kubelet/server/stats.(*summaryProviderImpl).Get()\r\n pkg/kubelet/server/stats/summary.go:70 +0x7e\r\n k8s.io/kubernetes/pkg/kubelet/server/stats.(*resourceAnalyzer).Get()\r\n <autogenerated>:1 +0x74\r\n k8s.io/kubernetes/pkg/kubelet/eviction.(*managerImpl).synchronize()\r\n pkg/kubelet/eviction/eviction_manager.go:258 +0x14b\r\n k8s.io/kubernetes/pkg/kubelet/eviction.(*managerImpl).Start.func2()\r\n pkg/kubelet/eviction/eviction_manager.go:203 +0x66\r\n\r\nPrevious write at 0x00c00066d938 by goroutine 104:\r\n [failed to restore the stack]\r\n\r\nGoroutine 106 (running) created at:\r\n k8s.io/kubernetes/pkg/kubelet/eviction.(*managerImpl).Start()\r\n pkg/kubelet/eviction/eviction_manager.go:201 +0x304\r\n k8s.io/kubernetes/pkg/kubelet.(*Kubelet).initializeRuntimeDependentModules()\r\n pkg/kubelet/kubelet.go:1296 +0x656\r\n k8s.io/kubernetes/pkg/kubelet.(*Kubelet).initializeRuntimeDependentModules-fm()\r\n pkg/kubelet/kubelet.go:1274 +0x44\r\n sync.(*Once).doSlow()\r\n GOROOT/src/sync/once.go:66 +0x109\r\n sync.(*Once).Do()\r\n GOROOT/src/sync/once.go:57 +0x68\r\n k8s.io/kubernetes/pkg/kubelet.(*Kubelet).updateRuntimeUp()\r\n pkg/kubelet/kubelet.go:2116 +0x652\r\n k8s.io/kubernetes/pkg/kubelet.TestUpdateNodeStatusWithLease()\r\n pkg/kubelet/kubelet_node_status_test.go:904 +0x2739\r\n testing.tRunner()\r\n GOROOT/src/testing/testing.go:1108 +0x202\r\n\r\nGoroutine 104 (running) created at:\r\n testing.(*T).Run()\r\n GOROOT/src/testing/testing.go:1159 +0x796\r\n testing.runTests.func1()\r\n GOROOT/src/testing/testing.go:1430 +0xa6\r\n testing.tRunner()\r\n GOROOT/src/testing/testing.go:1108 +0x202\r\n testing.runTests()\r\n GOROOT/src/testing/testing.go:1428 +0x5aa\r\n testing.(*M).Run()\r\n GOROOT/src/testing/testing.go:1338 +0x4eb\r\n main.main()\r\n bazel-out/k8-fastbuild/bin/pkg/kubelet/linux_amd64_race_stripped/go_default_test%/testmain.go:266 +0x304\r\n runtime.main()\r\n GOROOT/src/runtime/proc.go:204 +0x208\r\n k8s.io/kubernetes/vendor/github.com/cilium/ebpf.init()\r\n vendor/github.com/cilium/ebpf/prog.go:362 +0x3f8\r\n k8s.io/kubernetes/vendor/github.com/cilium/ebpf.init()\r\n vendor/github.com/cilium/ebpf/syscalls.go:392 +0x38b\r\n k8s.io/kubernetes/vendor/github.com/cilium/ebpf.init()\r\n vendor/github.com/cilium/ebpf/syscalls.go:216 +0x31d\r\n k8s.io/kubernetes/vendor/github.com/cilium/ebpf.init()\r\n vendor/github.com/cilium/ebpf/syscalls.go:188 +0x2b0\r\n runtime.doInit()\r\n GOROOT/src/runtime/proc.go:5590 +0x89\r\n k8s.io/kubernetes/vendor/github.com/cilium/ebpf/internal/btf.init()\r\n vendor/github.com/cilium/ebpf/internal/btf/btf.go:656 +0x18f\r\n==================\r\nE0803 17:08:37.174713 23 eviction_manager.go:260] eviction manager: failed to get summary stats: failed to get root cgroup stats: failed to get cgroup stats for \"/\": unexpected number of containers: 0\r\nI0803 17:08:37.178686 23 kubelet_network.go:77] Setting Pod CIDR: -> 10.0.0.0/24,2000::/10\r\n testing.go:1023: race detected during execution of test\r\n--- FAIL: TestUpdateNodeStatusWithLease (0.04s)\r\n```\r\n\r\nthe test sets `kubelet.machineInfo.MemoryCapacity` in an unprotected way that races with the background eviction manager goroutine, which calls GetCachedMachineInfo, also in an unprotected way\r\n\r\n_Originally posted by @liggitt in https://github.com/kubernetes/kubernetes/pull/93605#issuecomment-668141263_\r\n\r\n/sig node\r\n/kind flake\r\n/cc @dashpole" | data race in TestUpdateNodeStatusWithLease | https://api.github.com/repos/kubernetes/kubernetes/issues/93715/comments | 2 | 2020-08-05T13:32:17Z | 2020-08-06T23:16:20Z | https://github.com/kubernetes/kubernetes/issues/93715 | 673,543,318 | 93,715 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
I have a deployment with 2 pods and LoadBalancer service associated that expose ELB in AWS.
When i do `kubectl delete pod xyz` i see that a pod got removed from list of endpoints however traffic from outside a cluster is still reaching the pod that being deleted (during its gracefull shutdown perio... | AWS ELB forwards traffic to deleted pod | https://api.github.com/repos/kubernetes/kubernetes/issues/93713/comments | 6 | 2020-08-05T09:31:57Z | 2020-11-16T21:43:30Z | https://github.com/kubernetes/kubernetes/issues/93713 | 673,397,470 | 93,713 |
[
"kubernetes",
"kubernetes"
] | OS: Alpine v3.11.6
Kubernetes v1.18.6
Downloaded Kubelet file from: storage.googleapi.com/.../amd64/kubelet
Kubelet service is not working in worker node. Though kube-proxy service is running. I have attached the error file and service file of the kubelet.
Error: start-stop-daemon: failed to exec `/usr/local/bin/... | start-stop-daemon: failed to exec `/usr/local/bin/kubelet': No such file or directory | https://api.github.com/repos/kubernetes/kubernetes/issues/93712/comments | 15 | 2020-08-05T08:43:05Z | 2021-06-24T09:41:35Z | https://github.com/kubernetes/kubernetes/issues/93712 | 673,366,168 | 93,712 |
[
"kubernetes",
"kubernetes"
] | my pod status shows as "PENDING". When I run kubectl describe pod on the pod, I get the following:
NAME READY STATUS RESTARTS AGE
nginx-deployment-6b474476c4-dq26w 0/1 Pending 0 37m
nginx-deployment-6b474476c4-wjblx 0/1 Pending 0 37m
**What h... | node get DiskPressure status true | https://api.github.com/repos/kubernetes/kubernetes/issues/93711/comments | 5 | 2020-08-05T07:19:11Z | 2021-01-02T09:38:00Z | https://github.com/kubernetes/kubernetes/issues/93711 | 673,314,842 | 93,711 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
The HTTPHeader [api](https://github.com/kubernetes/api/blob/4859c947397736b7b452bf4564e7b9b231a5b8f7/core/v1/types.go#L2034) only support plaintext. Maybe we can have something like this
```
// HTTPHea... | Probe API HTTPHeader with ValueFrom | https://api.github.com/repos/kubernetes/kubernetes/issues/93708/comments | 13 | 2020-08-05T04:56:29Z | 2022-01-18T11:08:24Z | https://github.com/kubernetes/kubernetes/issues/93708 | 673,252,999 | 93,708 |
[
"kubernetes",
"kubernetes"
] | Hi Team,
Can you please look into this issue.
PLUGIN STATUS RESULT COUNT
e2e complete failed 1
Our k8s environment uses proxy and is this causing these failures? Please let us know whether e2e runs behind the proxy? or we need any argument to pass while running with proxy.
attached tar file for the latest run wi... | e2e test failed with admission webhook and CustomResourceConversionWebhook | https://api.github.com/repos/kubernetes/kubernetes/issues/93705/comments | 11 | 2020-08-05T03:30:59Z | 2021-07-21T05:28:36Z | https://github.com/kubernetes/kubernetes/issues/93705 | 673,225,516 | 93,705 |
[
"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**:
Running `kube... | Regression for kubeadm reset --force (unmount /var/lib/kubelet/ directory) | https://api.github.com/repos/kubernetes/kubernetes/issues/93700/comments | 1 | 2020-08-05T01:01:22Z | 2020-08-05T01:03:43Z | https://github.com/kubernetes/kubernetes/issues/93700 | 673,176,063 | 93,700 |
[
"kubernetes",
"kubernetes"
] | It looks UserInfo.UID is newer than other fields and while #49677 added it SubjectAccessReviewSpec for webhook authorization, it's still not being sent by client-go in headers. Also there is no flag in APIServer to process those headers. As a result all authorizers needing that, may not work correctly for SubjectAccess... | UserInfo.UID is not passed by client-go | https://api.github.com/repos/kubernetes/kubernetes/issues/93699/comments | 35 | 2020-08-04T23:36:47Z | 2024-09-05T13:53:39Z | https://github.com/kubernetes/kubernetes/issues/93699 | 673,148,510 | 93,699 |
[
"kubernetes",
"kubernetes"
] | **Which jobs are failing**:
* ci-kubernetes-e2e-gce-new-master-gci-kubectl-skew
* ci-kubernetes-e2e-gce-stable1-beta-gci-kubectl-skew
https://storage.googleapis.com/k8s-gubernator/triage/index.html?text=Kubectl&job=skew
**Which test(s) are failing**:
Steadily failing tests making signal from the skew jobs ... | Kubectl skew tests are failing | https://api.github.com/repos/kubernetes/kubernetes/issues/93694/comments | 28 | 2020-08-04T20:54:26Z | 2021-05-24T20:49:43Z | https://github.com/kubernetes/kubernetes/issues/93694 | 673,076,858 | 93,694 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI -->
**Which test(s) are failing**:
* ~~[sig-network] Loadbalancing: L7 GCE [Slow] [Feature:Ingress] should support multiple TLS certs~~
* ~~[sig-network] Loadbalancing: L7 GCE [Slow] [Feature:Ing... | [Failing Test] sig-network-ingress-gce | https://api.github.com/repos/kubernetes/kubernetes/issues/93693/comments | 19 | 2020-08-04T20:54:22Z | 2020-09-24T16:24:44Z | https://github.com/kubernetes/kubernetes/issues/93693 | 673,076,775 | 93,693 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
I patched back https://github.com/kubernetes/kubernetes/pull/89629/commits/6c2562a579b2356c54898d262ec578d5fded1e24 to 1.18.1 and while the code applies cleanly the meaning of the variables doesn't correspond directly.
I used dlv to look at the values of mntInfo.Root and subpath.Path at the point... | fix for https://github.com/kubernetes/kubernetes/issues/68211 not working on 1.18.1 with containerd | https://api.github.com/repos/kubernetes/kubernetes/issues/93691/comments | 16 | 2020-08-04T20:41:13Z | 2021-05-02T22:28:39Z | https://github.com/kubernetes/kubernetes/issues/93691 | 673,068,285 | 93,691 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about flaky tests or jobs (pass or fail with no underlying change in code) in Kubernetes CI -->
**Which jobs are flaking**:
` gce-ubuntu-master-containerd (ci-kubernetes-e2e-ubuntu-gce-containerd)`
**Which test(s) are flaking**:
`[sig-instrumentation... | [Flaky Test] [sig-instrumentation] MetricsGrabber should grab all metrics from a ControllerManager (ci-kubernetes-e2e-ubuntu-gce-containerd) | https://api.github.com/repos/kubernetes/kubernetes/issues/93688/comments | 18 | 2020-08-04T16:28:54Z | 2020-09-16T17:46:21Z | https://github.com/kubernetes/kubernetes/issues/93688 | 672,922,064 | 93,688 |
[
"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 writin... | Atomic Writer creates symlink for configmap files before the files are created | https://api.github.com/repos/kubernetes/kubernetes/issues/93686/comments | 9 | 2020-08-04T14:49:44Z | 2022-09-02T21:27:10Z | https://github.com/kubernetes/kubernetes/issues/93686 | 672,852,760 | 93,686 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about flaky tests or jobs (pass or fail with no underlying change in code) in Kubernetes CI -->
**Which jobs are flaking**:
ci-kubernetes-e2e-gce-scale-performance
**Which test(s) are flaking**:
testing/load/config.yaml
**Testgrid link**:
https://tes... | Performance test in 5k scale failed with because of fatal error: runqsteal: runq overflow error | https://api.github.com/repos/kubernetes/kubernetes/issues/93685/comments | 11 | 2020-08-04T14:16:52Z | 2020-08-10T15:32:17Z | https://github.com/kubernetes/kubernetes/issues/93685 | 672,828,453 | 93,685 |
[
"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-controll... | kube-controller-manager modifies ELB listeners and removes HTTPS protocol from ELB | https://api.github.com/repos/kubernetes/kubernetes/issues/93684/comments | 10 | 2020-08-04T12:33:01Z | 2021-01-02T10:39:03Z | https://github.com/kubernetes/kubernetes/issues/93684 | 672,756,723 | 93,684 |
[
"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 was do the ... | kube-proxy v1.19.0-rc.3 add reject rules in iptables | https://api.github.com/repos/kubernetes/kubernetes/issues/93682/comments | 15 | 2020-08-04T12:12:57Z | 2020-08-05T04:09:09Z | https://github.com/kubernetes/kubernetes/issues/93682 | 672,744,433 | 93,682 |
[
"kubernetes",
"kubernetes"
] | We are currently migrating from Docker Swarm to k8s (bare metal) and we cant reach the SFTP service in the pod.
Service:
> Name: mlflow-artifacts-store
> Namespace: mlflow
> Labels: app.kubernetes.io/instance=mlflow-artifacts-store
> ... | NodePort is not exposed over the kube-ipvs0 interface | https://api.github.com/repos/kubernetes/kubernetes/issues/93674/comments | 15 | 2020-08-04T08:37:02Z | 2020-08-05T13:43:50Z | https://github.com/kubernetes/kubernetes/issues/93674 | 672,613,601 | 93,674 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
I would like to make KubeletPreStartContainerRPCTimeoutInSecs configurable.
**Why is this needed**:
Currently, kubelet calls device plugin's `PreStartContainer ` endpoint with [hardcorded timeout ... | Device Plugin: Add PreStartTimeoutSeconds field in DevicePluginOptions | https://api.github.com/repos/kubernetes/kubernetes/issues/93671/comments | 8 | 2020-08-04T07:35:46Z | 2021-04-02T17:57:17Z | https://github.com/kubernetes/kubernetes/issues/93671 | 672,576,166 | 93,671 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
Process Env then allow Env to replace existing values and Env don't have to guarantee the order
**Why is this needed**:
**For example**：
```
- env:
- name: RABBITMQ_NODENAME
value: rabbi... | Process Env then allow Env to replace existing values and Env don't have to guarantee the order | https://api.github.com/repos/kubernetes/kubernetes/issues/93668/comments | 6 | 2020-08-04T06:28:09Z | 2021-03-18T19:08:23Z | https://github.com/kubernetes/kubernetes/issues/93668 | 672,539,731 | 93,668 |
[
"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 USER 9... | The GID defined by "USER" in Dockerfile does not work in container of Pod | https://api.github.com/repos/kubernetes/kubernetes/issues/93666/comments | 7 | 2020-08-04T02:31:06Z | 2020-08-05T03:04:40Z | https://github.com/kubernetes/kubernetes/issues/93666 | 672,458,909 | 93,666 |
[
"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**:
There are som... | Cleanup wait forever loops in pv_controller_test.go | https://api.github.com/repos/kubernetes/kubernetes/issues/93662/comments | 4 | 2020-08-03T20:05:26Z | 2020-08-28T15:04:18Z | https://github.com/kubernetes/kubernetes/issues/93662 | 672,312,033 | 93,662 |
[
"kubernetes",
"kubernetes"
] | **Which jobs are flaking**:
- ci-kubernetes-integration-master
- pull-kubernetes-integration
**Which test(s) are flaking**:
TestPostBindPlugin
**Testgrid link**:
- https://testgrid.k8s.io/sig-release-master-blocking#integration-master&width=5&include-filter-by-regex=test%2Fintegration%2Fscheduler
- htt... | [Flaky Test] scheduler integration test TestPostBindPlugin | https://api.github.com/repos/kubernetes/kubernetes/issues/93659/comments | 1 | 2020-08-03T18:58:58Z | 2020-08-04T16:58:21Z | https://github.com/kubernetes/kubernetes/issues/93659 | 672,277,719 | 93,659 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
The kubeadm `/var/lib/kubelet` dir does not allow non-root read-access per default:
https://github.com/kubernetes/kubernetes/blob/ec560b9737537be8c688776461bc700e8ddedb9d/cmd/kubeadm/app/phases/kubelet/config.go#L181-L184
To be able to rely on rootless directories inside this path, it would be... | Kubeadm creates /var/lib/kubelet with 0700 permissions | https://api.github.com/repos/kubernetes/kubernetes/issues/93652/comments | 12 | 2020-08-03T14:34:16Z | 2020-08-04T06:19:35Z | https://github.com/kubernetes/kubernetes/issues/93652 | 672,121,213 | 93,652 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about flaky tests or jobs (pass or fail with no underlying change in code) in Kubernetes CI -->
**Which jobs are flaking**:
`integration master (ci-kubernetes-integration-master)`
**Which test(s) are flaking**:
`test-cmd.run_kubectl_apply_tests `
... | [Flaky Test] run_kubectl_apply_tests (ci-kubernetes-integration-master) | https://api.github.com/repos/kubernetes/kubernetes/issues/93651/comments | 9 | 2020-08-03T14:29:23Z | 2020-09-18T02:34:46Z | https://github.com/kubernetes/kubernetes/issues/93651 | 672,117,903 | 93,651 |
[
"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**:
Pod status be... | Pods that exceed the ephemeral storage limit are recreated with no backoff | https://api.github.com/repos/kubernetes/kubernetes/issues/93649/comments | 11 | 2020-08-03T12:18:35Z | 2021-02-15T01:42:10Z | https://github.com/kubernetes/kubernetes/issues/93649 | 672,035,852 | 93,649 |
[
"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 system-re... | The system-reserved parameter has no effect | https://api.github.com/repos/kubernetes/kubernetes/issues/93648/comments | 7 | 2020-08-03T11:57:12Z | 2021-01-08T14:02:38Z | https://github.com/kubernetes/kubernetes/issues/93648 | 672,023,548 | 93,648 |
[
"kubernetes",
"kubernetes"
] |
**What happened**:
Most of the kubernetes pod while deploying gets stuck for 10 mins atleast with error context deadline exceeded and the same happens while terminating as well.
**What you expected to happen**:
Pods should be deployed and terminated without getting stuck
**How to reproduce it (as minimally an... | Pod Getting stuck while starting/terminating with error "context deadline exceeded" | https://api.github.com/repos/kubernetes/kubernetes/issues/93647/comments | 4 | 2020-08-03T11:32:39Z | 2020-08-03T17:15:14Z | https://github.com/kubernetes/kubernetes/issues/93647 | 672,010,253 | 93,647 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
kubernets etcd version are different from each other (1 out of 3) after upgrade from v1.17.6 to v1.18.3
**What you expected to happen**:
kubernetes to hold the versions in sync, that they continue to work together.
**How to reproduce it (as minimally and precisely as possible)**:
Unknown -- ... | After k8s upgrade, ETCD landed in different versions | https://api.github.com/repos/kubernetes/kubernetes/issues/93644/comments | 9 | 2020-08-03T08:54:15Z | 2020-08-03T10:38:50Z | https://github.com/kubernetes/kubernetes/issues/93644 | 671,914,513 | 93,644 |
[
"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 use cl... | Panic in event handler will be blocked by defer func but it should propagate up | https://api.github.com/repos/kubernetes/kubernetes/issues/93641/comments | 4 | 2020-08-03T08:27:58Z | 2020-09-02T01:43:14Z | https://github.com/kubernetes/kubernetes/issues/93641 | 671,898,928 | 93,641 |
[
"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**:
start the sch... | cannot redirect log by the option: --log-dir or --log-file | https://api.github.com/repos/kubernetes/kubernetes/issues/93639/comments | 2 | 2020-08-03T06:42:04Z | 2020-08-03T07:02:39Z | https://github.com/kubernetes/kubernetes/issues/93639 | 671,835,927 | 93,639 |
[
"kubernetes",
"kubernetes"
] | ```
Preface: IMO, we should not fix root OWNERS approvers by adding more people to it. We should fix it by distributing the
responsibility (per area) to SIG TLs, and sub-project TLs. I actually think we should consider removing folks from root OWNERS approvers.
```
Follow up from: https://github.com/kubernetes/k... | Fix root OWNERS approvers | https://api.github.com/repos/kubernetes/kubernetes/issues/93637/comments | 25 | 2020-08-02T23:22:37Z | 2021-10-29T14:52:31Z | https://github.com/kubernetes/kubernetes/issues/93637 | 671,710,390 | 93,637 |
[
"kubernetes",
"kubernetes"
] | Hi all,
I'm new to kubernetes world. Recently I have installed k8's 1.18 in my cluster.
But when i am checking for the kubectl version i could see two different parameters "server version" & "client version".
Can anyone explain me what is this exactly.
Will this version mismatch cause issue in cluster ?
upda... | server version and client version in Kubernetes (kubectl version) | https://api.github.com/repos/kubernetes/kubernetes/issues/93635/comments | 4 | 2020-08-02T13:59:56Z | 2020-08-02T17:27:24Z | https://github.com/kubernetes/kubernetes/issues/93635 | 671,621,518 | 93,635 |
[
"kubernetes",
"kubernetes"
] | It's not obvious to me whether it's good practice to use interfaces defined in `k8s.io/apiserver/pkg/registry/rest` for subresource implementation or not, but it somewhat works. For example there is `NamedCreater` that helps creating subresource and it is documented so. I Also used `Lister` and `Watcher` in my REST imp... | Using standard kubernetes verbs for subresources | https://api.github.com/repos/kubernetes/kubernetes/issues/93634/comments | 12 | 2020-08-02T06:32:00Z | 2021-01-02T01:30:00Z | https://github.com/kubernetes/kubernetes/issues/93634 | 671,562,620 | 93,634 |
[
"kubernetes",
"kubernetes"
] | Hello everyone, I want to deploy just one pod on a node, I set the NodeAffinity and PodAntiAffinity for the deployment.
However after the deployment finishes, there are two pods on the node, one is failed, and another one is running.
This is my yaml file as below,
apiVersion: apps/v1
kind: Deployment
metadata:... | fail to deploy pod when setting NodeAffinity in yaml | https://api.github.com/repos/kubernetes/kubernetes/issues/93624/comments | 7 | 2020-08-01T07:00:06Z | 2020-08-14T08:26:25Z | https://github.com/kubernetes/kubernetes/issues/93624 | 670,598,751 | 93,624 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI -->
**Which jobs are failing**:
pull-kubernetes-verify
**Which test(s) are failing**:
publishing-bot
**Since when has it been failing**:
07-31 12:23 PDT
**Testgrid link**:
https://testgrid... | Failing Test: pull-kubernetes-verify - publishing-bot | https://api.github.com/repos/kubernetes/kubernetes/issues/93623/comments | 3 | 2020-08-01T05:18:24Z | 2020-08-01T21:20:39Z | https://github.com/kubernetes/kubernetes/issues/93623 | 670,538,115 | 93,623 |
[
"kubernetes",
"kubernetes"
] | We still don't have any CI jobs for this architecture, so we should just remove support for it.
It's been close to 2 years since we opened this issue - https://github.com/kubernetes/kubernetes/issues/67721
| Remove support for s390x | https://api.github.com/repos/kubernetes/kubernetes/issues/93621/comments | 20 | 2020-08-01T02:47:36Z | 2021-02-01T16:14:25Z | https://github.com/kubernetes/kubernetes/issues/93621 | 670,452,806 | 93,621 |
[
"kubernetes",
"kubernetes"
] | Need to follow up on:
- https://github.com/kubernetes/kubernetes/issues/87056#issuecomment-666493661
/sig architecture
/assign | Document requirements for adding new architectures | https://api.github.com/repos/kubernetes/kubernetes/issues/93620/comments | 11 | 2020-08-01T02:40:44Z | 2022-01-31T21:16:52Z | https://github.com/kubernetes/kubernetes/issues/93620 | 670,448,981 | 93,620 |
[
"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**: Kubelet would ... | Following instructions to install production environment | https://api.github.com/repos/kubernetes/kubernetes/issues/93616/comments | 2 | 2020-07-31T20:39:35Z | 2020-08-03T10:26:28Z | https://github.com/kubernetes/kubernetes/issues/93616 | 670,211,030 | 93,616 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
I created a restrictive PodSecurityPolicy, restricted, that is available to all service accounts and authorized users. I created a permissive PodSecurityPolicy, privileged, that is only authorized for use by service accounts in specific namespaces. It is not available in the psp-example namespace... | PodSecurityPolicy admission plugin selects and uses policy that service account is not authorized to use. | https://api.github.com/repos/kubernetes/kubernetes/issues/93615/comments | 5 | 2020-07-31T20:19:06Z | 2020-08-01T03:01:34Z | https://github.com/kubernetes/kubernetes/issues/93615 | 670,187,404 | 93,615 |
[
"kubernetes",
"kubernetes"
] | **Which jobs are flaking**:
pull-kubernetes-integration
**Which test(s) are flaking**:
test/integration/master
**Testgrid link**:
**Reason for failure**:
There are ~5 tests that average more than 30 seconds each.
https://testgrid.k8s.io/presubmits-kubernetes-blocking#pull-kubernetes-integration&gra... | test/integration/master package tests are slow, package times out | https://api.github.com/repos/kubernetes/kubernetes/issues/93609/comments | 35 | 2020-07-31T18:00:32Z | 2024-12-29T16:41:02Z | https://github.com/kubernetes/kubernetes/issues/93609 | 670,069,808 | 93,609 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
The kubemark hollow-kubelet should expose setting --register-with-taints through args for the test.
**Why is this needed**:
1. It would be beneficial to have the nodes come up with taints to avoid sch... | Support for --register-with-taints in kubemark hollow-kubelet args | https://api.github.com/repos/kubernetes/kubernetes/issues/93608/comments | 9 | 2020-07-31T17:02:25Z | 2020-09-07T08:33:42Z | https://github.com/kubernetes/kubernetes/issues/93608 | 670,018,743 | 93,608 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
On a call to ListNodes, the returning JSON had 'null' instead of an empty list in `ContainerImage.names`. Failing validation in the client.
```json
$ cat ~/error.json | jq '.items[39].status.images[11]'
{
"names": null,
"sizeBytes": 226150943
}
```
**What you expected to happen**:
... | ListNodes sometimes returns 'null' instead of empty list for .items[].status.images[].names (v1.10) | https://api.github.com/repos/kubernetes/kubernetes/issues/93606/comments | 8 | 2020-07-31T15:20:07Z | 2020-12-28T20:51:13Z | https://github.com/kubernetes/kubernetes/issues/93606 | 669,925,576 | 93,606 |
Subsets and Splits
Unique Owner-Repo Count
Counts the number of unique owner-repos in the dataset, providing a basic understanding of diverse repositories.