issue_owner_repo listlengths 2 2 | issue_body stringlengths 0 261k ⌀ | issue_title stringlengths 1 925 | issue_comments_url stringlengths 56 81 | issue_comments_count int64 0 2.5k | issue_created_at stringlengths 20 20 | issue_updated_at stringlengths 20 20 | issue_html_url stringlengths 37 62 | issue_github_id int64 387k 2.91B | issue_number int64 1 131k |
|---|---|---|---|---|---|---|---|---|---|
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs -->
**Which jobs are failing / job(s) where test is present**:
* ci-kubernetes-e2e-gce-new-master-upgrade-master-parallel
* ci-kubernetes-e2e-gce-new-master-gci-kubectl-skew
**Which test(s) are failing**:
[sig-c... | [Failing Test] [sig-cli] Kubectl client [k8s.io] Simple pod should handle in-cluster config | https://api.github.com/repos/kubernetes/kubernetes/issues/81845/comments | 12 | 2019-08-23T15:52:00Z | 2019-09-01T01:38:50Z | https://github.com/kubernetes/kubernetes/issues/81845 | 484,599,292 | 81,845 |
[
"kubernetes",
"kubernetes"
] | **What happened**: Kubernetes takes much time to realize the Node goes down when it is the one that `locks the kube-control-manager endpoint`.
**What you expected to happen**: Kubernetes should take the same time when I remove the `NIC interface` from a note that `locks the kube-control-manager endpoint` realizes th... | Leader election when Leader Machine goes down | https://api.github.com/repos/kubernetes/kubernetes/issues/81837/comments | 11 | 2019-08-23T13:16:20Z | 2021-03-03T12:54:20Z | https://github.com/kubernetes/kubernetes/issues/81837 | 484,525,353 | 81,837 |
[
"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... | Can ResourceQuota limit CustomResource hard num | https://api.github.com/repos/kubernetes/kubernetes/issues/81827/comments | 3 | 2019-08-23T06:47:38Z | 2019-08-24T17:17:33Z | https://github.com/kubernetes/kubernetes/issues/81827 | 484,358,699 | 81,827 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs -->
Setting PodPriority directly when adminssion Priority enable,the Pod is rejected.
To fix this, we need to create new priority classes for these tests.
**Which jobs are failing**:
https://gcsweb.k8s.io/g... | [Failing Tests] ci-kubernetes-node-kubelet-serial which set PodPriority are failing when adminssion Priority enable | https://api.github.com/repos/kubernetes/kubernetes/issues/81824/comments | 9 | 2019-08-23T04:14:26Z | 2020-01-16T15:48:23Z | https://github.com/kubernetes/kubernetes/issues/81824 | 484,321,061 | 81,824 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
### Solution 1: when the InitializerConfiguration's resource is `deployment`
```yaml
apiVersion: admissionregistration.k8s.io/v1alpha1
kind: InitializerConfiguration
metadata:
name: test-testser... | why deployment.spec.template.metadata.initializers.pending=[] has no effective | https://api.github.com/repos/kubernetes/kubernetes/issues/81823/comments | 2 | 2019-08-23T03:15:10Z | 2019-08-23T03:18:50Z | https://github.com/kubernetes/kubernetes/issues/81823 | 484,308,491 | 81,823 |
[
"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 looked at t... | Server side printers describe age columns as timestamps | https://api.github.com/repos/kubernetes/kubernetes/issues/81817/comments | 10 | 2019-08-23T00:25:14Z | 2020-06-18T17:30:52Z | https://github.com/kubernetes/kubernetes/issues/81817 | 484,273,684 | 81,817 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
I have a service , which have underlying set of pods that opens TCP socket on 17500. However the Service will forward the request to pod that are already connected and serving requests which causes conne... | Kubernetes Service enable TCP check | https://api.github.com/repos/kubernetes/kubernetes/issues/81813/comments | 8 | 2019-08-22T23:14:31Z | 2020-01-21T04:08:38Z | https://github.com/kubernetes/kubernetes/issues/81813 | 484,257,940 | 81,813 |
[
"kubernetes",
"kubernetes"
] | Need to push the latest CoreDNS image to gcr.io
The 1.6.2 image is available in docker coredns/coredns:1.6.2
This is the script used for pushing the image:
```
#!/bin/sh
if [ -z "$1" -o -z "$2" -o -z "$3" -o -z "$4" ]; then
echo "usage: $0 <src-reg> <image> <tag> <dst-reg>" > /dev/stderr
echo "e... | Push the CoreDNS 1.6.2 image in gcr.io | https://api.github.com/repos/kubernetes/kubernetes/issues/81810/comments | 3 | 2019-08-22T20:50:41Z | 2019-08-29T13:09:31Z | https://github.com/kubernetes/kubernetes/issues/81810 | 484,210,032 | 81,810 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
When using `kubectl get --raw "..."`, the response body should be printed without any modification.
**Why is this needed**:
When using `kubectl get --raw`, it is necessary to make use of the "continue" token for iterating through collections. Unfortunately, the continue tok... | kubectl --raw should print unmodified response body | https://api.github.com/repos/kubernetes/kubernetes/issues/81806/comments | 11 | 2019-08-22T19:39:01Z | 2020-10-23T18:00:43Z | https://github.com/kubernetes/kubernetes/issues/81806 | 484,174,995 | 81,806 |
[
"kubernetes",
"kubernetes"
] | [import-boss](https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/code-generator/cmd/import-boss/main.go) is used in our CI tests ([./hack/verify-import-boss.sh](https://github.com/kubernetes/kubernetes/blob/master/hack/verify-import-boss.sh)) to verify import restrictions in various places througho... | Document the use of import-boss | https://api.github.com/repos/kubernetes/kubernetes/issues/81804/comments | 20 | 2019-08-22T19:00:13Z | 2020-06-22T21:14:09Z | https://github.com/kubernetes/kubernetes/issues/81804 | 484,159,167 | 81,804 |
[
"kubernetes",
"kubernetes"
] | We recently discovered in https://github.com/kubernetes/kubernetes/pull/81246#issuecomment-523510399 that the import restrictions for the e2e testing framework, [/test/e2e/framework/.import-restrictions](https://github.com/kubernetes/kubernetes/blob/master/test/e2e/framework/.import-restrictions), are not being taken i... | [e2e] e2e framework import-restrictions need to be fixed | https://api.github.com/repos/kubernetes/kubernetes/issues/81803/comments | 7 | 2019-08-22T18:39:34Z | 2020-01-29T18:49:16Z | https://github.com/kubernetes/kubernetes/issues/81803 | 484,150,426 | 81,803 |
[
"kubernetes",
"kubernetes"
] | with this PR merging we found some pkg/controller imports that went unnoticed because we now also check _test.go files:
https://github.com/kubernetes/kubernetes/pull/81752
there are a few suspicious imports that need double checking by different sigs:
- TODO bring sig owners
https://github.com/kubernetes/kubern... | evaluate newly discovered import depedencies in pkg/controller | https://api.github.com/repos/kubernetes/kubernetes/issues/81799/comments | 7 | 2019-08-22T18:15:39Z | 2020-03-15T20:28:37Z | https://github.com/kubernetes/kubernetes/issues/81799 | 484,140,417 | 81,799 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
I use calico as a network plugin. When the node reboots, calico takes a few minutes to recover the network and refresh the routing table. During this time, POD IP can not be used, business
relying on t... | Pod created before container network ready | https://api.github.com/repos/kubernetes/kubernetes/issues/81781/comments | 14 | 2019-08-22T11:21:26Z | 2020-02-29T20:36:22Z | https://github.com/kubernetes/kubernetes/issues/81781 | 483,934,318 | 81,781 |
[
"kubernetes",
"kubernetes"
] | **What happened**: kube-scheduler panics when client-go tries to finish the existing event series, see: https://logs.openlabtesting.org/logs/periodic-4/16/github.com/kubernetes/cloud-provider-openstack/master/cloud-provider-openstack-acceptance-test-e2e-conformance/ecdc3cc/logs/kubernetes/kube-scheduler.log
**What ... | kube-scheduler panics when trying to finish its event series | https://api.github.com/repos/kubernetes/kubernetes/issues/81779/comments | 0 | 2019-08-22T11:01:09Z | 2019-08-23T15:23:32Z | https://github.com/kubernetes/kubernetes/issues/81779 | 483,921,893 | 81,779 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
The kube-proxy sets `/proc/sys/net/ipv4/vs/conn_reuse_mode` to zero
https://github.com/kubernetes/kubernetes/blob/master/pkg/proxy/ipvs/proxier.go#L340
This has the effect that when:
- kube-proxy uses ipvs mode and an ipvs virtualserver is configured with only a few realservers (pod replicas)
... | kube-proxy ipvs conn_reuse_mode setting causes errors with high load from single client | https://api.github.com/repos/kubernetes/kubernetes/issues/81775/comments | 59 | 2019-08-22T09:08:46Z | 2021-09-08T01:32:58Z | https://github.com/kubernetes/kubernetes/issues/81775 | 483,865,998 | 81,775 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
1. when I create a pod,the pod first has no resource to allocate

desc pod:

2.wait some minutes for resource release
3.when have enough resour... | pod successfully assigned event miss when pod first encounter FailedScheduling | https://api.github.com/repos/kubernetes/kubernetes/issues/81773/comments | 7 | 2019-08-22T08:39:31Z | 2020-01-23T03:55:07Z | https://github.com/kubernetes/kubernetes/issues/81773 | 483,850,051 | 81,773 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
I have a CRD file and apply it to k8s:
```
# cat crd-12.yaml
kind: CustomResourceDefinition
apiVersion: apiextensions.k8s.io/v1beta1
metadata:
name: authorizationpolicies.rbac.istio.io
labels:
app: istio-pilot
istio: rbac
heritage: Tiller
release: istio
spec:
grou... | The created CRD cannot be recognized | https://api.github.com/repos/kubernetes/kubernetes/issues/81772/comments | 2 | 2019-08-22T08:32:33Z | 2019-08-31T09:21:36Z | https://github.com/kubernetes/kubernetes/issues/81772 | 483,846,663 | 81,772 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs -->
**Which test(s) are failing**:
When `--clean-start` is specified in kubetest, the `SetupSuite` is trying to delete all namespaces except `kube-system`, `default` and `kube-public` (see [here](https://github.com/k... | e2e SetupSuite is sometimes unable to delete kube-node-lease namespace | https://api.github.com/repos/kubernetes/kubernetes/issues/81766/comments | 1 | 2019-08-22T06:44:39Z | 2019-08-23T11:55:47Z | https://github.com/kubernetes/kubernetes/issues/81766 | 483,800,600 | 81,766 |
[
"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 doing ... | Deployment leaves more replicasets than revisionHistoryLimit | https://api.github.com/repos/kubernetes/kubernetes/issues/81761/comments | 5 | 2019-08-22T02:11:07Z | 2019-08-23T07:00:11Z | https://github.com/kubernetes/kubernetes/issues/81761 | 483,732,035 | 81,761 |
[
"kubernetes",
"kubernetes"
] | At one point hyperkube was going to take everything over but that day is gone:
https://github.com/kubernetes/kubernetes/issues/16508
We don't have any owners for hyperkube and we have pending issues like https://github.com/kubernetes/kubernetes/issues/80374 and https://github.com/kubernetes/kubernetes/issues/71719
... | Move hyperkube binary and images out from main k/k repository | https://api.github.com/repos/kubernetes/kubernetes/issues/81760/comments | 29 | 2019-08-22T02:04:38Z | 2019-11-07T18:54:42Z | https://github.com/kubernetes/kubernetes/issues/81760 | 483,730,619 | 81,760 |
[
"kubernetes",
"kubernetes"
] | This is likely related to #80586, but is required for us to measure and increase coverage in the right areas of Kubernetes.
We'd like verification, but this seems to have led us to discover:
- [69 gated, deprecated, or non-ga fields](https://github.com/cncf/apisnoop/blob/v3_rainbow/org/explorations/field_properties... | Add OpenAPI Field/Properties for release, feature_gate, required, and deprecated metadata | https://api.github.com/repos/kubernetes/kubernetes/issues/81759/comments | 27 | 2019-08-22T01:53:42Z | 2021-06-10T07:52:47Z | https://github.com/kubernetes/kubernetes/issues/81759 | 483,728,044 | 81,759 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
When the Kubelet is under disk pressure, it garbage-collects unused container images. If this isn't enough, it evicts pods and then deletes their (now unused) container images. If the disk pressure is due to external data files present in the same partition as the datastore, this can proceed until a... | Kubelet garbage-collects the pause image, which might be unpullable in ContainerD | https://api.github.com/repos/kubernetes/kubernetes/issues/81756/comments | 34 | 2019-08-22T01:21:48Z | 2022-04-12T11:51:08Z | https://github.com/kubernetes/kubernetes/issues/81756 | 483,721,152 | 81,756 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
A new test ca... | Use hostpath pod instead of ssh in volumemode e2e test | https://api.github.com/repos/kubernetes/kubernetes/issues/81751/comments | 12 | 2019-08-21T22:27:54Z | 2019-12-20T01:37:23Z | https://github.com/kubernetes/kubernetes/issues/81751 | 483,681,512 | 81,751 |
[
"kubernetes",
"kubernetes"
] | **Which jobs are failing**:
Conformance - OpenStack
**Which test(s) are failing**:
Most of them
**Since when has it been failing**:
08-20
**Testgrid link**:
https://testgrid.k8s.io/sig-release-master-informing#Conformance%20-%20OpenStack
**Reason for failure**:
```
should execute prestop http hook... | [Failing Test] Conformance - OpenStack | https://api.github.com/repos/kubernetes/kubernetes/issues/81746/comments | 21 | 2019-08-21T20:58:37Z | 2019-09-12T13:50:57Z | https://github.com/kubernetes/kubernetes/issues/81746 | 483,649,091 | 81,746 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
I have a StatefulSet, with a single pod, and a single persistent volume. The volume is a local volume.
```
Name: local-pv-e943245f
Labels: <none>
Annotations: pv.kubernetes.io/bound-by-controller: yes
pv.kubernetes.io/provisioned-by: local-volu... | Race condition when mounting local storage volumes leads to data loss | https://api.github.com/repos/kubernetes/kubernetes/issues/81737/comments | 13 | 2019-08-21T18:28:44Z | 2020-01-19T12:29:36Z | https://github.com/kubernetes/kubernetes/issues/81737 | 483,581,075 | 81,737 |
[
"kubernetes",
"kubernetes"
] | `kubectl logs -f` doesn't work for Windows node.
After some investigation, I think the problem is that for Docker the log file `kubectl logs` reads is a symlink to the actual docker container log file.
On linux, I believe fsnotify follows symlink by default https://github.com/fsnotify/fsnotify/issues/199, so it w... | kubectl logs -f doesn't work for Windows node | https://api.github.com/repos/kubernetes/kubernetes/issues/81735/comments | 2 | 2019-08-21T17:47:18Z | 2019-08-23T13:53:25Z | https://github.com/kubernetes/kubernetes/issues/81735 | 483,560,208 | 81,735 |
[
"kubernetes",
"kubernetes"
] | I followed the document to create an e2e cluster https://github.com/kubernetes/kubernetes/blob/master/cluster/gce/windows/README-GCE-Windows-kube-up.md
However, `gcloud compute ssh` doesn't work after the cluster is up.
I got the following error:
```
Warning: Permanently added 'compute.3660176483394069101' (ECD... | SSH in Windows test cluster doesn't work | https://api.github.com/repos/kubernetes/kubernetes/issues/81734/comments | 4 | 2019-08-21T17:41:50Z | 2019-08-23T10:27:31Z | https://github.com/kubernetes/kubernetes/issues/81734 | 483,557,680 | 81,734 |
[
"kubernetes",
"kubernetes"
] | #78458 introduced readyz as a readiness endpoint for the apiserver. In that PR, we repurpose healthz to act as a liveness endpoint which behavior can change when `--maximum-startup-sequence-duration` is set to a non-zero value. Instead of repurposing healthz, let's just create an actual independent liveness endpoint (i... | Create a livez endpoint instead of repurposing healthz | https://api.github.com/repos/kubernetes/kubernetes/issues/81733/comments | 0 | 2019-08-21T17:17:22Z | 2019-08-30T02:56:33Z | https://github.com/kubernetes/kubernetes/issues/81733 | 483,546,968 | 81,733 |
[
"kubernetes",
"kubernetes"
] | We have multiple copies of pkg/version in various spots. In #81173, we create a copy of pkg/version in component-base. This will eventually allow for the removal of pkg/version completely, but we can also use this to replace the kubectl usage (and possibly other usages).
/assign
/cc @liggitt
| Collapse various pkg/version to the one which will be present in component-base | https://api.github.com/repos/kubernetes/kubernetes/issues/81731/comments | 2 | 2019-08-21T17:09:30Z | 2019-09-17T21:27:17Z | https://github.com/kubernetes/kubernetes/issues/81731 | 483,543,700 | 81,731 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
kube-proxy ... | kube-proxy fails to delete nat entries with IPv6 | https://api.github.com/repos/kubernetes/kubernetes/issues/81729/comments | 16 | 2019-08-21T16:27:12Z | 2019-11-16T16:51:42Z | https://github.com/kubernetes/kubernetes/issues/81729 | 483,524,497 | 81,729 |
[
"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 k8s is ... | cpuset.cpus file is not updated for the pod created with Guaranteed QoS class | https://api.github.com/repos/kubernetes/kubernetes/issues/81728/comments | 6 | 2019-08-21T16:07:18Z | 2019-11-13T10:05:52Z | https://github.com/kubernetes/kubernetes/issues/81728 | 483,514,278 | 81,728 |
[
"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-serial`
**Which test(s) are failing**:
`NodeFeature:HugePage`-tests
**Since when has it been failing**:
Unsure
**Testgrid link**:
https://testgr... | [Flaky tests] NodeFeature:HugePage in ci-kubernetes-node-kubelet-serial | https://api.github.com/repos/kubernetes/kubernetes/issues/81726/comments | 7 | 2019-08-21T15:35:32Z | 2019-12-06T07:45:45Z | https://github.com/kubernetes/kubernetes/issues/81726 | 483,496,754 | 81,726 |
[
"kubernetes",
"kubernetes"
] | **What happened**: When creating a `PersistentVolume` and setting a `matchFields` selector in `spec.nodeAffinity.required.nodeSelectorTerms`, Pod scheduling fails.
**What you expected to happen**: Pod scheduling succeeds.
**How to reproduce it (as minimally and precisely as possible)**:
- Create a StorageClass o... | Volumes with `nodeSelectorTerm`s using `matchFields` not handled properly during scheduling | https://api.github.com/repos/kubernetes/kubernetes/issues/81725/comments | 10 | 2019-08-21T15:11:11Z | 2020-09-13T22:29:15Z | https://github.com/kubernetes/kubernetes/issues/81725 | 483,482,110 | 81,725 |
[
"kubernetes",
"kubernetes"
] | The bitbucket.org/ww/goautoneg package is hosted at bitbucket.org using a Mercurial repository. This is currently at risk of being deleted next year: https://bitbucket.org/blog/sunsetting-mercurial-support-in-bitbucket | bitbucket.org/ww/goautoneg dependency at risk of being deleted | https://api.github.com/repos/kubernetes/kubernetes/issues/81724/comments | 7 | 2019-08-21T14:22:23Z | 2019-08-22T12:23:08Z | https://github.com/kubernetes/kubernetes/issues/81724 | 483,452,977 | 81,724 |
[
"kubernetes",
"kubernetes"
] | Add the reason the pod was killed, e.g. exceeded memory limit, liveness probe, readiness probe...
Kubelet outputs
"Killing container with id docker://your-example-application:Need to kill Pod"
Reason: "Killing"
This message is unhelpful when it comes to diagnosing why the pod was killed, and can be improved wit... | Give the proper reason for killing pods | https://api.github.com/repos/kubernetes/kubernetes/issues/81723/comments | 73 | 2019-08-21T14:08:55Z | 2025-02-28T07:36:07Z | https://github.com/kubernetes/kubernetes/issues/81723 | 483,444,850 | 81,723 |
[
"kubernetes",
"kubernetes"
] | /priority important-longterm
/sig scheduling
/assign
Currently, the scheduler perf works pretty well for most of the time, but some issues could affect the benchmark numbers. We could improve the accuracy and usability through the following tasks:
- [x] Get a precise benchmarking test result for each test
... | Enhancement for scheduler perf | https://api.github.com/repos/kubernetes/kubernetes/issues/81719/comments | 25 | 2019-08-21T11:07:59Z | 2020-04-03T14:45:37Z | https://github.com/kubernetes/kubernetes/issues/81719 | 483,354,826 | 81,719 |
[
"kubernetes",
"kubernetes"
] | i have a manual k8s cluster with VMs running in Azure cloud(its not on AKS).I am getting pending status for external ip. So my question is will i get a external ip for loadbalancer from azure cloud with this setup or cloud provider provides external ip only when we run our cluster in Azure K8s service. | external-ip-pending | https://api.github.com/repos/kubernetes/kubernetes/issues/81717/comments | 7 | 2019-08-21T09:59:33Z | 2020-01-20T14:55:36Z | https://github.com/kubernetes/kubernetes/issues/81717 | 483,323,171 | 81,717 |
[
"kubernetes",
"kubernetes"
] | `kubectl apply -f prometheus-statefulset.yaml`
```
#kubectl describe -n kube-system pods prometheus-0
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning FailedScheduling 102s (x27... | kubectl apply -f prometheus-statefulset.yaml storageclass.storage.k8s.io "standard" not found | https://api.github.com/repos/kubernetes/kubernetes/issues/81714/comments | 1 | 2019-08-21T09:01:19Z | 2019-08-21T09:30:51Z | https://github.com/kubernetes/kubernetes/issues/81714 | 483,291,284 | 81,714 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
When a new po... | Restart For Containers With Liveness Probing Failure | https://api.github.com/repos/kubernetes/kubernetes/issues/81713/comments | 12 | 2019-08-21T08:51:19Z | 2020-09-10T14:34:36Z | https://github.com/kubernetes/kubernetes/issues/81713 | 483,285,989 | 81,713 |
[
"kubernetes",
"kubernetes"
] |
**What happened**:
The cri parse did not parse containerd log
**What you expected to happen**:
The cri parser can parse containerd log correctly
**How to reproduce it (as minimally and precisely as possible)**:
Here is what logs looks like:
2019-08-21T09:24:33.260739149+02:00 stdout F 2019-08-21 07:24:33.... | The cri parse did not parse containerd(1.2.5) log(kubernetes 1.14.3) | https://api.github.com/repos/kubernetes/kubernetes/issues/81710/comments | 1 | 2019-08-21T07:39:17Z | 2019-08-21T07:40:39Z | https://github.com/kubernetes/kubernetes/issues/81710 | 483,250,735 | 81,710 |
[
"kubernetes",
"kubernetes"
] | For example, we send one binding API call, and bind several pods to nodes during this call.
/sig api-machinery
/kind support | Does kubernetes APIServer support executing batch operations in one call ? | https://api.github.com/repos/kubernetes/kubernetes/issues/81694/comments | 2 | 2019-08-21T02:03:37Z | 2019-08-21T11:05:08Z | https://github.com/kubernetes/kubernetes/issues/81694 | 483,161,414 | 81,694 |
[
"kubernetes",
"kubernetes"
] | While investigating one flaky test for in-tree GCE PD in Windows "should store data"
https://testgrid.k8s.io/sig-windows#gce-windows-master&width=20&include-filter-by-regex=should%20store%20data, we noticed the following behavior.
1. Start a pod with a GCE PD volume, and write some content to a file (use echo comma... | Data caching issue for writing and reading files in Windows container | https://api.github.com/repos/kubernetes/kubernetes/issues/81690/comments | 9 | 2019-08-20T23:18:59Z | 2020-10-03T22:28:44Z | https://github.com/kubernetes/kubernetes/issues/81690 | 483,125,881 | 81,690 |
[
"kubernetes",
"kubernetes"
] | curl /apis/batch/v1beta1/namespaces/pod999/cronjobs?limit=2 returns all cronjobs instead of 2. This also applies to events and all other resources.
In https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.15/#event-v1-core
There is a query parameter called limit where limit is a maximum number of respo... | api limit parameter doesn't work | https://api.github.com/repos/kubernetes/kubernetes/issues/81686/comments | 5 | 2019-08-20T21:58:13Z | 2019-08-26T21:25:38Z | https://github.com/kubernetes/kubernetes/issues/81686 | 483,103,002 | 81,686 |
[
"kubernetes",
"kubernetes"
] | I want to only return a single pod from the api to reduce api load and have a small response body.
There is a `--chunk-size` option which returns 1 pod at a time, but paginates over all pods, so that does not help. | support --limit in kubectl get | https://api.github.com/repos/kubernetes/kubernetes/issues/81683/comments | 9 | 2019-08-20T21:38:43Z | 2022-03-28T12:03:24Z | https://github.com/kubernetes/kubernetes/issues/81683 | 483,095,953 | 81,683 |
[
"kubernetes",
"kubernetes"
] | This is a tracking issue for the following requirements. These requirements were byproduct of adding dualstack and even a bigger discussion wrt overall UX. Please add references to other threads, comments, PRs below.
Requirements:
1. Allow users to change cluster cidrs on a running cluster. The use case is, users ... | Handling changes to: Cluster CIDRs and Service CIDRS | https://api.github.com/repos/kubernetes/kubernetes/issues/81677/comments | 17 | 2019-08-20T19:08:32Z | 2024-03-28T17:10:53Z | https://github.com/kubernetes/kubernetes/issues/81677 | 483,032,216 | 81,677 |
[
"kubernetes",
"kubernetes"
] | I have posted this to StackOverflow (https://stackoverflow.com/questions/57566773/how-to-change-the-umask-when-mounting-volumes-in-kubernetes-pods) however, I think there is something missing in the design and as such it should be posted here.
I have tried this in Kubernetes 1.5
Given a `SecurityContext` for a pod,... | There seems to be no way of setting permissions on the mount path | https://api.github.com/repos/kubernetes/kubernetes/issues/81676/comments | 8 | 2019-08-20T18:44:21Z | 2020-01-19T04:21:37Z | https://github.com/kubernetes/kubernetes/issues/81676 | 483,021,929 | 81,676 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
Right now you can only specify a single CIDR block to kube-proxy as the cluster CIDR via `--cluster-cidr` (per docs, `traffic sent to a Service cluster IP from outside this range will be masqueraded and traffic sent from pods to an external LoadBalancer IP will be directed to the r... | kube-proxy --cluster-cidr should support multiple CIDRs | https://api.github.com/repos/kubernetes/kubernetes/issues/81675/comments | 20 | 2019-08-20T18:20:07Z | 2021-04-21T16:36:24Z | https://github.com/kubernetes/kubernetes/issues/81675 | 483,010,555 | 81,675 |
[
"kubernetes",
"kubernetes"
] | Not sure if this is a bug or I am doing something wrong...
I am trying to expose 5 ports for an Informix Container which is within a statefulSet. It has a headless service attached, to allow other internal stateless sets communicate with it internally.
I can ping the headless service `informix-set-service` from ... | Issues with Ports on headless service attached to Stateless Set | https://api.github.com/repos/kubernetes/kubernetes/issues/81666/comments | 3 | 2019-08-20T15:07:40Z | 2019-08-21T09:53:00Z | https://github.com/kubernetes/kubernetes/issues/81666 | 482,919,788 | 81,666 |
[
"kubernetes",
"kubernetes"
] | **Which jobs are failing**:
gce-master-scale-performance
**Which test(s) are failing**:
load
**Since when has it been failing**:
load failed on 2019-08-19, green otherwise
**Testgrid link**:
https://k8s-testgrid.appspot.com/sig-scalability-gce#gce-master-scale-performance
**Reason for failure**:
> [mea... | [Failing Test] gce-master-scale-performance - 5k load | https://api.github.com/repos/kubernetes/kubernetes/issues/81665/comments | 3 | 2019-08-20T14:45:13Z | 2019-08-30T12:38:44Z | https://github.com/kubernetes/kubernetes/issues/81665 | 482,906,397 | 81,665 |
[
"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**:
Based on resp... | Different verbs for one operation | https://api.github.com/repos/kubernetes/kubernetes/issues/81659/comments | 6 | 2019-08-20T13:37:42Z | 2019-08-26T21:21:47Z | https://github.com/kubernetes/kubernetes/issues/81659 | 482,866,644 | 81,659 |
[
"kubernetes",
"kubernetes"
] | As #81189 has been merged, there are a lot of packages that cannot pass the static check and we need to clean them up!
Step 1: Remove one or two packages (related packages) from the list in - https://github.com/kubernetes/kubernetes/blame/master/hack/.staticcheck_failures
Step 2: Run hack/verify-staticcheck.sh and ... | Fix static check failures | https://api.github.com/repos/kubernetes/kubernetes/issues/81657/comments | 80 | 2019-08-20T13:08:45Z | 2020-06-23T02:14:33Z | https://github.com/kubernetes/kubernetes/issues/81657 | 482,850,808 | 81,657 |
[
"kubernetes",
"kubernetes"
] | **Which jobs are failing**:
gce-master-scale-performance
**Which test(s) are failing**:
density
**Since when has it been failing**:
density failed on 2019-08-01, 2019-08-08 and 2019-08-18, green otherwise
**Testgrid link**:
https://k8s-testgrid.appspot.com/sig-scalability-gce#gce-master-scale-performance
... | [Failing Test] gce-master-scale-performance - 5k density | https://api.github.com/repos/kubernetes/kubernetes/issues/81654/comments | 5 | 2019-08-20T11:58:01Z | 2019-09-02T13:58:04Z | https://github.com/kubernetes/kubernetes/issues/81654 | 482,816,687 | 81,654 |
[
"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**:
```worker nod... | worker nodes appear many created status containers | https://api.github.com/repos/kubernetes/kubernetes/issues/81646/comments | 15 | 2019-08-20T08:03:51Z | 2020-01-23T10:01:15Z | https://github.com/kubernetes/kubernetes/issues/81646 | 482,706,243 | 81,646 |
[
"kubernetes",
"kubernetes"
] | I have an EKS cluster and want to create Persistence storage for Prometheus pod with EBS. The PVC status in cluster shows as Bound but the pod is getting failed to start up due to missing Volumes.
Verified that EBS volume is also not created.
**Root Volume Encryption enabled:** Yes
**Kubenetes Version:** : 1.... | PVC in Bound status but pod not able to find volume | https://api.github.com/repos/kubernetes/kubernetes/issues/81644/comments | 5 | 2019-08-20T07:37:36Z | 2020-01-17T09:40:38Z | https://github.com/kubernetes/kubernetes/issues/81644 | 482,694,932 | 81,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**:
After upgradi... | Unable to connect to a http service after upgrade to kubernetes 1.13.7 | https://api.github.com/repos/kubernetes/kubernetes/issues/81642/comments | 14 | 2019-08-20T07:17:51Z | 2019-10-31T21:13:59Z | https://github.com/kubernetes/kubernetes/issues/81642 | 482,686,907 | 81,642 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
Add kubelet eviction plugins. So we can customize kubelet eviction-manager behaviors.
**Why is this needed**:
kubelet already supported device plugins, so we can allocate special resouce for pods.But s... | Add Pod eviction plugins | https://api.github.com/repos/kubernetes/kubernetes/issues/81641/comments | 3 | 2019-08-20T06:23:50Z | 2019-12-19T07:22:41Z | https://github.com/kubernetes/kubernetes/issues/81641 | 482,667,080 | 81,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**:
pod deploy and ... | OutOfcpu occurs when exceed Allocatable CPU resource | https://api.github.com/repos/kubernetes/kubernetes/issues/81639/comments | 5 | 2019-08-20T06:15:43Z | 2020-01-17T09:40:40Z | https://github.com/kubernetes/kubernetes/issues/81639 | 482,664,462 | 81,639 |
[
"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**:
Duplicate upd... | duplicate update notification when kube-apiserver restart | https://api.github.com/repos/kubernetes/kubernetes/issues/81638/comments | 6 | 2019-08-20T06:15:18Z | 2019-08-21T11:12:37Z | https://github.com/kubernetes/kubernetes/issues/81638 | 482,664,345 | 81,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**:
Occasionally,... | AWS: node lifecycle controller occasionally removes k8s nodes from the cluster immediately after startup | https://api.github.com/repos/kubernetes/kubernetes/issues/81636/comments | 17 | 2019-08-20T04:45:51Z | 2020-10-19T17:26:56Z | https://github.com/kubernetes/kubernetes/issues/81636 | 482,641,511 | 81,636 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
master failed... | iptables rule wrong order causes legitimate packets rejected | https://api.github.com/repos/kubernetes/kubernetes/issues/81635/comments | 13 | 2019-08-20T04:22:32Z | 2019-08-26T19:22:53Z | https://github.com/kubernetes/kubernetes/issues/81635 | 482,636,280 | 81,635 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
1. client-go distinguish the errors of 4 layer and 7 layer. like "Connection reset by peer"(4 layer) and http error from server(7 layer). [now the 4 layer is fused into 7 layer error to make response. ](https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/client-... | add livenessProbe and readinessProbe for kube-proxy | https://api.github.com/repos/kubernetes/kubernetes/issues/81630/comments | 19 | 2019-08-20T03:40:01Z | 2020-02-24T23:42:14Z | https://github.com/kubernetes/kubernetes/issues/81630 | 482,627,374 | 81,630 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
A way for CRDs to specify a custom preferred propagationPolicy for deletion.
**Why is this needed**:
I am speaking as a developer of a CRD with a corresponding controller (using [Kubebuilder](https://... | Allow specification of preferred CRD deletion propagationPolicy | https://api.github.com/repos/kubernetes/kubernetes/issues/81628/comments | 9 | 2019-08-20T00:36:56Z | 2020-10-21T20:33:19Z | https://github.com/kubernetes/kubernetes/issues/81628 | 482,589,330 | 81,628 |
[
"kubernetes",
"kubernetes"
] | CustomResources metadata.name is currently validated using NameIsDNSSubdomain function. This naming convention is too strict for some CustomResourceDefinition use-cases. The current behavior could be default, but it would be useful to allow regex definition for metadata.name in the validation schema to be used for en... | Allow CustomResources to define the regex that should be enforced for metadata.name | https://api.github.com/repos/kubernetes/kubernetes/issues/81619/comments | 6 | 2019-08-19T21:19:36Z | 2020-02-07T15:56:36Z | https://github.com/kubernetes/kubernetes/issues/81619 | 482,533,636 | 81,619 |
[
"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**:
Apiserver pan... | Apiserver panics creating a stateful set | https://api.github.com/repos/kubernetes/kubernetes/issues/81616/comments | 6 | 2019-08-19T20:52:21Z | 2019-12-24T01:41:11Z | https://github.com/kubernetes/kubernetes/issues/81616 | 482,522,115 | 81,616 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
Created a serv... | AWS NLB service doesn't remove Security Group rules on delete | https://api.github.com/repos/kubernetes/kubernetes/issues/81610/comments | 11 | 2019-08-19T19:10:43Z | 2022-08-26T15:07:11Z | https://github.com/kubernetes/kubernetes/issues/81610 | 482,479,072 | 81,610 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
[FakeMounter](https://github.com/kubernetes/kubernetes/blob/master/pkg/util/mount/fake.go) doesn't return an error when the path already exists when running Windows tests.
**What you expected to happen**:
Expected FakeMounter to return an error if running Windows tests and trying to mount a path... | FakeMount doesn't imitate Windows behavior | https://api.github.com/repos/kubernetes/kubernetes/issues/81609/comments | 11 | 2019-08-19T18:40:52Z | 2020-05-22T03:46:38Z | https://github.com/kubernetes/kubernetes/issues/81609 | 482,466,586 | 81,609 |
[
"kubernetes",
"kubernetes"
] | Packages for 1.14.6 are missing from https://packages.cloud.google.com/apt/dists/kubernetes-xenial/main/binary-amd64/Packages.
/kind bug | Missing Ubuntu packages for 1.14.6 | https://api.github.com/repos/kubernetes/kubernetes/issues/81603/comments | 4 | 2019-08-19T15:57:12Z | 2019-08-20T07:49:48Z | https://github.com/kubernetes/kubernetes/issues/81603 | 482,393,935 | 81,603 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
I suggest adding one comment to remind users to upgrade the bash version.
The patch like this:
``` diff
$ git diff
diff --git a/cluster/gce/gci/configure-helper.sh b/cluster/gce/gci/configure-helper.sh
index 53dc09f076..6edfaed050 100644
--- a/cluster/gce/gci/configure-he... | Add comments when rely on a particular bash version | https://api.github.com/repos/kubernetes/kubernetes/issues/81598/comments | 8 | 2019-08-19T13:22:54Z | 2020-01-30T03:38:24Z | https://github.com/kubernetes/kubernetes/issues/81598 | 482,309,505 | 81,598 |
[
"kubernetes",
"kubernetes"
] | Hello!
Does configmap supported in endpoints ?
I would create a lot of endpoints which hava a same ip-value, I want to define the ip-value in configmap, and then endpoints use it.
like :
a1-endpoints.yaml
***
-ip : 192.168.0.1 (want to define in config)
port: 11000
***
a2-endpoint... | How can I use the configmap in endpoints ? | https://api.github.com/repos/kubernetes/kubernetes/issues/81597/comments | 6 | 2019-08-19T12:46:15Z | 2020-01-16T16:24:50Z | https://github.com/kubernetes/kubernetes/issues/81597 | 482,291,514 | 81,597 |
[
"kubernetes",
"kubernetes"
] | i use kubernetes version 1.15, i am trying pod priority,but i found same question.
1.I created a globalDefault priority A, but the pod I created that does not display the declaration priorityClassName does not use priority A.
This is different [priorityclass](https://kubernetes.io/docs/concepts/configuration/pod-pr... | pod priority is different the office article | https://api.github.com/repos/kubernetes/kubernetes/issues/81596/comments | 9 | 2019-08-19T12:42:36Z | 2020-01-30T08:43:25Z | https://github.com/kubernetes/kubernetes/issues/81596 | 482,289,775 | 81,596 |
[
"kubernetes",
"kubernetes"
] | I use scripts under https://github.com/kubernetes/kubernetes/tree/master/cluster/addons/prometheus to install kube-state-metrics, but found that there is no metrics be collected from it, and it always output error like this, although I have config rbac for it.
I0819 10:03:47.668858 1 round_trippers.go:438] GET h... | kube-state-metrics get metrics forbidden | https://api.github.com/repos/kubernetes/kubernetes/issues/81590/comments | 6 | 2019-08-19T10:12:42Z | 2019-09-23T09:52:36Z | https://github.com/kubernetes/kubernetes/issues/81590 | 482,223,475 | 81,590 |
[
"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**:
In kube-proxy... | Network requests would fail in service.spec.sessionAffinity= ClientIP when deleting pod in kube-proxy ipvs mode | https://api.github.com/repos/kubernetes/kubernetes/issues/81587/comments | 4 | 2019-08-19T10:04:27Z | 2019-08-25T10:30:56Z | https://github.com/kubernetes/kubernetes/issues/81587 | 482,219,713 | 81,587 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
Add support for AWS NLB access log configuration via annotations. The same annotations currently supported by the ELB classic could be reused:
```
service.beta.kubernetes.io/aws-load-balancer-access-log-enabled
service.beta.kubernetes.io/aws-load-balancer-access-log-s3-bucket-na... | AWS NLB: support for access log annotations | https://api.github.com/repos/kubernetes/kubernetes/issues/81584/comments | 20 | 2019-08-19T07:29:03Z | 2020-11-07T03:47:04Z | https://github.com/kubernetes/kubernetes/issues/81584 | 482,149,998 | 81,584 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
I using CPU m... | HPA two downscale action cooldown time is too short | https://api.github.com/repos/kubernetes/kubernetes/issues/81581/comments | 3 | 2019-08-19T06:24:18Z | 2019-08-22T05:44:23Z | https://github.com/kubernetes/kubernetes/issues/81581 | 482,126,815 | 81,581 |
[
"kubernetes",
"kubernetes"
] | My mac can visit k8s dashboard, but other pc can't. What's the reason ?
- @kubernetes/UI @kubernetes/dashboard
- I have tried with the latest version of my channel (Stable or Edge)
- macOS Version: 10.14
- Docker for Mac: version: 19.03.1
- k8s version : 1.14.3
- eneble k8s on docker for mac se... | other pc can't visit k8s dashboard | https://api.github.com/repos/kubernetes/kubernetes/issues/81578/comments | 3 | 2019-08-19T01:17:12Z | 2019-08-19T07:48:10Z | https://github.com/kubernetes/kubernetes/issues/81578 | 482,063,576 | 81,578 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Kubelet fails to start up on CoreOS which has been PXE booted
```
Aug 18 22:40:07 hostname kubelet-wrapper[20685]: F0818 22:40:07.479501 20685 kubelet.go:1370] Failed to start ContainerManager failed to get rootfs info: failed to get device for dir "/var/lib/kubelet": could not find device with ... | Unable to start server when multiple tmpfs exist | https://api.github.com/repos/kubernetes/kubernetes/issues/81575/comments | 11 | 2019-08-18T23:12:33Z | 2019-11-28T13:42:13Z | https://github.com/kubernetes/kubernetes/issues/81575 | 482,049,551 | 81,575 |
[
"kubernetes",
"kubernetes"
] | I am having hard time finding documentation exec/attach.
Here, https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.14, under "Pod v1 core"
/ "Misc", there is only "Read Log" documented.
Are they documented somewhere? If not, maybe we can have this issue as a task for documenting them.
/sig docs | Exec/Attach documentation | https://api.github.com/repos/kubernetes/kubernetes/issues/81566/comments | 4 | 2019-08-18T13:06:50Z | 2020-01-15T14:59:51Z | https://github.com/kubernetes/kubernetes/issues/81566 | 481,991,942 | 81,566 |
[
"kubernetes",
"kubernetes"
] | **Which jobs are failing**:
pull-kubernetes-local-e2e is failing
**Which test(s) are failing**:
https://prow.k8s.io/view/gcs/kubernetes-jenkins/pr-logs/pull/80547/pull-kubernetes-local-e2e/1163011106638139392/
where 14 out of 1398 tests failed.
I have run pull-kubernetes-local-e2e around 10 times in the past w... | pull-kubernetes-local-e2e always fails | https://api.github.com/repos/kubernetes/kubernetes/issues/81565/comments | 6 | 2019-08-18T12:47:13Z | 2019-11-11T02:27:00Z | https://github.com/kubernetes/kubernetes/issues/81565 | 481,990,027 | 81,565 |
[
"kubernetes",
"kubernetes"
] | kubelet 1.14.3 didn't send server certificate csr to apiserver. | kubelet 1.14.3 didn't send server certificate csr to apiserver. | https://api.github.com/repos/kubernetes/kubernetes/issues/81564/comments | 7 | 2019-08-18T11:07:44Z | 2020-01-15T12:57:52Z | https://github.com/kubernetes/kubernetes/issues/81564 | 481,981,296 | 81,564 |
[
"kubernetes",
"kubernetes"
] | I am following [this](https://kubernetes.io/docs/tasks/access-application-cluster/ingress-minikube/) tutorial on my Minikube with vm-driver set to none. My nginx-ingress-controller keeps crashing as in logs below. Is it expected issue? Can it work with vm-driver not set to none?
```
VirtualBox:~/msc/graphene$ sudo ... | nginx-ingress-controller keeps crashing on Minikube (with vm-driver=none) | https://api.github.com/repos/kubernetes/kubernetes/issues/81556/comments | 7 | 2019-08-17T17:44:52Z | 2019-10-22T00:01:01Z | https://github.com/kubernetes/kubernetes/issues/81556 | 481,909,941 | 81,556 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
Internal LoadBalancer is currently regional in scope. We want to support the ability to connect to the LoadBalancer from regions other than the one it was created in. The GlobalAccess option allows this.... | Support GlobalAccess for GCE Internal Loadbalancers | https://api.github.com/repos/kubernetes/kubernetes/issues/81555/comments | 8 | 2019-08-17T17:20:04Z | 2019-12-18T20:52:14Z | https://github.com/kubernetes/kubernetes/issues/81555 | 481,907,520 | 81,555 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Kubernetes allowed more that 40 EBS volumes to be mounted to a node in violation of the AWS recommended limit.
**What you expected to happen**:
The number of EBS volumes mounted is capped at the limit for the node type.
**How to reproduce it (as minimally and precisely as possible)**:
... | Too many EBS volumes mounted to a node | https://api.github.com/repos/kubernetes/kubernetes/issues/81533/comments | 10 | 2019-08-16T23:06:41Z | 2020-01-19T21:38:36Z | https://github.com/kubernetes/kubernetes/issues/81533 | 481,815,156 | 81,533 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
There are many spots in API comments that are broken (pointing to https://git.k8s.io/community/contributors/devel/api-conventions.md). One example is here: https://github.com/kubernetes/api/blob/master/core/v1/types.go#L3491, a quick search for that URL currently shows [84 results on github](https:/... | Many links in API documentation broken | https://api.github.com/repos/kubernetes/kubernetes/issues/81526/comments | 15 | 2019-08-16T19:09:15Z | 2019-10-03T13:11:54Z | https://github.com/kubernetes/kubernetes/issues/81526 | 481,745,800 | 81,526 |
[
"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 the writa... | When runtime imagefs mount is not on root filesystem, writable layer usage does not count toward ephemeral storage consumption | https://api.github.com/repos/kubernetes/kubernetes/issues/81523/comments | 15 | 2019-08-16T18:14:28Z | 2021-02-08T22:17:15Z | https://github.com/kubernetes/kubernetes/issues/81523 | 481,725,892 | 81,523 |
[
"kubernetes",
"kubernetes"
] | follow-up from https://github.com/kubernetes/kubernetes/pull/79604#discussion_r314407261
Update the godoc on the CRD API types to follow conventions by matching the serialized field name
/sig api-machinery
/kind cleanup
/assign
/priority important-soon
/area custom-resources | clean up CRD type godoc | https://api.github.com/repos/kubernetes/kubernetes/issues/81519/comments | 4 | 2019-08-16T17:21:41Z | 2019-08-30T13:25:31Z | https://github.com/kubernetes/kubernetes/issues/81519 | 481,706,967 | 81,519 |
[
"kubernetes",
"kubernetes"
] | A lot of our go verification scripts are included in [golangci-lint](https://github.com/golangci/golangci-lint), which is designed to aggregate the tools for CI. It looks like the following are included:
- govet
- golint
- gofmt
- misspell
- staticcheck (https://github.com/kubernetes/kubernetes/pull/81189)
Th... | Investigate golangci-lint to simplify our verify-* scripts | https://api.github.com/repos/kubernetes/kubernetes/issues/81518/comments | 22 | 2019-08-16T17:16:56Z | 2021-03-11T22:27:29Z | https://github.com/kubernetes/kubernetes/issues/81518 | 481,705,268 | 81,518 |
[
"kubernetes",
"kubernetes"
] | My mac can visit k8s dashboard, but other pc can't. What's the reason ?
- [ ] I have tried with the latest version of my channel (Stable or Edge)
- macOS Version: 10.14
- Docker for Mac: version: 19.03.1
- k8s version : 1.14.3
- eneble k8s on docker for mac setting
- apply k8s dashboard.yaml
- m... | other pc can't visit k8s dashboard | https://api.github.com/repos/kubernetes/kubernetes/issues/81513/comments | 1 | 2019-08-16T14:21:31Z | 2019-08-19T01:18:59Z | https://github.com/kubernetes/kubernetes/issues/81513 | 481,633,272 | 81,513 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
After discovering [#50140](https://github.com/kubernetes/kubernetes/pull/50140) I then found that whilst it added `--field-selector` for `kubectl get` it didn't generalise it to other commands, such as `kubectl top`
It should be added for ... | add field selector for kubectl top | https://api.github.com/repos/kubernetes/kubernetes/issues/81511/comments | 6 | 2019-08-16T12:40:17Z | 2020-01-17T01:32:35Z | https://github.com/kubernetes/kubernetes/issues/81511 | 481,591,031 | 81,511 |
[
"kubernetes",
"kubernetes"
] | [environment]
kubernetes 1.9.2
--etcd-servers-overrides=isolate.harmonycloud.cn/hleases#http://10.10.101.176:2379
crd.yaml
`apiVersion: apiextensions.k8s.io/v1beta1
kind: CustomResourceDefinition
metadata:
name: hleases.isolate.harmonycloud.cn
spec:
group: isolate.harmonycloud.cn
version: v1alpha1
... | is kubernetes 1.9.2 don't support --etcd-servers-overrides crd type | https://api.github.com/repos/kubernetes/kubernetes/issues/81508/comments | 38 | 2019-08-16T10:40:53Z | 2023-09-28T06:11:43Z | https://github.com/kubernetes/kubernetes/issues/81508 | 481,551,052 | 81,508 |
[
"kubernetes",
"kubernetes"
] | system : CentOS Linux release 7.6.1810 (Core) 64bit
deploy : ansible-playbook
# kubectl version
```
Client Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.8", GitCommit:"0c6d31a99f81476dfc9871ba3cf3f597bec29b58", GitTreeState:"clean", BuildDate:"2019-07-08T08:46:01Z", GoVersion:"go1.11.5", Compi... | kubernetes from 1.9.11 version update 1.13.8 version kube-apiserver error [31244]: E0816 available_controller.go:316] v1beta1.apps | https://api.github.com/repos/kubernetes/kubernetes/issues/81504/comments | 7 | 2019-08-16T08:27:54Z | 2019-08-20T01:24:40Z | https://github.com/kubernetes/kubernetes/issues/81504 | 481,501,367 | 81,504 |
[
"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 image ... | `flags` should be initialized for apparmor-loader | https://api.github.com/repos/kubernetes/kubernetes/issues/81498/comments | 2 | 2019-08-16T05:42:01Z | 2019-08-21T07:29:32Z | https://github.com/kubernetes/kubernetes/issues/81498 | 481,450,474 | 81,498 |
[
"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**:
PR https://... | "location" and "subscriptionId" should get got from Azure IMDS when useInstanceMetadata is true | https://api.github.com/repos/kubernetes/kubernetes/issues/81496/comments | 1 | 2019-08-16T05:24:10Z | 2019-08-17T02:10:21Z | https://github.com/kubernetes/kubernetes/issues/81496 | 481,446,810 | 81,496 |
[
"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... | what is the svc of dashboard-metrics-scraper mean in dashboard of version V2.0.0 | https://api.github.com/repos/kubernetes/kubernetes/issues/81492/comments | 6 | 2019-08-16T01:22:23Z | 2020-01-15T12:57:52Z | https://github.com/kubernetes/kubernetes/issues/81492 | 481,401,587 | 81,492 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
The following two tests take roughly 70 minutes in ci-kubernetes-e2e-gci-gce-serial:
- `[sig-autoscaling] [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`
... | The serial HPA e2e tests are too slow | https://api.github.com/repos/kubernetes/kubernetes/issues/81491/comments | 20 | 2019-08-16T00:39:24Z | 2020-03-12T17:22:24Z | https://github.com/kubernetes/kubernetes/issues/81491 | 481,393,955 | 81,491 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
The following two tests take roughly 65 minutes in ci-kubernetes-e2e-gci-gce-serial:
- `[k8s.io] [sig-node] Kubelet [Serial] [Slow] [k8s.io] [sig-node] regular resource usage tracking resource tracking for 100 pods per node`
- `[k8s.io] [sig-node] Kubelet [Serial] [Slow] [k8s.io] [sig-node] regula... | The serial regular resource usage tracking e2e tests are too slow | https://api.github.com/repos/kubernetes/kubernetes/issues/81490/comments | 15 | 2019-08-16T00:32:28Z | 2020-04-11T02:44:08Z | https://github.com/kubernetes/kubernetes/issues/81490 | 481,392,727 | 81,490 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
SCTP nodeport service is not working for all IPs present in the node when ipvs is enabled. It is working only for node's InternalIP.
**What you expected to happen**:
SCTP nodeport service must work for all ips present in the node when ipvs is enabled.
**How to reproduce it (as minimally and p... | SCTP nodeport service is not working for all IPs present in the node when ipvs is enabled. | https://api.github.com/repos/kubernetes/kubernetes/issues/81474/comments | 3 | 2019-08-15T15:55:41Z | 2019-08-29T01:26:10Z | https://github.com/kubernetes/kubernetes/issues/81474 | 481,218,396 | 81,474 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Please refer: https://github.com/kubernetes/cloud-provider-aws/issues/51
I set the proper annotations, as per the documentation in Kubernetes, to the service of `type: LoadBalancer` using an AWS NLB:
```
service.beta.kubernetes.io/aws-load-balancer-connection-draining-timeout: "30"
service.... | Override NLB health check values based on annotations | https://api.github.com/repos/kubernetes/kubernetes/issues/81469/comments | 17 | 2019-08-15T13:59:13Z | 2020-08-08T01:06:27Z | https://github.com/kubernetes/kubernetes/issues/81469 | 481,164,377 | 81,469 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
```
Source:
Type: Glusterfs (a Glusterfs mount on the host that shares a pod's lifetime)
EndpointsName: server
EndpointsNamespace: 0xc0006a17a0
Path: gv0
ReadOnly: false
Events: <none>
```
**What you ex... | kubectl gluster EndpointNamespace not showing properly | https://api.github.com/repos/kubernetes/kubernetes/issues/81466/comments | 2 | 2019-08-15T09:55:05Z | 2019-08-20T03:44:03Z | https://github.com/kubernetes/kubernetes/issues/81466 | 481,079,306 | 81,466 |
[
"kubernetes",
"kubernetes"
] | Hi all,
It would be useful to have the context name included when performing kubectl calls.
Below an example of what I mean:

I think this would be an useful feature for folks who work with multiple cont... | Add context name to output when using kubectl calls | https://api.github.com/repos/kubernetes/kubernetes/issues/81459/comments | 6 | 2019-08-15T07:35:21Z | 2020-01-14T19:42:20Z | https://github.com/kubernetes/kubernetes/issues/81459 | 481,031,767 | 81,459 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
https://kubernetes.io/docs/concepts/cluster-administration/kubelet-garbage-collection/#container-collection
Currently container garbage collection doesn't consider exit time of dead containers, there are many dead containers that exited some months ago on our production kuberne... | garbage collect dead containers that have exited for a very long time | https://api.github.com/repos/kubernetes/kubernetes/issues/81451/comments | 17 | 2019-08-15T05:44:37Z | 2019-09-05T05:44:55Z | https://github.com/kubernetes/kubernetes/issues/81451 | 481,003,006 | 81,451 |
Subsets and Splits
Unique Owner-Repo Count
Counts the number of unique owner-repos in the dataset, providing a basic understanding of diverse repositories.