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"
] | During an upgrade process, the upgrade failed about halfway through and my cluster is in a broken state. I am not able to use any kubectl commands, as I receive "Unable to connect to the server: EOF" and the logs for kubelet are shown as in the question. I am not sure how to go about fixing this. For reference, this ha... | Kubelet logs "node '<master-node>' not found" | https://api.github.com/repos/kubernetes/kubernetes/issues/93352/comments | 2 | 2020-07-22T19:27:42Z | 2020-07-22T19:42:39Z | https://github.com/kubernetes/kubernetes/issues/93352 | 663,996,995 | 93,352 |
[
"kubernetes",
"kubernetes"
] | I have never seen any sort of compatibility matrix for components of open source kubernetes clusters. Does anything like this exist? Components like etcd, networking, storage, coreDNS, and docker/kubernetes themselves would be extremely handy when troubleshooting errors. | Kubernetes, Docker, Calico Compatibility Matrix? | https://api.github.com/repos/kubernetes/kubernetes/issues/93351/comments | 3 | 2020-07-22T19:23:33Z | 2020-07-22T20:51:13Z | https://github.com/kubernetes/kubernetes/issues/93351 | 663,994,768 | 93,351 |
[
"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-aks-engine-azure-master-staging-windows
**Which test(s) are flaking**:
There is a race condition in the one of t... | [Flaky test] [sig-windows] ci-kubernetes-e2e-aks-engine-azure-master-staging-windows | https://api.github.com/repos/kubernetes/kubernetes/issues/93349/comments | 5 | 2020-07-22T17:55:44Z | 2020-08-27T02:41:03Z | https://github.com/kubernetes/kubernetes/issues/93349 | 663,945,059 | 93,349 |
[
"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**:
Seemingly i... | etcd index out of range during startup | https://api.github.com/repos/kubernetes/kubernetes/issues/93348/comments | 9 | 2020-07-22T17:32:32Z | 2020-12-20T19:41:10Z | https://github.com/kubernetes/kubernetes/issues/93348 | 663,931,493 | 93,348 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
There are a number of places where sig-storage e2e tests make use of shared utilities to perform common operations such as creating or deleting Pods. These helpers are spread throughout files in `test/e... | Clean up sig-storage e2e test utils | https://api.github.com/repos/kubernetes/kubernetes/issues/93347/comments | 12 | 2020-07-22T17:30:35Z | 2021-09-01T17:43:34Z | https://github.com/kubernetes/kubernetes/issues/93347 | 663,930,312 | 93,347 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
Continuing conversation from Issue: https://github.com/kubernetes/kubectl/issues/825
`KUBECONFIG=~/.kube/config`
This is a great feature. However, it's really annoying for CI/CD pipelines where yo... | Support KUBECONFIG_BASE64 env | https://api.github.com/repos/kubernetes/kubernetes/issues/93346/comments | 20 | 2020-07-22T16:50:42Z | 2021-04-21T03:54:24Z | https://github.com/kubernetes/kubernetes/issues/93346 | 663,906,664 | 93,346 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
We recently upgraded to 1.17.9 using kubeadm and now the controller manager and scheduler are serving on their default secure port and the old insecure port is 0 which disabled it. Now when you run `kubectl get componentstatuses` it shows that these two components are unhealthy even though they ar... | componentstatuses doesn't work when Scheduler and Controller Manager are running on secure port | https://api.github.com/repos/kubernetes/kubernetes/issues/93342/comments | 8 | 2020-07-22T16:15:45Z | 2021-04-25T20:53:36Z | https://github.com/kubernetes/kubernetes/issues/93342 | 663,884,303 | 93,342 |
[
"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-master-scale-correctness
**Which test(s) are flaking**:
[sig-network] ESIPP [Slow] should work for type=LoadBalancer
**Testgrid... | [Flaky test] [sig-network] ESIPP [Slow] should work for type=LoadBalancer | https://api.github.com/repos/kubernetes/kubernetes/issues/93341/comments | 5 | 2020-07-22T16:07:00Z | 2020-07-27T14:30:18Z | https://github.com/kubernetes/kubernetes/issues/93341 | 663,878,449 | 93,341 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
When pods failed to schedule due to insufficient CPU, Kubernetes metrics don't show them as unschedulable. They are under pending section, but not in the unschedulable queue:
```
# HELP scheduler_pending_pods [ALPHA] Number of pending pods, by the queue type. 'active' means number of pods in act... | Incorrect metrics on unschedulable pod | https://api.github.com/repos/kubernetes/kubernetes/issues/93339/comments | 6 | 2020-07-22T15:53:49Z | 2020-07-24T16:48:44Z | https://github.com/kubernetes/kubernetes/issues/93339 | 663,869,343 | 93,339 |
[
"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**:
Whenever a ... | Kubelet rejects pod scheduled based on newly added node labels which have not been observed by the kubelet yet | https://api.github.com/repos/kubernetes/kubernetes/issues/93338/comments | 32 | 2020-07-22T15:52:36Z | 2021-02-25T14:13:30Z | https://github.com/kubernetes/kubernetes/issues/93338 | 663,868,508 | 93,338 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
When a pod communicates with the service, traffic comes and goes to the IP of the service, but sometimes traffic arrives with the IP of underlying pod, which causes connection to be reset.
**What you expected to happen**:
All traffic with the service should be coming from the service's IP.
**... | Packets from service sometimes arrive with the IP of pod, not service | https://api.github.com/repos/kubernetes/kubernetes/issues/93337/comments | 24 | 2020-07-22T15:49:04Z | 2021-01-23T00:40:00Z | https://github.com/kubernetes/kubernetes/issues/93337 | 663,865,923 | 93,337 |
[
"kubernetes",
"kubernetes"
] | Hello everyone,
I'm working on k8s cluster version of 1.16 and found some interesting things about HostPath.
Pods can able to access the home directory of the nodes which one pods located on.
This capability allows to change configs like ssh (`allowed_keys`) and etc.
That is the pod.yaml example
```
apiVer... | Kubernetes Hostpath allows to HomeDirectory of Worker Node | https://api.github.com/repos/kubernetes/kubernetes/issues/93335/comments | 4 | 2020-07-22T14:56:29Z | 2020-07-22T21:53:27Z | https://github.com/kubernetes/kubernetes/issues/93335 | 663,827,623 | 93,335 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI -->
**Which jobs are failing**:
`conformance-ga-only (ci-kubernetes-conformance-kind-ga-only)`
**Which test(s) are failing**:
`Overall`
**Since when has it been failing**:
`2020-07-21 20... | [Flaky Test] some tests affected by pod scheduling timeouts | https://api.github.com/repos/kubernetes/kubernetes/issues/93334/comments | 15 | 2020-07-22T14:33:29Z | 2020-07-23T04:19:31Z | https://github.com/kubernetes/kubernetes/issues/93334 | 663,810,177 | 93,334 |
[
"kubernetes",
"kubernetes"
] | **Firstly, this is an issue found on k3s, not k8s.
I have a config yaml file like this:**
```
apiVersion: v1
data:
Corefile: |
.:53 {
errors
health
kubernetes cluster.local in-addr.arpa ip6.arpa {
pods insecure
upstream
fallthrough in-addr.arpa i... | Fail to get self-defined configmap configuration after system reboots | https://api.github.com/repos/kubernetes/kubernetes/issues/93326/comments | 11 | 2020-07-22T10:03:36Z | 2020-07-23T02:39:43Z | https://github.com/kubernetes/kubernetes/issues/93326 | 663,636,428 | 93,326 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
We use Helm to deploy our application.
Before the main app deploy, we have a preparation job with initContainers, which waits for the environment correct setup.
That's is the app-prepare config
```
apiVersion: batch/v1
kind: Job
metadata:
[REDUCTED]
spec:
activeDeadlineSeconds: 1800
... | Deploy failed due default-token can't be reached | https://api.github.com/repos/kubernetes/kubernetes/issues/93325/comments | 11 | 2020-07-22T10:00:17Z | 2021-04-20T06:56:57Z | https://github.com/kubernetes/kubernetes/issues/93325 | 663,634,215 | 93,325 |
[
"kubernetes",
"kubernetes"
] | Versions of golang.org/x/text before 0.3.3 hurts from https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14040
This seems to be fixed on master and 1.19 branch.
Would it be possible to upgrade 1.17 and 1.18 branches too?
The 0.17.x releases seems to still be getting upgrades (0.17.9 had one 7 days ago).
... | CVE in golang.org/x/text dependency | https://api.github.com/repos/kubernetes/kubernetes/issues/93324/comments | 8 | 2020-07-22T09:46:16Z | 2020-07-29T08:46:04Z | https://github.com/kubernetes/kubernetes/issues/93324 | 663,629,715 | 93,324 |
[
"kubernetes",
"kubernetes"
] | **Which jobs are flaking**:
ci-kubernetes-node-kubelet-serial-hugepages
**Which test(s) are flaking**:
all
**Testgrid link**:
https://k8s-testgrid.appspot.com/sig-node-kubelet#kubelet-serial-gce-e2e-hugepages
**Reason for failure**:
```
I0721 23:42:19.157] goroutine 234 [running]:
I0721 23:42:19.... | ci-kubernetes-node-kubelet-serial-hugepages panics when restarting kubelet | https://api.github.com/repos/kubernetes/kubernetes/issues/93323/comments | 8 | 2020-07-22T09:14:01Z | 2020-08-27T03:51:19Z | https://github.com/kubernetes/kubernetes/issues/93323 | 663,605,083 | 93,323 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI -->
**Which jobs are failing**:
> gce-cos-master-alpha-features (ci-kubernetes-e2e-gci-gce-alpha-features )
**Which test(s) are failing**:
> - Overall
> - Test
> - [sig-storage] CSI Volumes [D... | [Failing Test] gce-cos-master-alpha-features (ci-kubernetes-e2e-gci-gce-alpha-features ) | https://api.github.com/repos/kubernetes/kubernetes/issues/93321/comments | 1 | 2020-07-22T07:43:29Z | 2020-07-23T15:59:41Z | https://github.com/kubernetes/kubernetes/issues/93321 | 663,548,970 | 93,321 |
[
"kubernetes",
"kubernetes"
] | **What happened**: Kubernetes is using GRPC for a lot of stuff (CSI, ...) to allow for extensibility, however, the grpc-go driver contained a bug which basically means that writing GRPC servers for kubernetes was not allowed due to a broken implementation in the go client (https://github.com/grpc/grpc-go/issues/2628). ... | google.golang.org/grpc cannot be upgraded >= v1.30.0 | https://api.github.com/repos/kubernetes/kubernetes/issues/93320/comments | 23 | 2020-07-22T06:49:51Z | 2022-03-09T02:46:18Z | https://github.com/kubernetes/kubernetes/issues/93320 | 663,520,417 | 93,320 |
[
"kubernetes",
"kubernetes"
] | I am trouble shooting with port-proxy error. following error says pod bbb007990753841253c0e13c66675ec527a45565d6b610ea6e01d0c6b3669660
But I cannot found it with `kubectl get pods -A -o wide`
How should I use the command?
```bash
E0722 02:20:51.372460 27715 portforward.go:400] an error occurred forwarding 80... | How to search specific pod? | https://api.github.com/repos/kubernetes/kubernetes/issues/93315/comments | 4 | 2020-07-22T02:32:19Z | 2020-10-20T23:24:27Z | https://github.com/kubernetes/kubernetes/issues/93315 | 663,426,896 | 93,315 |
[
"kubernetes",
"kubernetes"
] | The following comments are incomplete.
https://github.com/kubernetes/kubernetes/blob/98814409bab818d942e3c341d76eb594f12675a5/staging/src/k8s.io/api/core/v1/types.go#L5493-L5504
For example, comments for "ResourceQuotaScopeTerminating" should be:
```
// Match all pod objects where `spec.activeDeadlineSeconds ... | Comments on ResourceQuota are incomplete | https://api.github.com/repos/kubernetes/kubernetes/issues/93312/comments | 13 | 2020-07-22T00:51:09Z | 2020-12-09T00:28:36Z | https://github.com/kubernetes/kubernetes/issues/93312 | 663,395,489 | 93,312 |
[
"kubernetes",
"kubernetes"
] | **Which jobs are failing**:
`capg-conformance-v1alpha3-k8s-master (ci-cluster-api-provider-gcp-make-conformance-v1alpha3-k8s-ci-artifacts)`
**Which test(s) are failing**:
`[sig-instrumentation] Events API should delete a collection of events [Conformance] `
`[sig-instrumentation] Events API should ensure that an ... | capg-conformance-v1alpha3-k8s-master (ci-cluster-api-provider-gcp-make-conformance-v1alpha3-k8s-ci-artifacts) | https://api.github.com/repos/kubernetes/kubernetes/issues/93309/comments | 7 | 2020-07-21T22:13:30Z | 2020-07-29T16:09:49Z | https://github.com/kubernetes/kubernetes/issues/93309 | 663,342,098 | 93,309 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
I tried to enabled DSR loadbalancers on kube-proxy Windows but there was an error shown
"Platform does not support feature Direct Server Return (DSR)"
**What you expected to happen**:
I expected kube-proxy to run in DSR mode on a supported Windows build.
**How to reproduce it (as minimally a... | Windows HNS version check for DSR feature is failing on RS5, even though it is supported | https://api.github.com/repos/kubernetes/kubernetes/issues/93304/comments | 3 | 2020-07-21T17:33:44Z | 2020-07-22T05:32:07Z | https://github.com/kubernetes/kubernetes/issues/93304 | 663,188,492 | 93,304 |
[
"kubernetes",
"kubernetes"
] | **Which jobs are failing**:
ci-kubernetes-node-kubelet-conformance
**Which test(s) are failing**:
- Variable Expansion should succeed in writing subpaths in container
- Variable Expansion should verify that a failing subpath expansion can be modified during the lifecycle of a container
**Since when has it ... | node-kubelet-conformance fails with "pod ... was not deleted" | https://api.github.com/repos/kubernetes/kubernetes/issues/93302/comments | 17 | 2020-07-21T16:38:43Z | 2020-07-22T02:52:44Z | https://github.com/kubernetes/kubernetes/issues/93302 | 663,155,837 | 93,302 |
[
"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 Resourc... | ResourceQuota tests flaky on 1.16 in kubeadm clusters | https://api.github.com/repos/kubernetes/kubernetes/issues/93301/comments | 5 | 2020-07-21T16:19:56Z | 2020-07-22T13:32:20Z | https://github.com/kubernetes/kubernetes/issues/93301 | 663,143,450 | 93,301 |
[
"kubernetes",
"kubernetes"
] | I noticed ResourceConfigForPod isn't checking `initContainers` here:
https://github.com/kubernetes/kubernetes/blob/b6174e605fd6e23b48131dec9e45043b38372c3c/pkg/kubelet/cm/helpers_linux.go#L144-L150
The methods called by `ResourceConfigForPod` (`PodRequestsAndLimits` and `GetPodQOS`) **do** check `initContainers`,... | ResourceConfigForPod doesn't consider initContainers when computing cpuLimitsDeclared / memoryLimitsDeclared | https://api.github.com/repos/kubernetes/kubernetes/issues/93300/comments | 2 | 2020-07-21T16:13:50Z | 2021-08-17T18:41:38Z | https://github.com/kubernetes/kubernetes/issues/93300 | 663,139,117 | 93,300 |
[
"kubernetes",
"kubernetes"
] | There were two patches merged recently in the kernel that will significantly improve the IPVS proxier:
1. http://patchwork.ozlabs.org/project/netfilter-devel/patch/20200701151719.4751-1-ja@ssi.bg/
2. http://patchwork.ozlabs.org/project/netfilter-devel/patch/20200708161638.13584-1-kim.andrewsy@gmail.com/
The first ... | [ipvs] set conn_reuse_mode=1 on linux kernel version >= v5.9 | https://api.github.com/repos/kubernetes/kubernetes/issues/93297/comments | 11 | 2020-07-21T15:05:45Z | 2021-07-08T21:01:20Z | https://github.com/kubernetes/kubernetes/issues/93297 | 663,089,504 | 93,297 |
[
"kubernetes",
"kubernetes"
] | **Which jobs are flaking**:
pull-kubernetes-e2e-azure-disk-windows
**Which test(s) are flaking**:
* Dynamic Provisioning [single-az] should create a deployment object, write and read to it, delete the pod and write and read to it again [kubernetes.io/azure-disk] [disk.csi.azure.com] [Windows]
**Testgrid lin... | Dynamic Provisioning [single-az] should create a deployment object, write and read to it, delete the pod and write and read to it again [kubernetes.io/azure-disk] [disk.csi.azure.com] [Windows] | https://api.github.com/repos/kubernetes/kubernetes/issues/93295/comments | 14 | 2020-07-21T14:43:03Z | 2020-08-24T15:15:40Z | https://github.com/kubernetes/kubernetes/issues/93295 | 663,071,893 | 93,295 |
[
"kubernetes",
"kubernetes"
] | @liggitt
how to do this?
An admin that wants to remove access to exec or attach should remove all access to pods/exec and pods/attach.
I tried this:
- apiGroups: [""]
resources: ["pods/exec", "pods/attach"]
verbs: [""]
But seems like this is not the right way to do it. Could you please suggest how can... | how to disable exec into a pod | https://api.github.com/repos/kubernetes/kubernetes/issues/93292/comments | 7 | 2020-07-21T13:25:13Z | 2020-07-27T15:49:46Z | https://github.com/kubernetes/kubernetes/issues/93292 | 663,012,686 | 93,292 |
[
"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 a node... | "instance not found" error is reported for recreated Azure nodes | https://api.github.com/repos/kubernetes/kubernetes/issues/93287/comments | 4 | 2020-07-21T11:26:59Z | 2020-07-22T23:53:41Z | https://github.com/kubernetes/kubernetes/issues/93287 | 662,906,572 | 93,287 |
[
"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 using th... | Init containers require CPU limit in order for container to be in guaranteed QoS | https://api.github.com/repos/kubernetes/kubernetes/issues/93282/comments | 12 | 2020-07-21T08:42:36Z | 2022-09-14T17:03:54Z | https://github.com/kubernetes/kubernetes/issues/93282 | 662,755,193 | 93,282 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI -->
**Which jobs are failing**:
n/a
**Which test(s) are failing**:
"should resolve connection reset issue #74839 [Slow]"
**Since when has it been failing**:
it never worked
**Testgrid... | The test "should resolve connection reset issue #74839 [Slow]" does not support IPv6 | https://api.github.com/repos/kubernetes/kubernetes/issues/93281/comments | 16 | 2020-07-21T08:40:31Z | 2021-01-20T10:18:00Z | https://github.com/kubernetes/kubernetes/issues/93281 | 662,753,556 | 93,281 |
[
"kubernetes",
"kubernetes"
] | On one of our large clusters (k8s 1.16) under a steady load of write calls, there was a brief period of ~1 min when all write requests were being heavily stalled. Meaning, the write call latencies spiked to upwards of 5s and many of those API calls got back HTTP 500 failures due to kube-apiserver seeing “timed out” or ... | Defrag on etcd node causing API 500s | https://api.github.com/repos/kubernetes/kubernetes/issues/93280/comments | 31 | 2020-07-21T06:57:49Z | 2025-02-21T21:39:18Z | https://github.com/kubernetes/kubernetes/issues/93280 | 662,667,850 | 93,280 |
[
"kubernetes",
"kubernetes"
] | k8s 版本1.14
kubelet 状态正常无报错
检查heapsterlogs发现如下报错:
E0721 06:15:20.050642 1 manager.go:101] Error in scraping containers from kubelet:x.x.x.x:10250: failed to get all container stats from Kubelet URL "https://10.100.3.66:10250/stats/container/": Post https://x.x.x.x:10250/stats/container/: dial tcp x.x.x.x:10250:... | heapster安装成功,kubectl top node 一个节点正常一个节点 unknown | https://api.github.com/repos/kubernetes/kubernetes/issues/93279/comments | 2 | 2020-07-21T06:45:50Z | 2020-07-21T07:10:23Z | https://github.com/kubernetes/kubernetes/issues/93279 | 662,658,468 | 93,279 |
[
"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 looking... | sig-release 1.19 informing tests for windows are testing against 1.18 | https://api.github.com/repos/kubernetes/kubernetes/issues/93278/comments | 0 | 2020-07-21T03:41:57Z | 2020-07-21T22:18:07Z | https://github.com/kubernetes/kubernetes/issues/93278 | 662,539,713 | 93,278 |
[
"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**:
Node Events... | [Azure] Node Event doesn't contain the detailed errors when controller manager failed to create routes | https://api.github.com/repos/kubernetes/kubernetes/issues/93277/comments | 6 | 2020-07-21T03:14:59Z | 2020-10-16T15:17:04Z | https://github.com/kubernetes/kubernetes/issues/93277 | 662,521,973 | 93,277 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
Presubmit tests for windows in 1.20 and to see windows tests in release blocking [dashboard like 1.19](https://k8s-testgrid.appspot.com/sig-release-1.19-blocking) for 1.20
**Why is this needed**:
The... | Presubmit tests for Windows and release blocking tests | https://api.github.com/repos/kubernetes/kubernetes/issues/93276/comments | 30 | 2020-07-21T03:02:06Z | 2022-06-02T16:52:03Z | https://github.com/kubernetes/kubernetes/issues/93276 | 662,513,519 | 93,276 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
The current scheduler parameters are set in a scheduler configuration file as global settings. As the scheduling framework and multiple scheduling profiles are introduced, it will be useful to support s... | scheduler: support scheduling profile-level configuration parameters | https://api.github.com/repos/kubernetes/kubernetes/issues/93270/comments | 40 | 2020-07-20T23:44:57Z | 2022-12-16T18:54:39Z | https://github.com/kubernetes/kubernetes/issues/93270 | 662,383,961 | 93,270 |
[
"kubernetes",
"kubernetes"
] | This issue is primarily to track the inclusion of the fix for https://github.com/golang/go/issues/40213 into Kubernetes.
**What happened**:
After uncleanly rebooting the node running kube-apiserver, a node went into the "NotReady" state and stayed that way even after all nodes were running again. Once in this mo... | network glitch can lead to node stuck in "NotReady" state | https://api.github.com/repos/kubernetes/kubernetes/issues/93268/comments | 8 | 2020-07-20T21:56:58Z | 2020-12-21T00:46:11Z | https://github.com/kubernetes/kubernetes/issues/93268 | 662,305,259 | 93,268 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
"ingress" subcommand to "kubectl create"
**Why is this needed**:
This feature has originally been requested over 3 years ago with the March 2017 issue https://github.com/kubernetes/kubernetes/issues/4... | kubectl create ingress | https://api.github.com/repos/kubernetes/kubernetes/issues/93267/comments | 21 | 2020-07-20T21:47:02Z | 2020-10-15T15:06:25Z | https://github.com/kubernetes/kubernetes/issues/93267 | 662,297,518 | 93,267 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
After working around an issue (#93265) that required us to rename a set of envs for the purposes of obtaining values from either an internal or external set of database secrets during, we ran into yet another problem with updating them where the original env names get deleted even though they are pr... | Deployment objects using optional envs with the same name are unexpectedly removed during updates - but exist out of the box | https://api.github.com/repos/kubernetes/kubernetes/issues/93266/comments | 3 | 2020-07-20T21:22:31Z | 2020-07-20T21:38:41Z | https://github.com/kubernetes/kubernetes/issues/93266 | 662,277,505 | 93,266 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
We have added a new set of container envs for a Deployment object to grab database user/pass from a Secret. Since the name of the secret can differ if the database is internal or external and they are mutually exclusive since it is not valid to have both the internal and external secrets in same nam... | $setElementOrder error encountered updating Deployment removing and reordering multiple env vars with same name | https://api.github.com/repos/kubernetes/kubernetes/issues/93265/comments | 7 | 2020-07-20T20:49:17Z | 2020-12-19T22:20:11Z | https://github.com/kubernetes/kubernetes/issues/93265 | 662,249,285 | 93,265 |
[
"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 pr https:... | Kueblet fails to start due to device plugin manager on windows | https://api.github.com/repos/kubernetes/kubernetes/issues/93262/comments | 6 | 2020-07-20T20:04:46Z | 2020-07-21T09:31:47Z | https://github.com/kubernetes/kubernetes/issues/93262 | 662,210,759 | 93,262 |
[
"kubernetes",
"kubernetes"
] | ```
=== RUN TestWebhookAdmissionWithoutWatchCache/node.k8s.io.v1alpha1.runtimeclasses/deletecollection
=== RUN TestWebhookAdmissionWithoutWatchCache/node.k8s.io.v1alpha1.runtimeclasses/deletecollection
E0720 14:42:14.176652 108028 runtime.go:78] Observed a panic: "invalid memory address or nil pointer dereferen... | Nested trace panic observed | https://api.github.com/repos/kubernetes/kubernetes/issues/93257/comments | 7 | 2020-07-20T15:47:56Z | 2020-07-21T02:51:48Z | https://github.com/kubernetes/kubernetes/issues/93257 | 661,973,875 | 93,257 |
[
"kubernetes",
"kubernetes"
] | Changing the type of an existing metric should be considered harmful unless absolutely necessary. Preferably, a new metric would be defined instead of changing the type of the existing metric.
/sig scheduling
/cc @ahg-g | scheduler/metrics.go: add comment warning against changing metric types | https://api.github.com/repos/kubernetes/kubernetes/issues/93255/comments | 3 | 2020-07-20T15:28:46Z | 2020-07-20T15:36:47Z | https://github.com/kubernetes/kubernetes/issues/93255 | 661,954,297 | 93,255 |
[
"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**:
k8s version: ... | when kubelet device manager get preferred allocation, lock and unlock operations maybe are in reverse order | https://api.github.com/repos/kubernetes/kubernetes/issues/93238/comments | 4 | 2020-07-20T01:44:03Z | 2020-07-21T00:57:42Z | https://github.com/kubernetes/kubernetes/issues/93238 | 661,252,081 | 93,238 |
[
"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**:
Two services ... | Windows Kubeproxy has Connectivity issues when one of the multiple services referencing a same endpoint is deleted or updated | https://api.github.com/repos/kubernetes/kubernetes/issues/93229/comments | 13 | 2020-07-19T19:04:43Z | 2020-09-01T23:35:07Z | https://github.com/kubernetes/kubernetes/issues/93229 | 661,008,586 | 93,229 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI -->
**Which jobs are failing**:
`kubeadm-kinder-master (ci-kubernetes-e2e-kubeadm-kinder-master)`
**Which test(s) are failing**:
`task-09-reset`
`task-10-delete`
`task-01-add-kubernetes-vers... | [Failing Test] kubeadm-kinder-master (ci-kubernetes-e2e-kubeadm-kinder-master) | https://api.github.com/repos/kubernetes/kubernetes/issues/93223/comments | 14 | 2020-07-19T13:53:57Z | 2020-07-27T17:52:50Z | https://github.com/kubernetes/kubernetes/issues/93223 | 660,850,310 | 93,223 |
[
"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-gci-gce-scalability
* ci-kubernetes-e2e-gci-gce-scalability-networkpolicies
* pull-kubernetes-e2e-gce-100-perf... | [flaky] SchedulingThroughput - SchedulingThroughput error: scheduler throughput: actual throughput 81.200000 lower than threshold 90.000000] | https://api.github.com/repos/kubernetes/kubernetes/issues/93217/comments | 35 | 2020-07-19T04:22:09Z | 2020-07-27T19:46:41Z | https://github.com/kubernetes/kubernetes/issues/93217 | 660,578,812 | 93,217 |
[
"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-e2e-gce
**Which test(s) are flaking**:
Discovery should validate PreferredVersion for each APIGroup
**Testg... | [flaky] Discovery should validate PreferredVersion for each APIGroup | https://api.github.com/repos/kubernetes/kubernetes/issues/93215/comments | 2 | 2020-07-19T02:30:37Z | 2024-05-09T17:12:40Z | https://github.com/kubernetes/kubernetes/issues/93215 | 660,528,844 | 93,215 |
[
"kubernetes",
"kubernetes"
] | These tests have flaked consistently since https://github.com/kubernetes/kubernetes/pull/92442 merged: https://storage.googleapis.com/k8s-gubernator/triage/index.html?pr=1&text=not%20found&test=MirrorPodWithGracePeriod
in many cases, they are the only failure in a test run:
* https://prow.k8s.io/view/gcs/kubernetes... | MirrorPodWithGracePeriod test flaking in 5% of pull-kubernetes-node-e2e runs | https://api.github.com/repos/kubernetes/kubernetes/issues/93210/comments | 10 | 2020-07-18T17:25:05Z | 2020-07-22T05:32:20Z | https://github.com/kubernetes/kubernetes/issues/93210 | 660,270,946 | 93,210 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
In the Kubernetes documentation about [Termination of Pods](https://kubernetes.io/docs/concepts/workloads/pods/pod/#termination-of-pods) it says:
> When a user requests deletion of a Pod, the system ... | Pod termination documentation should clarify termination signals | https://api.github.com/repos/kubernetes/kubernetes/issues/93209/comments | 2 | 2020-07-18T16:50:04Z | 2020-10-02T17:14:49Z | https://github.com/kubernetes/kubernetes/issues/93209 | 660,253,688 | 93,209 |
[
"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**:
**What you ... | Bugs | https://api.github.com/repos/kubernetes/kubernetes/issues/93206/comments | 1 | 2020-07-18T12:43:15Z | 2020-07-18T14:35:00Z | https://github.com/kubernetes/kubernetes/issues/93206 | 660,129,121 | 93,206 |
[
"kubernetes",
"kubernetes"
] | Binary K8S Kube-Apiserver, Kube-Scheduler, Kube-Controller component configuration information is there a quick and easy way to get it, rather than through a configuration file | Gets binary K8S configuration information | https://api.github.com/repos/kubernetes/kubernetes/issues/93205/comments | 5 | 2020-07-18T05:28:52Z | 2020-08-06T14:38:37Z | https://github.com/kubernetes/kubernetes/issues/93205 | 659,919,629 | 93,205 |
[
"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**: container star... | run kubelet with non-root user | https://api.github.com/repos/kubernetes/kubernetes/issues/93204/comments | 5 | 2020-07-18T04:15:37Z | 2020-12-15T16:41:23Z | https://github.com/kubernetes/kubernetes/issues/93204 | 659,884,457 | 93,204 |
[
"kubernetes",
"kubernetes"
] | Hi. currently i'm extending the kubernetes API with CRD.
And I saw the following article in [api-convention](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status)
```
However, conditions are observations and not, themselves, state machines,
n... | How distinguished the state without using condition? | https://api.github.com/repos/kubernetes/kubernetes/issues/93203/comments | 2 | 2020-07-18T02:23:46Z | 2020-10-29T15:49:31Z | https://github.com/kubernetes/kubernetes/issues/93203 | 659,829,462 | 93,203 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Using "subPath" to access a mount point mounted by another container in the same pod does not work.
Given a deployment like the following, "server-1" is not able to access the files mounted by "provider".
```
apiVersion: apps/v1
kind: Deployment
metadata:
name: bugreport
labels:
app:... | subPath not working with mountPropagation | https://api.github.com/repos/kubernetes/kubernetes/issues/93202/comments | 4 | 2020-07-17T23:27:41Z | 2020-12-15T04:29:21Z | https://github.com/kubernetes/kubernetes/issues/93202 | 659,732,148 | 93,202 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
Kubemark controller should only use nodes for its template that are hollow nodes, rather than any node.
**Why is this needed**:
I want to perf-test the cluster autoscaler using clusters the contain re... | Support Real and Hollow node configurations in the same cluster. | https://api.github.com/repos/kubernetes/kubernetes/issues/93200/comments | 2 | 2020-07-17T19:10:13Z | 2020-09-18T05:24:46Z | https://github.com/kubernetes/kubernetes/issues/93200 | 659,544,898 | 93,200 |
[
"kubernetes",
"kubernetes"
] | It seems a backport is needed for #85043 to v1.16.13 as stated in https://github.com/kubernetes/kubernetes/pull/85043#issuecomment-659875085.
**What happened**:
Kube-scheduler and kube-controller-manager fails their health checks after installing 1.16.13.
**What you expected to happen**:
All control plane pods are ... | kube-scheduler and kube-controller-manager fails health checks on insecure port on 1.16.13 | https://api.github.com/repos/kubernetes/kubernetes/issues/93194/comments | 8 | 2020-07-17T16:21:23Z | 2020-08-14T12:44:22Z | https://github.com/kubernetes/kubernetes/issues/93194 | 659,394,941 | 93,194 |
[
"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**: After applying... | After applying kuboard.yaml at master node, no resources found in kube-system namespace. | https://api.github.com/repos/kubernetes/kubernetes/issues/93192/comments | 6 | 2020-07-17T15:37:56Z | 2020-07-19T02:59:50Z | https://github.com/kubernetes/kubernetes/issues/93192 | 659,357,403 | 93,192 |
[
"kubernetes",
"kubernetes"
] | This situation was discovered when I wanted to remove deprecated functionality in https://github.com/kubernetes/kubernetes/pull/90243. Unfortunately, due to how we are constructing client in almost every kubectl command this removal ended up with the following bug https://github.com/kubernetes/kubernetes/issues/90074.
... | kubectl --local is not quite local across all the commands | https://api.github.com/repos/kubernetes/kubernetes/issues/93188/comments | 25 | 2020-07-17T14:24:56Z | 2023-03-15T14:34:07Z | https://github.com/kubernetes/kubernetes/issues/93188 | 659,299,221 | 93,188 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI -->
**Which jobs are failing**:
`gce-device-plugin-gpu-master (ci-kubernetes-e2e-gce-device-plugin-gpu)`
**Which test(s) are failing**:
`[sig-scheduling] [Feature:GPUDevicePlugin] run Nvidia G... | [Failing Test] [sig-scheduling] [Feature:GPUDevicePlugin] run Nvidia GPU Device Plugin tests (ci-kubernetes-e2e-gce-device-plugin-gpu) | https://api.github.com/repos/kubernetes/kubernetes/issues/93187/comments | 10 | 2020-07-17T14:21:37Z | 2020-07-20T16:02:52Z | https://github.com/kubernetes/kubernetes/issues/93187 | 659,296,700 | 93,187 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Sometimes we see a pod not being scheduled because the scheduler thinks there are not enough resources:
```
I0713 16:28:36.138069 1 filter_out_schedulable.go:60] Filtering out schedulables
I0713 16:28:36.138724 1 filter_out_schedulable.go:106] Pod default.backoffice-57687f7994-4frt4 m... | Scheduler and cluster auto scaler don't agree on available resources | https://api.github.com/repos/kubernetes/kubernetes/issues/93186/comments | 14 | 2020-07-17T13:42:57Z | 2020-09-08T08:20:09Z | https://github.com/kubernetes/kubernetes/issues/93186 | 659,268,140 | 93,186 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
When I use kube-proxy in ipvs mode, the node can not connect to master when I create a service with externalIPs which use the node ip, it shows `connect: no route to host`, when I `ping` the master ip, it shows `Destination Host Unreachable`, but the node can connect to other ip. When I use iptab... | ipvs mode can not handle externalIPs | https://api.github.com/repos/kubernetes/kubernetes/issues/93175/comments | 12 | 2020-07-17T07:17:06Z | 2022-09-26T03:13:16Z | https://github.com/kubernetes/kubernetes/issues/93175 | 658,952,926 | 93,175 |
[
"kubernetes",
"kubernetes"
] |
The rolling- Update command has been removed and replaced with the rollout command
The original implementation of rolling update can use the command `Kubectl rolling-update RC-demo --image=nginx:1.7.9`, but now how do I implement rolling update?
[Instructions for removing the rolling- Update command](https://gith... | rolling-update change to rollout question | https://api.github.com/repos/kubernetes/kubernetes/issues/93174/comments | 1 | 2020-07-17T05:02:54Z | 2020-07-20T15:40:47Z | https://github.com/kubernetes/kubernetes/issues/93174 | 658,864,970 | 93,174 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI -->
**Which jobs are failing**:
set the deploy with the nodeSelector configCode
...
nodeSelector:
test-node-write: "1"
then kubectl label no test-node-001 test-node-write=1
the... | use the k8s 1.16.1 then the nodeSelector can't use the labe name with the '-' | https://api.github.com/repos/kubernetes/kubernetes/issues/93173/comments | 10 | 2020-07-17T03:44:09Z | 2020-12-15T01:26:21Z | https://github.com/kubernetes/kubernetes/issues/93173 | 658,815,512 | 93,173 |
[
"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**:
If I have the a... | A PSP with apparmor annotations does not allow windows pods to be scheduled | https://api.github.com/repos/kubernetes/kubernetes/issues/93165/comments | 4 | 2020-07-16T23:51:58Z | 2020-10-23T06:18:00Z | https://github.com/kubernetes/kubernetes/issues/93165 | 658,675,065 | 93,165 |
[
"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-node-e2e fails about 50% of the time
**Which test(s) are failing**:
Unclear, at least some of the failures are timing out.
**Since when has it ... | pull-kubernetes-node-e2e fails half the time | https://api.github.com/repos/kubernetes/kubernetes/issues/93163/comments | 3 | 2020-07-16T22:13:35Z | 2020-07-18T17:24:52Z | https://github.com/kubernetes/kubernetes/issues/93163 | 658,616,329 | 93,163 |
[
"kubernetes",
"kubernetes"
] | When upgrading kubernetes cluster with kubeadm, I am seeing the below errors when running "kubeadm upgrade plan". I am not sure how to work around these errors. I am able to wget the files from the URL's mentioned below, so I do not think this would be a connectivity issue. I am running a 1.16 cluster attempting to upg... | Kubernetes upgrade fails with context deadline exceeded | https://api.github.com/repos/kubernetes/kubernetes/issues/93161/comments | 26 | 2020-07-16T21:09:29Z | 2020-07-22T20:33:44Z | https://github.com/kubernetes/kubernetes/issues/93161 | 658,572,800 | 93,161 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
We're using k8s with cilium as CNI backend.
Recently we discovered that cilium will not create any endpoint entries for services without selector.
After investigation we found that endpointslices resource will be not created in case we will create endpoint resource manually.
**What you expected... | EndpointSlices resource is not created for selector less services | https://api.github.com/repos/kubernetes/kubernetes/issues/93157/comments | 5 | 2020-07-16T20:22:04Z | 2020-07-17T00:37:29Z | https://github.com/kubernetes/kubernetes/issues/93157 | 658,535,928 | 93,157 |
[
"kubernetes",
"kubernetes"
] | Hi! K8s 1.18.2 (ubuntu 20 LTS) Multi-master cluster
I need shell bash command or script for get kubectl get nodes output for one worker node STATUS ready?
I see periodically worker status error. I want to made the alert for zabbix monitoring server if the status isn't ready to screaming ALERT
But I find commands onl... | How to get kubectl get nodes output for one worker STATUS ready? | https://api.github.com/repos/kubernetes/kubernetes/issues/93153/comments | 8 | 2020-07-16T18:58:45Z | 2020-12-15T20:44:41Z | https://github.com/kubernetes/kubernetes/issues/93153 | 658,470,963 | 93,153 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
Support the pod used nodeName schedule, volume controller can binding pvc to pod.
**Why is this needed**:
Now, when we use the nodeName field to run the Pod on a specific node, scheduler will skip update. This causes, the Volume controller to never start binding of the PVC.
The... | Support the pod used nodeName schedule, volume controller can binding pvc to pod. | https://api.github.com/repos/kubernetes/kubernetes/issues/93145/comments | 11 | 2020-07-16T15:51:21Z | 2020-07-22T02:30:49Z | https://github.com/kubernetes/kubernetes/issues/93145 | 658,325,304 | 93,145 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Service is having one pod as a backend. kube-proxy is running in iptable mode. When the pod dies, stake conntrack entries are still remaining. TCP connections to node ports are not getting terminated as both ends are active. But the conntrack entry is stake resulting in packets not reaching the ba... | conntrack entries are not getting cleared when pod moves | https://api.github.com/repos/kubernetes/kubernetes/issues/93143/comments | 15 | 2020-07-16T13:42:26Z | 2020-09-09T07:14:16Z | https://github.com/kubernetes/kubernetes/issues/93143 | 658,212,157 | 93,143 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
I was trying to deploy OpenStack on Kubernetes(multinode) Env.
While deploying the MariaDB and rabbitmq pods facing volume mounting issue. Please find the below errors:
MariaDB:
Type Reason Age From Message
---- ------ ---- ... | Kubernetes Openstack-helm(multinode) Volume Issue[Unable to attach or mount volumes: unmounted volumes=[mysql-data],] | https://api.github.com/repos/kubernetes/kubernetes/issues/93139/comments | 10 | 2020-07-16T07:48:58Z | 2021-01-08T19:07:34Z | https://github.com/kubernetes/kubernetes/issues/93139 | 657,946,416 | 93,139 |
[
"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**: Trying to depl... | Kubernetes Pod PUT Rest API not equivalent to kubectl replace -f testPod.yaml --force | https://api.github.com/repos/kubernetes/kubernetes/issues/93135/comments | 2 | 2020-07-16T03:13:13Z | 2020-07-16T18:57:23Z | https://github.com/kubernetes/kubernetes/issues/93135 | 657,808,898 | 93,135 |
[
"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 NetworkPoli... | NetworkPolicy describe output for egress-all should mention destination instead of source | https://api.github.com/repos/kubernetes/kubernetes/issues/93131/comments | 8 | 2020-07-16T01:53:41Z | 2020-08-28T13:35:08Z | https://github.com/kubernetes/kubernetes/issues/93131 | 657,779,409 | 93,131 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**: A field in kubeconfig, and a flag to kubectl to prevent the underlying client from following any redirects.
**Why is this needed**: kubectl generally doesn't need to follow redirects. In most cases, fol... | Allow kubectl (and client-go and other client libs) to not follow redirects | https://api.github.com/repos/kubernetes/kubernetes/issues/93129/comments | 13 | 2020-07-15T23:24:39Z | 2021-06-11T00:54:05Z | https://github.com/kubernetes/kubernetes/issues/93129 | 657,724,005 | 93,129 |
[
"kubernetes",
"kubernetes"
] | Currently the Kubernetes scheduler integration benchmarks support workloads of a particular kind -- simulated nodes are created and then an initial set of pods are scheduled. Once this setup is complete, a second and final set of pods are scheduled and various metrics are measured. I propose improving this to support a... | scheduler: support arbitrary workloads in integration benchmarks | https://api.github.com/repos/kubernetes/kubernetes/issues/93117/comments | 7 | 2020-07-15T18:53:53Z | 2020-09-17T21:08:47Z | https://github.com/kubernetes/kubernetes/issues/93117 | 657,576,109 | 93,117 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
Hey,
I recently tried to update the labels for an existing volumeClaimTemplate inside a statefulset. Kubernetes errored out with the following message:
```
error: statefulsets.apps "<redacted>" is ... | Allow updating volumeClaimTemplates labels | https://api.github.com/repos/kubernetes/kubernetes/issues/93115/comments | 15 | 2020-07-15T16:32:32Z | 2023-01-10T15:49:29Z | https://github.com/kubernetes/kubernetes/issues/93115 | 657,489,708 | 93,115 |
[
"kubernetes",
"kubernetes"
] | **What happened**: The latest release of the debian-base image, v2.1.0, contains a vulnerable version of the apt package. This [CVE](https://security-tracker.debian.org/tracker/CVE-2020-3810) impacts apt version 1.8.2.
**What you expected to happen**: Image should be updated to use at least apt 1.8.2.1 to clear the ... | Update apt to version 1.8.2.1 in debian base image | https://api.github.com/repos/kubernetes/kubernetes/issues/93114/comments | 5 | 2020-07-15T16:28:47Z | 2020-08-17T21:56:42Z | https://github.com/kubernetes/kubernetes/issues/93114 | 657,487,182 | 93,114 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI -->
**Which jobs are failing**:
`integration-master (ci-kubernetes-integration-master)`
**Which test(s) are failing**:
`k8s.io/kubernetes/test/integration/ipamperf.TestMain`
`k8s.io/kubernete... | [sig-scheduling] IPAM / Scheduler Performance tests fail on timeout | https://api.github.com/repos/kubernetes/kubernetes/issues/93112/comments | 11 | 2020-07-15T15:25:47Z | 2021-01-24T19:21:56Z | https://github.com/kubernetes/kubernetes/issues/93112 | 657,441,383 | 93,112 |
[
"kubernetes",
"kubernetes"
] | Cloud: AWS
Kubernetes cluster: EKS(1.17)
Installed calico
https://docs.aws.amazon.com/eks/latest/userguide/calico.html
Issue: In Networkpolicy, how can I block ports. I just need to block one port: 6379.
Because if I try to enable the required ports then, I guess I have to enable a thousand ports. The pods ar... | How to block a port in NetworkPolicy | https://api.github.com/repos/kubernetes/kubernetes/issues/93111/comments | 10 | 2020-07-15T12:06:58Z | 2020-07-26T14:39:47Z | https://github.com/kubernetes/kubernetes/issues/93111 | 657,298,768 | 93,111 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Running a non-AKS k8s v1.18.5 cluster on Azure, with 50 VMSS attached (each containing one or two nodes).
When we do attach several new VMSSes, or create/replace several nodes, the controller-managed gets quickly throttled by Azure API, for instance like so:
```
kube-controller-manager[20143... | Azure cloud provider hits the VMSS VMs List API more than it should | https://api.github.com/repos/kubernetes/kubernetes/issues/93106/comments | 0 | 2020-07-15T09:47:18Z | 2020-07-21T22:00:07Z | https://github.com/kubernetes/kubernetes/issues/93106 | 657,216,919 | 93,106 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Create Pod with AppArmor according to `https://kubernetes.io/docs/tutorials/clusters/apparmor/`.
I want to forbid command `mount` in container, but it fails. Am I missing anything?
**What you expected to happen**:
`mount` command is forbidden as my spec configurated.
**How to reproduce it... | AppArmor does not work in k8s 1.15 | https://api.github.com/repos/kubernetes/kubernetes/issues/93105/comments | 5 | 2020-07-15T09:41:51Z | 2020-12-13T02:41:00Z | https://github.com/kubernetes/kubernetes/issues/93105 | 657,213,270 | 93,105 |
[
"kubernetes",
"kubernetes"
] | As @soltysh suggests:
kubectl command are going to get rid of the dependency to the generators, and ultimately remove them entirely.
The main goal is to simplyfy the use of kubectl command.
This is already done in `kubectl run`, see https://github.com/kubernetes/kubernetes/pull/87077 and https://github.com/kubernete... | Remove generators from kubectl commands | https://api.github.com/repos/kubernetes/kubernetes/issues/93100/comments | 52 | 2020-07-15T08:00:09Z | 2022-03-30T00:34:08Z | https://github.com/kubernetes/kubernetes/issues/93100 | 657,146,959 | 93,100 |
[
"kubernetes",
"kubernetes"
] | It may be environmental, it may be all or some of the pieces that form a Kubernetes cluster, golang, CNI, etcd, iptables but my observations are that IPv6 cluster are performing worse than IPv4 ones, some order the magnitude slow, and another people is finding similiar behaviors as reported here i.e.
> This also o... | Investigate IPv6 (possible) slowness | https://api.github.com/repos/kubernetes/kubernetes/issues/93098/comments | 8 | 2020-07-15T07:15:38Z | 2020-09-09T07:21:54Z | https://github.com/kubernetes/kubernetes/issues/93098 | 657,121,212 | 93,098 |
[
"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**:
 with long drain times which we would like to quickly rollback in the face of issues. The current rolling update deployments can take 12+ hours due to drain time, number of pods, and max unavailability. If something were to ... | RFI: Improved scheduling in support of blue-green deployments which don't consume 2x capacity | https://api.github.com/repos/kubernetes/kubernetes/issues/93082/comments | 8 | 2020-07-14T23:02:45Z | 2020-09-14T23:04:28Z | https://github.com/kubernetes/kubernetes/issues/93082 | 656,948,529 | 93,082 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
kube-scheduler doesn't appear to consider `ImageLocalityPriority` when scheduling pods to nodes, even when it's explicitly enabled via a custom policy or plugin. It appears `ImageLocalityPriority` [should be registered as a default policy](https://github.com/kubernetes/kubernetes/blob/e2a822d9f3c2... | ImageLocalityPriority ignored by kube-scheduler | https://api.github.com/repos/kubernetes/kubernetes/issues/93079/comments | 11 | 2020-07-14T22:00:21Z | 2021-08-05T18:07:57Z | https://github.com/kubernetes/kubernetes/issues/93079 | 656,924,716 | 93,079 |
[
"kubernetes",
"kubernetes"
] | /sig scheduling
/sig api-machinery
Pod .spec.schedulerName is set as part of deserialization
https://github.com/kubernetes/kubernetes/blob/5e8ccda71cc676e070cd0f5d7b6990b8ebc24c1f/pkg/apis/core/v1/defaults.go#L219-L221
This is business logic and, as such, should live in a create registry function.
The prob... | Pod .spec.schedulerName should not be set as part of deserialization | https://api.github.com/repos/kubernetes/kubernetes/issues/93067/comments | 34 | 2020-07-14T18:29:08Z | 2021-05-28T16:18:11Z | https://github.com/kubernetes/kubernetes/issues/93067 | 656,812,287 | 93,067 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
On a test system kubelet was unable re-create a PodSandbox, picking an already used "Attempt Number" when there were multiple PodSandboxes in "NotReady" State.
**What you expected to happen**:
kubelet setting the "Attempt" number to the next available "Attempts"
**How to reproduce it (as... | kubeRuntimeManager.podSandboxChanged() expects SandboxStatuses to be ordered by Attempts | https://api.github.com/repos/kubernetes/kubernetes/issues/93064/comments | 10 | 2020-07-14T17:40:05Z | 2021-03-12T09:38:26Z | https://github.com/kubernetes/kubernetes/issues/93064 | 656,784,351 | 93,064 |
[
"kubernetes",
"kubernetes"
] | I have two statefulsets with one replica for each: `data-teleporter-t10-rs1` and `md-teleporter-105-dv16-sv15-ss1`.
I rebooted the node running those pods.
While the node was going down, I deleted those pods with `--force --grace-period=0`.
**What happened**:
`data-teleporter-t10-rs1-0` pod was immediately delet... | Stateful POD created but not scheduled | https://api.github.com/repos/kubernetes/kubernetes/issues/93062/comments | 14 | 2020-07-14T17:30:18Z | 2020-12-24T18:14:12Z | https://github.com/kubernetes/kubernetes/issues/93062 | 656,778,935 | 93,062 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
The changes introduced by this ( https://github.com/kubernetes/kubernetes/pull/90948 ) PR will not work with Windows as Docker for Windows does not support: no-new-privileges security flag.
**How to reproduce it (as minimally and precisely as possible)**:
Run any pod with kubelet built from... | Kubelet cannot start any pod on Windows: no-new-privileges not supported by docker on Windows. | https://api.github.com/repos/kubernetes/kubernetes/issues/93061/comments | 6 | 2020-07-14T16:31:34Z | 2020-09-16T11:22:09Z | https://github.com/kubernetes/kubernetes/issues/93061 | 656,745,025 | 93,061 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
We would love to see support for AWS internal network loadbalancer with instances registered by IPs rather than instance IDs as is now by default.
**Why is this needed**:
There is a known bug - when you have an internal network load balancer with a target group specified by... | Support for AWS internal network loadbalancer with instances registered by IPs rather than instance IDs | https://api.github.com/repos/kubernetes/kubernetes/issues/93059/comments | 8 | 2020-07-14T14:37:05Z | 2021-01-04T18:34:01Z | https://github.com/kubernetes/kubernetes/issues/93059 | 656,663,591 | 93,059 |
[
"kubernetes",
"kubernetes"
] | Hi Team
We have been read only file system attribute in container security policy with .net Core app. .Net core stream input request to disk if size is greater than 30kb. And for those request we get read only file system. We understand it’s because of readonlyfilesystem attribute, but does this attribute make full ... | Readonlyfilesystem container security policy | https://api.github.com/repos/kubernetes/kubernetes/issues/93058/comments | 6 | 2020-07-14T12:14:33Z | 2021-04-01T22:38:16Z | https://github.com/kubernetes/kubernetes/issues/93058 | 656,566,207 | 93,058 |
[
"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 ipvs rule... | The ipvs rules wasn't update when i apply change. | https://api.github.com/repos/kubernetes/kubernetes/issues/93057/comments | 8 | 2020-07-14T10:35:04Z | 2020-07-15T15:35:49Z | https://github.com/kubernetes/kubernetes/issues/93057 | 656,510,495 | 93,057 |
Subsets and Splits
Unique Owner-Repo Count
Counts the number of unique owner-repos in the dataset, providing a basic understanding of diverse repositories.