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"
] | # error
Hey, All friends, my pod is exit with code 137 when i connect mysql in this pod.
# error message
```
command terminated with non-zero exit code: Error executing in Docker Container: 137
```
# environment
* kubernetes: 1.14.1
* docker: 18.0.9
* mysql: 5.7
* install method: helm
# What
![image](... | 137 exit code, but my limit is not set | https://api.github.com/repos/kubernetes/kubernetes/issues/77924/comments | 5 | 2019-05-15T12:05:58Z | 2019-05-16T06:52:41Z | https://github.com/kubernetes/kubernetes/issues/77924 | 444,400,741 | 77,924 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
Every k8s release most of the kube* binaries are build and loaded to github relases page. But for some reason, the kubeadm is not part of the list.
Can it be added?
(Alternativelly, hyperkube build)
... | add kubeadm to the releases binary/pakages list | https://api.github.com/repos/kubernetes/kubernetes/issues/77921/comments | 11 | 2019-05-15T10:08:19Z | 2019-07-09T11:37:14Z | https://github.com/kubernetes/kubernetes/issues/77921 | 444,350,522 | 77,921 |
[
"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**:
Warning Fail... | [EBS Volume (AWS) ]AttachVolume.Attach failed for volume "redis-data": error finding instance ip-10-10-178-213.cn-north-1.compute.internal: "instance not found" | https://api.github.com/repos/kubernetes/kubernetes/issues/77920/comments | 8 | 2019-05-15T09:54:51Z | 2020-08-05T00:30:32Z | https://github.com/kubernetes/kubernetes/issues/77920 | 444,343,915 | 77,920 |
[
"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**:
kubernetes ve... | RoleBinding with a ClusterRole not able to restrict permission in namespace | https://api.github.com/repos/kubernetes/kubernetes/issues/77919/comments | 2 | 2019-05-15T09:37:26Z | 2019-05-15T10:04:09Z | https://github.com/kubernetes/kubernetes/issues/77919 | 444,335,520 | 77,919 |
[
"kubernetes",
"kubernetes"
] | /kind bug
/kind feature
We are trying to configure vsphere cloud provider for kubernetes cluster, according to below support link for dynamic provisioning from vmware. There was no problem with kubernetres version v1.8, the issue appeared after deploying new kubernetes cluster with version 1.12.
https://vmware.g... | MountVolume.SetUp failed for volume pvc mount failed: exit status 32 | https://api.github.com/repos/kubernetes/kubernetes/issues/77916/comments | 2 | 2019-05-15T09:03:55Z | 2019-05-21T05:50:34Z | https://github.com/kubernetes/kubernetes/issues/77916 | 444,319,430 | 77,916 |
[
"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 ... | after azure disk attach succeeded, always return lun(-1) which is incorrect | https://api.github.com/repos/kubernetes/kubernetes/issues/77911/comments | 0 | 2019-05-15T08:25:56Z | 2019-05-16T15:48:55Z | https://github.com/kubernetes/kubernetes/issues/77911 | 444,302,454 | 77,911 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Simulated a node failure on my 3 master 1 worker cluster by pausing the second master in VirtualBox.
The round robin entry for a load balancer service of mine still has the pods IP that went down with the node (after an hour of waiting).
**What you expected to happen**:
I thought kube-proxy would... | kube-proxy ipvs doesn't update IPs after node failure | https://api.github.com/repos/kubernetes/kubernetes/issues/77903/comments | 21 | 2019-05-15T06:32:47Z | 2022-03-19T17:40:18Z | https://github.com/kubernetes/kubernetes/issues/77903 | 444,259,890 | 77,903 |
[
"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/
-->
I want to set kube-proxy bindaddress ... | Set kube-proxy bindaddress through kubeadm config file failed | https://api.github.com/repos/kubernetes/kubernetes/issues/77876/comments | 8 | 2019-05-14T17:45:18Z | 2019-05-20T01:26:04Z | https://github.com/kubernetes/kubernetes/issues/77876 | 444,043,590 | 77,876 |
[
"kubernetes",
"kubernetes"
] |
**What happened**:
Containers are getting terminated by systemd without respecting the `terminationGracePeriodSeconds` set in the pod yaml on reboot or shutdown of a node.
**What you expected to happen**:
`terminationGracePeriodSeconds` is respected by systemd when using systemd as the cgroup manager.
**Ho... | Stop timeout isn't respected at shutdown/reboot | https://api.github.com/repos/kubernetes/kubernetes/issues/77873/comments | 23 | 2019-05-14T16:50:13Z | 2020-03-25T23:24:35Z | https://github.com/kubernetes/kubernetes/issues/77873 | 444,020,806 | 77,873 |
[
"kubernetes",
"kubernetes"
] | The branch [`release-1.15`][branch] was just created.
Please update the [publishing-bot's configuration][config] to also publish this
new branch.
[branch]: https://github.com/kubernetes/kubernetes/tree/release-1.15
[config]: https://github.com/kubernetes/kubernetes/tree/master/staging/publishing
<!-- no assignments ... | Update publishing-bot for release-1.15 | https://api.github.com/repos/kubernetes/kubernetes/issues/77871/comments | 2 | 2019-05-14T15:58:05Z | 2019-05-14T18:21:33Z | https://github.com/kubernetes/kubernetes/issues/77871 | 443,997,524 | 77,871 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
Same as in this 2017 request:
https://github.com/kubernetes/kubernetes/issues/42481
In GCP service of type=LoadBalancer with port mappings is exposed but IP is in 'ephemeral' state, so the 'only' thing missing is to signal to the underlying platform provider e.g. via 'loadBal... | Attach a static IP by name to a service with type=LoadBalancer | https://api.github.com/repos/kubernetes/kubernetes/issues/77869/comments | 14 | 2019-05-14T15:16:08Z | 2020-01-06T11:20:00Z | https://github.com/kubernetes/kubernetes/issues/77869 | 443,975,187 | 77,869 |
[
"kubernetes",
"kubernetes"
] |
**What happened**:
We reached a corner case in our kubernetes cluster:
1. a network partition between kubelet and the apiserver. ALL our nodes unable to report to the apiserver (misconfiguration of the loadbalancer between kubelet and the apiserver).
2. As expected, after 40 seconds, all the nodes status turn to U... | All Pods on an unreachable node are marked NotReady upon the node turned Unknown | https://api.github.com/repos/kubernetes/kubernetes/issues/77864/comments | 19 | 2019-05-14T11:02:58Z | 2024-04-26T03:33:06Z | https://github.com/kubernetes/kubernetes/issues/77864 | 443,850,553 | 77,864 |
[
"kubernetes",
"kubernetes"
] | I have a problem with the resolution of name outside kubernetes (like google or api of service use) wouldn't update because the TTL of the records is setted to a value like 4292482298.
When kubedns' pod start the ttl is correctly setted to 300 and it is refreshed every 5 minutes.
With dig i'm monitoring the ttl count... | k8s-dns ttl never expire | https://api.github.com/repos/kubernetes/kubernetes/issues/77860/comments | 6 | 2019-05-14T10:20:29Z | 2019-07-11T22:52:03Z | https://github.com/kubernetes/kubernetes/issues/77860 | 443,832,346 | 77,860 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
1.set --maxim... | Init Container will be removed by kubeGC when we set --maximum-dead-containers-per-container=0 | https://api.github.com/repos/kubernetes/kubernetes/issues/77859/comments | 13 | 2019-05-14T09:12:09Z | 2019-10-19T20:41:16Z | https://github.com/kubernetes/kubernetes/issues/77859 | 443,799,677 | 77,859 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Duplicate ReplicaSetunder the managed Deploy in the cluster
**What you expected to happen**:
about kube-scheduler ?
**How to reproduce it (as minimally and precisely as possible)**:
i can not reproduce it by Fixed method
**Anything else we need to know?**:
**Environment**:
- Kubernetes ve... | Duplicate ReplicaSetunder the managed Deploy in the cluster | https://api.github.com/repos/kubernetes/kubernetes/issues/77858/comments | 6 | 2019-05-14T08:59:32Z | 2019-10-12T04:42:09Z | https://github.com/kubernetes/kubernetes/issues/77858 | 443,793,774 | 77,858 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
When I use ku... | kubectl logs with flag --since-time return logs before the timesamp | https://api.github.com/repos/kubernetes/kubernetes/issues/77856/comments | 9 | 2019-05-14T08:35:54Z | 2019-11-10T09:05:03Z | https://github.com/kubernetes/kubernetes/issues/77856 | 443,782,789 | 77,856 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
We are having a multi master (03 master nodes) setup with keepalived responsible for the master VIP. The setup is worked fine until last week, One of our master nodes (`kube1`) which was serving our vip got crashed last week causing outage to our kubernetes services.
Ideally, keepalive virtual... | HA master failover issues. | https://api.github.com/repos/kubernetes/kubernetes/issues/77850/comments | 5 | 2019-05-14T06:02:24Z | 2019-05-15T17:04:32Z | https://github.com/kubernetes/kubernetes/issues/77850 | 443,724,966 | 77,850 |
[
"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 ... | exit with 137 code, and not limit resource | https://api.github.com/repos/kubernetes/kubernetes/issues/77849/comments | 4 | 2019-05-14T04:53:25Z | 2019-05-14T14:47:01Z | https://github.com/kubernetes/kubernetes/issues/77849 | 443,709,626 | 77,849 |
[
"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**:
```
$ ls -l ... | `kubectl` ignores non-existing config file pointed by the `KUBECONFIG` environment variable | https://api.github.com/repos/kubernetes/kubernetes/issues/77826/comments | 7 | 2019-05-13T18:06:23Z | 2019-09-03T11:11:28Z | https://github.com/kubernetes/kubernetes/issues/77826 | 443,531,078 | 77,826 |
[
"kubernetes",
"kubernetes"
] | Hello,
I experienced weird situation where AWS classic ELB was changed.
I have this annotations on service (ingress service)
```
Annotations:
service.beta.kubernetes.io/aws-load-balancer-backend-protocol: http
service.beta.kubernetes.io/aws-load-balancer-proxy-protocol: *
service.beta.kubernetes.io/aws... | AWS ELB configuration changed | https://api.github.com/repos/kubernetes/kubernetes/issues/77813/comments | 8 | 2019-05-13T13:53:00Z | 2020-01-03T14:17:17Z | https://github.com/kubernetes/kubernetes/issues/77813 | 443,411,417 | 77,813 |
[
"kubernetes",
"kubernetes"
] | The attempt https://prow.k8s.io/view/gcs/kubernetes-jenkins/logs/ci-kubernetes-e2e-gce-scale-performance/1126965275330088960 has failed. I will write here when I find something.
/kind bug
/assign
/sig scalability
/cc @wojtek-t @mm4tt @krzysied | #1126965275330088960 of ci-kubernetes-e2e-gce-scale-performance has failed | https://api.github.com/repos/kubernetes/kubernetes/issues/77808/comments | 16 | 2019-05-13T12:40:08Z | 2019-08-12T09:10:22Z | https://github.com/kubernetes/kubernetes/issues/77808 | 443,376,120 | 77,808 |
[
"kubernetes",
"kubernetes"
] | # error
Hey, All friends, my pod is exit with code 137 when i connect mysql in this pod.
# error message
```
command terminated with non-zero exit code: Error executing in Docker Container: 137
```
# environment
* kubernetes: 1.14.1
* docker: 18.0.9
* mysql: 5.7
* install method: helm
# What
![image](... | container exit with code 137, and not limit resource | https://api.github.com/repos/kubernetes/kubernetes/issues/77806/comments | 1 | 2019-05-13T11:30:55Z | 2019-05-14T04:53:21Z | https://github.com/kubernetes/kubernetes/issues/77806 | 443,347,885 | 77,806 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
After upgrade a working cluster from 1.13.5 to 1.14.1 using the kubeadm upgrade apply command, kubelet started to spurt the following error messages :
`kubelet[2635221]: E0513 09:55:54.814239 2635221 reflector.go:126] k8s.io/client-go/informers/factory.go:133: Failed to list *v1beta1.RuntimeClass:... | Upgrading cluster running cri-o from 1.13.5 to 1.14.1 yields errors on runtimeclasses access | https://api.github.com/repos/kubernetes/kubernetes/issues/77801/comments | 21 | 2019-05-13T08:48:32Z | 2020-06-22T08:31:47Z | https://github.com/kubernetes/kubernetes/issues/77801 | 443,277,334 | 77,801 |
[
"kubernetes",
"kubernetes"
] | Hi ,all
I'm in order create k8s cluster into the virtualbox. but can't connect coredns from cluster networking . thanks for your help.
* version
```sh
~$ kubectl version
Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.1", GitCommit:"b7394102d6ef778017f2ca4046abbaa23b88c290", GitTreeState:"c... | busybox can't connect coredns service? | https://api.github.com/repos/kubernetes/kubernetes/issues/77800/comments | 9 | 2019-05-13T08:44:24Z | 2019-10-14T16:41:11Z | https://github.com/kubernetes/kubernetes/issues/77800 | 443,275,159 | 77,800 |
[
"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**:
kubernetes ... | KUBE_SERVER_PLATFORMS[@]: unbound variable building images on CircleCI | https://api.github.com/repos/kubernetes/kubernetes/issues/77799/comments | 4 | 2019-05-13T08:27:48Z | 2019-05-13T09:05:55Z | https://github.com/kubernetes/kubernetes/issues/77799 | 443,268,122 | 77,799 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
Some sort of digital signatures or checksums for add-ons to prevent malicious ones, similar to the way packaging works on Debian, etc.
**Why is this needed**:
To prevent packages being modified with malicious code | Checksums/signatures for add-ons | https://api.github.com/repos/kubernetes/kubernetes/issues/77789/comments | 9 | 2019-05-12T17:23:35Z | 2019-11-09T20:53:03Z | https://github.com/kubernetes/kubernetes/issues/77789 | 443,127,287 | 77,789 |
[
"kubernetes",
"kubernetes"
] | The `PodSecurityContext` type has a field called `RunAsNonRoot` to indicate that a container must run as non-root user. The description for this field includes the sentence `If unset or false, no such validation will be performed.`, which would mean that setting the field to `false` or to `nil` (unset) have the same ef... | PodSecurityContext RunAsNonRoot API description does not reflect implementation | https://api.github.com/repos/kubernetes/kubernetes/issues/77787/comments | 9 | 2019-05-12T15:52:25Z | 2019-12-04T07:41:09Z | https://github.com/kubernetes/kubernetes/issues/77787 | 443,119,027 | 77,787 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs -->
**Which jobs are failing**:
* ci-kubernetes-e2e-gce-master-new-downgrade-cluster
* ci-kubernetes-e2e-gce-master-new-downgrade-cluster-parallel
**Since when has it been failing**:
These jobs have been failing... | [Failing Tests] cluster downgrade e2e tests are timing out | https://api.github.com/repos/kubernetes/kubernetes/issues/77784/comments | 2 | 2019-05-12T00:06:29Z | 2019-05-30T18:08:50Z | https://github.com/kubernetes/kubernetes/issues/77784 | 443,048,160 | 77,784 |
[
"kubernetes",
"kubernetes"
] | I execute this command in the chrome browser:
https://127.0.0.1:10250/exec/default/nginx/21709854-5ae5-4917-899c-91b0e2913741/nginx?command=ls&output=1&stderr=1
The result returned is:
Upgrade request required
How do I need to change to get the results back correctly? | about exec command | https://api.github.com/repos/kubernetes/kubernetes/issues/77776/comments | 1 | 2019-05-11T15:09:13Z | 2019-05-11T16:03:29Z | https://github.com/kubernetes/kubernetes/issues/77776 | 443,004,094 | 77,776 |
[
"kubernetes",
"kubernetes"
] | IETF is working on a draft version for TCP which is an extension for Multipath Operation with Multiple Addresses "draft-ietf-mptcp-rfc6824bis-15"
Reference
https://tools.ietf.org/html/draft-ietf-mptcp-rfc6824bis-15
Currently, I am aware that Kubernetes does not support multi-homing and list it as non-goal item... | Support for MPTCP, Multipath in TCP protocol | https://api.github.com/repos/kubernetes/kubernetes/issues/77771/comments | 8 | 2019-05-11T12:08:52Z | 2019-10-20T06:51:15Z | https://github.com/kubernetes/kubernetes/issues/77771 | 442,986,527 | 77,771 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
This is on a cluster that I upgrade from 1.11.10 to 1.12.8. It's not clear whether the upgrade is related to the issue or not.
I am seeing apiserver repeatedly fail and be restarted, with this error:
```
Unable to perform initial IP allocation check: unable to refresh the service IP block: Get ... | DNS hostname "localhost" causes failing apiserver | https://api.github.com/repos/kubernetes/kubernetes/issues/77764/comments | 19 | 2019-05-10T23:05:52Z | 2019-11-09T04:37:29Z | https://github.com/kubernetes/kubernetes/issues/77764 | 442,922,909 | 77,764 |
[
"kubernetes",
"kubernetes"
] | While discussing https://github.com/kubernetes/enhancements/pull/737#discussion_r277895607, we came across a problem that is - the fact that a volume requires remount is tracked inside Actual State of World and not desired state of the world.
Resize required is also currently tracked inside ASOW. Resize required is ... | Remount requires flag should be tracked inside desired state of world | https://api.github.com/repos/kubernetes/kubernetes/issues/77758/comments | 11 | 2019-05-10T20:41:10Z | 2020-03-09T02:50:44Z | https://github.com/kubernetes/kubernetes/issues/77758 | 442,886,761 | 77,758 |
[
"kubernetes",
"kubernetes"
] | Found this last night while adding storage revision integration tests CRDs.
When a CRD is updated, the rest storage for the [old version of the CRD is torn down](https://github.com/kubernetes/kubernetes/blob/07e3b7cdcac30c513d40f5d16f43bc4d2f869f67/staging/src/k8s.io/apiextensions-apiserver/pkg/apiserver/customresou... | Transient custom resource failures during CRD storage version update | https://api.github.com/repos/kubernetes/kubernetes/issues/77752/comments | 3 | 2019-05-10T19:46:03Z | 2019-05-10T19:53:31Z | https://github.com/kubernetes/kubernetes/issues/77752 | 442,869,076 | 77,752 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
For plugins to be more extensible, scheduler framework should expose more scheduler state as part of the framework handle. Examples could be the scheduling queue, or informers.
**Why is this needed**:... | Scheduler framework handle should have more of scheduler's state | https://api.github.com/repos/kubernetes/kubernetes/issues/77746/comments | 10 | 2019-05-10T17:12:22Z | 2019-10-11T08:22:26Z | https://github.com/kubernetes/kubernetes/issues/77746 | 442,815,130 | 77,746 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
Currently when creating a service of type loadbalancer in AWS the service can be configured to whitelist IP ranges. This is done via the annotation `service.beta.kubernetes.io/load-balancer-source-rang... | Support ipv6 cidr block when creating load balancer security group | https://api.github.com/repos/kubernetes/kubernetes/issues/77745/comments | 8 | 2019-05-10T16:29:52Z | 2021-05-27T05:31:58Z | https://github.com/kubernetes/kubernetes/issues/77745 | 442,800,302 | 77,745 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
When creating an EBS volume, we're currently waiting for the volume be in the correct state before proceeding:
https://github.com/kubernetes/kubernetes/blob/88ed776c6b447b1882a5fe99df0cfcaba1da4e72/staging/src/k8s.io/legacy-cloud-providers/aws/aws.go#L2398-L2421
However, we're using the inte... | EBS API polling when creating a volume | https://api.github.com/repos/kubernetes/kubernetes/issues/77741/comments | 1 | 2019-05-10T14:12:43Z | 2019-07-09T15:26:05Z | https://github.com/kubernetes/kubernetes/issues/77741 | 442,740,338 | 77,741 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
Liveness/Readiness checks for external Endpoints.
As I understand, kube-proxy does load-balancing over `Endpoints` with multiple targets like
```
apiVersion: v1
kind: Endpoints
metadata:
nam... | Liveness/Readiness check for external Endpoints Services | https://api.github.com/repos/kubernetes/kubernetes/issues/77738/comments | 4 | 2019-05-10T13:00:24Z | 2019-05-12T03:21:45Z | https://github.com/kubernetes/kubernetes/issues/77738 | 442,708,020 | 77,738 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
When creating a PVC in a storage class managed by [Rook](https://github.com/rook/rook/), it is provisioned (by the rook operator) with a delay varying between 0.5 and 15s.
**What you expected to happen**:
The PVC is provisioned immediately.
**How to reproduce it (as minimally and precisel... | PVC provisioning delay between 0.5 and 15s | https://api.github.com/repos/kubernetes/kubernetes/issues/77737/comments | 14 | 2019-05-10T12:56:13Z | 2019-10-13T11:12:09Z | https://github.com/kubernetes/kubernetes/issues/77737 | 442,706,278 | 77,737 |
[
"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 current... | NodeLifecycleController is overloading kube-apiserver | https://api.github.com/repos/kubernetes/kubernetes/issues/77733/comments | 32 | 2019-05-10T11:34:29Z | 2019-11-07T15:53:11Z | https://github.com/kubernetes/kubernetes/issues/77733 | 442,673,275 | 77,733 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
Make preemption and pod priorities per namespace.
**Why is this needed**:
Clusters use namespaces for dev/prod division, or even multi-tenancy. It would be good to not consider pods in a production na... | Make preemption and priorities per namespace | https://api.github.com/repos/kubernetes/kubernetes/issues/77732/comments | 8 | 2019-05-10T09:16:29Z | 2019-10-07T13:54:46Z | https://github.com/kubernetes/kubernetes/issues/77732 | 442,619,574 | 77,732 |
[
"kubernetes",
"kubernetes"
] | PLEG is not healthy: pleg was last seen active 3m3.928932625s ago; threshold is 3m0s
| PLEG is not healthy | https://api.github.com/repos/kubernetes/kubernetes/issues/77728/comments | 11 | 2019-05-10T08:04:26Z | 2020-01-05T12:02:30Z | https://github.com/kubernetes/kubernetes/issues/77728 | 442,590,465 | 77,728 |
[
"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... | Is it possible for a PV to be mounted on the same node twice | https://api.github.com/repos/kubernetes/kubernetes/issues/77727/comments | 5 | 2019-05-10T07:51:47Z | 2019-10-07T09:50:45Z | https://github.com/kubernetes/kubernetes/issues/77727 | 442,585,695 | 77,727 |
[
"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... | Share one master node across multiple clusters | https://api.github.com/repos/kubernetes/kubernetes/issues/77725/comments | 3 | 2019-05-10T07:19:28Z | 2019-05-10T13:00:55Z | https://github.com/kubernetes/kubernetes/issues/77725 | 442,574,142 | 77,725 |
[
"kubernetes",
"kubernetes"
] | I noticed that kube-scheduler --policy-config-file flag is labeled DEPRECATED since v1.11.
Without --policy-config-file flag, if I want to use shcheduler extender to add new scheduling rules, how should i do ?
| kube-scheduler --policy-config-file flag is labeled DEPRECATED | https://api.github.com/repos/kubernetes/kubernetes/issues/77724/comments | 8 | 2019-05-10T07:05:23Z | 2020-06-26T13:01:19Z | https://github.com/kubernetes/kubernetes/issues/77724 | 442,569,284 | 77,724 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
We can use `--max-requests-inflight --max-mutating-requests-inflight` to control the number of the requests. But if too many request about event ,or we use `--etcd-servers-overrides` to override the eve... | Add max-requests-inflight of event request | https://api.github.com/repos/kubernetes/kubernetes/issues/77723/comments | 9 | 2019-05-10T07:00:41Z | 2019-10-10T12:30:09Z | https://github.com/kubernetes/kubernetes/issues/77723 | 442,567,800 | 77,723 |
[
"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**:
Following azu... | some azure metrics are wrong | https://api.github.com/repos/kubernetes/kubernetes/issues/77721/comments | 0 | 2019-05-10T05:54:44Z | 2019-05-13T10:42:14Z | https://github.com/kubernetes/kubernetes/issues/77721 | 442,549,894 | 77,721 |
[
"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**:
Azure cloud... | Some service tags are not supported from Azure LoadBalancer services | https://api.github.com/repos/kubernetes/kubernetes/issues/77717/comments | 1 | 2019-05-10T05:14:52Z | 2019-05-10T10:45:59Z | https://github.com/kubernetes/kubernetes/issues/77717 | 442,541,751 | 77,717 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
After fixing golint failures under `test/e2e` (now still in progress), we need to put `gomega` for each `Expect()` and `HaveOccurred()`.
Then common error checking code has become like:
`gomega.Expect(err).To(gomega.HaveOccurred())`
We can replace this code with `framework.ExpectError(err)`... | Use framework.ExpectError() for e2e tests | https://api.github.com/repos/kubernetes/kubernetes/issues/77706/comments | 15 | 2019-05-10T01:13:39Z | 2019-07-03T02:47:32Z | https://github.com/kubernetes/kubernetes/issues/77706 | 442,496,247 | 77,706 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
The metrics-server is unable to get metrics for pods with init containers.
**What you expected to happen**:
Metrics for pods with init containers show up.
**How to reproduce it (as minimally and precisely as possible)**:
Create a pod with an init container. Metrics are not gathered for that ... | initContainer metrics fail for cri-o runtime | https://api.github.com/repos/kubernetes/kubernetes/issues/77700/comments | 8 | 2019-05-09T21:39:08Z | 2020-01-06T00:14:49Z | https://github.com/kubernetes/kubernetes/issues/77700 | 442,447,596 | 77,700 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
Cache resource requests per Pod per resource name (using a map) and pass it to calls of requirements.subtract() in getPodsToPreempt of preemption
**Why is this needed**:
In requirements.subtract(), we iterate over all containers of the Pod to calculate new quantity.
Such itera... | Cache resource requests per Pod per resource name in getPodsToPreempt | https://api.github.com/repos/kubernetes/kubernetes/issues/77697/comments | 5 | 2019-05-09T20:54:49Z | 2019-05-18T15:28:02Z | https://github.com/kubernetes/kubernetes/issues/77697 | 442,429,301 | 77,697 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
The feature that would be interested to add is the capacity to prevent all pods in certain namespaces to be scheduled on some worker with a specific label.
**Why is this needed**:
It's needed notably in the case of a kubernetes multi-tenant cluster. Let's imagine a specific... | Taint toleration configured on namespace level | https://api.github.com/repos/kubernetes/kubernetes/issues/77687/comments | 5 | 2019-05-09T18:25:29Z | 2019-05-13T02:53:48Z | https://github.com/kubernetes/kubernetes/issues/77687 | 442,370,460 | 77,687 |
[
"kubernetes",
"kubernetes"
] | I ran this command:
```bash
kubectl describe service --output=json
```
and it says
```console
unknown flag: --output
```
I would expect this command to optionally output json.
@kubernetes/sig-cli-feature-requests
| The following command does not recognize the --output=json flag | https://api.github.com/repos/kubernetes/kubernetes/issues/77683/comments | 3 | 2019-05-09T17:42:28Z | 2019-05-09T23:01:35Z | https://github.com/kubernetes/kubernetes/issues/77683 | 442,353,478 | 77,683 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
This is a followup on #64393 , since it only added the new CNI capabilities to the dockershim. They shoud be added to the CRI too
**Why is this needed**:
Runtimes should have at least feature pari... | Take advantage of new CNI capabilities | https://api.github.com/repos/kubernetes/kubernetes/issues/77682/comments | 9 | 2019-05-09T17:31:34Z | 2019-05-17T18:37:35Z | https://github.com/kubernetes/kubernetes/issues/77682 | 442,349,287 | 77,682 |
[
"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 a Vmware n... | When a Vmware node goes down, Kubernetes is unaware and PV isn't released | https://api.github.com/repos/kubernetes/kubernetes/issues/77678/comments | 9 | 2019-05-09T16:33:04Z | 2019-12-10T22:00:17Z | https://github.com/kubernetes/kubernetes/issues/77678 | 442,326,628 | 77,678 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
If a `kubectl-foo` plugin binary exists, both `kubectl foo -n namespace` and `kubectl -n namespace foo` should work. Currently, only the first command would call the plugin binary, the second one would ... | Kubectl plugins: support global options | https://api.github.com/repos/kubernetes/kubernetes/issues/77666/comments | 34 | 2019-05-09T15:03:31Z | 2020-12-12T18:32:59Z | https://github.com/kubernetes/kubernetes/issues/77666 | 442,284,890 | 77,666 |
[
"kubernetes",
"kubernetes"
] | ## What happened:
During https://github.com/kubernetes/kubernetes/pull/75917 we discovered a failing test because of wrong int/float conversion on apply.
The problem got traced to how a json string gets decoded by sigs.k8s.io/yaml.
The string is:
```
{
"apiVersion": "v1",
"kind": "Service",
"metadata"... | Possible bug when decoding yaml/json into unstructured | https://api.github.com/repos/kubernetes/kubernetes/issues/77665/comments | 9 | 2019-05-09T14:29:03Z | 2020-12-01T23:47:03Z | https://github.com/kubernetes/kubernetes/issues/77665 | 442,267,124 | 77,665 |
[
"kubernetes",
"kubernetes"
] | We are trying to configure vsphere cloud provider according to below support link for dynamic provisioning from vmware. There was no problem with kubernetres version v1.8, the issue appeared after deploying new kubernetes cluster with version 1.12.
https://vmware.github.io/vsphere-storage-for-kubernetes/documentatio... | vsphere_volume_util.go:187] Cloud provider not initialized properly | https://api.github.com/repos/kubernetes/kubernetes/issues/77663/comments | 29 | 2019-05-09T14:09:38Z | 2019-10-22T05:57:35Z | https://github.com/kubernetes/kubernetes/issues/77663 | 442,257,460 | 77,663 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
Allow `services` to be filtered by `spec.type`.
```
[rodencor@karminac ~]$ kubectl get svc --all-namespaces --field-selector=spec.type=LoadBalancer
Error from server (BadRequest): Unable to find "/... | Support service type as a field selector | https://api.github.com/repos/kubernetes/kubernetes/issues/77662/comments | 23 | 2019-05-09T14:03:45Z | 2024-04-21T22:50:28Z | https://github.com/kubernetes/kubernetes/issues/77662 | 442,254,508 | 77,662 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
I am interested in reducing the amount of time it takes for an endpoint to be removed from a service when a worker node goes down. I know that the --node-monitor-grace-period can be reduced from the default of 40s, but I'm more interested in a way to trigger this through the API.... | Add mechanism to tell kubernetes that a node has gone down | https://api.github.com/repos/kubernetes/kubernetes/issues/77660/comments | 15 | 2019-05-09T13:20:47Z | 2019-10-20T20:04:14Z | https://github.com/kubernetes/kubernetes/issues/77660 | 442,233,415 | 77,660 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
We observed... | In HA setup, nodes are becoming NotReady in case of single master outage | https://api.github.com/repos/kubernetes/kubernetes/issues/77658/comments | 6 | 2019-05-09T13:09:45Z | 2020-01-03T07:10:21Z | https://github.com/kubernetes/kubernetes/issues/77658 | 442,228,317 | 77,658 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Kubelet had crashed one one of the heavily loaded instances in AWS EC2 cluster (r4.8xlarge).
Logs show the following traceback:
```
May 9 00:12:17 ip-10-117-0-156.eu-west-1.compute.internal kubelet: panic: runtime error: invalid memory address or nil pointer dereference
May 9 00:12:17 ip-10... | Kubelet crashing with SIGSEGV under load | https://api.github.com/repos/kubernetes/kubernetes/issues/77655/comments | 4 | 2019-05-09T11:58:13Z | 2019-05-10T00:52:24Z | https://github.com/kubernetes/kubernetes/issues/77655 | 442,199,201 | 77,655 |
[
"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**:
Docker daemon... | Kubelet restarts Docker daemon frequently in AWS M5 instances | https://api.github.com/repos/kubernetes/kubernetes/issues/77654/comments | 6 | 2019-05-09T11:42:49Z | 2019-05-12T04:34:49Z | https://github.com/kubernetes/kubernetes/issues/77654 | 442,193,560 | 77,654 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
This all happened in a `GKE 1.13.5-gke.10` alpha cluster.
1. `kube-proxy` stopped working and inspecting the logs showed messages like:
```
E0509 02:05:11.750695 6 reflector.go:125] k8s.io/client-go/informers/factory.go:132: Failed to list *v1.Service: Unauthorized
E0509 02:05:11.75521... | BoundServiceAccountTokenVolume: kube-proxy doesn't reload ServiceAccount tokens | https://api.github.com/repos/kubernetes/kubernetes/issues/77651/comments | 6 | 2019-05-09T10:23:59Z | 2019-06-12T01:10:55Z | https://github.com/kubernetes/kubernetes/issues/77651 | 442,163,333 | 77,651 |
[
"kubernetes",
"kubernetes"
] | **What happened**: we have a 3 master node setup with 2 CoreDNS pods (default setup). In case of a single node failure (killing the node that hosted one of the CoreDNS pods) DNS resolve stops working for 5 minutes. After the failed node reports 'NotReady', the CoreDNS still reports happy, and after 5mins the pod re-cre... | No DNS resolve for 5 min after node failure (CoreDNS) | https://api.github.com/repos/kubernetes/kubernetes/issues/77650/comments | 15 | 2019-05-09T09:09:23Z | 2019-06-14T06:22:08Z | https://github.com/kubernetes/kubernetes/issues/77650 | 442,130,601 | 77,650 |
[
"kubernetes",
"kubernetes"
] | Set namespace of monitoring, and Deployed a DaemonSet with no node selector, but it's not running in all of them. Does DaemonSet only work in namespace of kube-system?
my yaml as follows:
```
apiVersion: apps/v1
kind: DaemonSet
metadata:
name: fluentd-es-v2.5.0
#namespace: kube-system
namespace: monitorin... | Does DaemonSet only work in namespace of kube-system? | https://api.github.com/repos/kubernetes/kubernetes/issues/77648/comments | 3 | 2019-05-09T07:49:46Z | 2019-05-09T08:50:50Z | https://github.com/kubernetes/kubernetes/issues/77648 | 442,097,639 | 77,648 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Kubeadm fails to register node and results in the following error --
\# kubeadm init phase upload-config kubelet -v 10
I0509 12:17:06.897161 13262 initconfiguration.go:105] detected and using CRI socket: /var/run/dockershim.sock
I0509 12:17:06.897514 13262 interface.go:384] Looking... | kubeadm fails with error execution phase upload-config/kubelet: Error writing Crisocket information for the control-plane node: timed out waiting for the condition | https://api.github.com/repos/kubernetes/kubernetes/issues/77646/comments | 13 | 2019-05-09T07:22:44Z | 2020-03-02T13:16:22Z | https://github.com/kubernetes/kubernetes/issues/77646 | 442,087,404 | 77,646 |
[
"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 create a jo... | InitContainer exec failed when job-pod start, the Restartcount can't used for backoffLimit | https://api.github.com/repos/kubernetes/kubernetes/issues/77644/comments | 2 | 2019-05-09T07:12:53Z | 2019-05-21T04:56:39Z | https://github.com/kubernetes/kubernetes/issues/77644 | 442,084,116 | 77,644 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
`kubectl expl... | explain deployment.spec.strategy.rollingUpdate.maxSurge and maxUnavailable wrong defaults | https://api.github.com/repos/kubernetes/kubernetes/issues/77641/comments | 3 | 2019-05-09T06:44:01Z | 2019-05-09T23:08:54Z | https://github.com/kubernetes/kubernetes/issues/77641 | 442,074,725 | 77,641 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
pods schedule... | pods scheduled to nodes having a high number of mount points take long time to startup | https://api.github.com/repos/kubernetes/kubernetes/issues/77638/comments | 6 | 2019-05-09T06:03:32Z | 2020-02-11T23:03:51Z | https://github.com/kubernetes/kubernetes/issues/77638 | 442,063,636 | 77,638 |
[
"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**:
pods schedule... | pods scheduled to nodes having a high number of mounting points take long time to startup | https://api.github.com/repos/kubernetes/kubernetes/issues/77637/comments | 1 | 2019-05-09T05:52:55Z | 2019-05-09T06:01:27Z | https://github.com/kubernetes/kubernetes/issues/77637 | 442,061,102 | 77,637 |
[
"kubernetes",
"kubernetes"
] | This task is to start adopting distroless static images wherever possible in the `test/images` directory.
thread from: https://github.com/kubernetes/kubernetes/pull/77625#issuecomment-490747530 | Migrate test/images to use distroless static image wherever possible | https://api.github.com/repos/kubernetes/kubernetes/issues/77635/comments | 7 | 2019-05-09T05:31:17Z | 2019-10-06T07:24:48Z | https://github.com/kubernetes/kubernetes/issues/77635 | 442,056,254 | 77,635 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
As a develope... | The comments on SharedInformer are inadequate | https://api.github.com/repos/kubernetes/kubernetes/issues/77634/comments | 1 | 2019-05-09T04:45:44Z | 2019-05-10T04:44:25Z | https://github.com/kubernetes/kubernetes/issues/77634 | 442,047,398 | 77,634 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
For example, I have an existing configmap, configured like this:
`
apiVersion: v1
kind: ConfigMap
metadata:
name: a-config
data:
application.properties: |-
test.name=aaa
`
Then, in the... | Allows configmap to reference existing configmap | https://api.github.com/repos/kubernetes/kubernetes/issues/77632/comments | 5 | 2019-05-09T03:37:19Z | 2019-05-10T02:36:09Z | https://github.com/kubernetes/kubernetes/issues/77632 | 442,034,570 | 77,632 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
`LimitRange` was applied to my namespaces with existing pods running. Most of these are lightweight but a few had resource `requests` that exceeded the new `limit`.
For example, an existing container would have:
```
resources:
requests:
cpu: "200m"
... | Existing pods after restrictive LimitRange applied may cause issues | https://api.github.com/repos/kubernetes/kubernetes/issues/77629/comments | 16 | 2019-05-09T02:31:49Z | 2020-08-24T11:51:51Z | https://github.com/kubernetes/kubernetes/issues/77629 | 442,021,545 | 77,629 |
[
"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... | Measuring the period of downtime when upgrading kubeadm from version 1.13.0 to v1.14.0 | https://api.github.com/repos/kubernetes/kubernetes/issues/77628/comments | 4 | 2019-05-09T02:17:29Z | 2019-05-09T16:49:31Z | https://github.com/kubernetes/kubernetes/issues/77628 | 442,018,550 | 77,628 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
`kubectl log` for kubeapiserver, schedulers and controllermanager only show startup and "stale" data.
**What you expected to happen**:
I expected to see all the logs as they are logged
**How to reproduce it (as minimally and precisely as possible)**:
`kubectl log kube-apiserver-pod-name -... | Kube Components no longer log to STDERR/STDOUT | https://api.github.com/repos/kubernetes/kubernetes/issues/77624/comments | 13 | 2019-05-09T01:19:21Z | 2019-11-18T23:26:00Z | https://github.com/kubernetes/kubernetes/issues/77624 | 442,007,607 | 77,624 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
kubelet doesn't seem to be able to manage containers started with CRI-O any more
I'm testing kubelet + CRI-O on an Ubuntu 18.04 server installation, inside a qemu/kvm VM managed by Vagrant (see https://github.com/olberger/vagrant-k8s-kubevirt-katacontainers/tree/539c9d06ffa611aa2d08da6cfa617d42... | kubelet fails starting CRI-O containers (Ubuntu 18.04 + systemd cgroups driver) | https://api.github.com/repos/kubernetes/kubernetes/issues/77615/comments | 35 | 2019-05-08T20:50:15Z | 2019-05-15T23:35:25Z | https://github.com/kubernetes/kubernetes/issues/77615 | 441,925,937 | 77,615 |
[
"kubernetes",
"kubernetes"
] | The total provisioning time metrics introduced here - https://github.com/kubernetes/kubernetes/pull/66389 are not acurate. This is because, they only measure single execution of provisioning(and deletion) and do not count retries.
These should instead time, total time taken when first PVC was created and time when ... | Total provisioning metrics are not correct | https://api.github.com/repos/kubernetes/kubernetes/issues/77608/comments | 2 | 2019-05-08T16:51:00Z | 2019-06-01T03:45:14Z | https://github.com/kubernetes/kubernetes/issues/77608 | 441,830,940 | 77,608 |
[
"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 pod name ... | Pod name is missing in suggested cmd usage when executing `kubectl attach` | https://api.github.com/repos/kubernetes/kubernetes/issues/77604/comments | 1 | 2019-05-08T16:03:33Z | 2019-05-20T15:05:21Z | https://github.com/kubernetes/kubernetes/issues/77604 | 441,811,862 | 77,604 |
[
"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**:
Docker has ... | Pod logs: long lines are corrupted when using timestamps=true | https://api.github.com/repos/kubernetes/kubernetes/issues/77603/comments | 41 | 2019-05-08T15:33:09Z | 2022-11-02T02:59:52Z | https://github.com/kubernetes/kubernetes/issues/77603 | 441,797,514 | 77,603 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs -->
**Which jobs are failing**:
ci-kubernetes-kubemark-gce-scale
**Which test(s) are failing**:
Density test
**Since when has it been failing**:
Run 1125829298771464196. 2019-05-07 18:27:02 +0000 UTC
**Te... | [Failing Test] Kubemark-5000 | https://api.github.com/repos/kubernetes/kubernetes/issues/77602/comments | 6 | 2019-05-08T15:31:11Z | 2019-05-10T07:09:32Z | https://github.com/kubernetes/kubernetes/issues/77602 | 441,796,612 | 77,602 |
[
"kubernetes",
"kubernetes"
] | **Which jobs are failing**:
https://prow.k8s.io/view/gcs/kubernetes-jenkins/logs/ci-kubernetes-integration-master/1126051507540594695
**Which test(s) are failing**:
scheduler.TestUnreservePlugin
**Since when has it been failing**:
Ran 9 times between 5/6 and 5/7, succeeding only once. Not present anywhere else... | [Flaking Tests] scheduler.TestUnreservePlugin flaking in ci-kubernetes-integration-master | https://api.github.com/repos/kubernetes/kubernetes/issues/77601/comments | 7 | 2019-05-08T15:14:52Z | 2019-05-11T23:07:53Z | https://github.com/kubernetes/kubernetes/issues/77601 | 441,788,677 | 77,601 |
[
"kubernetes",
"kubernetes"
] | Once it is possible to opt out of secret based SA tokens, any preexisting secrets should be removed.
Action items:
1. Clean up legacy tokens for the controller service accounts after a release
/sig auth
/sig api-machinery
@kubernetes/sig-auth-feature-requests
xref: #70679 #71275 #72179 #77599
/prior... | Token request: proactively remove unused secret based SA tokens | https://api.github.com/repos/kubernetes/kubernetes/issues/77600/comments | 9 | 2019-05-08T15:14:37Z | 2021-11-04T15:17:19Z | https://github.com/kubernetes/kubernetes/issues/77600 | 441,788,555 | 77,600 |
[
"kubernetes",
"kubernetes"
] | The controller manager will optionally use the `TokenRequest` API to provision tokens for controllers. These SA based controllers no longer need secret based tokens.
Action items:
1. Determine how to opt out of the token controller generated secrets (generically)
1. Use the above generic functionality to make i... | Token request: opt out of the token controller generated secrets | https://api.github.com/repos/kubernetes/kubernetes/issues/77599/comments | 11 | 2019-05-08T15:11:04Z | 2021-11-04T15:17:12Z | https://github.com/kubernetes/kubernetes/issues/77599 | 441,786,822 | 77,599 |
[
"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**:
ReplicaSet le... | ReplicaSet leaves inactive pod not counted in its replicas | https://api.github.com/repos/kubernetes/kubernetes/issues/77597/comments | 11 | 2019-05-08T14:30:05Z | 2019-08-05T20:17:38Z | https://github.com/kubernetes/kubernetes/issues/77597 | 441,765,923 | 77,597 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
daemon controller should have the ability to control the max replicas of its pods
**Why is this needed**:
Now when we first create a daemonset, the pods created immediately on all nodes selected by d... | DaemonSet pods should be created gracefully when first create daemonset | https://api.github.com/repos/kubernetes/kubernetes/issues/77594/comments | 11 | 2019-05-08T13:27:24Z | 2019-10-10T15:06:02Z | https://github.com/kubernetes/kubernetes/issues/77594 | 441,734,950 | 77,594 |
[
"kubernetes",
"kubernetes"
] | Hi,
I have brought up minikube setup over AWS EC2 instance . I provisioned EBS Volumes using dynamicstorageclasss option . PVC creation is successful . (verified EBS volume also got created from AWS WUI) .
But when i try to create by application deployment my pod fails with the below error
AttachVolume.Attach fa... | Not able to Attach Volume using minikube hosted in AWS EC2 instance | https://api.github.com/repos/kubernetes/kubernetes/issues/77591/comments | 5 | 2019-05-08T13:03:52Z | 2020-01-03T08:11:14Z | https://github.com/kubernetes/kubernetes/issues/77591 | 441,724,489 | 77,591 |
[
"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 create... | when user tries to access kubectl get pods error "The connection to the server localhost:8080 was refused - did you specify the right host or port?" | https://api.github.com/repos/kubernetes/kubernetes/issues/77588/comments | 4 | 2019-05-08T09:45:07Z | 2019-05-08T13:10:45Z | https://github.com/kubernetes/kubernetes/issues/77588 | 441,645,534 | 77,588 |
[
"kubernetes",
"kubernetes"
] | Hello @justinsb , I have saw the commit `c741b8f3ae8d68a22d556b509979fa4e1a5fa7f7`, can we check the `TargetPort` for enqueue to serivce cotnroller work queue?
basecause of, In many case for Public Cloud, We always abstract a set for health checks
, such as TargetGroup in AWS, instanceGroup in aliyun. We can map ... | if update the TargetPort can I set the item into service controller work enqueue ? | https://api.github.com/repos/kubernetes/kubernetes/issues/77586/comments | 1 | 2019-05-08T08:56:22Z | 2019-06-22T01:52:13Z | https://github.com/kubernetes/kubernetes/issues/77586 | 441,624,674 | 77,586 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**: An E2E test to verify the pod scheduling and execution behavior on NodeAffinity type "prefferedDuringSchedulingIgnoredDuringExecution"
**Why is this needed**: The proposed test ensures that the scheduling and execution behavior of the pod on the nodes is verified for Node Affinit... | E2E Proposal: To verify 'preferredDuringSchedulingIgnoredDuringExecution' Node Affinity type | https://api.github.com/repos/kubernetes/kubernetes/issues/77581/comments | 5 | 2019-05-08T06:07:56Z | 2019-10-05T15:08:47Z | https://github.com/kubernetes/kubernetes/issues/77581 | 441,566,383 | 77,581 |
[
"kubernetes",
"kubernetes"
] | Hello, guys, I might need your help. I am unable to get memory metrics when configuring metrics-server.
- Kubernetes 1.13.5
- metrics-server 0.3.1
- kernel
CentOS Linux release 7.6.1810 (Core) 4.4.176-1.el7.elrepo.x86_64 x86_64
```
kubectl version
Client Version: version.Info{Major:"1", Minor:"13", Gi... | hpa Unable to get memory metrics | https://api.github.com/repos/kubernetes/kubernetes/issues/77575/comments | 14 | 2019-05-08T03:33:20Z | 2022-11-29T17:42:09Z | https://github.com/kubernetes/kubernetes/issues/77575 | 441,535,380 | 77,575 |
[
"kubernetes",
"kubernetes"
] | This test just merged in #77457 and is flaky. Example failure in https://prow.k8s.io/view/gcs/kubernetes-jenkins/pr-logs/pull/77564/pull-kubernetes-integration/1125927448479797249/
```
framework_test.go:310: test #1: Expected the unreserve plugin to be called only once.
```
/sig scheduling
/cc @bsalamat @danie... | TestUnreservePlugin is flaky | https://api.github.com/repos/kubernetes/kubernetes/issues/77573/comments | 14 | 2019-05-08T01:33:34Z | 2019-10-05T07:01:18Z | https://github.com/kubernetes/kubernetes/issues/77573 | 441,511,440 | 77,573 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
We're trying to measure persistent volume utilization and Prometheus is currently reporting `kubelet_volume_stats_used_bytes` that is 20x+ the size of the corresponding persistent volume claim. It's happening in two persistent volumes that are both glusterfs -- they're not the only gluster volumes... | Unexpectedly large results from kubelet_volume_stats_used_bytes | https://api.github.com/repos/kubernetes/kubernetes/issues/77570/comments | 9 | 2019-05-08T00:49:38Z | 2020-11-03T12:08:33Z | https://github.com/kubernetes/kubernetes/issues/77570 | 441,503,350 | 77,570 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
The [scheduling framework KEP](https://github.com/kubernetes/enhancements/blob/master/keps/sig-scheduling/20180409-scheduling-framework.md) is now implementable. We have [already added](https://github.com/kubernetes/kubernetes/pull/75848) plugin interfaces and extension points for ... | Add Post-bind extension point to the scheduling framework | https://api.github.com/repos/kubernetes/kubernetes/issues/77566/comments | 2 | 2019-05-07T23:27:56Z | 2019-05-30T00:24:21Z | https://github.com/kubernetes/kubernetes/issues/77566 | 441,486,871 | 77,566 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
The [scheduling framework KEP](https://github.com/kubernetes/enhancements/blob/master/keps/sig-scheduling/20180409-scheduling-framework.md) is now implementable. We have [already added](https://github.com/kubernetes/kubernetes/pull/75848) plugin interfaces and extension points for ... | Add Queue Sort extension point to the scheduling framework | https://api.github.com/repos/kubernetes/kubernetes/issues/77565/comments | 1 | 2019-05-07T23:09:35Z | 2019-05-07T23:30:01Z | https://github.com/kubernetes/kubernetes/issues/77565 | 441,482,744 | 77,565 |
[
"kubernetes",
"kubernetes"
] | Updating "loadBalancerSourceRanges" in the kubernetes service definition doesnt update the AWS security group
AWS security group must be in sync when we update the service definitions.
Create service.yaml file
kind: Service
apiVersion: v1
metadata:
name: proxy-service-external
namespace: test
labels... | AWS not updating security group for loadBalancerSourceRanges | https://api.github.com/repos/kubernetes/kubernetes/issues/77557/comments | 32 | 2019-05-07T19:51:39Z | 2024-05-16T02:01:59Z | https://github.com/kubernetes/kubernetes/issues/77557 | 441,417,006 | 77,557 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs -->
**Which jobs are failing**: sig-scalability-gce/gce-scale-performance
**Which test(s) are failing**: Up
**Since when has it been failing**: since today
**Testgrid link**: https://k8s-testgrid.appspot.com/... | Large tests (>500 nodes) fail on cluster set-up | https://api.github.com/repos/kubernetes/kubernetes/issues/77551/comments | 5 | 2019-05-07T15:38:54Z | 2019-05-13T12:02:34Z | https://github.com/kubernetes/kubernetes/issues/77551 | 441,302,286 | 77,551 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
When initializing client-go fake dynamic client, it requires an empty slice of objects or causes a panic:
```go
func () {
fake.NewSimpleDynamicClient(runtime.NewScheme(), []runtime.Object{}...)
}
```
**What you expected to happen**:
The following not to panic
```go
func() {
f... | Client-go fake dynamic client forces initialization with an empty slice of objects | https://api.github.com/repos/kubernetes/kubernetes/issues/77547/comments | 3 | 2019-05-07T14:52:44Z | 2019-05-08T06:12:46Z | https://github.com/kubernetes/kubernetes/issues/77547 | 441,277,872 | 77,547 |
[
"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**:
Following the... | Enabling the unsafe net.ipv4.route.min_pmtu sysctl | https://api.github.com/repos/kubernetes/kubernetes/issues/77546/comments | 10 | 2019-05-07T14:28:56Z | 2019-07-06T11:10:36Z | https://github.com/kubernetes/kubernetes/issues/77546 | 441,265,072 | 77,546 |
[
"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**:
For pod's res... | When restartPolicy is never and sandbox is exited,we should set pod phase is Failed | https://api.github.com/repos/kubernetes/kubernetes/issues/77544/comments | 8 | 2019-05-07T12:27:46Z | 2020-03-26T15:06:02Z | https://github.com/kubernetes/kubernetes/issues/77544 | 441,204,976 | 77,544 |
Subsets and Splits
Unique Owner-Repo Count
Counts the number of unique owner-repos in the dataset, providing a basic understanding of diverse repositories.