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"
] | <!--
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... | kubernetes 1.13.10 cluster worker node cannot resolve dns | https://api.github.com/repos/kubernetes/kubernetes/issues/83040/comments | 5 | 2019-09-24T03:22:28Z | 2019-10-23T14:19:39Z | https://github.com/kubernetes/kubernetes/issues/83040 | 497,432,062 | 83,040 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
I have a cont... | Multiple persistent volumes mounting is not working | https://api.github.com/repos/kubernetes/kubernetes/issues/83039/comments | 8 | 2019-09-24T03:09:40Z | 2020-03-01T01:41:25Z | https://github.com/kubernetes/kubernetes/issues/83039 | 497,429,068 | 83,039 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
The problem we have is that the Windows pods in Kubernetes cluster were getting evicted with The node was low on resource: ephemeral-storage. error. When tried to set an ephemeral storage limit, the following were observed.The pod is only running if the ephemeral-storage limit is set to 16Gi or hi... | Pod ephemeral local storage usage exceeds the total limit of containers xxGi | https://api.github.com/repos/kubernetes/kubernetes/issues/83038/comments | 18 | 2019-09-24T02:31:13Z | 2020-05-16T14:36:55Z | https://github.com/kubernetes/kubernetes/issues/83038 | 497,419,952 | 83,038 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**: Kubernetes API... | kube-apiserver: failover on multi-member etcd cluster fails certificate check on DNS mismatch | https://api.github.com/repos/kubernetes/kubernetes/issues/83028/comments | 30 | 2019-09-23T18:43:10Z | 2019-10-16T19:31:16Z | https://github.com/kubernetes/kubernetes/issues/83028 | 497,262,794 | 83,028 |
[
"kubernetes",
"kubernetes"
] | https://github.com/kubernetes/kubernetes/issues/49466 suggests an option to limit the restart count for pods. Since deployments are limited to restartPolicy "Always" this isn't useful for deployments.
It would be great if there were a variant of restartCountLimit that applied only during new deployments. The basic i... | Restart limit for deployments | https://api.github.com/repos/kubernetes/kubernetes/issues/83026/comments | 6 | 2019-09-23T16:53:13Z | 2021-04-16T10:11:01Z | https://github.com/kubernetes/kubernetes/issues/83026 | 497,213,808 | 83,026 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
```
kubectl get componentstatus
NAME AGE
scheduler <unknown>
controller-manager <unknown>
etcd-0 <unknown>
```
**What you expected to happen**:
`get componentstatus` should be able to have its results formated as a table by kubectl
**How to rep... | `kubectl get componentstatus` fails to write as table | https://api.github.com/repos/kubernetes/kubernetes/issues/83024/comments | 12 | 2019-09-23T14:43:05Z | 2019-11-28T15:40:11Z | https://github.com/kubernetes/kubernetes/issues/83024 | 497,142,205 | 83,024 |
[
"kubernetes",
"kubernetes"
] | **Which jobs are failing**:
gce-master-scale-performance
**Which test(s) are failing**:
density & load
**Since when has it been failing**:
2019-09-20
**Testgrid link**:
https://k8s-testgrid.appspot.com/sig-scalability-gce#gce-master-scale-performance
**Reason for failure**:
etcd very slow during log ro... | [Failing Test] GCE 5K Performance - COS regression | https://api.github.com/repos/kubernetes/kubernetes/issues/83020/comments | 6 | 2019-09-23T13:21:28Z | 2019-09-25T08:42:19Z | https://github.com/kubernetes/kubernetes/issues/83020 | 497,094,528 | 83,020 |
[
"kubernetes",
"kubernetes"
] | It seems that again we started sending waaaay more watch bookmarks:
http://perf-dash.k8s.io/#/?jobname=gce-5000Nodes&metriccategoryname=APIServer&metricname=LoadInitEventsCount&resource=*core.Secret
The regression happened between these two runs:
https://github.com/kubernetes/kubernetes/compare/c7c89f8c6...84fe3db... | Regression of watch bookmarks | https://api.github.com/repos/kubernetes/kubernetes/issues/83016/comments | 3 | 2019-09-23T09:33:27Z | 2019-09-23T09:49:01Z | https://github.com/kubernetes/kubernetes/issues/83016 | 496,989,692 | 83,016 |
[
"kubernetes",
"kubernetes"
] | **Kubernetes Installation Make Easy**:
**I feel lets make to improve the Kubernetes installation little easy rather doing to many stuff in too many nodes of commands.*:
How Can we approach:
I feel that writing up a config file of which node to be controlplane / etcd / worker and Type of Network with Kube-insta... | Simplify Installation of K8s | https://api.github.com/repos/kubernetes/kubernetes/issues/83012/comments | 2 | 2019-09-23T08:12:33Z | 2019-10-09T13:18:49Z | https://github.com/kubernetes/kubernetes/issues/83012 | 496,952,068 | 83,012 |
[
"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 default... | update the daemonSet default updateStrategy type to OnDelete | https://api.github.com/repos/kubernetes/kubernetes/issues/83007/comments | 5 | 2019-09-23T07:31:02Z | 2019-09-25T20:51:43Z | https://github.com/kubernetes/kubernetes/issues/83007 | 496,936,256 | 83,007 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
(1)
I deploy a single-node cluster of K8S version 1.16 , with kubeadm
(2)
I check each K8S' components and print them in the following , which I think, conform to the IPv6DualStack requirement of relevant K8S components , referring to https://kubernetes.io/docs/concepts/services-networking/dua... | fialed to test IPv6DualStack feature of release version 1.16.0 | https://api.github.com/repos/kubernetes/kubernetes/issues/83006/comments | 16 | 2019-09-23T07:12:04Z | 2020-02-23T03:59:41Z | https://github.com/kubernetes/kubernetes/issues/83006 | 496,929,704 | 83,006 |
[
"kubernetes",
"kubernetes"
] | One of my nodes in K8S not ready， as below
10.40.24.49 NotReady <none> 108d v1.11.2
[root@idp-01-p2pi-k8s-node-10.40.24.49]#
[~]#journalctl -f -u kubelet
-- Logs begin at Wed 2019-08-14 20:57:07 WIB. --
Sep 20 15:22:42 ida-lj4700146 kubelet[3975]: I0920 15:22:42.117196 3975 fsHandler.go:135] du ... | K8s node NotReady | https://api.github.com/repos/kubernetes/kubernetes/issues/83002/comments | 9 | 2019-09-23T04:39:09Z | 2020-02-21T08:17:37Z | https://github.com/kubernetes/kubernetes/issues/83002 | 496,890,727 | 83,002 |
[
"kubernetes",
"kubernetes"
] | Today I found one node status not good suddenly， the detail as below.
what's problem， and how can I fix？
30.68.0.33 NotReady,SchedulingDisabled <none> 25d v1.11.2
Sep 20 12:39:24 b-app-ps-225 kubelet[46044]: I0920 12:39:24.664733 46044 reflector.go:240] Listing and watching *v1.Pod from k8s.io/k... | k8s node NotReady | https://api.github.com/repos/kubernetes/kubernetes/issues/83000/comments | 8 | 2019-09-23T02:58:20Z | 2020-02-21T18:27:39Z | https://github.com/kubernetes/kubernetes/issues/83000 | 496,873,527 | 83,000 |
[
"kubernetes",
"kubernetes"
] | I've got a Java application that uses the Fabric8 kubernetes-client to create a job, and then set a watch on it. I recently started seeing a new warning msg in the application log.
I'm using K8s 1.15.3 and kubernetes-client 4.5.2.
I have a K8s cluster with 3 master nodes and 1 worker/minion node (adding more, but... | Going from single master to 3 masters triggers Fabric8 Java client watcher EOFException+reconnect | https://api.github.com/repos/kubernetes/kubernetes/issues/82999/comments | 8 | 2019-09-23T02:55:08Z | 2020-02-21T00:09:36Z | https://github.com/kubernetes/kubernetes/issues/82999 | 496,873,030 | 82,999 |
[
"kubernetes",
"kubernetes"
] |
**What happened**:
Upgrading to 1.16.0 causes Cluster nodes to never be ready on arm64
**What you expected to happen**:
Cluster should become ready
**How to reproduce it (as minimally and precisely as possible)**:
1.) ```kubeadm init --pod-network-cidr=10.244.0.0/16```
2.) Join from 2 other arm boards usin... | 1.16 upgrade causes nodes to never enter ready state arm64 | https://api.github.com/repos/kubernetes/kubernetes/issues/82997/comments | 24 | 2019-09-22T23:36:47Z | 2020-06-23T09:59:44Z | https://github.com/kubernetes/kubernetes/issues/82997 | 496,847,678 | 82,997 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
This requires... | EndpointSliceController keeps enqueuing deleted service even its cleanup is successful | https://api.github.com/repos/kubernetes/kubernetes/issues/82995/comments | 3 | 2019-09-22T16:52:18Z | 2019-10-08T22:42:29Z | https://github.com/kubernetes/kubernetes/issues/82995 | 496,804,038 | 82,995 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
```
root@soe13:~# kubeadm init --pod-network-cidr=10.244.0.0/16 --cri-socket=/var/run/crio/crio.sock
[init] Using Kubernetes version: v1.16.0
[preflight] Running pre-flight checks
[preflight] Pulling images required for setting up a Kubernetes cluster
[preflight] This might take a minute or t... | Kubelet fails to start with 6443: connection refused, kubeadm 1.16, Ubuntu 18.04. | https://api.github.com/repos/kubernetes/kubernetes/issues/82988/comments | 10 | 2019-09-22T14:03:54Z | 2020-04-27T22:16:28Z | https://github.com/kubernetes/kubernetes/issues/82988 | 496,783,057 | 82,988 |
[
"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 am getting ... | Liveness probe errored: rpc error: code = DeadlineExceeded desc = context deadline exceeded | https://api.github.com/repos/kubernetes/kubernetes/issues/82987/comments | 53 | 2019-09-22T13:45:17Z | 2024-10-01T20:38:32Z | https://github.com/kubernetes/kubernetes/issues/82987 | 496,780,995 | 82,987 |
[
"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**:
Cluster upg... | Cluster upgrade from 1.15.4 to 1.16.0 failing (Master NotReady) using kubeadm | https://api.github.com/repos/kubernetes/kubernetes/issues/82982/comments | 10 | 2019-09-22T11:05:20Z | 2019-09-23T07:13:51Z | https://github.com/kubernetes/kubernetes/issues/82982 | 496,764,540 | 82,982 |
[
"kubernetes",
"kubernetes"
] | **What happened**: `kubectl get all` is not documented therefore `kubectl get -h` provides no content about this hidden, but powerful option
**What you expected to happen**: `kubectl get -h` provides the "all" resource as, at least, an example.
**How to reproduce it (as minimally and precisely as possible)**: `ku... | kubectl get all not documented | https://api.github.com/repos/kubernetes/kubernetes/issues/82979/comments | 3 | 2019-09-22T04:17:07Z | 2019-09-24T00:47:16Z | https://github.com/kubernetes/kubernetes/issues/82979 | 496,731,597 | 82,979 |
[
"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**:
kubeadm init ... | kubeadm init --feature-gates panic | https://api.github.com/repos/kubernetes/kubernetes/issues/82978/comments | 3 | 2019-09-22T04:07:39Z | 2019-09-22T19:53:23Z | https://github.com/kubernetes/kubernetes/issues/82978 | 496,731,039 | 82,978 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
Few days ago I watched this kubectl code base tour by @soltysh on Youtube
(https://www.youtube.com/watch?v=uz8TS3V9qqY). He talks about a design
pattern that almost every command follows. But I found ... | kubectl proxy and delete-context command should follow similar design pattern as other commands. | https://api.github.com/repos/kubernetes/kubernetes/issues/82970/comments | 7 | 2019-09-21T19:47:50Z | 2020-02-06T09:06:16Z | https://github.com/kubernetes/kubernetes/issues/82970 | 496,693,782 | 82,970 |
[
"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 run
... | docker_build_opts bound variable | https://api.github.com/repos/kubernetes/kubernetes/issues/82962/comments | 1 | 2019-09-21T13:16:11Z | 2019-09-25T20:50:21Z | https://github.com/kubernetes/kubernetes/issues/82962 | 496,654,980 | 82,962 |
[
"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 cluster s... | Controller manager keeps running and stops working after failed update leader lock | https://api.github.com/repos/kubernetes/kubernetes/issues/82960/comments | 5 | 2019-09-21T10:42:43Z | 2020-02-20T23:08:36Z | https://github.com/kubernetes/kubernetes/issues/82960 | 496,642,309 | 82,960 |
[
"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 daemons... | The daemonset's pods and static pods are still Running when the node is NotReady | https://api.github.com/repos/kubernetes/kubernetes/issues/82958/comments | 22 | 2019-09-21T08:31:44Z | 2022-01-19T18:44:58Z | https://github.com/kubernetes/kubernetes/issues/82958 | 496,630,736 | 82,958 |
[
"kubernetes",
"kubernetes"
] | https://kubernetes.io/docs/tasks/tls/managing-tls-in-a-cluster/
The note mentions that the CA that sings the CertificateSigningRequest may be different than the cluster CA. Typically ( at least on GKE ) the clusterCA is used.
This creates a number of problems:
- there is no way (that I found) to identify which C... | CertificateSigningRequest and the root CA pubkey | https://api.github.com/repos/kubernetes/kubernetes/issues/82952/comments | 14 | 2019-09-20T21:11:17Z | 2019-09-30T18:59:40Z | https://github.com/kubernetes/kubernetes/issues/82952 | 496,548,423 | 82,952 |
[
"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... | kubectl: how to print a union of fields in custom-columns | https://api.github.com/repos/kubernetes/kubernetes/issues/82950/comments | 8 | 2019-09-20T19:40:04Z | 2020-06-14T08:49:33Z | https://github.com/kubernetes/kubernetes/issues/82950 | 496,515,931 | 82,950 |
[
"kubernetes",
"kubernetes"
] | ### Flaky Job: pr:pull-kubernetes-kubemark-e2e-gce-big
Flakes in the past week: **55**
Consistency: **92.70%**
#### Flakiest tests by flake count:
| Test | Flake Count |
| --- | --- |
| Stage | 33 |
| Timeout | 25 |
| TearDown | 13 |
#### Previously closed issues for this job flaking:
#62267 #73105 #78701 #65466
... | pr:pull-kubernetes-kubemark-e2e-gce-big flaked 55 times in the past week | https://api.github.com/repos/kubernetes/kubernetes/issues/82949/comments | 9 | 2019-09-20T18:16:13Z | 2020-05-18T16:24:38Z | https://github.com/kubernetes/kubernetes/issues/82949 | 496,484,565 | 82,949 |
[
"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**:
One of our ... | Empty Azure VM scale sets consume vmss_list API needlessly | https://api.github.com/repos/kubernetes/kubernetes/issues/82948/comments | 5 | 2019-09-20T16:41:50Z | 2019-09-29T03:11:39Z | https://github.com/kubernetes/kubernetes/issues/82948 | 496,447,955 | 82,948 |
[
"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**:
hack/local-up... | local-up-cluster.sh -O doesn't work in the latest code of master branch | https://api.github.com/repos/kubernetes/kubernetes/issues/82944/comments | 1 | 2019-09-20T15:42:38Z | 2019-09-23T05:49:23Z | https://github.com/kubernetes/kubernetes/issues/82944 | 496,422,658 | 82,944 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
I have 2 node... | kubeadm --apiserver-advertise-adress not working | https://api.github.com/repos/kubernetes/kubernetes/issues/82943/comments | 33 | 2019-09-20T14:47:40Z | 2020-04-30T07:29:22Z | https://github.com/kubernetes/kubernetes/issues/82943 | 496,394,277 | 82,943 |
[
"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 a ... | Add support for "Specification Extensions" in openAPIV3Schema to CRDs | https://api.github.com/repos/kubernetes/kubernetes/issues/82942/comments | 50 | 2019-09-20T14:42:13Z | 2024-06-11T20:19:21Z | https://github.com/kubernetes/kubernetes/issues/82942 | 496,391,358 | 82,942 |
[
"kubernetes",
"kubernetes"
] | [root@iZj6c2fj4e2ampu34u8c1wZ kubernetes]# systemctl status kube-apiserver
● kube-apiserver.service - Kubernetes API Server
Loaded: loaded (/usr/lib/systemd/system/kube-apiserver.service; enabled; vendor preset: disabled)
Active: active (running) since Fri 2019-09-20 19:26:24 CST; 22s ago
Docs: https://g... | start apiserver error | https://api.github.com/repos/kubernetes/kubernetes/issues/82937/comments | 6 | 2019-09-20T11:32:53Z | 2019-09-24T18:23:41Z | https://github.com/kubernetes/kubernetes/issues/82937 | 496,301,121 | 82,937 |
[
"kubernetes",
"kubernetes"
] | **Which jobs are failing**: Which jobs are failing: ci-kubernetes-e2e-gce-scale-correctness
**Which test(s) are failing**: all
**Since when has it been failing**: Sep 19, 2019
**Testgrid link**: https://k8s-testgrid.appspot.com/sig-scalability-gce#gce-master-scale-correctness
**Reason for failure**: etcd di... | [Failing Test] GCE 5k Correctness - etcd not started | https://api.github.com/repos/kubernetes/kubernetes/issues/82936/comments | 4 | 2019-09-20T11:14:54Z | 2019-09-23T10:48:46Z | https://github.com/kubernetes/kubernetes/issues/82936 | 496,293,959 | 82,936 |
[
"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 metrics c... | inconsistent configurations for cadvisor scrape metrics and metrics exported by prometheus endpoint | https://api.github.com/repos/kubernetes/kubernetes/issues/82933/comments | 7 | 2019-09-20T10:30:22Z | 2020-02-17T14:50:39Z | https://github.com/kubernetes/kubernetes/issues/82933 | 496,275,871 | 82,933 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
Nowadays in disruption controller we only run a worker and a recheck worker to sync the pdbs. But in most controllers we can configure the number of workers. Should we make it configurable?
**Why is this... | Disruption controller support configure workers' number | https://api.github.com/repos/kubernetes/kubernetes/issues/82930/comments | 7 | 2019-09-20T09:40:38Z | 2021-03-09T03:46:13Z | https://github.com/kubernetes/kubernetes/issues/82930 | 496,252,792 | 82,930 |
[
"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... | k8s storage using rook,delete pv ,pvc then create pvc shows peding | https://api.github.com/repos/kubernetes/kubernetes/issues/82926/comments | 4 | 2019-09-20T08:48:53Z | 2019-10-22T09:28:59Z | https://github.com/kubernetes/kubernetes/issues/82926 | 496,227,908 | 82,926 |
[
"kubernetes",
"kubernetes"
] | ## What happened ?
I have made a test, first I created a statefulset with wrong container image, so pod gets wrong.
I updated container image to ```nginx``` , but pod still in ErrImagePull state, and I saw container image not changed.
According to this line : https://github.com/kubernetes/kubernetes/blob/release-1... | StatefulsetController dose not delete pod after statefulset updated | https://api.github.com/repos/kubernetes/kubernetes/issues/82925/comments | 2 | 2019-09-20T08:45:19Z | 2019-09-24T08:57:44Z | https://github.com/kubernetes/kubernetes/issues/82925 | 496,226,232 | 82,925 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
With #76805 merged we should enable strict serializers in Kubernetes components:
- [x] kube-proxy (#82927)
- [x] kube-scheduler (#83030)
- ~~kube-controller-manager~~ (not using a config file right no... | Enable strict serializers in components by default | https://api.github.com/repos/kubernetes/kubernetes/issues/82924/comments | 4 | 2019-09-20T08:35:55Z | 2019-11-05T09:02:24Z | https://github.com/kubernetes/kubernetes/issues/82924 | 496,221,831 | 82,924 |
[
"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 upgradin... | AWS ELB LoadBalancer not being updated in v1.14.7
| https://api.github.com/repos/kubernetes/kubernetes/issues/82923/comments | 44 | 2019-09-20T08:22:54Z | 2019-11-14T22:33:45Z | https://github.com/kubernetes/kubernetes/issues/82923 | 496,216,096 | 82,923 |
[
"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**: Flexvolume binar... | Flexvolume binary mount succeed, but kubelet cannot observe mounted volume if there are too many files in the mount directory with fsGroup | https://api.github.com/repos/kubernetes/kubernetes/issues/82918/comments | 6 | 2019-09-20T06:14:54Z | 2019-10-18T01:22:53Z | https://github.com/kubernetes/kubernetes/issues/82918 | 496,166,571 | 82,918 |
[
"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 had a csi ... | CSI mounter is not idempotent when setting up mount | https://api.github.com/repos/kubernetes/kubernetes/issues/82917/comments | 6 | 2019-09-20T05:47:33Z | 2020-02-17T09:45:38Z | https://github.com/kubernetes/kubernetes/issues/82917 | 496,157,933 | 82,917 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Cron jobs stopped creating new jobs after many days running OK. I have more than 100 cronjobs.
**What you expected to happen**:
Cronjobs should be created as usual.
**How to reproduce it (as minimally and precisely as possible)**:
Create, say, 150 cron jobs that create new job hourly. Leave ... | Cronjobs not creating new jobs after considerable amount of time. | https://api.github.com/repos/kubernetes/kubernetes/issues/82915/comments | 10 | 2019-09-20T05:08:45Z | 2020-03-08T15:39:36Z | https://github.com/kubernetes/kubernetes/issues/82915 | 496,148,053 | 82,915 |
[
"kubernetes",
"kubernetes"
] | v3.2.0 of kustomize was released yesterday, we are still at v2.0.3+ Can we please update?
https://github.com/kubernetes-sigs/kustomize/releases
(Will also help with https://github.com/kubernetes/kubernetes/issues/77024)
/sig cli
/sig cluster-lifecycle | Update to newer kustomize | https://api.github.com/repos/kubernetes/kubernetes/issues/82905/comments | 19 | 2019-09-19T22:32:29Z | 2020-10-30T09:30:15Z | https://github.com/kubernetes/kubernetes/issues/82905 | 496,056,682 | 82,905 |
[
"kubernetes",
"kubernetes"
] | https://github.com/kubernetes/klog/releases/tag/v1.0.0 was released today.
/good-first-issue | Update kubernetes/kubernetes to klog 1.0.0 | https://api.github.com/repos/kubernetes/kubernetes/issues/82904/comments | 3 | 2019-09-19T22:17:06Z | 2019-09-23T15:03:39Z | https://github.com/kubernetes/kubernetes/issues/82904 | 496,052,158 | 82,904 |
[
"kubernetes",
"kubernetes"
] | I am creating an nfs server deployment / service into my k8s cluster
```
apiVersion: v1
kind: Service
metadata:
name: nfs
labels:
app: nfs
spec:
selector:
app: nfs
ports:
- name: tcp-2049
port: 2049
protocol: TCP
- name: rpcbind
port: 111
protocol: UDP
---
apiVer... | Kubernetes create an nfs deployment and volume | https://api.github.com/repos/kubernetes/kubernetes/issues/82903/comments | 6 | 2019-09-19T22:07:52Z | 2020-03-07T15:15:36Z | https://github.com/kubernetes/kubernetes/issues/82903 | 496,049,173 | 82,903 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
Automatic validation of OpenAPI fields that contain common formats like IP addresses, dates and timestamps.
We would need to identify a list of common validations.
Validation of common formats should work well for native types and CRDs. We don't want to do something that ju... | CRDs: OpenAPI validation of common formats | https://api.github.com/repos/kubernetes/kubernetes/issues/82901/comments | 7 | 2019-09-19T21:29:05Z | 2019-11-26T21:33:52Z | https://github.com/kubernetes/kubernetes/issues/82901 | 496,035,440 | 82,901 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
A cache of CRD conversion results.
Cache entries should be keyed by UID (namespace, name), GVK and resource version, I believe.
**Why is this needed**:
Based on the benchmarks data we gathered for the [CRD scalability targets](https://github.com/kubernetes/enhancements/b... | Cache CRD conversion results | https://api.github.com/repos/kubernetes/kubernetes/issues/82900/comments | 5 | 2019-09-19T21:16:09Z | 2020-02-04T20:42:54Z | https://github.com/kubernetes/kubernetes/issues/82900 | 496,030,508 | 82,900 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
An interface that allows PreFilter plugins to update their state after PreFilter was called, similar to what we have for [predicates metadata (add/remove pods)](https://github.com/kubernetes/kubernetes/blob/master/pkg/scheduler/algorithm/predicates/metadata.go#L38-L41).
**Why is... | A new API for updating prefilter calculations | https://api.github.com/repos/kubernetes/kubernetes/issues/82897/comments | 14 | 2019-09-19T19:54:23Z | 2019-09-25T18:06:42Z | https://github.com/kubernetes/kubernetes/issues/82897 | 495,996,361 | 82,897 |
[
"kubernetes",
"kubernetes"
] | ```
kubeadm upgrade plan
[upgrade/config] Making sure the configuration is correct:
[upgrade/config] Reading configuration from the cluster...
[upgrade/config] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -oyaml'
[preflight] Running pre-flight checks.
[preflight] Some f... | Can't upgrade to 1.16.0: [ERROR CoreDNSUnsupportedPlugins]: there are unsupported plugins in the CoreDNS | https://api.github.com/repos/kubernetes/kubernetes/issues/82889/comments | 34 | 2019-09-19T18:14:06Z | 2020-02-27T03:39:35Z | https://github.com/kubernetes/kubernetes/issues/82889 | 495,952,807 | 82,889 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs -->
**Which jobs are failing**:
pr:pull-kubernetes-integration
**Which test(s) are failing**:
test/integration/volumescheduling TestVolumeProvision
**Since when has it been failing**:
2 days ago on #82648.
2... | [Failing Test] test/integration/volumescheduling TestVolumeProvision | https://api.github.com/repos/kubernetes/kubernetes/issues/82885/comments | 5 | 2019-09-19T15:02:05Z | 2019-12-03T01:37:10Z | https://github.com/kubernetes/kubernetes/issues/82885 | 495,857,963 | 82,885 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Kubectl shell completion might be depressingly slow.
Main problem that completion uses constructions like:
```
kubectl get -o template '--template={{ range .items }}{{ .metadata.name }} {{ end }}' configmap
```
to get resource names. But in large installations they can be extremely slow.... | kubectl completion is too slow | https://api.github.com/repos/kubernetes/kubernetes/issues/82883/comments | 14 | 2019-09-19T14:58:07Z | 2024-10-15T20:28:30Z | https://github.com/kubernetes/kubernetes/issues/82883 | 495,855,392 | 82,883 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
@kubernetes/sig-Storage-feature-requests
/sig Storage
**What would you like to be added**:
I would like the `kubernetes.io/azure-file` provisioner to add metadata to the file share such as `KubernetesCluster`, `Name`, `kubernetes.io/creat... | kubernetes.io/azure-file provisioner to add metadata to the persistent file share in azure (not just in the cluster). | https://api.github.com/repos/kubernetes/kubernetes/issues/82881/comments | 6 | 2019-09-19T14:33:17Z | 2020-02-24T14:11:45Z | https://github.com/kubernetes/kubernetes/issues/82881 | 495,839,390 | 82,881 |
[
"kubernetes",
"kubernetes"
] | I deploy the nginx on k8s. One of the nodes is the ARM Ubuntu16.04.
The pod on the ARM can't enter the Running state.
I'll be appreciate if someone give me a solution.
[root@k8s-master2 ssl]# kubectl get pods
NAME READY STATUS RESTARTS AGE
nginx-7bb7cd8db5-6s9m4 1/1 Runn... | cannot join network of a non running container --on ARM Ubuntu 16.04 | https://api.github.com/repos/kubernetes/kubernetes/issues/82880/comments | 3 | 2019-09-19T13:27:35Z | 2019-09-23T06:44:31Z | https://github.com/kubernetes/kubernetes/issues/82880 | 495,799,584 | 82,880 |
[
"kubernetes",
"kubernetes"
] | **Which test(s) are failing**:
"SecurityContext RunAsUserName should not be able to create pods with unknown usernames"
**Reason for failure**:
The test checks that the container fails with reason: "ContainerCannotRun" which is specific to dockershim. With ContainerD, the reason for failing to start a containe... | Windows Test: SecurityContext RunAsUserName should not be able to create pods with unknown usernames fails with ContainerD | https://api.github.com/repos/kubernetes/kubernetes/issues/82876/comments | 9 | 2019-09-19T11:39:24Z | 2020-03-03T17:25:26Z | https://github.com/kubernetes/kubernetes/issues/82876 | 495,744,934 | 82,876 |
[
"kubernetes",
"kubernetes"
] | One example:
https://prow.k8s.io/view/gcs/kubernetes-jenkins/pr-logs/pull/82832/pull-kubernetes-e2e-gce-100-performance/1174602482194583552/
```
:0
[measurement call APIResponsiveness - APIResponsiveness error: top latency metric: there should be no high-latency requests, but: [got: {Resource:persistentvolumes Su... | kubernetes-e2e-gce-100-performance is flaky | https://api.github.com/repos/kubernetes/kubernetes/issues/82875/comments | 9 | 2019-09-19T10:53:35Z | 2019-12-24T10:18:47Z | https://github.com/kubernetes/kubernetes/issues/82875 | 495,724,017 | 82,875 |
[
"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 am followin... | Unknown field "preserveUnknownFields" when create CRD | https://api.github.com/repos/kubernetes/kubernetes/issues/82874/comments | 3 | 2019-09-19T10:26:50Z | 2019-09-19T12:22:39Z | https://github.com/kubernetes/kubernetes/issues/82874 | 495,711,263 | 82,874 |
[
"kubernetes",
"kubernetes"
] |
**What happened**:
We upgraded a new deployment using helm in a kubernetes 1.13.10 cluster, the new pods failed liveness due to some issue, but traffic was being routed to these new pods instead of being sent to the old healthy pods.
**What you expected to happen**:
Until the new pods are healthy traffic should... | Traffic routed to replica set with not ready pods | https://api.github.com/repos/kubernetes/kubernetes/issues/82872/comments | 11 | 2019-09-19T09:00:04Z | 2019-09-19T13:17:33Z | https://github.com/kubernetes/kubernetes/issues/82872 | 495,666,047 | 82,872 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
It is possible to provide a custom IP to be used as node IP to the kubelet process using the kubelet's `--node-ip <some-ip>` parameter. The provided IP address is not only [validated](https://github.com/kubernetes/kubernetes/blob/92107f3/pkg/kubelet/kubelet_node_status.go#L565-L... | Replace kubelet node IP validation error with warning or allow skipping | https://api.github.com/repos/kubernetes/kubernetes/issues/82869/comments | 10 | 2019-09-19T07:52:46Z | 2020-03-30T19:17:51Z | https://github.com/kubernetes/kubernetes/issues/82869 | 495,633,264 | 82,869 |
[
"kubernetes",
"kubernetes"
] | **What happened**: There's a typo typo in https://github.com/kubernetes/kubernetes and https://kubernetes.io/docs/setup/release/notes/
**What you expected to happen**: “depreciated” should be “deprecated”.
**How to reproduce it (as minimally and precisely as possible)**:
View the release notes
**Anything els... | Typo in v1.16 release notes | https://api.github.com/repos/kubernetes/kubernetes/issues/82866/comments | 0 | 2019-09-19T07:08:45Z | 2019-09-19T18:06:05Z | https://github.com/kubernetes/kubernetes/issues/82866 | 495,614,719 | 82,866 |
[
"kubernetes",
"kubernetes"
] |
**What happened**:
In order to use rbd-nbd, installed rbd-nbd and disabled krbd.
But kubelet still saied:
"
rbd-nbd: getting rbd-nbd version failed with error
"
checked the code:
pkg/volume/rbd/rbd_util.go:
in line 246:
"
if _, err := e.Run("rbd-nbd", "--version"); err != nil {
klog.V(5).Infof("rbd-n... | pkg/volume/rbd/rbd_util.go can't use rbd-nbd | https://api.github.com/repos/kubernetes/kubernetes/issues/82864/comments | 9 | 2019-09-19T06:42:22Z | 2020-02-21T10:19:42Z | https://github.com/kubernetes/kubernetes/issues/82864 | 495,604,274 | 82,864 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
kubectl diff crushing if i add new port in manifest of existing statefulset without containerPort and will make diff
```
$ kubectl diff -f /tmp/StatefulSet.yaml
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0... | Kubectl diff panic when one port has not containerPort port | https://api.github.com/repos/kubernetes/kubernetes/issues/82863/comments | 7 | 2019-09-19T06:38:37Z | 2020-02-28T20:17:31Z | https://github.com/kubernetes/kubernetes/issues/82863 | 495,602,907 | 82,863 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
I have the ... | [v1.16.1] informer-gen is broken for packages in a folder with a dot in them? | https://api.github.com/repos/kubernetes/kubernetes/issues/82860/comments | 6 | 2019-09-19T04:59:24Z | 2019-09-27T12:49:05Z | https://github.com/kubernetes/kubernetes/issues/82860 | 495,573,798 | 82,860 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
apimachiner... | apimachinery change breaks clients generated against v1.14 | https://api.github.com/repos/kubernetes/kubernetes/issues/82859/comments | 15 | 2019-09-19T04:26:06Z | 2019-10-03T02:42:40Z | https://github.com/kubernetes/kubernetes/issues/82859 | 495,565,733 | 82,859 |
[
"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**:
Recent inst... | [v1.16.1] Panic in controller manager | https://api.github.com/repos/kubernetes/kubernetes/issues/82854/comments | 6 | 2019-09-19T03:32:18Z | 2019-10-03T01:09:36Z | https://github.com/kubernetes/kubernetes/issues/82854 | 495,554,034 | 82,854 |
[
"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**:
Use GNU Make ... | compile failure: `execvp: /bin/bash: Argument list too long' | https://api.github.com/repos/kubernetes/kubernetes/issues/82852/comments | 1 | 2019-09-19T02:18:38Z | 2019-09-19T05:45:30Z | https://github.com/kubernetes/kubernetes/issues/82852 | 495,537,201 | 82,852 |
[
"kubernetes",
"kubernetes"
] | I installed isti v1.3 in the kubernetes v1.1.4.3 cluster and created the service named NodePort in the name: istio-ingressgateway.
Service/istio-ingressgateway NodePort 10.101.149.203 <none> 15020:30039/TCP,80:31380/TCP,443:31390/TCP,31400:31400/TCP,15029:30557/TCP,15030:31540/TCP,15031: 30098/TCP, 15032:30811/TCP, ... | can't open "nodePort for istio-system/istio-ingressgateway:tcp" (:31400/tcp), skipping this nodePort: listen tcp :31400: bind: address already in use | https://api.github.com/repos/kubernetes/kubernetes/issues/82851/comments | 3 | 2019-09-19T02:00:30Z | 2019-09-19T11:29:51Z | https://github.com/kubernetes/kubernetes/issues/82851 | 495,533,110 | 82,851 |
[
"kubernetes",
"kubernetes"
] |
I use kubernetes +containrd+kata building my running environment.
I create a pod.
when I run kubect cp command , copy local file to specified directory in the remote pod.
command as below:
kubectl cp local_file pod_name:/root/
then, "kubectl cp" cannot end.
version :
kata 1.7.0
containerd v1.2.6
kube... | kubectl cp command hangs, it cannot end | https://api.github.com/repos/kubernetes/kubernetes/issues/82849/comments | 5 | 2019-09-19T01:30:22Z | 2020-02-16T21:33:38Z | https://github.com/kubernetes/kubernetes/issues/82849 | 495,526,856 | 82,849 |
[
"kubernetes",
"kubernetes"
] | the leader election code should be emitting events against the v1beta1 Events API. This change also concerns any kubernetes component (such as kube-scheduler or the controller-manager) that uses the `leaderelection` package.
Part of #76674
/kind feature
/sig scalability
/sig instrumentation
/priority important... | migrate the leader election to use v1beta1 Events | https://api.github.com/repos/kubernetes/kubernetes/issues/82846/comments | 6 | 2019-09-18T21:57:14Z | 2020-04-08T17:51:40Z | https://github.com/kubernetes/kubernetes/issues/82846 | 495,474,600 | 82,846 |
[
"kubernetes",
"kubernetes"
] | I am running k8s 1.15 and I see kubectl top --help is returning the following info:
...This command requires Heapster to be correctly configured and working on the server.
As far as I know Heaspter is deprecated since 1.11.
1) Should the command help be updated i.e. replace Heapster with Metrics Server?
2) Wi... | kubectl top command | https://api.github.com/repos/kubernetes/kubernetes/issues/82843/comments | 2 | 2019-09-18T20:25:29Z | 2019-10-05T04:51:12Z | https://github.com/kubernetes/kubernetes/issues/82843 | 495,437,301 | 82,843 |
[
"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**:
Moving https:... | NodeStageVolume is called before each call to NodePublishVolume | https://api.github.com/repos/kubernetes/kubernetes/issues/82838/comments | 7 | 2019-09-18T16:32:18Z | 2020-02-16T20:32:39Z | https://github.com/kubernetes/kubernetes/issues/82838 | 495,333,719 | 82,838 |
[
"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... | Some volume provisioners do not support pvc selector | https://api.github.com/repos/kubernetes/kubernetes/issues/82837/comments | 3 | 2019-09-18T16:16:22Z | 2019-10-20T14:05:43Z | https://github.com/kubernetes/kubernetes/issues/82837 | 495,326,187 | 82,837 |
[
"kubernetes",
"kubernetes"
] | Now that new Events API is ready, we can migrate the kube-scheduler to emit events against the new API.
This is part of #76674
/assign | Migrate kube-scheduler to use v1beta1 Events | https://api.github.com/repos/kubernetes/kubernetes/issues/82835/comments | 4 | 2019-09-18T15:17:51Z | 2019-09-19T03:44:02Z | https://github.com/kubernetes/kubernetes/issues/82835 | 495,293,644 | 82,835 |
[
"kubernetes",
"kubernetes"
] | **What happened**: Failed to install kubectl and kubeadm via YUM repos. Basically there appears to be a dependency on conntrack-tools-1.4.4-4.el7.x86_64 and libnetfilter_ctfilter-1.0.0-9.el7.x86_64 which seems to be no longer available on the centos repos, nor on the mirrors.
**What you expected to happen**: Install... | conntrack-tools issue on 1.15.3 (install related) | https://api.github.com/repos/kubernetes/kubernetes/issues/82828/comments | 3 | 2019-09-18T12:36:17Z | 2020-01-16T14:32:42Z | https://github.com/kubernetes/kubernetes/issues/82828 | 495,198,102 | 82,828 |
[
"kubernetes",
"kubernetes"
] | Now that new Events API is ready, we can migrate the kube-controller-manager to emit events against the new API.
This is part of #76674 | Migrate kube-controller-manager to use v1beta1 Events | https://api.github.com/repos/kubernetes/kubernetes/issues/82827/comments | 13 | 2019-09-18T12:27:01Z | 2021-02-10T22:35:44Z | https://github.com/kubernetes/kubernetes/issues/82827 | 495,193,494 | 82,827 |
[
"kubernetes",
"kubernetes"
] | API server latency for PV creation depends on underlying cloud API latency. We have admission plugin that examines incoming PV and adds topology labels and node selector:
https://github.com/kubernetes/kubernetes/blob/61774cd7176cae0c0324d23ab20e6c6b3038153f/plugin/pkg/admission/storage/persistentvolume/label/admissi... | API server latency is affected by cloud provider latency | https://api.github.com/repos/kubernetes/kubernetes/issues/82826/comments | 1 | 2019-09-18T12:26:34Z | 2019-09-20T19:27:39Z | https://github.com/kubernetes/kubernetes/issues/82826 | 495,193,282 | 82,826 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
NodePort only responding when connecting locally from node but not from other machines on the network.
**What you expected to happen**:
NodePort should be accessible from other machines as well
**How to reproduce it (as minimally and precisely as possible)**:
NodePort service definition
```... | NodePort only responding when connecting locally from node but not from other machines. | https://api.github.com/repos/kubernetes/kubernetes/issues/82825/comments | 11 | 2019-09-18T11:51:46Z | 2024-12-29T21:40:09Z | https://github.com/kubernetes/kubernetes/issues/82825 | 495,176,613 | 82,825 |
[
"kubernetes",
"kubernetes"
] | I like to change the control manager --terminated-pod-gc-threshold value from the default 12500 pods to a small value in my kubernetes cluster. Like 100 or 50. Setting this flag to a small one will cause any issues ? Why kubernetes itself set it to a very high value by default. Is that purposefully set ?
| Set kubernetes controller-manager "terminated-pod-gc-threshold" flag to a small value | https://api.github.com/repos/kubernetes/kubernetes/issues/82824/comments | 6 | 2019-09-18T11:16:31Z | 2020-02-16T07:19:41Z | https://github.com/kubernetes/kubernetes/issues/82824 | 495,160,900 | 82,824 |
[
"kubernetes",
"kubernetes"
] | Now that new Events API is ready, we can migrate the kube-proxy to emit events against the new API.
This is part of #76674
| Migrate kube-proxy to use v1beta1 Events | https://api.github.com/repos/kubernetes/kubernetes/issues/82819/comments | 7 | 2019-09-18T09:16:16Z | 2020-02-20T16:04:21Z | https://github.com/kubernetes/kubernetes/issues/82819 | 495,096,506 | 82,819 |
[
"kubernetes",
"kubernetes"
] | **This is not a regression - it's a test issue introduced by our extensions**
<!-- 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 test
**Since when has it been... | [Failing Test] [sig scalability] gce-master-scale-performance - load test fails and started taking ~3h longer | https://api.github.com/repos/kubernetes/kubernetes/issues/82818/comments | 4 | 2019-09-18T09:16:02Z | 2019-09-25T07:08:19Z | https://github.com/kubernetes/kubernetes/issues/82818 | 495,096,346 | 82,818 |
[
"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**:
[k8s.io] Security Context should run with an image specified user ID [It]
[k8s.io] Security Context When creating... | [Failing Test] Security Context should run with an image specified user ID | https://api.github.com/repos/kubernetes/kubernetes/issues/82816/comments | 1 | 2019-09-18T08:48:07Z | 2019-10-18T19:37:25Z | https://github.com/kubernetes/kubernetes/issues/82816 | 495,079,766 | 82,816 |
[
"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-storage] EmptyDir volumes [It] pod should support shared volumes between containers [Conformance]
**Sinc... | [Failing Test] [sig-storage]EmptyDir volumes pod should support shared volumes between containers | https://api.github.com/repos/kubernetes/kubernetes/issues/82811/comments | 3 | 2019-09-18T06:01:50Z | 2019-09-18T18:11:33Z | https://github.com/kubernetes/kubernetes/issues/82811 | 495,006,512 | 82,811 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
Getting `/healthz?verbose=true` from apiserver presently returns output like:
```
[+]ping ok
[+]log ok
[+]etcd ok
[+]poststarthook/generic-apiserver-start-informers ok
[+]poststarthook/start-apiexte... | /healthz?verbose=true should report component timings | https://api.github.com/repos/kubernetes/kubernetes/issues/82808/comments | 16 | 2019-09-17T21:32:45Z | 2020-03-02T23:26:28Z | https://github.com/kubernetes/kubernetes/issues/82808 | 494,862,691 | 82,808 |
[
"kubernetes",
"kubernetes"
] | Hi; I'm tapping this out on my phone, so please forgive the missing boilerplate. Using client v1.15.0, server 1.15.3, kubectl 1.15.3 (as reported by apt) on Ubuntu 18.04, kubectl isn't working the way I expect.
Try some command `kubectl -n namespace exec podname -c containername -ti bash -c "command"`. I tried this w... | kubectl exec sometimes interprets options right of the opening command as its own | https://api.github.com/repos/kubernetes/kubernetes/issues/82806/comments | 3 | 2019-09-17T20:12:15Z | 2019-09-17T20:37:17Z | https://github.com/kubernetes/kubernetes/issues/82806 | 494,828,539 | 82,806 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
We are running multiple Azure Kubernetes services that accept long running websocket connections. These services are externally exposed through an Azure load balancer and they handle multiple concurrent connections from clients. During these connections, the client sends a fairly constant stream of ... | Websocket connection failures | https://api.github.com/repos/kubernetes/kubernetes/issues/82799/comments | 18 | 2019-09-17T17:52:10Z | 2019-10-03T18:01:37Z | https://github.com/kubernetes/kubernetes/issues/82799 | 494,765,428 | 82,799 |
[
"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 schedu... | kube-scheduler panic on PodAffinity | https://api.github.com/repos/kubernetes/kubernetes/issues/82796/comments | 9 | 2019-09-17T16:55:26Z | 2019-09-26T22:25:41Z | https://github.com/kubernetes/kubernetes/issues/82796 | 494,739,702 | 82,796 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
OOM reached on nodes
**What you expected to happen**:
pods are evicted based on eviction rules before triggering OOM
**How to reproduce it (as minimally and precisely as possible)**:
Configure the kubelet to grant additional memory to kubeReserved and or systemReserved past what is given ... | Eviction signals do not consider reserved compute resources | https://api.github.com/repos/kubernetes/kubernetes/issues/82793/comments | 6 | 2019-09-17T15:49:34Z | 2020-02-14T17:57:14Z | https://github.com/kubernetes/kubernetes/issues/82793 | 494,707,276 | 82,793 |
[
"kubernetes",
"kubernetes"
] | hi, I am trying to build a 3 master cluster but I am getting below error c. can some help me.
kubeadm init --config config.yaml
W0917 10:44:31.802396 10260 strict.go:54] error unmarshaling configuration schema.GroupVersionKind{Group:"kubeadm.k8s.io", Version:"v1beta1", Kind:"ClusterConfiguration"}: error unmarsh... | k8s high availability / multi master cluster issue | https://api.github.com/repos/kubernetes/kubernetes/issues/82792/comments | 2 | 2019-09-17T15:21:06Z | 2019-09-30T14:04:45Z | https://github.com/kubernetes/kubernetes/issues/82792 | 494,691,041 | 82,792 |
[
"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... | Kubeadm init --config config.yaml issue ( high avalibulity cluster ) | https://api.github.com/repos/kubernetes/kubernetes/issues/82791/comments | 4 | 2019-09-17T15:17:18Z | 2019-09-17T17:16:46Z | https://github.com/kubernetes/kubernetes/issues/82791 | 494,688,843 | 82,791 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
Our tooling that makes the list of conformance tests needs to allow conformance tests to be marked as disruptive.
**Why is this needed**:
To test default, conformance behavior which may be disruptive (e.g. taint eviction)
ref #82663
/sig testing
/area conformance | Allow conformance tests to be marked as Disruptive | https://api.github.com/repos/kubernetes/kubernetes/issues/82787/comments | 0 | 2019-09-17T14:13:31Z | 2019-09-25T18:06:30Z | https://github.com/kubernetes/kubernetes/issues/82787 | 494,650,615 | 82,787 |
[
"kubernetes",
"kubernetes"
] | Dear Pull Requests integrators,
We are an international group of researchers investigating Pull Requests management activities. We implemented an automated approach, named CARTESIAN, for prioritizing Pull Requests (PRs) received by an open-source project according to the likelihood of acceptance/response. We would lik... | Survey on Pull Request Prioritization | https://api.github.com/repos/kubernetes/kubernetes/issues/82786/comments | 3 | 2019-09-17T12:00:26Z | 2019-09-17T12:37:32Z | https://github.com/kubernetes/kubernetes/issues/82786 | 494,579,499 | 82,786 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
initContainers does not accept imagePullSecrets. No way to configure a secret so initContainers can connect to a private repository.
**What you expected to happen**:
Adding an imagePullSecrets under spec should work for both container and initContainers
**How to reproduce it (as minimally and... | initContainers does not accept imagePullSecrets | https://api.github.com/repos/kubernetes/kubernetes/issues/82782/comments | 9 | 2019-09-17T10:23:43Z | 2022-10-11T07:13:24Z | https://github.com/kubernetes/kubernetes/issues/82782 | 494,536,108 | 82,782 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
Add support for Azure Write Accelerator on Azure Disks - https://docs.microsoft.com/azure/virtual-machines/windows/how-to-enable-write-accelerator
**Why is this needed**:
For high performance applicat... | Azure: Add Support for Write Accelerator | https://api.github.com/repos/kubernetes/kubernetes/issues/82781/comments | 10 | 2019-09-17T10:03:42Z | 2020-02-13T05:37:26Z | https://github.com/kubernetes/kubernetes/issues/82781 | 494,526,467 | 82,781 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
Currently, when AAD login is configured, refresh token timeout would make kubectl print an error, not able to re-login without manually remove the tokens. Expect kubectl to promote user to login again.
... | kubectl: Azure AAD authentication should handle refresh token timeout | https://api.github.com/repos/kubernetes/kubernetes/issues/82776/comments | 14 | 2019-09-17T06:42:32Z | 2020-03-25T02:14:06Z | https://github.com/kubernetes/kubernetes/issues/82776 | 494,432,347 | 82,776 |
[
"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 building... | reset `binfmt_misc` is needn't when build arm images on arm platform | https://api.github.com/repos/kubernetes/kubernetes/issues/82775/comments | 17 | 2019-09-17T06:27:30Z | 2021-02-20T08:55:42Z | https://github.com/kubernetes/kubernetes/issues/82775 | 494,426,766 | 82,775 |
[
"kubernetes",
"kubernetes"
] | Hi All,
We have two EKS cluster running, we are running the kubectl command from one cluster to deploy the pod in other cluster, we are getting error like below.
when the kind is deployment instead of pod, we are able to deploy.
**Error: release test-api failed: pods "test-api" is forbidden: pod does not have "ku... | Not able to deploy kind:pod from another cluster. | https://api.github.com/repos/kubernetes/kubernetes/issues/82774/comments | 5 | 2019-09-17T05:34:46Z | 2021-03-12T23:18:52Z | https://github.com/kubernetes/kubernetes/issues/82774 | 494,410,330 | 82,774 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
If a node with illegal cidr is added into a cluster, there is a error message in kube-controller-manager.ERROR. The error message only appears once, the cluster will be thought as normal and do nothing if the error message is missed. Everything is ok until controller-managers change leader or rest... | kube-controller-manager crash when node.Spec.PodCIDR is out of range, is the result as expected? | https://api.github.com/repos/kubernetes/kubernetes/issues/82773/comments | 16 | 2019-09-17T04:05:56Z | 2020-03-13T04:26:18Z | https://github.com/kubernetes/kubernetes/issues/82773 | 494,388,984 | 82,773 |
[
"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**:
[k8s.io] Container Manager Misc [Serial] Validate OOM score adjustments [NodeFeature:OOMScoreAdj] once the node i... | [Failing Test] [sig-node] pod infra containers oom-score-adj should be -998 and best effort container's should be 1000 | https://api.github.com/repos/kubernetes/kubernetes/issues/82771/comments | 8 | 2019-09-17T03:32:03Z | 2019-10-07T15:43:11Z | https://github.com/kubernetes/kubernetes/issues/82771 | 494,381,430 | 82,771 |
[
"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**:
Hello, on m... | kubectl get node slowly | https://api.github.com/repos/kubernetes/kubernetes/issues/82770/comments | 12 | 2019-09-17T03:30:47Z | 2020-04-26T14:45:21Z | https://github.com/kubernetes/kubernetes/issues/82770 | 494,381,139 | 82,770 |
[
"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 kube-apiser... | kube-apiserver sometimes times out contacting MutatingWebhook | https://api.github.com/repos/kubernetes/kubernetes/issues/82768/comments | 17 | 2019-09-17T01:25:34Z | 2020-06-17T17:08:10Z | https://github.com/kubernetes/kubernetes/issues/82768 | 494,352,572 | 82,768 |
Subsets and Splits
Unique Owner-Repo Count
Counts the number of unique owner-repos in the dataset, providing a basic understanding of diverse repositories.