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"
] | We have a document on how to do cherry picks:
https://github.com/kubernetes/community/blob/master/contributors/devel/sig-release/cherry-picks.md#initiate-a-cherry-pick
But we don't have a document which lays out what PRs are good candidates for cherry-picks, do we? This will help both reviewers and release managers... | Document what kind of PRs are good for cherry-picks | https://api.github.com/repos/kubernetes/kubernetes/issues/82467/comments | 12 | 2019-09-08T13:00:28Z | 2019-10-23T17:24:39Z | https://github.com/kubernetes/kubernetes/issues/82467 | 490,751,575 | 82,467 |
[
"kubernetes",
"kubernetes"
] | I read community/contributors/design-proposals/resource-management/hugepages.md, and said that :
Initially, a pod may not consume multiple huge page sizes in a single pod spec. Attempting to use hugepages-2Mi and hugepages-1Gi in the same pod spec will fail validation. We believe it is rare for applications to atte... | Some questions about Huge Pages and NUMA | https://api.github.com/repos/kubernetes/kubernetes/issues/82469/comments | 6 | 2019-09-08T09:09:57Z | 2019-09-18T10:00:29Z | https://github.com/kubernetes/kubernetes/issues/82469 | 490,773,470 | 82,469 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
https://git... | kubectl describe pvc should also show APIGoup of DataSource | https://api.github.com/repos/kubernetes/kubernetes/issues/82463/comments | 2 | 2019-09-08T06:30:18Z | 2019-09-12T01:29:30Z | https://github.com/kubernetes/kubernetes/issues/82463 | 490,716,686 | 82,463 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
Currently, Azure cloud provider invokes `VirtualMachineScaleSetVMsClient.Get()` and `VirtualMachineScaleSetVMsClient.GetInstanceView()` to fetch VMSS nodes information:
https://github.com/kubernetes/... | Reduce vmssVM API calls with InstanceView expansion | https://api.github.com/repos/kubernetes/kubernetes/issues/82460/comments | 3 | 2019-09-08T02:43:56Z | 2019-09-26T21:39:52Z | https://github.com/kubernetes/kubernetes/issues/82460 | 490,702,728 | 82,460 |
[
"kubernetes",
"kubernetes"
] | Mirroring this from: https://github.com/kubernetes-sigs/kustomize/issues/970 now that kustomize is actually in kubectl. Feel free to redirect me if that's wrong. Also @Liujingfang1 who was against this so they can say why if they want.
**What would you like to be added**:
Right now resoruces in kustomize.config.k8... | Kustomize resources from remote url | https://api.github.com/repos/kubernetes/kubernetes/issues/82459/comments | 6 | 2019-09-07T23:13:40Z | 2024-11-04T17:43:10Z | https://github.com/kubernetes/kubernetes/issues/82459 | 490,689,764 | 82,459 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
The default human-readable printer in `kubectl get` prints many timestamps as relative to the current date; eg, the AGE column in pods is calculated from the timestamp in this way.
It would be nice to be able to do this with custom columns as well.
**Why is this needed**:
... | A way to display relative timestamps with custom-columns | https://api.github.com/repos/kubernetes/kubernetes/issues/82457/comments | 6 | 2019-09-07T19:24:05Z | 2020-02-04T21:53:27Z | https://github.com/kubernetes/kubernetes/issues/82457 | 490,671,384 | 82,457 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
It would be useful to be able to add environment variables to ClusterConfiguration in a similar way as extraArgs can be.
**Why is this needed**:
I use k8s on PI boards, where RAM is limited. Now I've ... | kubeadm: Ability to add environment variables to static pod manifests | https://api.github.com/repos/kubernetes/kubernetes/issues/82456/comments | 3 | 2019-09-07T16:21:52Z | 2019-09-08T19:30:15Z | https://github.com/kubernetes/kubernetes/issues/82456 | 490,653,691 | 82,456 |
[
"kubernetes",
"kubernetes"
] | Description of problem:
A shared PVC (on Ceph and VolumeMode=Filesystem ) can't be used at same time in more than one pod.
The second pod is stuck in "ContainerCreating" state with error:
~~~
# oc get pod
NAME READY STATUS RESTARTS AGE
virt-launcher-vm-dv-ci... | RWX PVC fails with 'multi attach error' | https://api.github.com/repos/kubernetes/kubernetes/issues/82453/comments | 6 | 2019-09-07T12:11:14Z | 2019-09-10T15:30:19Z | https://github.com/kubernetes/kubernetes/issues/82453 | 490,628,759 | 82,453 |
[
"kubernetes",
"kubernetes"
] | kubernetes 1.13
if I change mounted configmap data
then update one pod image by "kubectl edit pod"
pod fail to start
message: |
oci runtime error: container_linux.go:247: starting container process caused "process_linux.go:364: container init caused \"rootfs_linux.go:54: mounting \\\"/var/lib/kubele... | update pod failed | https://api.github.com/repos/kubernetes/kubernetes/issues/82451/comments | 12 | 2019-09-07T07:21:17Z | 2020-02-22T15:47:42Z | https://github.com/kubernetes/kubernetes/issues/82451 | 490,603,175 | 82,451 |
[
"kubernetes",
"kubernetes"
] | Follow up from @BenTheElder 's comment in https://github.com/kubernetes/kubernetes/pull/82188#issuecomment-526869867
We should change any instances to use kubetest directly, end users can do the same as well | Deprecating and remove hack/e2e.go | https://api.github.com/repos/kubernetes/kubernetes/issues/82448/comments | 2 | 2019-09-07T01:35:29Z | 2019-11-07T17:05:06Z | https://github.com/kubernetes/kubernetes/issues/82448 | 490,576,466 | 82,448 |
[
"kubernetes",
"kubernetes"
] | Per PR [82420](https://github.com/kubernetes/kubernetes/pull/82420) the test `Kubernetes e2e suite [sig-network] Services should preserve source pod IP for traffic thru service cluster IP [LinuxOnly]` fails to error properly. One line of particular interest from that PR:
`
If you wonder why it does not fail on dock... | [Tracking Issue] Ensure SIG-Networking Source Pod IP preservation test errors properly | https://api.github.com/repos/kubernetes/kubernetes/issues/82445/comments | 3 | 2019-09-06T23:32:29Z | 2019-10-10T23:27:21Z | https://github.com/kubernetes/kubernetes/issues/82445 | 490,559,293 | 82,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/
-->
**What happened**:
Attempt to cr... | CRD with a single element in spec.versions is not allowed | https://api.github.com/repos/kubernetes/kubernetes/issues/82443/comments | 5 | 2019-09-06T21:43:11Z | 2019-09-06T22:35:52Z | https://github.com/kubernetes/kubernetes/issues/82443 | 490,534,612 | 82,443 |
[
"kubernetes",
"kubernetes"
] | Manual node scheduling workaround can be removed from in-tree hostpath e2e tests when the topology supported csi hostpath driver image is released.
Related issue: https://github.com/kubernetes-csi/csi-driver-host-path/issues/54
Related comment: https://github.com/kubernetes-csi/csi-driver-host-path/pull/88#issuecom... | Remove manual node scheduling workaround from in-tree hostpath e2e tests | https://api.github.com/repos/kubernetes/kubernetes/issues/82441/comments | 7 | 2019-09-06T20:51:53Z | 2020-05-04T08:47:49Z | https://github.com/kubernetes/kubernetes/issues/82441 | 490,517,881 | 82,441 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Using trivial probes significantly contributes to CPU/system load.
**What you expected to happen**:
Trivial probes should be performant
**How to reproduce it (as minimally and precisely as possible)**:
1. Create a cluster (minimal reproduction done on an m5.large ec2 instance, creating a s... | High system load/CPU utilization with trivial liveness and readiness exec probes | https://api.github.com/repos/kubernetes/kubernetes/issues/82440/comments | 88 | 2019-09-06T20:24:31Z | 2024-12-23T18:51:03Z | https://github.com/kubernetes/kubernetes/issues/82440 | 490,507,785 | 82,440 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
As described at https://github.com/intel/sriov-network-device-plugin/pull/160#issuecomment-528482988 when I ran "go get k8s.io/kubernetes" it gave me the following error:
...initial bit snipped...
go: k8s.io/cluster-bootstrap@v0.0.0: unknown revision v0.0.0
go: k8s.io/kube-proxy@v0.0.0: unkno... | Unable to use go modules in device plugins | https://api.github.com/repos/kubernetes/kubernetes/issues/82437/comments | 8 | 2019-09-06T19:05:27Z | 2019-10-17T18:26:29Z | https://github.com/kubernetes/kubernetes/issues/82437 | 490,479,004 | 82,437 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
While upgrading from v1.15 to try out kubernetes v1.16.0-beta.2, kube-apiserver is printing error messages:
```
customresource_handler.go:307] the server could not properly serve the CR schema
```
This also **brakes** the API server since the user is unable to even delete the "faulty" CR
**... | Regression in v1.16.0-beta.2 - the server could not properly serve the CR schema | https://api.github.com/repos/kubernetes/kubernetes/issues/82436/comments | 7 | 2019-09-06T18:11:30Z | 2019-09-10T19:42:56Z | https://github.com/kubernetes/kubernetes/issues/82436 | 490,457,300 | 82,436 |
[
"kubernetes",
"kubernetes"
] | The PodTemplate API is unused and increases the API surface needlessly.
It should be removed so it's not a default DoS vector.
From https://github.com/kubernetes/kubernetes/pull/81689#issuecomment-523285651
> Does anyone use the PodTemplate API?
> It was created for #170, which was never implemented.
> I'd... | Deprecate the PodTemplate API | https://api.github.com/repos/kubernetes/kubernetes/issues/82435/comments | 18 | 2019-09-06T17:08:02Z | 2019-12-17T18:21:11Z | https://github.com/kubernetes/kubernetes/issues/82435 | 490,431,073 | 82,435 |
[
"kubernetes",
"kubernetes"
] | When running aggregated apiservers that want to automatically get their authentication configuration from `kubectl get -n kube-system configmap/extension-apiserver-authentication`, the "last one wins" behavior means that you can end up in cases where the aggregated apiserver trusts server-two, but not server-one. We c... | `cm/extension-apiserver-authentication` is "last one wins" | https://api.github.com/repos/kubernetes/kubernetes/issues/82429/comments | 3 | 2019-09-06T15:39:53Z | 2019-11-07T17:03:11Z | https://github.com/kubernetes/kubernetes/issues/82429 | 490,394,816 | 82,429 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
The scheduler currently provides a number of useful metrics to track its health. We would like to add more metrics to track the impact of various filter/predicate and score/priority functions on scheduling decisions.
A couple of suggestions:
1) Add a vector counter to track t... | Add metrics to track filter and scoring behavior of the scheduler | https://api.github.com/repos/kubernetes/kubernetes/issues/82427/comments | 2 | 2019-09-06T15:33:29Z | 2020-01-07T03:00:35Z | https://github.com/kubernetes/kubernetes/issues/82427 | 490,391,640 | 82,427 |
[
"kubernetes",
"kubernetes"
] | It looks like currently we are trying to remove staging directory when `NodeStage` call errors out/times out - https://github.com/kubernetes/kubernetes/blob/c58767b1e2981bd7826b4336de0c2756fa975339/pkg/volume/csi/csi_attacher.go#L331
This is problematic because in case of timeout, the staging path might still be in-... | Staging/mount directory should not be removed if nodestage/publish times out | https://api.github.com/repos/kubernetes/kubernetes/issues/82426/comments | 3 | 2019-09-06T15:19:41Z | 2019-12-17T22:49:58Z | https://github.com/kubernetes/kubernetes/issues/82426 | 490,384,845 | 82,426 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs -->
**Which jobs are failing**:
gce-master-scale-performance
**Which test(s) are failing**:
load
**Since when has it been failing**:
run from 09/02
**Testgrid link**:
https://k8s-testgrid.appspot.com/sig... | [Failing Test] gce-master-scale-performance - load 09/02 | https://api.github.com/repos/kubernetes/kubernetes/issues/82422/comments | 3 | 2019-09-06T14:56:14Z | 2019-12-06T10:14:13Z | https://github.com/kubernetes/kubernetes/issues/82422 | 490,372,800 | 82,422 |
[
"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 deployed... | kubectl --dry-run does not report error when secret is not encrypted with base64 | https://api.github.com/repos/kubernetes/kubernetes/issues/82421/comments | 6 | 2019-09-06T14:35:44Z | 2019-10-06T20:28:07Z | https://github.com/kubernetes/kubernetes/issues/82421 | 490,362,192 | 82,421 |
[
"kubernetes",
"kubernetes"
] | **Which jobs are failing**:
ci-kubernetes-node-kubelet-orphans
**Which test(s) are failing**:
[k8s.io] Security Context When creating a container with runAsNonRoot should run with an image specified user ID
**Since when has it been failing**:
https://github.com/kubernetes/kubernetes/compare/a1f1f0b59...baaec43... | [Failing Test] [k8s.io] Security Context | https://api.github.com/repos/kubernetes/kubernetes/issues/82419/comments | 5 | 2019-09-06T11:38:57Z | 2019-12-09T01:16:02Z | https://github.com/kubernetes/kubernetes/issues/82419 | 490,280,798 | 82,419 |
[
"kubernetes",
"kubernetes"
] | **Which jobs are failing**:
ci-kubernetes-node-kubelet-orphans
**Which test(s) are failing**:
[sig-storage] EmptyDir volumes pod should support shared volumes between containers
**Since when has it been failing**:
https://github.com/kubernetes/kubernetes/compare/a1f1f0b59...baaec43cd
**Testgrid link**:
htt... | [Failing Test] [sig-storage] EmptyDir volumes | https://api.github.com/repos/kubernetes/kubernetes/issues/82418/comments | 5 | 2019-09-06T11:20:38Z | 2019-10-15T15:50:14Z | https://github.com/kubernetes/kubernetes/issues/82418 | 490,273,786 | 82,418 |
[
"kubernetes",
"kubernetes"
] | Which jobs are failing:
ci-kubernetes-node-kubelet-orphans
Which test(s) are failing:
[sig-storage] EmptyDir volumes pod should support shared volumes between containers
Since when has it been failing:
https://github.com/kubernetes/kubernetes/compare/a1f1f0b59...baaec43cd
Testgrid link:
https://testgrid.k8... | [Failing Test] [sig-storage] EmptyDir volumes | https://api.github.com/repos/kubernetes/kubernetes/issues/82417/comments | 2 | 2019-09-06T11:17:46Z | 2019-09-06T11:19:17Z | https://github.com/kubernetes/kubernetes/issues/82417 | 490,272,744 | 82,417 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
When I use local-up-cluste.sh to build a local k8s environment, it end up with following information "kube-proxy terminated unexpectedly, see /tmp/kube-proxy.log"
In /tmp/kube-proxy.log
```
E0906 18:25:04.661869 41689 node.go:124] Failed to retrieve node info: nodes "127.0.0.1" not found
E0... | kube-proxy error when use hack/local-up-cluster.sh | https://api.github.com/repos/kubernetes/kubernetes/issues/82412/comments | 4 | 2019-09-06T10:32:52Z | 2019-11-18T01:28:30Z | https://github.com/kubernetes/kubernetes/issues/82412 | 490,255,047 | 82,412 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
[health-monitor.sh](https://github.com/kubernetes/kubernetes/blob/master/cluster/gce/gci/health-monitor.sh#L79) should save kubelet coredump before restarting it.
**Why is this needed**:
We were unable to understand kubelet restart, which caused https://github.com/kubernetes/k... | health-monitor should save kubelet coredump before restarting it | https://api.github.com/repos/kubernetes/kubernetes/issues/82408/comments | 7 | 2019-09-06T09:50:48Z | 2020-05-04T11:50:48Z | https://github.com/kubernetes/kubernetes/issues/82408 | 490,236,597 | 82,408 |
[
"kubernetes",
"kubernetes"
] | Hi, dear authors:
I have an enhancement request of kubernetes's cli-->kubectl explain. Recently, I deploy to k8s clusters called master1 and master2. And has deployed the federation v2.
Now I want to see the federation's kinds like FederatedDeployment's substance. Just like this
```
[root@master1 Desktop]#... | how to use 'kubectl explain' to crd's substance. | https://api.github.com/repos/kubernetes/kubernetes/issues/82407/comments | 9 | 2019-09-06T09:41:11Z | 2023-06-14T14:17:14Z | https://github.com/kubernetes/kubernetes/issues/82407 | 490,232,084 | 82,407 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
I don't know if a method should be added or the existing `GenerateName` needs to be modified. I guess added for backward compatibility.
A method in the https://github.com/kubernetes/kubernetes/blob/84fe3db5cf58bf0fc8ff792b885465ceaf70a435/staging/src/k8s.io/apiserver/pkg/storage... | names.GenerateName() trunc even if name lenght is between 63 and 57. | https://api.github.com/repos/kubernetes/kubernetes/issues/82406/comments | 2 | 2019-09-06T09:17:06Z | 2019-12-05T12:46:59Z | https://github.com/kubernetes/kubernetes/issues/82406 | 490,220,301 | 82,406 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
I face issues with the deployment status. Its pods are ready and have **Running** status, however the deployment status doesn't show readiness.
```
$ kubectl get pods -l role=server
NAME READY STATUS RESTARTS AGE
server-bc9c5c7b8-2vv6f 3/3 Running 0... | Status inconsistencies between deployment and its pods | https://api.github.com/repos/kubernetes/kubernetes/issues/82405/comments | 14 | 2019-09-06T07:08:27Z | 2020-01-28T13:00:20Z | https://github.com/kubernetes/kubernetes/issues/82405 | 490,167,350 | 82,405 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
kubeadm should support domain name in AdvertiseAddress in phase "kubeadm alpha kubeconfig"
only ip address is supported now.
**Why is this needed**:
I need to generate discovery file for worker node on cloud and I don't know the ip address of control plane before master node... | kubeadm should support domain name in --apiserver-advertise-address in phase "kubeadm alpha kubeconfig" | https://api.github.com/repos/kubernetes/kubernetes/issues/82404/comments | 3 | 2019-09-06T05:53:54Z | 2019-09-08T19:33:45Z | https://github.com/kubernetes/kubernetes/issues/82404 | 490,143,357 | 82,404 |
[
"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**:
Used `kubectl... | kubectl proxy fails to proxy http call to service | https://api.github.com/repos/kubernetes/kubernetes/issues/82402/comments | 10 | 2019-09-06T05:05:10Z | 2020-06-22T07:17:24Z | https://github.com/kubernetes/kubernetes/issues/82402 | 490,131,198 | 82,402 |
[
"kubernetes",
"kubernetes"
] | kubeadm-config.yaml:
apiVersion: kubeadm.k8s.io/v1beta2
kind: ClusterConfiguration
kubernetesVersion: v1.15.3
controlPlaneEndpoint: "internal-ELB-K8sApiHTTP-APP-1600381234.cn-northwest-1.elb.amazonaws.com.cn:9443"
networking:
podSubnet: "10.244.0.0/16"
apiServer:
certSANs:
- "internal-ELB-K8sApiHTTP-APP-160... | "Must be a valid IP address or a valid RFC-1123 DNS subdomain" error occurred when installing kubernetes 1.15 cluster using kubeadm | https://api.github.com/repos/kubernetes/kubernetes/issues/82399/comments | 2 | 2019-09-06T03:51:03Z | 2019-09-06T08:00:31Z | https://github.com/kubernetes/kubernetes/issues/82399 | 490,114,776 | 82,399 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
I would like to be able to import pkg/credentialprovider.
**Why is this needed**:
https://github.com/google/go-containerregistry/issues/496
| Please move pkg/credentialprovider out of tree | https://api.github.com/repos/kubernetes/kubernetes/issues/82396/comments | 20 | 2019-09-06T02:20:55Z | 2021-01-19T15:21:28Z | https://github.com/kubernetes/kubernetes/issues/82396 | 490,094,418 | 82,396 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
We can introduce band into watcherBookmarkTimeBuckets where band is defined as
```
type band struct {
int64 start
map[int64][]*cacheWatcher
}
```
watchersBuckets becomes array of band's.
A new band is formed when the difference between clock.Now().Unix() and current s... | Introduce band in watcherBookmarkTimeBuckets to speed up lookup | https://api.github.com/repos/kubernetes/kubernetes/issues/82395/comments | 4 | 2019-09-06T01:02:14Z | 2019-09-06T20:42:56Z | https://github.com/kubernetes/kubernetes/issues/82395 | 490,078,212 | 82,395 |
[
"kubernetes",
"kubernetes"
] | Is kubernetes 1.17 a good time to deprecate `external-cloud-volume-plugin`:
https://cs.k8s.io/?q=external-cloud-volume-plugin&i=nope&files=&repos=kubernetes/kubernetes
/sig cloud-provider | Deprecate external-cloud-volume-plugin command line flag in controller-manager | https://api.github.com/repos/kubernetes/kubernetes/issues/82394/comments | 9 | 2019-09-06T00:54:48Z | 2020-02-06T19:37:36Z | https://github.com/kubernetes/kubernetes/issues/82394 | 490,076,750 | 82,394 |
[
"kubernetes",
"kubernetes"
] | Currently there are two api packages in the scheduler: [scheduler/api](https://github.com/kubernetes/kubernetes/tree/master/pkg/scheduler/api/) and [scheduler/apis](https://github.com/kubernetes/kubernetes/tree/master/pkg/scheduler/apis/), we should move everything under scheduler/api to scheduler/apis:
1) configur... | Move all scheduler API-related code to a single place | https://api.github.com/repos/kubernetes/kubernetes/issues/82390/comments | 11 | 2019-09-05T20:15:28Z | 2020-01-07T02:59:07Z | https://github.com/kubernetes/kubernetes/issues/82390 | 489,979,146 | 82,390 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
The `Should recreate evicted statefulset` conformance test in https://github.com/kubernetes/kubernetes/blob/master/test/e2e/apps/statefulset.go fails because `Pod ss-0 expected to be re-created at least once`. This was caused by the `Predicate PodFitsHostPorts failed` scheduling error. The root ... | Should recreate evicted statefulset conformance test may encounter host port conflict | https://api.github.com/repos/kubernetes/kubernetes/issues/82387/comments | 16 | 2019-09-05T19:02:01Z | 2019-12-20T16:35:48Z | https://github.com/kubernetes/kubernetes/issues/82387 | 489,942,459 | 82,387 |
[
"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**: Attempt to set n... | ValidateKubeletConfiguration does not check the values of KubeletReserved and SystemReserved | https://api.github.com/repos/kubernetes/kubernetes/issues/82386/comments | 10 | 2019-09-05T19:01:43Z | 2020-02-04T02:34:13Z | https://github.com/kubernetes/kubernetes/issues/82386 | 489,942,341 | 82,386 |
[
"kubernetes",
"kubernetes"
] | The Permit extension point allows running multiple registered permit plugins, if more than one permit plugin returns Wait with a timeout, then we wait for the shortest of the two timeouts.
The expectation is that the plugins that issue Wait will have logic, likely baked into the plugin itself, that accepts the pod a... | Rethink the Scheduler's Framework Permit API | https://api.github.com/repos/kubernetes/kubernetes/issues/82385/comments | 22 | 2019-09-05T18:57:25Z | 2019-10-19T13:47:38Z | https://github.com/kubernetes/kubernetes/issues/82385 | 489,940,552 | 82,385 |
[
"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 conf... | kubectl hangs on config set | https://api.github.com/repos/kubernetes/kubernetes/issues/82382/comments | 3 | 2019-09-05T18:03:11Z | 2019-09-06T05:03:58Z | https://github.com/kubernetes/kubernetes/issues/82382 | 489,917,021 | 82,382 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
Hello,
First, thank you for your work.
**What would you like to be added**:
In fact I would like something to be modified.
You documentation and "kubeadm init --help" read that you are using .local as the default DNS suffix for multiple ser... | .local and dns | https://api.github.com/repos/kubernetes/kubernetes/issues/82381/comments | 38 | 2019-09-05T17:50:19Z | 2024-01-30T05:11:53Z | https://github.com/kubernetes/kubernetes/issues/82381 | 489,910,756 | 82,381 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
Today it is impossible to differentiate users of the same username based on how they authenticated. For example, I could use OIDC to authenticate to a cluster and have the same username as an X509 certi... | Add Authenticator name to authentication.v1.UserInfo | https://api.github.com/repos/kubernetes/kubernetes/issues/82379/comments | 23 | 2019-09-05T17:08:24Z | 2020-03-28T20:32:23Z | https://github.com/kubernetes/kubernetes/issues/82379 | 489,892,559 | 82,379 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Currently kube-proxy when restarted exposes NetworkProgrammingLatency metric for all endpoints. When it gets restarted it records very long NetworkProgrammingLatency for services, which hasn't changed in a while, causing skew in NetworkProgrammingLatency.
**What you expected to happen**:
kube-p... | Investigate issues with Network Programming Latency SLO | https://api.github.com/repos/kubernetes/kubernetes/issues/82378/comments | 8 | 2019-09-05T16:14:34Z | 2020-08-21T01:09:00Z | https://github.com/kubernetes/kubernetes/issues/82378 | 489,863,327 | 82,378 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs -->
**Which jobs are failing**:
gce-master-scale-performance
**Which test(s) are failing**:
density
**Since when has it been failing**:
09/04 (previous fail is for load test, not density)
**Testgrid link*... | [Failing Test] gce-master-scale-performance - slow POST nodes after kubelet restarted in the middle of the test | https://api.github.com/repos/kubernetes/kubernetes/issues/82377/comments | 6 | 2019-09-05T16:03:28Z | 2019-09-06T12:47:32Z | https://github.com/kubernetes/kubernetes/issues/82377 | 489,857,831 | 82,377 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
/sig scheduling
/priority important-longterm
/assign
We should remove the EBS/GCE/Azure/Cinder predicates from scheduler after CSIMigration goes GA (probably in 1.18).
https://github.com/kubernetes/kubernetes/blob/8c537b46939beed37133... | [scheduler] Remove deprecated EBS/GCE/Azure/Cinder predicates | https://api.github.com/repos/kubernetes/kubernetes/issues/82375/comments | 9 | 2019-09-05T15:30:37Z | 2024-08-26T11:02:14Z | https://github.com/kubernetes/kubernetes/issues/82375 | 489,839,380 | 82,375 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
I tried to create a deployment with duplicate containerPorts with hostIPs of two different address families. Only the first mapping was provided as input into my CNI plugin chain. Also, a log message from kubelet warning about a duplicate containerPort was created.
**What you expected to happen**... | Duplicate containerPorts not allowed across different address families | https://api.github.com/repos/kubernetes/kubernetes/issues/82373/comments | 7 | 2019-09-05T14:34:00Z | 2019-10-01T00:55:33Z | https://github.com/kubernetes/kubernetes/issues/82373 | 489,806,459 | 82,373 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
Option to specify "FS formatting" args for `mkfs` in `mount_linux.go.`
**Why is this needed**:
At present, there is no way to pass `ext4/xfs` formatting options for `mkfs` command in mount_linux.... | Allow user/storage plugin to pass filesystem formatting options to mount_linux. | https://api.github.com/repos/kubernetes/kubernetes/issues/82372/comments | 14 | 2019-09-05T14:22:34Z | 2020-05-29T08:35:37Z | https://github.com/kubernetes/kubernetes/issues/82372 | 489,790,967 | 82,372 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Creating this Service created a LB in AWS, which is what we want.
But we added the service.beta.kubernetes.io/aws-load-balancer-extra-security-groups annotation to add an existing SG to this LB. This also works, but because we specified tags for our LB, it overwrites the existing tags on the SG wit... | ELB tags will overwrite tags on existing Security group | https://api.github.com/repos/kubernetes/kubernetes/issues/82369/comments | 9 | 2019-09-05T11:34:53Z | 2020-03-24T00:40:06Z | https://github.com/kubernetes/kubernetes/issues/82369 | 489,695,819 | 82,369 |
[
"kubernetes",
"kubernetes"
] | http://perf-dash.k8s.io/#/?jobname=gce-5000Nodes&metriccategoryname=Network&metricname=Load_NetworkProgrammingLatency&Metric=NetworkProgrammingLatency
We regressed between 8/28 and 8/31, basically from: ~30s to 300s+.
Knowing the internals, it's probably that we have more node restarts (or kube-proxy restarts) or... | NetworkProgrammingLatency regressed in 5k-node clusters | https://api.github.com/repos/kubernetes/kubernetes/issues/82364/comments | 18 | 2019-09-05T10:41:27Z | 2021-01-05T14:07:22Z | https://github.com/kubernetes/kubernetes/issues/82364 | 489,672,556 | 82,364 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
apiserver discards oidc settings
**What you expected to happen**:
apiserver accepts and uses oidc settings
**How to reproduce it (as minimally and precisely as possible)**:
Insert into /etc/kubernetes/manifests/kube-apiserver.yaml
- --oidc-ca-file=/etc/ssl/certs/oc_ca.crt
- --oid... | api server discards oidc settings | https://api.github.com/repos/kubernetes/kubernetes/issues/82362/comments | 4 | 2019-09-05T08:38:24Z | 2019-09-26T19:11:16Z | https://github.com/kubernetes/kubernetes/issues/82362 | 489,609,588 | 82,362 |
[
"kubernetes",
"kubernetes"
] | # TL;DR:
iptables versions `1.8.1` and `1.8.2` have a bug causing rules of type
```
DROP all -- anywhere anywhere mark match 0x8000/0x8000 /* kubernetes firewall for dropping marked packets */
```
to be infinitely added to the `KUBE-FIREWALL` chain.
These iptable versions are cur... | iptables are spammed with entries in the KUBE-FIREWALL chain | https://api.github.com/repos/kubernetes/kubernetes/issues/82361/comments | 31 | 2019-09-05T08:08:28Z | 2019-11-18T16:59:21Z | https://github.com/kubernetes/kubernetes/issues/82361 | 489,594,945 | 82,361 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
**Why is this needed**:
according to [scheduler-extender](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/scheduling/scheduler_extender.md)
we can configure schedu... | kube-scheduler bind is async, scheduler-extender how to maintain node/pod cache | https://api.github.com/repos/kubernetes/kubernetes/issues/82359/comments | 6 | 2019-09-05T07:36:40Z | 2020-01-09T03:00:53Z | https://github.com/kubernetes/kubernetes/issues/82359 | 489,580,813 | 82,359 |
[
"kubernetes",
"kubernetes"
] | Here was a recent run:
https://storage.googleapis.com/kubernetes-jenkins/pr-logs/pull/82318/pull-kubernetes-node-e2e/1169446696074088448/build-log.txt
where we can see:
```
I0905 03:09:01.549] Failure Finished Test Suite on Host
I0905 03:09:01.549] unable to create gce instance with running docker daemon for ... | kubernetes-node-e2e fails | https://api.github.com/repos/kubernetes/kubernetes/issues/82358/comments | 5 | 2019-09-05T06:26:29Z | 2019-09-06T00:20:12Z | https://github.com/kubernetes/kubernetes/issues/82358 | 489,551,942 | 82,358 |
[
"kubernetes",
"kubernetes"
] | So I was reading this nice IBM [article ](https://developer.ibm.com/opentech/2017/06/21/tour-kubernetes-source-code-part-one-kubectl-api-server/) on Kubernetes code base walkthrough, but I could not find the files that the author has mentioned.
For example, he is taking a peek at create.go under the location https:/... | Project structure | https://api.github.com/repos/kubernetes/kubernetes/issues/82354/comments | 3 | 2019-09-05T03:21:02Z | 2019-09-05T11:51:29Z | https://github.com/kubernetes/kubernetes/issues/82354 | 489,506,312 | 82,354 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs -->
**Which jobs are failing**:
ci-kubernetes-node-kubelet-orphans
**Which test(s) are failing**:
[sig-node] RuntimeClass should reject a Pod requesting a deleted RuntimeClass [cos-stable1]
**Since when has it... | [Failing Test] [sig-node] RuntimeClass | https://api.github.com/repos/kubernetes/kubernetes/issues/82352/comments | 9 | 2019-09-05T02:13:48Z | 2020-02-07T13:54:37Z | https://github.com/kubernetes/kubernetes/issues/82352 | 489,490,084 | 82,352 |
[
"kubernetes",
"kubernetes"
] | Under Umbrella issue: #82312
/area conformance
/sig testing | PodSpec - new prorityClassName test | https://api.github.com/repos/kubernetes/kubernetes/issues/82351/comments | 2 | 2019-09-04T23:56:50Z | 2019-09-11T21:09:01Z | https://github.com/kubernetes/kubernetes/issues/82351 | 489,461,074 | 82,351 |
[
"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 occasion... | Kubelet marking pods as not ready when all containers are ready (and seem to be running fine) | https://api.github.com/repos/kubernetes/kubernetes/issues/82346/comments | 23 | 2019-09-04T19:46:19Z | 2021-04-23T08:26:21Z | https://github.com/kubernetes/kubernetes/issues/82346 | 489,359,967 | 82,346 |
[
"kubernetes",
"kubernetes"
] | **Which jobs are failing**:
CRI-O CI
**Which test(s) are failing**:
Services should allow pods to hairpin back to themselves through services
**Since when has it been failing**:
Since https://github.com/kubernetes/kubernetes/pull/81955 merged
**Testgrid link**:
https://openshift-gce-devel.appspot.com/build/origi... | service hairpin test fails when run with CRI-O | https://api.github.com/repos/kubernetes/kubernetes/issues/82341/comments | 6 | 2019-09-04T17:41:51Z | 2019-09-04T19:56:54Z | https://github.com/kubernetes/kubernetes/issues/82341 | 489,298,531 | 82,341 |
[
"kubernetes",
"kubernetes"
] | It looks like recovery from errors on nodestage and nodepublish is problematic for raw block devices because currently both are clubbed into one operation - `SetUpDevice`.
So what happens if staging succeeds but publishing fails? In that case - volume state is *not* recorded in volume_manager and as a result when po... | CSI Raw block error recovery is problematic | https://api.github.com/repos/kubernetes/kubernetes/issues/82340/comments | 8 | 2019-09-04T17:37:09Z | 2020-01-13T13:19:01Z | https://github.com/kubernetes/kubernetes/issues/82340 | 489,296,532 | 82,340 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
kubectl logs command should show default container's log if no container is specified
**Why is this needed**:
If there's more than one container in a pod, command like `kubectl logs your-pod` will f... | kubectl logs should show default container's log if no container specified | https://api.github.com/repos/kubernetes/kubernetes/issues/82339/comments | 10 | 2019-09-04T16:44:08Z | 2020-04-16T02:35:43Z | https://github.com/kubernetes/kubernetes/issues/82339 | 489,273,695 | 82,339 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
nodeSelector functionality is covered by node affinity, and so we should consider deprecating the old nodeSelector API.
**Why is this needed**:
Remove redundant functionality and code.
/sig schedul... | Deprecate nodeSelector | https://api.github.com/repos/kubernetes/kubernetes/issues/82331/comments | 8 | 2019-09-04T13:34:41Z | 2019-09-04T14:11:15Z | https://github.com/kubernetes/kubernetes/issues/82331 | 489,164,460 | 82,331 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
When using se... | Environment variable from secret pass in different way than from plain text | https://api.github.com/repos/kubernetes/kubernetes/issues/82327/comments | 6 | 2019-09-04T11:17:01Z | 2019-09-05T13:33:55Z | https://github.com/kubernetes/kubernetes/issues/82327 | 489,097,485 | 82,327 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
Support for newer docker versions: 19.x
**Why is this needed**:
New users trying to use kubernetes install the latest docker version. It's inconvenient see the following warning and have to uninstall ... | Support newer versions of docker: 19.x | https://api.github.com/repos/kubernetes/kubernetes/issues/82326/comments | 19 | 2019-09-04T10:57:35Z | 2019-11-01T13:50:58Z | https://github.com/kubernetes/kubernetes/issues/82326 | 489,088,954 | 82,326 |
[
"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 `k... | kubectl describe secret got "namespace: 12bytes" | https://api.github.com/repos/kubernetes/kubernetes/issues/82323/comments | 3 | 2019-09-04T10:34:01Z | 2019-09-04T10:57:55Z | https://github.com/kubernetes/kubernetes/issues/82323 | 489,078,375 | 82,323 |
[
"kubernetes",
"kubernetes"
] | Umbrella issue: #82312
/area conformance
/sig testing | PodSpec - new readinessGates test | https://api.github.com/repos/kubernetes/kubernetes/issues/82313/comments | 7 | 2019-09-04T04:42:09Z | 2020-04-01T19:46:49Z | https://github.com/kubernetes/kubernetes/issues/82313 | 488,936,699 | 82,313 |
[
"kubernetes",
"kubernetes"
] | Here are some untested PodSpec endpoints that new tests will be written for, which will be prioritised in this order:
- [readinessGates](https://github.com/kubernetes/kubernetes/issues/82313)
- [prorityClassName](https://github.com/kubernetes/kubernetes/issues/82545)
- hostIPC
- [hostPID](https://github.com/kuberne... | [Umbrella Issue] PodSpec endpoints | https://api.github.com/repos/kubernetes/kubernetes/issues/82312/comments | 14 | 2019-09-04T04:12:42Z | 2020-03-15T00:08:41Z | https://github.com/kubernetes/kubernetes/issues/82312 | 488,929,683 | 82,312 |
[
"kubernetes",
"kubernetes"
] | MaxInt const is exported in scheduler api https://github.com/kubernetes/kubernetes/blob/6cb788c80e93bf0292f0a846ff1b55f690fcc970/pkg/scheduler/api/types.go#L31 although it is not needed to be exported. It is only used by `plugins_test.go`.
https://github.com/kubernetes/kubernetes/pull/81263#discussion_r317606153 dis... | Unnecessarily Exported MaxInt in scheduler api types | https://api.github.com/repos/kubernetes/kubernetes/issues/82306/comments | 7 | 2019-09-04T01:22:34Z | 2019-09-17T16:30:25Z | https://github.com/kubernetes/kubernetes/issues/82306 | 488,892,752 | 82,306 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
With kubadm 1.15.3, running `kubeadm join phase preflight` returned
```
I0904 00:29:27.135405 6199 checks.go:209] validating availability of port 2380
I0904 00:29:27.135453 6199 checks.go:254] validating the existence and emptiness of directory /var/lib/etcd
error execution phase preflight... | kubeadm join phase preflight: [ERROR HTTPProxy]: parse https://xxxx::1:2a: invalid port ":2a" after host | https://api.github.com/repos/kubernetes/kubernetes/issues/82304/comments | 5 | 2019-09-04T00:47:00Z | 2019-09-04T13:50:20Z | https://github.com/kubernetes/kubernetes/issues/82304 | 488,885,638 | 82,304 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
A kubeadm-compatible mechanism for managing extended resources. A possible approach can be found in #81858.
This would (in my mind) establish parity around the "node feature advertisement" that node ... | Extended resources via kubelet configuration | https://api.github.com/repos/kubernetes/kubernetes/issues/82302/comments | 7 | 2019-09-04T00:30:40Z | 2020-02-12T18:57:38Z | https://github.com/kubernetes/kubernetes/issues/82302 | 488,882,347 | 82,302 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs -->
**Which jobs are failing**:
ci-kubernetes-e2e-gci-gce-serial
**Which test(s) are failing**:
[sig-network] DNS configMap nameserver [IPv4] Change stubDomain should be able to change stubDomain configuration [... | [Failing Test] [sig-network] DNS configMap nameserver [IPv4] | https://api.github.com/repos/kubernetes/kubernetes/issues/82298/comments | 5 | 2019-09-03T22:34:33Z | 2019-09-05T16:31:27Z | https://github.com/kubernetes/kubernetes/issues/82298 | 488,855,172 | 82,298 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
```
Error from server (BadRequest): error when creating "/tmp/test.yaml": Deployment in version "v1" cannot be handled as a Deployment: json: cannot unmarshal number into Go struct field EnvVar.spec.template.spec.containers.env.value of type string
```
**What you expected to happen**:
For the ... | Kubernetes unnecessarily requiring quoting on numeric env vars | https://api.github.com/repos/kubernetes/kubernetes/issues/82296/comments | 49 | 2019-09-03T20:41:45Z | 2023-07-14T00:19:29Z | https://github.com/kubernetes/kubernetes/issues/82296 | 488,812,650 | 82,296 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
Logging for the authentication mechanism used by a user for requests to the API server.
**Why is this needed**:
At the moment Kubernetes does not put the mechanism used to authenticate a user into it's audit logs. As Kubernetes supports multiple authentication mechanisms, ... | Authentication audit logging - denote the authentication mechanism used. | https://api.github.com/repos/kubernetes/kubernetes/issues/82295/comments | 23 | 2019-09-03T19:47:20Z | 2024-11-20T19:59:55Z | https://github.com/kubernetes/kubernetes/issues/82295 | 488,789,137 | 82,295 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
Kubelet servi... | Kubelet service fails to start | https://api.github.com/repos/kubernetes/kubernetes/issues/82293/comments | 4 | 2019-09-03T19:33:30Z | 2019-09-04T13:49:10Z | https://github.com/kubernetes/kubernetes/issues/82293 | 488,783,549 | 82,293 |
[
"kubernetes",
"kubernetes"
] | Over in KubeBuilder land, we've started to see issues around very large validation blocks going over size limits. Thus far, it's mainly just been the client-size-apply-induced annotation limit, but I worry that when we start getting multiple versions we might go over the 1M limit. For instance, see https://github.com... | Large CRDs go over size limits (e.g. those with embedded podspecs) | https://api.github.com/repos/kubernetes/kubernetes/issues/82292/comments | 16 | 2019-09-03T19:22:24Z | 2021-05-20T14:35:51Z | https://github.com/kubernetes/kubernetes/issues/82292 | 488,779,147 | 82,292 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
On Deployin... | Statefulset Pod are evicted , but containers are not killed | https://api.github.com/repos/kubernetes/kubernetes/issues/82290/comments | 7 | 2019-09-03T19:06:18Z | 2020-02-09T16:44:46Z | https://github.com/kubernetes/kubernetes/issues/82290 | 488,772,580 | 82,290 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs -->
**Which jobs are failing**:
ci-kubernetes-e2e-aks-engine-azure-1-16-windows
**Which test(s) are failing**:
[sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) [sig-autoscaling] [S... | [FLAKE] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) [sig-autoscaling] [Serial] [Slow] ReplicationController Should scale from 1 pod to 3 pods and from 3 to 5 and verify decision stability | https://api.github.com/repos/kubernetes/kubernetes/issues/82287/comments | 10 | 2019-09-03T17:15:16Z | 2019-09-12T13:53:29Z | https://github.com/kubernetes/kubernetes/issues/82287 | 488,725,666 | 82,287 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
HPA scaled replica up, however, some PODs stayed Pending as there was not enough CPU:
```
php-apache-74856f9778-6nmj2 0/1 Pending 0 24h
php-apache-74856f9778-f5blx 0/1 Pending 0 ... | Horizontal Pod Autoscaler does not scale down if upscaled PODs are not ready | https://api.github.com/repos/kubernetes/kubernetes/issues/82285/comments | 9 | 2019-09-03T16:55:24Z | 2020-05-21T16:35:44Z | https://github.com/kubernetes/kubernetes/issues/82285 | 488,717,166 | 82,285 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
In some hypervisors, e.g. VMware, the new volume size is not pushed to the VM after the in-use block device extend, and you have to run the `echo 1 > /sys/block/sdb/device/rescan` manually and resize the FS manually.
**What you expected to happen**:
The `echo 1 > /sys/block/sdb/device/rescan... | resizefs package has to trigger a block device rescan before resizing the FS | https://api.github.com/repos/kubernetes/kubernetes/issues/82281/comments | 7 | 2019-09-03T16:02:14Z | 2020-02-01T12:34:09Z | https://github.com/kubernetes/kubernetes/issues/82281 | 488,692,994 | 82,281 |
[
"kubernetes",
"kubernetes"
] | The upper test heavily flakes in master:
```
--- FAIL: TestCNIPlugin (0.12s)\n"}
cni_test.go:279: Mismatch in expected output for setup hook. Expected 'ADD /proc/12345/ns/net podNamespace podName test_infra_container', got 'VERSION dummy '\n"}
cni_test.go:341: PASS:\tAddNetworkList(*context.emptyCtx,*li... | pkg/kubelet/dockershim/network/cni/cni_test.go heavily flakes | https://api.github.com/repos/kubernetes/kubernetes/issues/82280/comments | 6 | 2019-09-03T15:47:07Z | 2019-09-05T16:03:46Z | https://github.com/kubernetes/kubernetes/issues/82280 | 488,684,777 | 82,280 |
[
"kubernetes",
"kubernetes"
] | There are multiple cert controllers that use the same base struct, so when they log, you cannot differentiate which is which.
```
I0903 14:02:46.745135 1 certificate_controller.go:114] Starting certificate controller
``` | Cannot tell which cert controller is started | https://api.github.com/repos/kubernetes/kubernetes/issues/82278/comments | 1 | 2019-09-03T15:17:00Z | 2019-09-11T22:25:02Z | https://github.com/kubernetes/kubernetes/issues/82278 | 488,668,185 | 82,278 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Nowadays, when pod dead and its network tear down, PLEG will get pod status from underlying runtime(e.g. docker) with an empty pod IP address. then kubelet tries to get podIP from *PLEG's runtime states cache* and use this pod's old status' IP address, so that the pod IP address will be consistent a... | kubelet: getnericPLEG still return an empty podIP when get podIP from older cached status | https://api.github.com/repos/kubernetes/kubernetes/issues/82276/comments | 4 | 2019-09-03T15:09:41Z | 2020-04-20T03:14:41Z | https://github.com/kubernetes/kubernetes/issues/82276 | 488,664,121 | 82,276 |
[
"kubernetes",
"kubernetes"
] | I am trying to run Azure e2e tests:
```
go run hack/e2e.go -- --test --test_args="--ginkgo.focus=azure.*Inline.*file -kubeconfig=$KUBECONFIG --provider=azure -cloud-config-file $PWD/azure.cfg " --check-version-skew=false
```
The test creates a volume in the cloud + runs a pod with the volume as in-line. The ... | Azure storage tests are not working | https://api.github.com/repos/kubernetes/kubernetes/issues/82272/comments | 4 | 2019-09-03T14:31:38Z | 2019-09-11T22:25:54Z | https://github.com/kubernetes/kubernetes/issues/82272 | 488,642,124 | 82,272 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs -->
**Which jobs are failing**:
A few minutes back, Just after `go get -d k8s.io/kubernetes`, I tried to build the project by running `make`
when I run I get the folllowing error:
```
> API rule violation: nam... | ERROR: KUBE API rule check failed. Reported violations differ from known violations. | https://api.github.com/repos/kubernetes/kubernetes/issues/82271/comments | 9 | 2019-09-03T13:59:59Z | 2019-12-05T02:06:17Z | https://github.com/kubernetes/kubernetes/issues/82271 | 488,624,055 | 82,271 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
There are some kubelet's bugs that can cause podIP to be lost when pod at terminating state,
which has led to a serious production accident in our cluster, as some workload controllers (e.g. endpoints controller, custom controller) rely heavily on podIP.
Nowadays, when pod dead and its network... | podIP get lost when pod at terminating state | https://api.github.com/repos/kubernetes/kubernetes/issues/82268/comments | 11 | 2019-09-03T13:07:06Z | 2022-06-01T10:20:50Z | https://github.com/kubernetes/kubernetes/issues/82268 | 488,595,231 | 82,268 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
Stop using the generic parallelizer code from `client-go` in the generic scheduler.
**Why is this needed**:
Currently the generic scheduler is using the `client-go` parallelizer:
https://github.com/kubernetes/kubernetes/blob/c7c89f8c6140e0639dc8ba2d8dcdd6fdbd5409ae/pkg/schedul... | [Scheduler] Golang channels to parallelize Node filtering | https://api.github.com/repos/kubernetes/kubernetes/issues/82265/comments | 9 | 2019-09-03T12:41:21Z | 2020-02-01T09:31:10Z | https://github.com/kubernetes/kubernetes/issues/82265 | 488,581,634 | 82,265 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
Just like the `defaultMode` parameter that allows setting permissions on files contained into a mounted secret volume, we should be able to have a parameter that allows setting permissions on the mounte... | Choose permissions on secret mounted volume | https://api.github.com/repos/kubernetes/kubernetes/issues/82263/comments | 7 | 2019-09-03T09:13:07Z | 2022-10-13T18:28:29Z | https://github.com/kubernetes/kubernetes/issues/82263 | 488,485,345 | 82,263 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
When we delet... | Always update pod status when pleg.ContainerDied occurs | https://api.github.com/repos/kubernetes/kubernetes/issues/82258/comments | 6 | 2019-09-03T06:57:00Z | 2020-01-31T09:07:28Z | https://github.com/kubernetes/kubernetes/issues/82258 | 488,425,588 | 82,258 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
Since we have already made some upgrade on etcd client with new client balancer
from https://kubernetes.io/blog/2019/08/30/announcing-etcd-3-4/.
**Why is this needed**:
I think k8s needs it because it is more robust and make the etcd traffic more balance.
@jingyih @jpbetz @xi... | When will we upgrade the etcd client to the new Client Balancer | https://api.github.com/repos/kubernetes/kubernetes/issues/82251/comments | 6 | 2019-09-03T02:46:55Z | 2019-09-03T15:35:06Z | https://github.com/kubernetes/kubernetes/issues/82251 | 488,366,624 | 82,251 |
[
"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**:
```
q := ... | resource.Quantity.String() destroys reflect.DeepEqual() | https://api.github.com/repos/kubernetes/kubernetes/issues/82242/comments | 23 | 2019-09-02T13:49:45Z | 2020-02-07T00:42:10Z | https://github.com/kubernetes/kubernetes/issues/82242 | 488,200,266 | 82,242 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
The ability to provide a list attributes that (if present) should be mapped from the ID token used for authentication into userinfo.extra fields. These attributes could then be used for authorization deci... | OIDC: Allow any claim from an ID token to be mapped to userinfo extra attributes | https://api.github.com/repos/kubernetes/kubernetes/issues/82236/comments | 9 | 2019-09-02T10:34:02Z | 2023-11-14T20:02:42Z | https://github.com/kubernetes/kubernetes/issues/82236 | 488,121,281 | 82,236 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
We deployed a StatefulSet that defines some resource requests and limits, in particular:
```
resources:
limits:
ephemeral-storage: 2048M
memory: 230M
requests:
cpu: 20m
memory: 230M
```
After the StatefulSet pods were up and running, we called the `/api/v1/nodes/<no... | Kubelet API `stats/summary` does not report ephemeral storage information for Pods with no volumes | https://api.github.com/repos/kubernetes/kubernetes/issues/82234/comments | 9 | 2019-09-02T09:55:19Z | 2020-06-21T09:33:24Z | https://github.com/kubernetes/kubernetes/issues/82234 | 488,105,251 | 82,234 |
[
"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... | why the contianer memory limit in cgroup not accurate | https://api.github.com/repos/kubernetes/kubernetes/issues/82230/comments | 6 | 2019-09-02T08:59:40Z | 2019-09-06T10:42:13Z | https://github.com/kubernetes/kubernetes/issues/82230 | 488,079,314 | 82,230 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
Kubelet rewrites container statuses of a pod to null terminated status when it is deleted. Apparently it is done in order to trigger a pod deletion request to the apiserver. It would be useful if we could... | Container statuses get wiped out after pod deletion | https://api.github.com/repos/kubernetes/kubernetes/issues/82218/comments | 5 | 2019-09-01T12:28:42Z | 2020-01-29T14:25:38Z | https://github.com/kubernetes/kubernetes/issues/82218 | 487,880,210 | 82,218 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
given hpa values:
```
spec:
metrics:
- resource:
name: memory
target:
averageUtilization: 80
type: Utilization
type: Resource
- resource:
name: cpu
target:
averageUtilization: 80
type: Utilization
type: Resource
``... | hpa.v2beta2.autoscaling starts scaling up when only half of target is reached | https://api.github.com/repos/kubernetes/kubernetes/issues/82217/comments | 2 | 2019-09-01T10:15:56Z | 2019-09-01T12:38:58Z | https://github.com/kubernetes/kubernetes/issues/82217 | 487,867,199 | 82,217 |
[
"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**:
Volume manage... | Flex volume: inconsistency between directory name and plugin name cause orphaned pod to fail to clean up | https://api.github.com/repos/kubernetes/kubernetes/issues/82215/comments | 5 | 2019-09-01T08:15:36Z | 2019-09-03T15:26:02Z | https://github.com/kubernetes/kubernetes/issues/82215 | 487,856,012 | 82,215 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
/sig testing
/sig node
Make runtime handler a variable that gets filled in by the test setup.
This is a follow-up issue https://github.com/kubernetes/kubernetes/pull/81915#discussion_r319733052
| Test cluster must configure test-handler | https://api.github.com/repos/kubernetes/kubernetes/issues/82213/comments | 11 | 2019-09-01T07:20:00Z | 2020-02-26T09:15:08Z | https://github.com/kubernetes/kubernetes/issues/82213 | 487,851,626 | 82,213 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
Ability to create empty ingresses
**Why is this needed**:
Empty ingresses will be patched later by scripts/apps to add/update/delete rules dynamically as needed.
Note: I am using the described stra... | Add ability to create empty ingress | https://api.github.com/repos/kubernetes/kubernetes/issues/82203/comments | 17 | 2019-08-31T08:51:34Z | 2024-08-16T11:05:18Z | https://github.com/kubernetes/kubernetes/issues/82203 | 487,748,037 | 82,203 |
[
"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-new-master-gci-kubectl-skew`
**Which test(s) are failing**:
`[sig-cli] Kubectl client [k8s.io] Kubectl logs should be able to retrieve and filter logs [C... | [Failing Test] [sig-cli] Kubectl client [k8s.io] Kubectl logs should be able to retrieve and filter logs [Conformance] | https://api.github.com/repos/kubernetes/kubernetes/issues/82201/comments | 6 | 2019-08-31T00:18:00Z | 2019-09-03T21:25:52Z | https://github.com/kubernetes/kubernetes/issues/82201 | 487,709,305 | 82,201 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
CRI CPU metrics are incorrect when using a large number of cores, due to a `uint64` overflow.
**What you expected to happen**:
CPU metrics should be correct for arbitrarily high numbers of cores.
**How to reproduce it (as minimally and precisely as possible)**:
Deploy a pod with 20 CPU units... | CRI pod CPU metrics incorrect for pods with 20+ CPUs | https://api.github.com/repos/kubernetes/kubernetes/issues/82195/comments | 2 | 2019-08-30T20:41:21Z | 2019-09-24T00:31:41Z | https://github.com/kubernetes/kubernetes/issues/82195 | 487,663,051 | 82,195 |
Subsets and Splits
Unique Owner-Repo Count
Counts the number of unique owner-repos in the dataset, providing a basic understanding of diverse repositories.