issue_owner_repo listlengths 2 2 | issue_body stringlengths 0 261k ⌀ | issue_title stringlengths 1 925 | issue_comments_url stringlengths 56 81 | issue_comments_count int64 0 2.5k | issue_created_at stringlengths 20 20 | issue_updated_at stringlengths 20 20 | issue_html_url stringlengths 37 62 | issue_github_id int64 387k 2.91B | issue_number int64 1 131k |
|---|---|---|---|---|---|---|---|---|---|
[
"kubernetes",
"kubernetes"
] | This might be fixed in latest version of snapshot controller but at least with the version currently installed via addon manager - https://github.com/kubernetes/kubernetes/blob/master/cluster/addons/volumesnapshots/volume-snapshot-controller/volume-snapshot-controller-deployment.yaml
We are leaking `volumesnapshot` ... | Snapshot e2e leak VolumeSnapshot resources | https://api.github.com/repos/kubernetes/kubernetes/issues/91702/comments | 10 | 2020-06-02T22:26:08Z | 2020-10-03T14:18:48Z | https://github.com/kubernetes/kubernetes/issues/91702 | 629,555,057 | 91,702 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
I configured webhook authz mode like below to authorize client request
```Console
--runtime-config=authentication.k8s.io/v1=true
--runtime-config=authorization.k8s.io/v1=true
--authentication-token-webhook-config-file=/etc/kubernetes/manifests/guard-webhook.yaml
--authorization-mode=Node,Web... | Group info is missing in subject access review request for webhook authz mode | https://api.github.com/repos/kubernetes/kubernetes/issues/91698/comments | 4 | 2020-06-02T19:51:45Z | 2020-06-04T06:50:41Z | https://github.com/kubernetes/kubernetes/issues/91698 | 629,470,943 | 91,698 |
[
"kubernetes",
"kubernetes"
] |
**What happened**:
Followed the guide to install cri-o as container runtime and calico as cni-plugin for CentOS7
**What you expected to happen**:
Working configuration
**How to reproduce it (as minimally and precisely as possible)**:
Just follow the guide for installing HA Cluster.
Set up cri-o with pre... | k8s with cri-o as runtime does not support calico as cni plugin | https://api.github.com/repos/kubernetes/kubernetes/issues/91695/comments | 3 | 2020-06-02T18:15:11Z | 2020-06-02T21:03:56Z | https://github.com/kubernetes/kubernetes/issues/91695 | 629,413,243 | 91,695 |
[
"kubernetes",
"kubernetes"
] | I am porting https://github.com/kubernetes/apimachinery/issues/70 to k/k per the [comment](https://github.com/kubernetes/apimachinery/issues/70#issuecomment-597302625)
We are using the StreamWatcher and seeing extremely high memory allocations. Attached is a memory profile:
[pprof.pilot-discovery.alloc_objects.al... | StreamWatcher memory leak | https://api.github.com/repos/kubernetes/kubernetes/issues/91686/comments | 9 | 2020-06-02T16:17:44Z | 2021-06-24T08:17:37Z | https://github.com/kubernetes/kubernetes/issues/91686 | 629,335,426 | 91,686 |
[
"kubernetes",
"kubernetes"
] | Hi,
I have two dedicated servers with docker installed on it. I want to configure one of the servers in Master but the kubeadm init command does not work. I have a timeout at step [kubelet-check]. Can you help me ?
| [kubelet-check] Initial timeout of 40s passed | https://api.github.com/repos/kubernetes/kubernetes/issues/91681/comments | 3 | 2020-06-02T14:55:24Z | 2020-06-05T20:30:21Z | https://github.com/kubernetes/kubernetes/issues/91681 | 629,271,060 | 91,681 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI -->
**Which jobs are failing**:
aks-engine-azure-windows-master-containerd-serial-slow
**Which test(s) are failing**:
[sig-windows] [Feature:Windows] Kubelet-Stats [Serial] Kubelet stats c... | tests: Kubelet stats collection for Windows fails | https://api.github.com/repos/kubernetes/kubernetes/issues/91677/comments | 1 | 2020-06-02T13:38:25Z | 2020-06-25T02:26:37Z | https://github.com/kubernetes/kubernetes/issues/91677 | 629,211,206 | 91,677 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
I have updated StatefulSet using `rollingUpdate strategy`, when `updateStrategy.rollingUpdate.partition==8` (`replicas==10`) I found new container image has bug. I would roll back the updated pod，set `updateStrategy.rollingUpdate.partition=10` and delete the updated pod(`kubectl delete pod`).Then ... | The rollback of StatefulSet can't be done by increasing rollingUpdate.partition | https://api.github.com/repos/kubernetes/kubernetes/issues/91676/comments | 14 | 2020-06-02T13:03:01Z | 2021-01-16T12:07:15Z | https://github.com/kubernetes/kubernetes/issues/91676 | 629,185,755 | 91,676 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
I have updated StatefulSet using `rollingUpdate strategy`, when `updateStrategy.rollingUpdate.partition==8` (`replicas==10`) I found new container image has bug. I would roll back the updated pod，set `updateStrategy.rollingUpdate.partition=10` and delete the updated pod(`kubectl delete pod`).Then ... | The rollback of StatefulSet can't be done by increasing rollingUpdate.partition | https://api.github.com/repos/kubernetes/kubernetes/issues/91675/comments | 2 | 2020-06-02T13:00:44Z | 2020-06-02T13:02:18Z | https://github.com/kubernetes/kubernetes/issues/91675 | 629,184,159 | 91,675 |
[
"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/
-->
`/sig apps`
**What happened**:
... | The rollback of StatefulSet can't be done by increasing rollingUpdate.partition | https://api.github.com/repos/kubernetes/kubernetes/issues/91674/comments | 1 | 2020-06-02T12:41:39Z | 2020-06-02T13:00:35Z | https://github.com/kubernetes/kubernetes/issues/91674 | 629,171,476 | 91,674 |
[
"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 found a dep... | Should Replicaset controller cleanup the failed pods | https://api.github.com/repos/kubernetes/kubernetes/issues/91672/comments | 8 | 2020-06-02T12:14:46Z | 2021-01-21T19:11:41Z | https://github.com/kubernetes/kubernetes/issues/91672 | 629,154,777 | 91,672 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
When applying deployment yaml file with kubectl few out of many host aliases are ignored, only applying partial hostaliases.
I tried with json also but bahavior is same, tried with kubectl edit again bahavior is same.
But when I updated directly in GKE console its applying correctly.
**What... | `kubectl apply` drops all hostAlias entries when removing a duplicate entry from an existing object | https://api.github.com/repos/kubernetes/kubernetes/issues/91670/comments | 13 | 2020-06-02T11:50:22Z | 2020-06-02T19:37:36Z | https://github.com/kubernetes/kubernetes/issues/91670 | 629,139,806 | 91,670 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
I would like to be able to use`$ref` as part of a CRD schema to enable a somewhat recursive schema to apply validation to child values in a map. Here is a simple JSON schema that shows what I mean.
(... | CustomResourceDefinition schemas should support $ref | https://api.github.com/repos/kubernetes/kubernetes/issues/91669/comments | 2 | 2020-06-02T10:24:26Z | 2020-06-02T11:51:03Z | https://github.com/kubernetes/kubernetes/issues/91669 | 629,086,771 | 91,669 |
[
"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**:
Deployed pod ... | Kubernetes v1.18.0 cpumanager: cpuset not assigned after pod restart | https://api.github.com/repos/kubernetes/kubernetes/issues/91668/comments | 8 | 2020-06-02T09:59:06Z | 2020-12-19T08:06:12Z | https://github.com/kubernetes/kubernetes/issues/91668 | 629,070,406 | 91,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**:
I created a... | Container has exited but pod Ready condition is still true | https://api.github.com/repos/kubernetes/kubernetes/issues/91667/comments | 8 | 2020-06-02T09:09:52Z | 2021-04-29T02:59:23Z | https://github.com/kubernetes/kubernetes/issues/91667 | 629,036,468 | 91,667 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Enabling gVisor sandbox lowered actual CPU capacity from the assigned capacity. For example, assigning 6 CPU cores to a node reduces it to 3 CPU cores capacity.
**What you expected to happen**:
CPU capacity and assigned CPU should match.
**How to reproduce it (as minimally and precisely as po... | Actual CPU capacity is lower than assigned CPU capacity when gVisor sandbox is enabled in GKE | https://api.github.com/repos/kubernetes/kubernetes/issues/91665/comments | 3 | 2020-06-02T08:39:47Z | 2020-07-15T13:26:28Z | https://github.com/kubernetes/kubernetes/issues/91665 | 629,015,135 | 91,665 |
[
"kubernetes",
"kubernetes"
] | Upgrade Kube-aws v1.15.5 cluster to the next version 1.16.8.
**What happened**:
I want to keep the Same node label for Master and Worker nodes as I'm using in v1.15 cluster to segregate the nodes with roles. When I tried to upgrade the cluster to V1.16 the --node-labels is restricted to use '**node-role**'
**Wha... | Kubernetes V1.16.8 doesn't support 'node-role' label using “--node-labels=node-role.kubernetes.io/master=” | https://api.github.com/repos/kubernetes/kubernetes/issues/91664/comments | 7 | 2020-06-02T08:05:54Z | 2020-09-15T14:17:33Z | https://github.com/kubernetes/kubernetes/issues/91664 | 628,992,247 | 91,664 |
[
"kubernetes",
"kubernetes"
] | When i changed max-pods parameter for kubelet and restart kubelet, all pods are terminated.
Expected behaviour: all pods stay safe on the machine without teiminating | When i changed max-pods parameter for kubelet and restart kubelet, all pods are terminated | https://api.github.com/repos/kubernetes/kubernetes/issues/91658/comments | 2 | 2020-06-02T03:36:04Z | 2020-06-19T06:00:47Z | https://github.com/kubernetes/kubernetes/issues/91658 | 628,874,206 | 91,658 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
I'm creating this issue as a tracking issue for improving the test and tooling coverage for our `dockerless` Kubelet. See the [KEP](https://github.com/kubernetes/enhancements/pull/1546) and [PR](https://github.com/kubernetes/kubernetes/pull/87746) for more background information - ... | Enhance the test/tooling coverage for `dockerless` Kubelet | https://api.github.com/repos/kubernetes/kubernetes/issues/91657/comments | 18 | 2020-06-02T02:29:38Z | 2020-12-18T09:44:14Z | https://github.com/kubernetes/kubernetes/issues/91657 | 628,852,012 | 91,657 |
[
"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**:
CoreDNS v1.6.... | Compatibility between coredns and kubernetes | https://api.github.com/repos/kubernetes/kubernetes/issues/91656/comments | 3 | 2020-06-02T02:23:15Z | 2020-07-02T14:22:45Z | https://github.com/kubernetes/kubernetes/issues/91656 | 628,849,691 | 91,656 |
[
"kubernetes",
"kubernetes"
] | **What would you like to see added?**
Currently, executing the unit tests in `pkg/kubelet/images/...` does not
actually execute the `throttledImageService` as defined in
`pkg/kubelet/images/helpers.go`. For all unit tests, `qps` is set to 0, so we
essentially use a non-throttled image service. Examining the code ... | Add unit test coverage using throttledImageService | https://api.github.com/repos/kubernetes/kubernetes/issues/91655/comments | 5 | 2020-06-02T02:09:20Z | 2020-06-11T00:14:09Z | https://github.com/kubernetes/kubernetes/issues/91655 | 628,845,162 | 91,655 |
[
"kubernetes",
"kubernetes"
] | This is part of #90962. | Revert assumed volume cache in Unreserve extension point | https://api.github.com/repos/kubernetes/kubernetes/issues/91654/comments | 2 | 2020-06-02T01:57:59Z | 2020-06-20T04:50:55Z | https://github.com/kubernetes/kubernetes/issues/91654 | 628,841,529 | 91,654 |
[
"kubernetes",
"kubernetes"
] | There is a secret that I can not delete it use "kubectl delete secret ceph-retain-bucket -n default". So I delete it in the etcd.
```
etcdctl --endpoints="https://10.2.20.159:2379" del --from-key /registry/secrets/default/ceph-retain-bucket
```
Command "kubectl get secret -n default“ nolonger show the secret again... | authentication error when delete secret in etcd | https://api.github.com/repos/kubernetes/kubernetes/issues/91653/comments | 8 | 2020-06-02T00:48:54Z | 2020-06-04T05:56:31Z | https://github.com/kubernetes/kubernetes/issues/91653 | 628,819,986 | 91,653 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**: CronJobs should have fields allowing for their start time to be randomized (as systemd's Timers have), or even distributed within a range to spread out in equal intervals with other CronJobs of a set. At t... | Cron job staggering / randomization / concurrency limiting | https://api.github.com/repos/kubernetes/kubernetes/issues/91652/comments | 36 | 2020-06-02T00:39:49Z | 2025-02-20T13:45:28Z | https://github.com/kubernetes/kubernetes/issues/91652 | 628,817,265 | 91,652 |
[
"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 https... | Volumes subPathExpr not being expanded. | https://api.github.com/repos/kubernetes/kubernetes/issues/91644/comments | 5 | 2020-06-01T19:17:40Z | 2020-06-02T05:33:11Z | https://github.com/kubernetes/kubernetes/issues/91644 | 628,665,155 | 91,644 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Build failed for `make test-e2e-node`
```
I0526 21:26:18.166413 56943 run_local.go:76] Running command: /home/zhi/os_k8s/go/src/k8s.io/kubernetes/_output/local/go/bin/ginkgo -nodes=8 -skip="\[Flaky\]|\[Slow\]|\[Serial\]" -untilItFails=false /home/zhi/os_k8s/go/src/k8s.io/kubernetes/_output/l... | Make failure for test-e2e-node | https://api.github.com/repos/kubernetes/kubernetes/issues/91641/comments | 17 | 2020-06-01T17:48:49Z | 2020-06-06T05:09:35Z | https://github.com/kubernetes/kubernetes/issues/91641 | 628,616,956 | 91,641 |
[
"kubernetes",
"kubernetes"
] | KEP: https://github.com/kubernetes/enhancements/tree/master/keps/sig-architecture/960-conformance-behaviors
PRs:
- [api-machinery](https://github.com/kubernetes/kubernetes/pull/91639)
- [apps](https://github.com/kubernetes/kubernetes/pull/91638)
- [network](https://github.com/kubernetes/kubernetes/pull/91647)
- ... | [Umbrella Issue] Conformance Behavior Mappings | https://api.github.com/repos/kubernetes/kubernetes/issues/91640/comments | 4 | 2020-06-01T17:42:41Z | 2020-07-28T23:25:38Z | https://github.com/kubernetes/kubernetes/issues/91640 | 628,613,534 | 91,640 |
[
"kubernetes",
"kubernetes"
] | The kube-scheduler is currently difficult to debug through logs. Logging is inconsistent and sparse, and critically helpful information is in some spots logged at too high of a level to be practically accessible (such as [node scores](https://github.com/kubernetes/kubernetes/blob/b618411f1edb98afe807866fb3a607356d72ba2... | Do contextual logging for scheduler | https://api.github.com/repos/kubernetes/kubernetes/issues/91633/comments | 116 | 2020-06-01T15:16:45Z | 2024-07-22T09:23:49Z | https://github.com/kubernetes/kubernetes/issues/91633 | 628,523,208 | 91,633 |
[
"kubernetes",
"kubernetes"
] | @Rahulwagh after restart my laptop unable to cluster using vagrant getting the below error
Connection to the server local host:8080 was refused - did you specify right host or port
_
Please advise | Connection to the server local host:8080 was refused - did you specify right host or port | https://api.github.com/repos/kubernetes/kubernetes/issues/91631/comments | 5 | 2020-06-01T14:57:54Z | 2020-08-10T21:12:11Z | https://github.com/kubernetes/kubernetes/issues/91631 | 628,500,555 | 91,631 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Deduplicating a duplicate entry from the `imagePullSecrets` field causes the entire field to become `null`.
**What you expected to happen**:
The `imagePullSecrets` field should be the updated list instead of `null`.
**How to reproduce it (as minimally and precisely as possible)**:
1. U... | kubectl apply removes all imagePullSecrets when user attempts to remove duplicate secrets | https://api.github.com/repos/kubernetes/kubernetes/issues/91629/comments | 2 | 2020-06-01T14:41:38Z | 2020-06-04T06:54:36Z | https://github.com/kubernetes/kubernetes/issues/91629 | 628,489,754 | 91,629 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
In the KCM we're missing output about a few defaults, and probably a few of the options could use some clarity around `--allocate-node-cidrs` , `--cloud-controller-manager`, and i believe several other options have no `Default:` note, See
https://kubernetes.io/docs/reference/command-line-tools-r... | Missing defaults and clarifying info for kube-controller-manager | https://api.github.com/repos/kubernetes/kubernetes/issues/91628/comments | 34 | 2020-06-01T13:49:15Z | 2022-04-24T11:57:11Z | https://github.com/kubernetes/kubernetes/issues/91628 | 628,452,166 | 91,628 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI -->
**Which jobs are failing**:
https://prow.k8s.io/view/gcs/kubernetes-jenkins/pr-logs/pull/91527/pull-kubernetes-e2e-kind/1267430115185266689
https://prow.k8s.io/view/gcs/kubernetes-jenkins/pr-... | Ginkgo timed out waiting for all parallel nodes to report back! | https://api.github.com/repos/kubernetes/kubernetes/issues/91626/comments | 3 | 2020-06-01T13:04:46Z | 2020-06-02T07:55:44Z | https://github.com/kubernetes/kubernetes/issues/91626 | 628,422,887 | 91,626 |
[
"kubernetes",
"kubernetes"
] | <!--
STOP -- PLEASE READ!
GitHub is not the right place for support requests.
If you're looking for help, check [Stack Overflow](https://stackoverflow.com/questions/tagged/kubernetes) and the [troubleshooting guide](https://kubernetes.io/docs/tasks/debug-application-cluster/troubleshooting/).
You can also pos... | add kubectl config rename-cluster for rename clustername | https://api.github.com/repos/kubernetes/kubernetes/issues/91623/comments | 3 | 2020-06-01T10:24:22Z | 2020-06-01T10:39:50Z | https://github.com/kubernetes/kubernetes/issues/91623 | 628,325,512 | 91,623 |
[
"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 have a cust... | generic-garbage-collector can't cleanup clusterroles with managedFields set | https://api.github.com/repos/kubernetes/kubernetes/issues/91621/comments | 3 | 2020-06-01T07:49:32Z | 2020-06-19T20:13:03Z | https://github.com/kubernetes/kubernetes/issues/91621 | 628,228,227 | 91,621 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
Currently `kube-apiserver` use the configuration of itself `--kubelet-https` to determine the use of https for kubelet connections.
If `--kubelet-https =true`, when apiserver initiates a connection t... | Let kube-apiserver select an HTTP or an HTTPS connection based on kubelet's configuration | https://api.github.com/repos/kubernetes/kubernetes/issues/91620/comments | 7 | 2020-06-01T06:56:43Z | 2020-06-02T00:53:25Z | https://github.com/kubernetes/kubernetes/issues/91620 | 628,201,424 | 91,620 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
When updating a deeply nested CRD in a local k8s cluster with `kubectl apply`,
the command finishes after more than 5 minutes.
The CRD has a field like [`corev1.PodSpec`](https://godoc.org/k8s.io/api/core/v1#PodSpec).
I did a brief experiment for how the nesting depth of manifests affects com... | JSON patch with kubectl has exponential time complexity for nesting depth of manifest | https://api.github.com/repos/kubernetes/kubernetes/issues/91615/comments | 9 | 2020-06-01T04:06:34Z | 2021-01-05T17:57:07Z | https://github.com/kubernetes/kubernetes/issues/91615 | 628,136,605 | 91,615 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
/sig auth
/sig api-machinery
**What would you like to be added**:
I would like the JWT token created by ServiceAccountToken controller to include optional labels from metadata
**Why is this needed**:
The JWT token created by ServiceAcc... | Support for metadata information in JWT token created by ServiceAccountToken controller | https://api.github.com/repos/kubernetes/kubernetes/issues/91610/comments | 10 | 2020-05-31T22:06:28Z | 2020-10-30T03:30:36Z | https://github.com/kubernetes/kubernetes/issues/91610 | 628,053,439 | 91,610 |
[
"kubernetes",
"kubernetes"
] | Is there any way where we can disable mounting of FAT/squashfs/cramfs/hfsplus/jffs2 inside a container in Kubernetes.
This is a security requirement to comply with.
| Disable unused filesystems in Kubernetes | https://api.github.com/repos/kubernetes/kubernetes/issues/91609/comments | 11 | 2020-05-31T15:13:13Z | 2020-10-28T19:59:50Z | https://github.com/kubernetes/kubernetes/issues/91609 | 627,982,823 | 91,609 |
[
"kubernetes",
"kubernetes"
] | Hi Guys,
Is there a way to label kubernetes daemonsets? Do not want daemonset to run on specific node. | @kubernetes daemonsets | https://api.github.com/repos/kubernetes/kubernetes/issues/91605/comments | 4 | 2020-05-30T18:14:07Z | 2020-05-31T16:08:42Z | https://github.com/kubernetes/kubernetes/issues/91605 | 627,788,642 | 91,605 |
[
"kubernetes",
"kubernetes"
] | **What happened**: We upgraded 15 kubernetes clusters from 1.17.5 to 1.18.2/1.18.3 and started to see that daemonsets does not work properly anymore.
The problem is that all daemonset pods does not provision. It will return following error message to events:
```
Events:
Type Reason Age ... | Some nodes are not considered in scheduling when there is zone imbalance | https://api.github.com/repos/kubernetes/kubernetes/issues/91601/comments | 129 | 2020-05-30T09:04:36Z | 2020-09-15T20:49:01Z | https://github.com/kubernetes/kubernetes/issues/91601 | 627,685,109 | 91,601 |
[
"kubernetes",
"kubernetes"
] | In my cluster, some of the pods were evicted, and the description shows it's due to lack of ephemeral-storage.
I checked the disk space of worker nodes. There is still plenty of disk space. But the kubelet logs showed the kubelet is still trying to evict pods. It's quite strange. Why?
```
Events:
Type Reaso... | The node was low on resource: ephemeral-storage, and pods were evicted | https://api.github.com/repos/kubernetes/kubernetes/issues/91600/comments | 10 | 2020-05-30T07:50:20Z | 2024-05-22T07:43:17Z | https://github.com/kubernetes/kubernetes/issues/91600 | 627,674,342 | 91,600 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**: add a new option in `kubectl get --output=yaml` which does NOT show [metadata.managedFields](https://kubernetes.io/docs/reference/using-api/api-concepts/#field-management) in the output.
May be `kubectl g... | hide metadata.managedFields in `kubectl get -o yaml` | https://api.github.com/repos/kubernetes/kubernetes/issues/91584/comments | 3 | 2020-05-29T15:01:10Z | 2020-05-29T17:47:34Z | https://github.com/kubernetes/kubernetes/issues/91584 | 627,333,972 | 91,584 |
[
"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**:
```
metadat... | watch of *v1.PartialObjectMetadat ended with: an error on the server | https://api.github.com/repos/kubernetes/kubernetes/issues/91582/comments | 6 | 2020-05-29T14:30:36Z | 2020-05-29T15:22:54Z | https://github.com/kubernetes/kubernetes/issues/91582 | 627,313,297 | 91,582 |
[
"kubernetes",
"kubernetes"
] | I've checked some jobs that timed out and something is odd with the test
```
[k8s.io] [sig-node] Pods Extended
^[[90mtest/e2e/framework/framework.go:592^[[0m
[k8s.io] Pod Container Status
^[[90mtest/e2e/framework/framework.go:592^[[0m
should never report success for a pending container
```
Check the... | [failing test] "Pod Container Status should never report success for a pending container" hangs and times out KIND jobs | https://api.github.com/repos/kubernetes/kubernetes/issues/91579/comments | 31 | 2020-05-29T13:33:47Z | 2020-06-05T07:01:02Z | https://github.com/kubernetes/kubernetes/issues/91579 | 627,272,482 | 91,579 |
[
"kubernetes",
"kubernetes"
] | /sig windows
**What happened**:
I have a Kubernetes cluster with 2 Windows worker nodes. When I run `kubectl top nodes` the Windows nodes report as unknown. I did some investigating and I am seeing errors in the logs.
**What you expected to happen**:
When I do `kubectl top nodes` or `kubectl top pods` the Windo... | Metrics server fails to pull metrics from Windows workers | https://api.github.com/repos/kubernetes/kubernetes/issues/91575/comments | 3 | 2020-05-29T12:39:32Z | 2020-06-26T21:14:26Z | https://github.com/kubernetes/kubernetes/issues/91575 | 627,239,371 | 91,575 |
[
"kubernetes",
"kubernetes"
] | This is the master Issue to track my porting effort to the illumos operating system and to allow me to ask questions about things in kubernetes.
The following things are part of this effort:
- [ ] Modify build tags to allow compilation #91572
- [ ] Update Vendor with upstream fixes
- [ ] github.com/moby/term
-... | Port to the illumos Operating system (Master Issue) | https://api.github.com/repos/kubernetes/kubernetes/issues/91570/comments | 18 | 2020-05-29T11:58:36Z | 2021-06-26T19:58:49Z | https://github.com/kubernetes/kubernetes/issues/91570 | 627,216,361 | 91,570 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
I used [apiserver-builder](https://github.com/kubernetes-sigs/apiserver-builder-alpha) v1.17 to extend a rest resource for apiserver. In the Get()/List() method I added the `CreationTimestamp` like this:
`<resourceInstanceName>.ObjectMeta.CreationTimestamp = metav1.Now()`.
In kubernetes 1.14 and 1... | kubectl sometimes get a <invalid> string in output CreationTimestamp column | https://api.github.com/repos/kubernetes/kubernetes/issues/91565/comments | 10 | 2020-05-29T07:25:21Z | 2020-10-30T08:35:33Z | https://github.com/kubernetes/kubernetes/issues/91565 | 627,058,585 | 91,565 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
The 'Successfully pulled image' event should contain the duration for image pulling.
**Why is this needed**:
Currently the success event is in this form:
```
May 29 05:42:16 tmp-node-e2e-f9c7d938-cos-stable-81-12871-103-0 kubelet[1939]: I0529 05:42:16.850647 1939 event.go:... | Add duration to image pulling event | https://api.github.com/repos/kubernetes/kubernetes/issues/91560/comments | 1 | 2020-05-29T06:07:52Z | 2020-06-20T04:50:40Z | https://github.com/kubernetes/kubernetes/issues/91560 | 627,022,838 | 91,560 |
[
"kubernetes",
"kubernetes"
] | **What happened**: kubelet neglects to mount all but 1 of a pod's CSI volumes that have the same volumeHandle even though they have different volumeAttributes.
I get this message:
```
Warning FailedMount 14s (x3 over 4m43s) kubelet, 127.0.0.1 Unable to attach or mount volumes: unmounted volumes=[pv1],... | kubelet neglects to mount all but 1 of a pod's CSI volumes that have the same volumeHandle even though they have different volumeAttributes | https://api.github.com/repos/kubernetes/kubernetes/issues/91556/comments | 6 | 2020-05-29T02:32:33Z | 2020-10-27T00:17:33Z | https://github.com/kubernetes/kubernetes/issues/91556 | 626,953,618 | 91,556 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
more levels for instrument events flow like:
Info, Critical, Error
**Why is this needed**:
Wanted to reuse https://github.com/kubernetes/kubernetes/blob/323f34858de18b862d43c40b2cced65ad8e24052/stagi... | Add new types for the Events | https://api.github.com/repos/kubernetes/kubernetes/issues/91552/comments | 32 | 2020-05-29T00:36:52Z | 2023-04-20T17:03:10Z | https://github.com/kubernetes/kubernetes/issues/91552 | 626,918,904 | 91,552 |
[
"kubernetes",
"kubernetes"
] | There are some tests under folder `test/integration/scheduler` that don't quite follow the [Golang table-driven](https://github.com/golang/go/wiki/TableDrivenTests) test style. Here are some symptoms:
- no `t.Run()` under `for _, test := range tests` loop ([good example](https://github.com/kubernetes/kubernetes/blob... | Table-driven scheduler integration tests | https://api.github.com/repos/kubernetes/kubernetes/issues/91551/comments | 7 | 2020-05-28T23:44:06Z | 2020-09-01T17:29:00Z | https://github.com/kubernetes/kubernetes/issues/91551 | 626,894,877 | 91,551 |
[
"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-kind
**Which test(s) are flaking**:
Unknown, exactly.
[k8s.io] [sig-node] Pods Extended [k8s.io] Pod Conta... | [Flaky Test] pull-kubernetes-e2e-kind [k8s.io] [sig-node] Pods Extended [k8s.io] slow | https://api.github.com/repos/kubernetes/kubernetes/issues/91550/comments | 6 | 2020-05-28T23:11:20Z | 2020-06-03T18:49:23Z | https://github.com/kubernetes/kubernetes/issues/91550 | 626,876,011 | 91,550 |
[
"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-master-parallel (ci-kubernetes-kind-e2e-parallel)`
`kind-ipv6-master-parallel (ci-kubernetes-kind-e2e-parallel)`
**Which t... | [Flaky Test] kind-{ipv6}-master-parallel (ci-kubernetes-kind-{ipv6}-e2e-parallel) | https://api.github.com/repos/kubernetes/kubernetes/issues/91548/comments | 18 | 2020-05-28T21:50:02Z | 2020-07-07T13:19:40Z | https://github.com/kubernetes/kubernetes/issues/91548 | 626,838,559 | 91,548 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Per title, if you attempt to launch a cluster with multiple cluster CIDRs (thus you are not passing `--cluster-cidr` to kube-proxy), NodePorts will be broken when the FORWARD chain in the filter table is set to default DROP. This is because there will be no rule for ACCEPT in KUBE-FORWARD matching c... | NodePorts broken on clusters when not passing cluster-cidr and FORWARD chain in filter defaults to DROP | https://api.github.com/repos/kubernetes/kubernetes/issues/91545/comments | 9 | 2020-05-28T18:27:23Z | 2020-10-29T19:22:33Z | https://github.com/kubernetes/kubernetes/issues/91545 | 626,720,244 | 91,545 |
[
"kubernetes",
"kubernetes"
] | CVSS Rating: [CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N](https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N)
There exists a Server Side Request Forgery (SSRF) vulnerability in kube-controller-manager that allows certain authorized users to leak up to 500 bytes of arbitrary info... | CVE-2020-8555: Half-Blind SSRF in kube-controller-manager | https://api.github.com/repos/kubernetes/kubernetes/issues/91542/comments | 4 | 2020-05-28T16:13:34Z | 2021-12-02T22:54:48Z | https://github.com/kubernetes/kubernetes/issues/91542 | 626,636,248 | 91,542 |
[
"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-scalability-100 (ci-kubernetes-e2e-gci-gce-scalability)`
**Which test(s) are failing**:
`ClusterLoaderV2`
`diffResources`
**Since when has i... | [Failing Test] gce-cos-master-scalability-100 (ci-kubernetes-e2e-gci-gce-scalability) | https://api.github.com/repos/kubernetes/kubernetes/issues/91540/comments | 5 | 2020-05-28T16:11:17Z | 2020-05-29T10:37:30Z | https://github.com/kubernetes/kubernetes/issues/91540 | 626,634,708 | 91,540 |
[
"kubernetes",
"kubernetes"
] | apiserver_request (total, latency histogram) metrics are likely the two most important metrics emitted by the kube-apiserver, aggregator, and aggregated-apiserver binaries. https://github.com/kubernetes/kubernetes/issues/76302 has been open for a year regarding some of the issues that have been ongoing problems. I want... | Moving apiserver_request metrics to stable status | https://api.github.com/repos/kubernetes/kubernetes/issues/91536/comments | 12 | 2020-05-28T15:28:17Z | 2021-03-09T16:47:46Z | https://github.com/kubernetes/kubernetes/issues/91536 | 626,603,363 | 91,536 |
[
"kubernetes",
"kubernetes"
] | how to write this rule in alb:(attached screenshot).
<img width="1202" alt="Screenshot 2020-05-28 at 5 01 52 PM" src="https://user-images.githubusercontent.com/5381105/83136407-10622f80-a105-11ea-82a8-c5567e2677b6.png">
`error msg: The Ingress "pub-ext" is invalid: spec.rules[0].host: Invalid value: "qa.*.mydom... | unable to use wildcard in host key of ingress yaml | https://api.github.com/repos/kubernetes/kubernetes/issues/91528/comments | 5 | 2020-05-28T11:33:18Z | 2020-05-28T15:23:47Z | https://github.com/kubernetes/kubernetes/issues/91528 | 626,437,174 | 91,528 |
[
"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 use the ... | v1.17+ vxlan mode 63 sec delay | https://api.github.com/repos/kubernetes/kubernetes/issues/91519/comments | 4 | 2020-05-28T07:00:11Z | 2020-05-28T15:26:06Z | https://github.com/kubernetes/kubernetes/issues/91519 | 626,267,000 | 91,519 |
[
"kubernetes",
"kubernetes"
] | Kubernetes Verison 1.16.6
CoreDNS 1.6.9
flannel 0.11.0
This is my coredns logs, i running some Java program in openjdk images
```
[root@k8s-master-1 ~]# kubectl logs -f coredns-b75bb577b-5dlbd -n kube-system
[ERROR] plugin/errors: 2 accountant-server-http-provider-6b8756994f-zzf49. A: read udp 172.30.57.16:5303... | My coredns output many i/o timeout error logs | https://api.github.com/repos/kubernetes/kubernetes/issues/91518/comments | 4 | 2020-05-28T03:21:59Z | 2020-05-29T14:46:27Z | https://github.com/kubernetes/kubernetes/issues/91518 | 626,182,528 | 91,518 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
It would be nice to pass a process a number that is a bit lower than the container memory limit so that its garbage collection or memory management can use that limit.
For example:
- setting `GOMEMLIMIT` or setting `NODEMEMLIMIT`
- setting `NODE_OPTS=--max-old-space-size=$... | Allow setting an environment variable to some fraction or multiple of a resource field | https://api.github.com/repos/kubernetes/kubernetes/issues/91514/comments | 43 | 2020-05-28T00:41:27Z | 2025-02-18T10:01:07Z | https://github.com/kubernetes/kubernetes/issues/91514 | 626,129,505 | 91,514 |
[
"kubernetes",
"kubernetes"
] |
**What would you like to be added**:
Capacity.storage on PVs, and resources.requests.storage on PVCs should be optional.
**Why is this needed**:
According to https://github.com/kubernetes/kubernetes/issues/68736, the resource limitations on PVs and PVCs are informational, and not enforcing. In this case, these v... | Capacity and Requests on PVs and PVCs should be optional | https://api.github.com/repos/kubernetes/kubernetes/issues/91509/comments | 10 | 2020-05-27T20:07:49Z | 2021-06-24T04:30:11Z | https://github.com/kubernetes/kubernetes/issues/91509 | 625,995,622 | 91,509 |
[
"kubernetes",
"kubernetes"
] | CVSS Rating: [CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:L](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:L) (6.0 Medium)
A cluster configured to use an affected container networking implementation is susceptible to man-in-the-middle (MitM) attacks. By sending “rogue” router ad... | CVE-2020-10749: IPv4 only clusters susceptible to MitM attacks via IPv6 rogue router advertisements | https://api.github.com/repos/kubernetes/kubernetes/issues/91507/comments | 7 | 2020-05-27T19:32:29Z | 2022-09-14T11:48:50Z | https://github.com/kubernetes/kubernetes/issues/91507 | 625,973,443 | 91,507 |
[
"kubernetes",
"kubernetes"
] | The API server's "insecure-port" has been [deprecated since 1.10](https://github.com/kubernetes/kubernetes/commit/2f175bc43279a1a4552610a42af0a006f4c6fba2), but never had a deadline for removal. Previous efforts to remove the port have been blocked by requirements for http healthz checks (https://github.com/kubernetes/... | Remove the apiserver insecure port | https://api.github.com/repos/kubernetes/kubernetes/issues/91506/comments | 22 | 2020-05-27T19:28:52Z | 2021-01-06T22:17:10Z | https://github.com/kubernetes/kubernetes/issues/91506 | 625,971,337 | 91,506 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
[KEP: Consistent Resource Version Semantics for List](https://github.com/kubernetes/enhancements/pull/1606).
**Why is this needed**:
Resource version semantics should be consistent for list requests regardless of pagination. | Consistent Resource Version Semantics for List | https://api.github.com/repos/kubernetes/kubernetes/issues/91503/comments | 2 | 2020-05-27T18:20:29Z | 2020-06-27T09:26:18Z | https://github.com/kubernetes/kubernetes/issues/91503 | 625,924,329 | 91,503 |
[
"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**:
UT TestVali... | UT TestValidateNodeIPParam does not really tests validateNodeIP | https://api.github.com/repos/kubernetes/kubernetes/issues/91498/comments | 2 | 2020-05-27T15:21:30Z | 2020-06-30T09:52:06Z | https://github.com/kubernetes/kubernetes/issues/91498 | 625,790,746 | 91,498 |
[
"kubernetes",
"kubernetes"
] |
**What happened**:
kubectl describe of host network pods only appears to show the IPv4 address.
**What you expected to happen**:
The IPv6 addresses(es) should be shown too (possibly even the local one).
The IP addresses are visible from within the pods using `ip addr`
**How to reproduce it (as mini... | host network pods do not show IPv6 address in 'kubectl describe' | https://api.github.com/repos/kubernetes/kubernetes/issues/91494/comments | 4 | 2020-05-27T13:54:24Z | 2020-06-30T17:47:23Z | https://github.com/kubernetes/kubernetes/issues/91494 | 625,717,344 | 91,494 |
[
"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**:
PVs are defin... | PVs using FlexVolume are inaccessible and cannot be recovered after controller restart | https://api.github.com/repos/kubernetes/kubernetes/issues/91493/comments | 6 | 2020-05-27T13:25:40Z | 2020-10-31T16:05:52Z | https://github.com/kubernetes/kubernetes/issues/91493 | 625,695,050 | 91,493 |
[
"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 scale-up ... | Priority-based preemption can easily violate PDBs even when unnecessary due to multiple issues with the implementation | https://api.github.com/repos/kubernetes/kubernetes/issues/91492/comments | 41 | 2020-05-27T12:31:25Z | 2025-02-14T19:58:34Z | https://github.com/kubernetes/kubernetes/issues/91492 | 625,654,985 | 91,492 |
[
"kubernetes",
"kubernetes"
] | Part of https://github.com/kubernetes/enhancements/issues/1602 effort
Allow users to change log out of k8s components by passing flag `--log-format=json`.
Details:
* Implement `Logger` interface from https://github.com/go-logr/logr (suggested code location `staging/src/k8s.io/component-base/logs/json`)
* Regi... | Implement json log format | https://api.github.com/repos/kubernetes/kubernetes/issues/91490/comments | 2 | 2020-05-27T11:42:47Z | 2020-06-16T09:10:31Z | https://github.com/kubernetes/kubernetes/issues/91490 | 625,622,755 | 91,490 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
maybe we can add a field `podSelector` for extender to decide whether this pod is needed to be handled. Or, some way to tell it the pod is itself ?
**Why is this needed**:
scheduler extender pods can ... | scheduler extender pods can not be scheduled because sheduler extender is unavailable | https://api.github.com/repos/kubernetes/kubernetes/issues/91489/comments | 11 | 2020-05-27T11:25:55Z | 2020-08-27T02:17:09Z | https://github.com/kubernetes/kubernetes/issues/91489 | 625,611,710 | 91,489 |
[
"kubernetes",
"kubernetes"
] | Hello,
**What happened**:
When we apply PodSecurityPolicy with rule:
```
runAsUser:
# Require the container to run without root privileges.
rule: 'MustRunAsNonRoot'
```
WIndows containers are still blocked instead we put:
```
securityContext:
windowsOptions:
runAsUserName: "Cont... | PodSecurityPolicy rule: 'MustRunAsNonRoot' and windowsOptions: runAsUserName not working | https://api.github.com/repos/kubernetes/kubernetes/issues/91482/comments | 3 | 2020-05-27T08:16:46Z | 2020-09-14T17:43:00Z | https://github.com/kubernetes/kubernetes/issues/91482 | 625,481,333 | 91,482 |
[
"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**:
```
[root@ma... | pod can not using set env，but the help message said it can | https://api.github.com/repos/kubernetes/kubernetes/issues/91477/comments | 4 | 2020-05-27T04:02:10Z | 2020-08-28T02:32:17Z | https://github.com/kubernetes/kubernetes/issues/91477 | 625,358,594 | 91,477 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
Kubelet currently does not handle machine shutdown. Kubelet should be able to detect machine shutdown and gracefully terminate pods with attempt to respect pod's requested grace period.
**Why is this... | Kubelet should handle node shutdown | https://api.github.com/repos/kubernetes/kubernetes/issues/91472/comments | 10 | 2020-05-26T22:43:34Z | 2020-11-12T22:58:26Z | https://github.com/kubernetes/kubernetes/issues/91472 | 625,246,427 | 91,472 |
[
"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 a... | Pods on unreachable kubelets are deleted not evicted | https://api.github.com/repos/kubernetes/kubernetes/issues/91465/comments | 13 | 2020-05-26T19:07:06Z | 2021-01-28T14:51:20Z | https://github.com/kubernetes/kubernetes/issues/91465 | 625,118,799 | 91,465 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
With Kubernetes one can define storage classes with provisioners. How does one find which provisioners are installed and available in the cluster? I didn't find away to get this info.
**Why is this nee... | An ability to find installed storage provisioners | https://api.github.com/repos/kubernetes/kubernetes/issues/91464/comments | 6 | 2020-05-26T18:47:31Z | 2020-10-24T01:07:40Z | https://github.com/kubernetes/kubernetes/issues/91464 | 625,106,369 | 91,464 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
e2e tests detect whether PSP is enabled based on presence of PSP API objects. An addon that proactively includes a PSP in a manifest can trigger that detection and enable PSP-specific e2e tests that should not be run.
**What you expected to happen**:
In addition to detecting presence of PSP obje... | IsPodSecurityPolicyEnabled e2e test detection is fragile | https://api.github.com/repos/kubernetes/kubernetes/issues/91463/comments | 0 | 2020-05-26T16:50:50Z | 2020-06-04T04:20:44Z | https://github.com/kubernetes/kubernetes/issues/91463 | 625,032,337 | 91,463 |
[
"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**:
[This issue o... | Replace does not work for services | https://api.github.com/repos/kubernetes/kubernetes/issues/91459/comments | 37 | 2020-05-26T15:11:02Z | 2021-08-23T18:22:37Z | https://github.com/kubernetes/kubernetes/issues/91459 | 624,959,566 | 91,459 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
In VolumeManager's `MountVolume`, it has 2 operations, `WaitForAttach` and `MountDevice`. `WaitForAttach` is to do attach on the node, and `MountDevice` is to mount the attached volume to mount point. But there were no corresponding structures to record the results of successful attach.
Between ... | [kubelet - VolumeManager] the result/status of waitforattach is not recorded, which would cause attached devices being left on the node | https://api.github.com/repos/kubernetes/kubernetes/issues/91458/comments | 9 | 2020-05-26T14:22:12Z | 2020-10-25T04:34:42Z | https://github.com/kubernetes/kubernetes/issues/91458 | 624,922,720 | 91,458 |
[
"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 adding a... | HPA with external metric scales incorrectly | https://api.github.com/repos/kubernetes/kubernetes/issues/91457/comments | 2 | 2020-05-26T14:16:18Z | 2020-06-02T08:48:58Z | https://github.com/kubernetes/kubernetes/issues/91457 | 624,918,407 | 91,457 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
#### deployment
```
Name: xxx-server
Namespace: default
CreationTimestamp: Mon, 25 May 2020 14:47:02 +0800
Labels: app=xxx-server
Annotations: deployment.kubernetes.io/revision: 1
kubectl.kubernetes.io/las... | can't access service:port | https://api.github.com/repos/kubernetes/kubernetes/issues/91445/comments | 6 | 2020-05-26T10:10:38Z | 2020-06-11T02:44:15Z | https://github.com/kubernetes/kubernetes/issues/91445 | 624,766,369 | 91,445 |
[
"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/
-->
**Description**
API Server allows ad... | API Server supports insecure TLS ciphersuites | https://api.github.com/repos/kubernetes/kubernetes/issues/91444/comments | 38 | 2020-05-26T09:47:05Z | 2025-02-14T14:40:51Z | https://github.com/kubernetes/kubernetes/issues/91444 | 624,751,196 | 91,444 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
When execute kubectl attach and kuberctl exec commods in multiple containers, it will show to execute kubectl describe commod to see all of the containers in this pod.
``` shell
kubectl exec <pod-name> -- ls -al
Defaulting container name to <container-foo>.
Use 'kubectl de... | More accurate description in multiple containers | https://api.github.com/repos/kubernetes/kubernetes/issues/91441/comments | 3 | 2020-05-26T08:36:01Z | 2020-07-22T06:05:12Z | https://github.com/kubernetes/kubernetes/issues/91441 | 624,701,801 | 91,441 |
[
"kubernetes",
"kubernetes"
] | As we know, kubernetes apiserver proxy allow you to access Node/Pod/Service out of cluster with credentials. The format should following this [doc](https://kubernetes.io/docs/tasks/access-application-cluster/access-cluster/#manually-constructing-apiserver-proxy-urls) For example, services.
https://dns-xxxxxxx.io:443... | APIServer proxy to pod with muliple port and schema | https://api.github.com/repos/kubernetes/kubernetes/issues/91438/comments | 9 | 2020-05-26T07:18:00Z | 2020-10-09T18:28:36Z | https://github.com/kubernetes/kubernetes/issues/91438 | 624,654,848 | 91,438 |
[
"kubernetes",
"kubernetes"
] | Please read projectcalico/calico#3585
#62537
The above issue and the corresponding issue are similar but I am using iptables mode.
```
$ kubectl -n kube-system logs -f kube-proxy-7tk2x
W0525 07:12:49.579969 1 server_others.go:330] Flag proxy-mode="" unknown, assuming iptables proxy
I0525 07:12:49.799825... | Source ip is not preserved even though externalTrafficPolicy is Local | https://api.github.com/repos/kubernetes/kubernetes/issues/91437/comments | 9 | 2020-05-26T05:34:00Z | 2020-05-29T16:56:38Z | https://github.com/kubernetes/kubernetes/issues/91437 | 624,612,175 | 91,437 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
share custom indexer among controllers to improve the overall performance
**Why is this needed**:
xref: https://github.com/kubernetes/kubernetes/issues/88229#issuecomment-633341770
current attach detach controller has a custom indexer to index pods by PVC keys to avoid i... | share custom indexer among controllers to improve the overall performance | https://api.github.com/repos/kubernetes/kubernetes/issues/91436/comments | 10 | 2020-05-26T03:12:50Z | 2020-06-11T05:42:57Z | https://github.com/kubernetes/kubernetes/issues/91436 | 624,572,473 | 91,436 |
[
"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**:
···
23310 r... | dlv debug kube-apiserver the cpu is very high when execute step by step | https://api.github.com/repos/kubernetes/kubernetes/issues/91434/comments | 5 | 2020-05-26T02:54:06Z | 2020-10-23T04:47:39Z | https://github.com/kubernetes/kubernetes/issues/91434 | 624,567,443 | 91,434 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
- show a clearer message that better informs the user of a potential conflict between changes done declaratively vs imperatively on the same object, inform whether the changes have been applied, what m... | improve Warning: kubectl apply should be used on resource created by either kubectl create --save-config or kubectl apply | https://api.github.com/repos/kubernetes/kubernetes/issues/91425/comments | 5 | 2020-05-26T01:35:35Z | 2020-10-04T02:05:06Z | https://github.com/kubernetes/kubernetes/issues/91425 | 624,546,538 | 91,425 |
[
"kubernetes",
"kubernetes"
] | ### Flaky Job: pr:pull-kubernetes-kubemark-e2e-gce-big
Flakes in the past week: **25**
Consistency: **93.90%**
#### Flakiest tests by flake count:
| Test | Flake Count |
| --- | --- |
| Timeout | 15 |
| TearDown | 11 |
| ClusterLoaderV2 | 9 |
| Kubemark TearDown | 5 |
| testing/load/config.yaml | 4 |
#### Previousl... | pr:pull-kubernetes-kubemark-e2e-gce-big flaked 25 times in the past week | https://api.github.com/repos/kubernetes/kubernetes/issues/91421/comments | 6 | 2020-05-25T21:47:57Z | 2020-12-25T11:31:12Z | https://github.com/kubernetes/kubernetes/issues/91421 | 624,496,933 | 91,421 |
[
"kubernetes",
"kubernetes"
] | Opening as an follow up analysis from https://github.com/kubernetes/kubernetes/issues/91367
Merging #91260 unexpectedly resulted in a huge flakiness of at least one of the apimachinery tests: https://github.com/kubernetes/kubernetes/issues/91367
That is definitely unexpected, because that PR only changes the size ... | WatchCache may accept watches that it should not | https://api.github.com/repos/kubernetes/kubernetes/issues/91415/comments | 8 | 2020-05-25T18:23:22Z | 2020-05-26T20:38:12Z | https://github.com/kubernetes/kubernetes/issues/91415 | 624,432,987 | 91,415 |
[
"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 add podSecu... | SecurityContext windowsOptions doesn't work on kind:Deployment | https://api.github.com/repos/kubernetes/kubernetes/issues/91414/comments | 5 | 2020-05-25T17:31:04Z | 2020-09-25T15:02:34Z | https://github.com/kubernetes/kubernetes/issues/91414 | 624,414,660 | 91,414 |
[
"kubernetes",
"kubernetes"
] | Is there a way I can use the TLS/ certificate to validate my private docker registry while pulling the image during the pod creation in k8s ?
Currently we have to use the username and password to create the image pull secret, don't wann use this way.
/sig CLI | Use TLS verification to pull the image from private docker registry in k8s | https://api.github.com/repos/kubernetes/kubernetes/issues/91413/comments | 5 | 2020-05-25T17:21:46Z | 2021-01-30T05:29:38Z | https://github.com/kubernetes/kubernetes/issues/91413 | 624,411,400 | 91,413 |
[
"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**:
Tried to crea... | Cannot create pod with long name | https://api.github.com/repos/kubernetes/kubernetes/issues/91410/comments | 5 | 2020-05-25T14:47:11Z | 2020-10-22T22:41:38Z | https://github.com/kubernetes/kubernetes/issues/91410 | 624,344,556 | 91,410 |
[
"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 created sev... | API-server repair considers ports with same port number but different protocols as same | https://api.github.com/repos/kubernetes/kubernetes/issues/91404/comments | 14 | 2020-05-25T08:17:14Z | 2020-06-16T01:14:11Z | https://github.com/kubernetes/kubernetes/issues/91404 | 624,129,142 | 91,404 |
[
"kubernetes",
"kubernetes"
] | When I run kubeadm init, I get the following error.
**[preflight] Pulling images required for setting up a Kubernetes cluster
[preflight] This might take a minute or two, depending on the speed of your internet connection
[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'... | [ERROR ImagePull]: failed to pull image k8s.gcr.io | https://api.github.com/repos/kubernetes/kubernetes/issues/91402/comments | 10 | 2020-05-25T04:38:37Z | 2024-06-06T05:42:31Z | https://github.com/kubernetes/kubernetes/issues/91402 | 624,039,385 | 91,402 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
I am trying to set maxRetriesForOnFailurePolicy so that docker MaxRetryCount will be set via deployment
**What you expected to happen**:
```
annotations:
kubernetes.io/maxRetriesForOnFailurePolicy: "5"
```
the above line should set docker MaxRetryCount to 5
/sig/api-machinery | kubernetes.io/maxRetriesForOnFailurePolicy does not set the MaxRetryCount in Docker | https://api.github.com/repos/kubernetes/kubernetes/issues/91396/comments | 3 | 2020-05-24T16:05:51Z | 2020-05-24T22:22:52Z | https://github.com/kubernetes/kubernetes/issues/91396 | 623,893,808 | 91,396 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
I have a CRD which was working fine in 1.17. But it fails with in 1.18.
CRD YAML:
https://github.com/kubedb/apimachinery/blob/ok117/api/crds/kubedb.com_memcacheds.yaml
In 1.18, I get the following error:
```
Error: CustomResourceDefinition.apiextensions.k8s.io "memcacheds.kubedb.com" is i... | Default value not allowed for in x-kubernetes-list-map-keys | https://api.github.com/repos/kubernetes/kubernetes/issues/91395/comments | 15 | 2020-05-24T14:45:57Z | 2020-07-28T16:15:23Z | https://github.com/kubernetes/kubernetes/issues/91395 | 623,878,935 | 91,395 |
[
"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**:
--resource-... | kubectl set selector --resource-version has no effect | https://api.github.com/repos/kubernetes/kubernetes/issues/91391/comments | 6 | 2020-05-24T04:03:20Z | 2020-10-23T08:51:41Z | https://github.com/kubernetes/kubernetes/issues/91391 | 623,789,364 | 91,391 |
[
"kubernetes",
"kubernetes"
] | **Which jobs are flaking**:
kubernetes-e2e-gce
**Which test(s) are flaking**:
[sig-api-machinery] client-go should negotiate watch and report errors with accept "application/vnd.kubernetes.protobuf,application/json"
**Testgrid link**:
https://prow.k8s.io/view/gcs/kubernetes-jenkins/pr-logs/pull/90253/pull-kube... | '[sig-api-machinery] client-go should negotiate watch and report errors' is flaky | https://api.github.com/repos/kubernetes/kubernetes/issues/91379/comments | 3 | 2020-05-23T12:10:31Z | 2020-05-23T17:19:01Z | https://github.com/kubernetes/kubernetes/issues/91379 | 623,646,905 | 91,379 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
I think at least white/blacklisting the (Cluster)Roles that can are referenced by (Cluster)RoleBindings would be a good start for security minded clusters.
Also maybe restricting the ApiGroups/Resource... | Allow restricting scope of (Cluster)RoleBinding a user can create with RBAC | https://api.github.com/repos/kubernetes/kubernetes/issues/91376/comments | 4 | 2020-05-23T07:16:17Z | 2020-05-24T05:26:34Z | https://github.com/kubernetes/kubernetes/issues/91376 | 623,599,700 | 91,376 |
[
"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/
-->
## Versions
**kubeadm version** ... | external etcd cluster restarting and make api server crashed | https://api.github.com/repos/kubernetes/kubernetes/issues/91375/comments | 4 | 2020-05-23T06:17:20Z | 2020-05-23T19:37:25Z | https://github.com/kubernetes/kubernetes/issues/91375 | 623,592,164 | 91,375 |
Subsets and Splits
Unique Owner-Repo Count
Counts the number of unique owner-repos in the dataset, providing a basic understanding of diverse repositories.