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"
] | Same as an issue that occurred for v1.14.0: the failing test causes ginkgo to exit non-zero which causes the script to abort without running the `saveResult` routine.
A recent PR to this script fixed a race but we didn't realize that now that the command was running in the foreground (and not the background) that th... | Conformance script for v1.16.0 doesn't report results to Sonobuoy if failures | https://api.github.com/repos/kubernetes/kubernetes/issues/83272/comments | 3 | 2019-09-28T17:48:13Z | 2019-10-25T05:55:56Z | https://github.com/kubernetes/kubernetes/issues/83272 | 499,800,557 | 83,272 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
Something like kubectl delete cm abcd --all-namespaces
**Why is this needed**:
There is no other way of doing this apart from scripting it. This would come in really handy if a bad change caused a res... | support delete resource by name with --all-namespaces=true | https://api.github.com/repos/kubernetes/kubernetes/issues/83266/comments | 8 | 2019-09-28T03:10:01Z | 2020-03-10T10:21:39Z | https://github.com/kubernetes/kubernetes/issues/83266 | 499,718,793 | 83,266 |
[
"kubernetes",
"kubernetes"
] | I tried to use a local volume block device in minikube. Its trying to call losetup with the -j option and its failing as the losetup in minikube does not provide this option. This may effect other distro's as well. The end result is lock block devices don't work on the platform. | local blockdevice | https://api.github.com/repos/kubernetes/kubernetes/issues/83265/comments | 16 | 2019-09-28T00:52:28Z | 2021-05-12T12:05:40Z | https://github.com/kubernetes/kubernetes/issues/83265 | 499,704,974 | 83,265 |
[
"kubernetes",
"kubernetes"
] | I have 5 nodes running in k8s cluster and with around 30 pods.
Some of the pods usually take high memory. At one stage we found a node went to "not ready" state when the sum of memory of all running pods exceeded node memory. Anyhow, I increased the resource request memory to high value for high memory pods but shoul... | Node "not ready" state when sum of all running pods exceed node capacity | https://api.github.com/repos/kubernetes/kubernetes/issues/83264/comments | 5 | 2019-09-27T22:10:59Z | 2020-02-25T13:56:17Z | https://github.com/kubernetes/kubernetes/issues/83264 | 499,671,977 | 83,264 |
[
"kubernetes",
"kubernetes"
] | #81517 makes it so that the iptables proxier only tries to do an iptables-restore when things have actually changed, rather than doing it every `iptablesSyncPeriod` whether or not things have changed. As @squeed just pointed out in that PR, it turns out there's some fallout from this:
1. If an `iptables-restore` cal... | fallout from kube-proxy no longer doing "unnecessary" updates | https://api.github.com/repos/kubernetes/kubernetes/issues/83263/comments | 15 | 2019-09-27T21:03:48Z | 2019-11-01T13:18:23Z | https://github.com/kubernetes/kubernetes/issues/83263 | 499,649,825 | 83,263 |
[
"kubernetes",
"kubernetes"
] | https://github.com/kubernetes/kubernetes/blob/release-1.16/staging/src/k8s.io/apiserver/pkg/authentication/token/cache/cached_token_authenticator.go#L70-L91
This code releases the lock to do the actual work. This means if there are N simultaneous requests for a token, apiserver will look it up N times. If that happe... | Authentication token cache can live-lock | https://api.github.com/repos/kubernetes/kubernetes/issues/83259/comments | 8 | 2019-09-27T20:09:42Z | 2019-12-19T04:36:55Z | https://github.com/kubernetes/kubernetes/issues/83259 | 499,628,707 | 83,259 |
[
"kubernetes",
"kubernetes"
] | @kubernetes/sig-contributor-experience-<group-suffix>
PROBLEM STATEMENT
Is there any way by which i can increase the CPU load on a pod such that for time being the CPU Request is more than the CPU Limits so that the pod gets reschedule to a new node.
```
Limits:
cpu: 500m
Requests:
cpu: 500m... | To increase the CPU load on a pod so that it would get scheduled to a new node | https://api.github.com/repos/kubernetes/kubernetes/issues/83256/comments | 6 | 2019-09-27T18:47:09Z | 2020-02-15T21:35:05Z | https://github.com/kubernetes/kubernetes/issues/83256 | 499,595,012 | 83,256 |
[
"kubernetes",
"kubernetes"
] | @kubernetes/sig-contributor-experience-<group-suffix>
PROBLEM STATEMENT
Is there any way by which i can increase the CPU load on a pod such that for time being the CPU Request is more than the CPU Limits so that the pod gets reschedule to a new node.
```
Limits:
cpu: 500m
Requests:
cpu: 500m... | To increase the CPU load on a pod so that it would get scheduled to a new node | https://api.github.com/repos/kubernetes/kubernetes/issues/83254/comments | 1 | 2019-09-27T16:55:10Z | 2019-09-27T18:36:36Z | https://github.com/kubernetes/kubernetes/issues/83254 | 499,548,862 | 83,254 |
[
"kubernetes",
"kubernetes"
] | CVE-2019-11253 is a denial of service vulnerability in the kube-apiserver, allowing authorized users sending malicious YAML or JSON payloads to cause kube-apiserver to consume excessive CPU or memory, potentially crashing and becoming unavailable. This vulnerability has been given an initial severity of High, with a sc... | CVE-2019-11253: Kubernetes API Server JSON/YAML parsing vulnerable to resource exhaustion attack | https://api.github.com/repos/kubernetes/kubernetes/issues/83253/comments | 17 | 2019-09-27T16:53:31Z | 2022-10-14T02:09:16Z | https://github.com/kubernetes/kubernetes/issues/83253 | 499,548,171 | 83,253 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
A consistent way for adding extended functionality to plugins.
**Why is this needed**:
Currently we have two types of plugins that support adding some sort of optional functionality: PreFilter allow adding "AddPod/RemovePod" implementations through an "Updater" interface, while... | [framework] a consistent interface for plugin extended functionality | https://api.github.com/repos/kubernetes/kubernetes/issues/83244/comments | 13 | 2019-09-27T13:41:09Z | 2019-10-01T20:01:13Z | https://github.com/kubernetes/kubernetes/issues/83244 | 499,453,536 | 83,244 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
Refactor priorities to use [NodeScore/NodeScoreList](https://github.com/kubernetes/kubernetes/blob/master/pkg/scheduler/framework/v1alpha1/interface.go#L35-L44) instead of [HostPriority/HostPriorityList](https://github.com/kubernetes/kubernetes/blob/master/pkg/scheduler/api/types.g... | [migration] Refactor priorities to use NodeScore/NodeScoreList | https://api.github.com/repos/kubernetes/kubernetes/issues/83241/comments | 6 | 2019-09-27T12:31:36Z | 2019-10-02T02:34:28Z | https://github.com/kubernetes/kubernetes/issues/83241 | 499,418,391 | 83,241 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
A separate cycle for filtering and scoring phases in the scheduler framework.
**Why is this needed**:
Currently, the scheduler framework is divided into two separate cycles, the schedulign and the binding cycles. These cycles are run in different threads which give some asy... | [Scheduler framework] Split scheduling cycle into filter and score cycles | https://api.github.com/repos/kubernetes/kubernetes/issues/83240/comments | 6 | 2019-09-27T11:55:33Z | 2020-02-24T16:35:43Z | https://github.com/kubernetes/kubernetes/issues/83240 | 499,402,805 | 83,240 |
[
"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 have a sma... | Kubectl works and all the pods are up but no traffic goes through | https://api.github.com/repos/kubernetes/kubernetes/issues/83235/comments | 1 | 2019-09-27T09:51:27Z | 2019-10-02T11:16:59Z | https://github.com/kubernetes/kubernetes/issues/83235 | 499,349,440 | 83,235 |
[
"kubernetes",
"kubernetes"
] | /kind bug
/sig network
/area ipvs
After the edge node deploys keepalived, the vip forwarding record of ipvsadm will be deleted
CNI ： calico v3.8.2
kubernetes: 1.14.7
proxyMode: ipvs
OS: centos 7
kernel: 4.4.190-1.el7.elrepo.x86_64
keepalived version: v1.3.5
ipvsadm version: v1.27
docker: 18.09.8
... | After the edge node deploys keepalived, the vip forwarding record of ipvsadm will be deleted. | https://api.github.com/repos/kubernetes/kubernetes/issues/83232/comments | 4 | 2019-09-27T08:36:23Z | 2020-02-24T11:30:41Z | https://github.com/kubernetes/kubernetes/issues/83232 | 499,313,563 | 83,232 |
[
"kubernetes",
"kubernetes"
] | controller.go:115] failed to ensure node lease exists, will retry in 7s, error: Get https://10.204.243.89:6443/apis/coordination.k8s.io/v1beta1/namespaces/kube-node-lease/leases/10.204.60.13?timeout=10s: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
k8s version v1.15
i config kube-apiser... | failed to ensure node lease exists, will retry in 7s ,the k8s node offen notReady | https://api.github.com/repos/kubernetes/kubernetes/issues/83230/comments | 9 | 2019-09-27T08:26:06Z | 2025-01-24T08:08:47Z | https://github.com/kubernetes/kubernetes/issues/83230 | 499,308,691 | 83,230 |
[
"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**:
Currently kub... | The cgroup name can't be nil while systemReserved is designated | https://api.github.com/repos/kubernetes/kubernetes/issues/83228/comments | 8 | 2019-09-27T08:15:59Z | 2020-03-07T15:15:37Z | https://github.com/kubernetes/kubernetes/issues/83228 | 499,304,147 | 83,228 |
[
"kubernetes",
"kubernetes"
] | Currently, DevicePluginPath is set to "/var/lib/kubelet/device-plugins".
[deviceplugin/v1alpha/constants.go](https://github.com/kubernetes/kubernetes/blob/master/pkg/kubelet/apis/deviceplugin/v1alpha/constants.go)
[deviceplugin/v1beta1/constants.go](https://github.com/kubernetes/kubernetes/blob/master/pkg/kubelet/api... | Suggest DevicePluginPath folder is created under the kubelet root directory | https://api.github.com/repos/kubernetes/kubernetes/issues/83226/comments | 6 | 2019-09-27T07:52:52Z | 2020-02-24T13:32:41Z | https://github.com/kubernetes/kubernetes/issues/83226 | 499,294,341 | 83,226 |
[
"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 installed k... | installed kubernetes with kubeadm have an error! | https://api.github.com/repos/kubernetes/kubernetes/issues/83225/comments | 25 | 2019-09-27T06:52:51Z | 2021-11-16T07:45:00Z | https://github.com/kubernetes/kubernetes/issues/83225 | 499,269,703 | 83,225 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
We encountered a problem in production to run databases with local PVs and StatefulSet. It's inconvenient to scale in the database when pods on the node to delete are not the last ordinal indices of the... | Feature Request: Scale in StatefulSet at an arbitrary position | https://api.github.com/repos/kubernetes/kubernetes/issues/83224/comments | 11 | 2019-09-27T03:49:25Z | 2021-11-22T02:25:30Z | https://github.com/kubernetes/kubernetes/issues/83224 | 499,219,358 | 83,224 |
[
"kubernetes",
"kubernetes"
] | Kubenetes built-in resource objects StatefulSet、Deployment、DaemonSet ... of fields AllowUnconditionalUpdate default is true。
```
// AllowUnconditionalUpdate is the default update policy for daemon set objects.
func (daemonSetStrategy) AllowUnconditionalUpdate() bool {
return true
}
```
Why CRD resource of fi... | CRD AllowUnconditionalUpdate modify | https://api.github.com/repos/kubernetes/kubernetes/issues/83222/comments | 9 | 2019-09-27T02:59:01Z | 2019-11-13T13:39:55Z | https://github.com/kubernetes/kubernetes/issues/83222 | 499,208,555 | 83,222 |
[
"kubernetes",
"kubernetes"
] | use client-go call kuberneres api
error : apiserver EOF
why ?
| apiserver EOF | https://api.github.com/repos/kubernetes/kubernetes/issues/83221/comments | 7 | 2019-09-27T02:48:32Z | 2020-02-25T19:01:17Z | https://github.com/kubernetes/kubernetes/issues/83221 | 499,206,091 | 83,221 |
[
"kubernetes",
"kubernetes"
] | @ddebroy brought this up.
If a volume is provisioned using the in-tree plugin - then the cluster is upgraded and migration is turned on - the path for migration may never pick up the volume for deletion since it is not annotated with the external provisioner name. This could result in leaked volumes/PV's.
We coul... | Volume+PV of volume provisioned by in-tree plugin and meant to be deleted by migration may be broken | https://api.github.com/repos/kubernetes/kubernetes/issues/83216/comments | 3 | 2019-09-27T00:46:59Z | 2019-09-27T00:48:01Z | https://github.com/kubernetes/kubernetes/issues/83216 | 499,178,159 | 83,216 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
When I run kubernetes 1.16, everything is working well:
```
kind create cluster --image gcr.io/istio-testing/kind-node:v1.16.0
<inside a pod>
$ curl google.com
... Success ...
$ nslookup google.com
... Success ...
```
Then I try to enable EndpointSlice:
```
kind create cluster --... | DNS resolution fails when EndpointSlice is enabled on 1.16 | https://api.github.com/repos/kubernetes/kubernetes/issues/83212/comments | 8 | 2019-09-26T23:15:20Z | 2019-10-08T23:45:46Z | https://github.com/kubernetes/kubernetes/issues/83212 | 499,157,697 | 83,212 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
Add readiness probe deny traffic function to startup probe function when readiness probe isn't declared.
**Why is this needed**:
Startup probe prevents a long starting container from triggering a live... | Include readiness probe deny traffic to startup probe functionality | https://api.github.com/repos/kubernetes/kubernetes/issues/83210/comments | 6 | 2019-09-26T22:37:57Z | 2020-02-27T02:31:42Z | https://github.com/kubernetes/kubernetes/issues/83210 | 499,147,846 | 83,210 |
[
"kubernetes",
"kubernetes"
] | In v1.16.0 https://github.com/kubernetes/kubernetes/pull/78447 migrated kube-scheduler to emit events against the v1beta1 API, but didn't implement a fallback to core/v1 in case `events.k8s.io/v1beta1` is not available. we should fix this.
The fix would targed v1.16.2
/assign @yastij
cc @wojtek-t @liggitt
/... | kube-scheduler should fallback to core/v1 Events if events.k8s.io/v1beta1 is unavailable | https://api.github.com/repos/kubernetes/kubernetes/issues/83203/comments | 2 | 2019-09-26T16:58:50Z | 2019-10-28T21:08:44Z | https://github.com/kubernetes/kubernetes/issues/83203 | 499,005,634 | 83,203 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
Allow aggregated apiservers to register long-running request (to e.g. filter them out like it is done with the `logs` subresource), or leave it completely up to the aggregated apiserver to terminate connections after timeouts.
**Why is this needed**:
There are cases where o... | Support long-running requests on aggregated apiservers | https://api.github.com/repos/kubernetes/kubernetes/issues/83200/comments | 12 | 2019-09-26T14:17:53Z | 2020-02-27T08:37:44Z | https://github.com/kubernetes/kubernetes/issues/83200 | 498,915,985 | 83,200 |
[
"kubernetes",
"kubernetes"
] | There is no reason this should be allowed to happen, especially that we can't configure duplicate plugins differently since plugin configs is a separate list .
/sig scheduling | [migration] Fail framework creation when duplicate plugins registered at the same extension point | https://api.github.com/repos/kubernetes/kubernetes/issues/83194/comments | 6 | 2019-09-26T13:22:15Z | 2019-10-03T21:39:55Z | https://github.com/kubernetes/kubernetes/issues/83194 | 498,881,645 | 83,194 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
[predicateMetadata](https://github.com/kubernetes/kubernetes/blob/e5f276a1ab226f3590634a240a6a82aa9fefcb49/pkg/scheduler/algorithm/predicates/metadata.go#L129) contains a collection of variables that gets populated before running predicates. We want to refactor it into a collecti... | [migration] Refactor predicateMetadata into a collection of sub types | https://api.github.com/repos/kubernetes/kubernetes/issues/83193/comments | 4 | 2019-09-26T13:13:05Z | 2019-10-08T22:42:44Z | https://github.com/kubernetes/kubernetes/issues/83193 | 498,876,357 | 83,193 |
[
"kubernetes",
"kubernetes"
] | `test/e2e/network/network_policy.go` needs a test to ensure that `ipBlock.except` clauses are implemented correctly. Specifically, that they are not implemented as "deny" rules.
eg, given a client pod with IP `A.B.C.D`, if you add a NetworkPolicy with:
spec:
ingress:
- from:
- ipBlock:
... | need a test of NetworkPolicy with IPBlock.Except | https://api.github.com/repos/kubernetes/kubernetes/issues/83191/comments | 2 | 2019-09-26T12:51:11Z | 2020-04-13T20:37:49Z | https://github.com/kubernetes/kubernetes/issues/83191 | 498,864,665 | 83,191 |
[
"kubernetes",
"kubernetes"
] | **test inject the token for the current service account into a Pod is failed**
**kubernetes version:** 1.5.3
**calico version:** 3.8.2
**os:** centos 7 4.4.193-1.el7.elrepo.x86_64
create pods yaml
```apiVersion: v1
kind: Pod
metadata:
name: sa-token-test
spec:
containers:
- name: container-test
... | can not inject the token for the current service account into a Pod | https://api.github.com/repos/kubernetes/kubernetes/issues/83189/comments | 5 | 2019-09-26T11:54:06Z | 2019-09-26T12:56:10Z | https://github.com/kubernetes/kubernetes/issues/83189 | 498,838,393 | 83,189 |
[
"kubernetes",
"kubernetes"
] | **Why is this needed**:
In some cases, a pod fails to reach a healthy state for an unrecoverable reason: bad configuration, bug in the software... when this happens, restarting the pod will not help with the problem and will just cause a load increase in the cluster due to the restarts.
My proposal is to define a... | [Feature request] Exponential backoff on restarts of unhealthy pods | https://api.github.com/repos/kubernetes/kubernetes/issues/83187/comments | 9 | 2019-09-26T11:03:46Z | 2019-12-27T13:35:40Z | https://github.com/kubernetes/kubernetes/issues/83187 | 498,816,355 | 83,187 |
[
"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 high ... | Kubernetes Node NotReady and unreachable | https://api.github.com/repos/kubernetes/kubernetes/issues/83186/comments | 13 | 2019-09-26T10:44:03Z | 2020-03-01T23:02:21Z | https://github.com/kubernetes/kubernetes/issues/83186 | 498,806,920 | 83,186 |
[
"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 kubelet m... | Dynamic kubelet config metrics missing | https://api.github.com/repos/kubernetes/kubernetes/issues/83183/comments | 9 | 2019-09-26T09:38:28Z | 2019-10-11T07:58:13Z | https://github.com/kubernetes/kubernetes/issues/83183 | 498,773,892 | 83,183 |
[
"kubernetes",
"kubernetes"
] | e.g. this one:
https://prow.k8s.io/view/gcs/kubernetes-jenkins/pr-logs/pull/83179/pull-kubernetes-integration/1177132150030340097/
/assign @krzysied
who was already looking into that | TaintBasedEviction test is flaky | https://api.github.com/repos/kubernetes/kubernetes/issues/83182/comments | 4 | 2019-09-26T09:35:10Z | 2020-01-22T01:42:06Z | https://github.com/kubernetes/kubernetes/issues/83182 | 498,772,025 | 83,182 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Provisioning of a volume with `volumeBindingMode: WaitForFirstConsumer` failed and this event were created on a **pod**:
```
Warning FailedScheduling <unknown> default-scheduler selectedNode annotation value "" not set to scheduled node "ip-172-18-14-249.ec2.internal"
```
The event doe... | Scheduler reports selectedNode annotation errors on late provisioning failure | https://api.github.com/repos/kubernetes/kubernetes/issues/83181/comments | 2 | 2019-09-26T08:32:24Z | 2019-10-04T15:50:34Z | https://github.com/kubernetes/kubernetes/issues/83181 | 498,739,060 | 83,181 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
[PV-Binder-Controller](https://github.com/kubernetes/kubernetes/blob/master/pkg/controller/volume/persistentvolume/pv_controller.go) has some performance issue, especially the latency of binding a volume, which is not acceptable for a high QPS k8s cluster.
**What you expected to happen**:
Fi... | Performance Issue of PV-Binder-Controller | https://api.github.com/repos/kubernetes/kubernetes/issues/83178/comments | 6 | 2019-09-26T08:03:56Z | 2020-02-23T10:05:43Z | https://github.com/kubernetes/kubernetes/issues/83178 | 498,725,217 | 83,178 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
[PV-Binder-Controller](https://github.com/kubernetes/kubernetes/blob/master/pkg/controller/volume/persistentvolume/pv_controller.go) will delete the new created (unused and unbound) PV if PV-Binder-Controller is on heavy load, when the PV related StorageClass ReclaimPolicy is OnDelete.
**Wh... | CRITICAL!! PV-Binder-Controller will delete the new created PV | https://api.github.com/repos/kubernetes/kubernetes/issues/83177/comments | 13 | 2019-09-26T07:45:08Z | 2019-10-09T15:21:55Z | https://github.com/kubernetes/kubernetes/issues/83177 | 498,716,249 | 83,177 |
[
"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**: With CentOS 7.... | kubelet service failed with wrong number of possible NUMA nodes | https://api.github.com/repos/kubernetes/kubernetes/issues/83175/comments | 1 | 2019-09-26T06:49:32Z | 2019-09-28T05:51:40Z | https://github.com/kubernetes/kubernetes/issues/83175 | 498,693,620 | 83,175 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
Refactor pkg/util to use https://github.com/kubernetes-sigs/legacyflag
**Why is this needed**:
This is part of a refactoring initiative run by @kubernetes/wg-component-standard to address the pain-points of backwards-compatible ComponentConfig migration.
/wg component-stan... | Refactor pkg/util to use legacyflags | https://api.github.com/repos/kubernetes/kubernetes/issues/83174/comments | 3 | 2019-09-26T05:37:59Z | 2019-09-27T06:24:58Z | https://github.com/kubernetes/kubernetes/issues/83174 | 498,669,496 | 83,174 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
Refactor pkg/kubelet to use https://github.com/kubernetes-sigs/legacyflag
**Why is this needed**:
This is part of a refactoring initiative run by @kubernetes/wg-component-standard to address the pain-points of backwards-compatible ComponentConfig migration.
/wg component-s... | Refactor pkg/kubelet to use legacyflags | https://api.github.com/repos/kubernetes/kubernetes/issues/83173/comments | 2 | 2019-09-26T05:37:33Z | 2019-09-27T05:29:17Z | https://github.com/kubernetes/kubernetes/issues/83173 | 498,669,373 | 83,173 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
Refactor pkg/kubectl to use https://github.com/kubernetes-sigs/legacyflag
**Why is this needed**:
This is part of a refactoring initiative run by @kubernetes/wg-component-standard to address the pain-points of backwards-compatible ComponentConfig migration.
/wg component-s... | Refactor pkg/kubectl to use legacyflags | https://api.github.com/repos/kubernetes/kubernetes/issues/83172/comments | 3 | 2019-09-26T05:30:48Z | 2019-09-27T05:34:11Z | https://github.com/kubernetes/kubernetes/issues/83172 | 498,667,490 | 83,172 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
Refactor pkg/kubeapiserver to use https://github.com/kubernetes-sigs/legacyflag
**Why is this needed**:
This is part of a refactoring initiative run by @kubernetes/wg-component-standard to address the pain-points of backwards-compatible ComponentConfig migration.
/wg compo... | Refactor pkg/kubeapiserver to use legacyflags | https://api.github.com/repos/kubernetes/kubernetes/issues/83171/comments | 2 | 2019-09-26T05:30:18Z | 2019-09-27T05:35:16Z | https://github.com/kubernetes/kubernetes/issues/83171 | 498,667,366 | 83,171 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
Refactor pkg/credentialprovider to use https://github.com/kubernetes-sigs/legacyflag
**Why is this needed**:
This is part of a refactoring initiative run by @kubernetes/wg-component-standard to address the pain-points of backwards-compatible ComponentConfig migration.
/wg ... | Refactor pkg/credentialprovider to use legacyflags | https://api.github.com/repos/kubernetes/kubernetes/issues/83170/comments | 3 | 2019-09-26T05:29:51Z | 2019-09-27T06:24:47Z | https://github.com/kubernetes/kubernetes/issues/83170 | 498,667,226 | 83,170 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
Refactor pkg/controller to use https://github.com/kubernetes-sigs/legacyflag
**Why is this needed**:
This is part of a refactoring initiative run by @kubernetes/wg-component-standard to address the pain-points of backwards-compatible ComponentConfig migration.
/wg componen... | Refactor pkg/controller to use legacyflags | https://api.github.com/repos/kubernetes/kubernetes/issues/83169/comments | 3 | 2019-09-26T05:24:11Z | 2019-09-27T06:24:51Z | https://github.com/kubernetes/kubernetes/issues/83169 | 498,665,609 | 83,169 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
Refactor pkg/client to use https://github.com/kubernetes-sigs/legacyflag
**Why is this needed**:
This is part of a refactoring initiative run by @kubernetes/wg-component-standard to address the pain-points of backwards-compatible ComponentConfig migration.
/wg component-st... | Refactor pkg/client to use legacyflags | https://api.github.com/repos/kubernetes/kubernetes/issues/83168/comments | 3 | 2019-09-26T05:23:41Z | 2019-09-27T06:24:55Z | https://github.com/kubernetes/kubernetes/issues/83168 | 498,665,468 | 83,168 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
Refactor hack/make-rules to use https://github.com/kubernetes-sigs/legacyflag
**Why is this needed**:
This is part of a refactoring initiative run by @kubernetes/wg-component-standard to address the pain-points of backwards-compatible ComponentConfig migration.
/wg compone... | Refactor hack/make-rules to use legacyflags | https://api.github.com/repos/kubernetes/kubernetes/issues/83167/comments | 7 | 2019-09-26T05:22:54Z | 2020-02-29T12:28:32Z | https://github.com/kubernetes/kubernetes/issues/83167 | 498,665,265 | 83,167 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
Refactor cmd/linkcheck to use https://github.com/kubernetes-sigs/legacyflag
**Why is this needed**:
This is part of a refactoring initiative run by @kubernetes/wg-component-standard to address the pain-points of backwards-compatible ComponentConfig migration.
/wg component... | Refactor cmd/linkcheck to use legacyflags | https://api.github.com/repos/kubernetes/kubernetes/issues/83166/comments | 6 | 2019-09-26T05:22:03Z | 2020-02-24T07:26:41Z | https://github.com/kubernetes/kubernetes/issues/83166 | 498,665,025 | 83,166 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
Refactor cmd/kubemark to use https://github.com/kubernetes-sigs/legacyflag
**Why is this needed**:
This is part of a refactoring initiative run by @kubernetes/wg-component-standard to address the pain-points of backwards-compatible ComponentConfig migration.
/wg component-... | Refactor cmd/kubemark to use legacyflags | https://api.github.com/repos/kubernetes/kubernetes/issues/83165/comments | 6 | 2019-09-26T05:21:03Z | 2020-02-24T07:26:40Z | https://github.com/kubernetes/kubernetes/issues/83165 | 498,664,743 | 83,165 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
Refactor cmd/kubelet to use https://github.com/kubernetes-sigs/legacyflag
**Why is this needed**:
This is part of a refactoring initiative run by @kubernetes/wg-component-standard to address the pain-points of backwards-compatible ComponentConfig migration.
/wg component-s... | Refactor cmd/kubelet to use legacyflags | https://api.github.com/repos/kubernetes/kubernetes/issues/83164/comments | 7 | 2019-09-26T05:20:37Z | 2020-02-29T13:29:27Z | https://github.com/kubernetes/kubernetes/issues/83164 | 498,664,633 | 83,164 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
Refactor cmd/kubectl to use https://github.com/kubernetes-sigs/legacyflag
**Why is this needed**:
This is part of a refactoring initiative run by @kubernetes/wg-component-standard to address the pain-points of backwards-compatible ComponentConfig migration.
/wg component-s... | Refactor cmd/kubectl to use legacyflags | https://api.github.com/repos/kubernetes/kubernetes/issues/83163/comments | 7 | 2019-09-26T05:19:55Z | 2020-02-29T13:29:24Z | https://github.com/kubernetes/kubernetes/issues/83163 | 498,664,444 | 83,163 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
Refactor cmd/kubeadmin to use https://github.com/kubernetes-sigs/legacyflag
**Why is this needed**:
This is part of a refactoring initiative run by @kubernetes/wg-component-standard to address the pain-points of backwards-compatible ComponentConfig migration.
/wg component... | Refactor cmd/kubeadmin to use legacyflags | https://api.github.com/repos/kubernetes/kubernetes/issues/83162/comments | 10 | 2019-09-26T05:18:51Z | 2020-02-29T13:29:23Z | https://github.com/kubernetes/kubernetes/issues/83162 | 498,664,137 | 83,162 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
Refactor cmd/kube-scheduler to use https://github.com/kubernetes-sigs/legacyflag
**Why is this needed**:
This is part of a refactoring initiative run by @kubernetes/wg-component-standard to address the pain-points of backwards-compatible ComponentConfig migration.
/wg comp... | Refactor cmd/kube-scheduler to use legacyflags | https://api.github.com/repos/kubernetes/kubernetes/issues/83161/comments | 7 | 2019-09-26T05:18:15Z | 2020-02-29T13:29:23Z | https://github.com/kubernetes/kubernetes/issues/83161 | 498,663,995 | 83,161 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
Refactor cmd/kube-proxy to use https://github.com/kubernetes-sigs/legacyflag
This is being implemented by #79916.
**Why is this needed**:
This is part of a refactoring initiative run by @kubernetes/wg-component-standard to address the pain-points of backwards-compatible Comp... | Refactor cmd/kube-proxy to use legacyflags | https://api.github.com/repos/kubernetes/kubernetes/issues/83160/comments | 8 | 2019-09-26T05:17:31Z | 2020-02-29T13:29:26Z | https://github.com/kubernetes/kubernetes/issues/83160 | 498,663,807 | 83,160 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
Refactor cmd/kube-controller-manager to use https://github.com/kubernetes-sigs/legacyflag
**Why is this needed**:
This is part of a refactoring initiative run by @kubernetes/wg-component-standard to address the pain-points of backwards-compatible ComponentConfig migration.
... | Refactor cmd/kube-controller-manager to use legacyflags | https://api.github.com/repos/kubernetes/kubernetes/issues/83157/comments | 7 | 2019-09-26T05:07:15Z | 2020-02-29T12:28:31Z | https://github.com/kubernetes/kubernetes/issues/83157 | 498,661,279 | 83,157 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
Refactor cmd/kube-apiserver to use https://github.com/kubernetes-sigs/legacyflag
**Why is this needed**:
This is part of a refactoring initiative run by @kubernetes/wg-component-standard to address the pain-points of backwards-compatible ComponentConfig migration.
/wg comp... | Refactor cmd/kube-apiserver to use legacyflags | https://api.github.com/repos/kubernetes/kubernetes/issues/83156/comments | 8 | 2019-09-26T05:06:33Z | 2020-02-29T12:28:30Z | https://github.com/kubernetes/kubernetes/issues/83156 | 498,661,116 | 83,156 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
Refactor cmd/hyperkube to use https://github.com/kubernetes-sigs/legacyflag
**Why is this needed**:
This is part of a refactoring initiative run by @kubernetes/wg-component-standard to address the pain-points of backwards-compatible ComponentConfig migration.
/wg component... | Refactor cmd/hyperkube to use legacyflags | https://api.github.com/repos/kubernetes/kubernetes/issues/83155/comments | 7 | 2019-09-26T05:05:45Z | 2020-02-29T12:28:29Z | https://github.com/kubernetes/kubernetes/issues/83155 | 498,660,911 | 83,155 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
Refactor cmd/genyaml to use https://github.com/kubernetes-sigs/legacyflag
**Why is this needed**:
This is part of a refactoring initiative run by @kubernetes/wg-component-standard to address the pain-points of backwards-compatible ComponentConfig migration.
/wg component-s... | Refactor cmd/genyaml to use legacyflags | https://api.github.com/repos/kubernetes/kubernetes/issues/83154/comments | 7 | 2019-09-26T05:04:36Z | 2020-02-29T12:28:28Z | https://github.com/kubernetes/kubernetes/issues/83154 | 498,660,629 | 83,154 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
Refactor cmd/genswaggertypedocs to use https://github.com/kubernetes-sigs/legacyflag
**Why is this needed**:
This is part of a refactoring initiative run by @kubernetes/wg-component-standard to address the pain-points of backwards-compatible ComponentConfig migration.
/wg ... | Refactor cmd/genswaggertypedocs to use legacyflags | https://api.github.com/repos/kubernetes/kubernetes/issues/83153/comments | 7 | 2019-09-26T05:03:33Z | 2020-02-29T12:28:27Z | https://github.com/kubernetes/kubernetes/issues/83153 | 498,660,376 | 83,153 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
Refactor cmd/genman to use https://github.com/kubernetes-sigs/legacyflag
**Why is this needed**:
This is part of a refactoring initiative run by @kubernetes/wg-component-standard to address the pain-points of backwards-compatible ComponentConfig migration.
/wg component-st... | Refactor cmd/genman to use legacyflags | https://api.github.com/repos/kubernetes/kubernetes/issues/83152/comments | 7 | 2019-09-26T05:01:59Z | 2020-02-29T12:28:26Z | https://github.com/kubernetes/kubernetes/issues/83152 | 498,659,935 | 83,152 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
Refactor cmd/genkubedocs to use https://github.com/kubernetes-sigs/legacyflag
**Why is this needed**:
This is part of a refactoring initiative run by @kubernetes/wg-component-standard to address the pain-points of backwards-compatible ComponentConfig migration.
/wg compone... | Refactor cmd/genkubedocs to use legacyflags | https://api.github.com/repos/kubernetes/kubernetes/issues/83151/comments | 7 | 2019-09-26T05:00:36Z | 2020-02-29T12:28:26Z | https://github.com/kubernetes/kubernetes/issues/83151 | 498,659,570 | 83,151 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
Refactor cmd/cloud-controller-manager to use https://github.com/kubernetes-sigs/legacyflag
**Why is this needed**:
This is part of a refactoring initiative run by @kubernetes/wg-component-standard to address the pain-points of backwards-compatible ComponentConfig migration.
... | Refactor cmd/cloud-controller-manager to use legacyflags | https://api.github.com/repos/kubernetes/kubernetes/issues/83150/comments | 7 | 2019-09-26T04:59:24Z | 2020-02-29T12:28:25Z | https://github.com/kubernetes/kubernetes/issues/83150 | 498,659,286 | 83,150 |
[
"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 did... | Endpoint object not updated if service port has a name instead of a numeric port | https://api.github.com/repos/kubernetes/kubernetes/issues/83145/comments | 8 | 2019-09-26T03:03:40Z | 2020-03-15T19:27:38Z | https://github.com/kubernetes/kubernetes/issues/83145 | 498,627,778 | 83,145 |
[
"kubernetes",
"kubernetes"
] | https://groups.google.com/d/msg/golang-announce/cszieYyuL9Q/g4Z7pKaqAgAJ
@kubernetes/release-team
@kubernetes/release-engineering
@kubernetes/product-security-committee
/area release-eng
/sig release
/kind bug | Update to use go 1.12.10 on all supported branches | https://api.github.com/repos/kubernetes/kubernetes/issues/83138/comments | 7 | 2019-09-26T00:06:15Z | 2019-09-28T01:39:39Z | https://github.com/kubernetes/kubernetes/issues/83138 | 498,581,253 | 83,138 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
Currently the apiserver has request latencies metrics, which are a histogram of requests to the apiserver. However, these request metrics do not include healthz. While we have recently added the ability to get back health check metrics from the healthz endpoint directly, we shoul... | Health check latency metrics | https://api.github.com/repos/kubernetes/kubernetes/issues/83136/comments | 6 | 2019-09-25T21:22:15Z | 2020-01-22T15:22:45Z | https://github.com/kubernetes/kubernetes/issues/83136 | 498,530,716 | 83,136 |
[
"kubernetes",
"kubernetes"
] | Sorry for this small noise, I was making [this demo](https://twitter.com/devhub_app/status/1177032681638572032?s=20). | Desktop Push Notifications 🎉 | https://api.github.com/repos/kubernetes/kubernetes/issues/83134/comments | 1 | 2019-09-25T20:30:51Z | 2019-09-26T01:32:16Z | https://github.com/kubernetes/kubernetes/issues/83134 | 498,507,886 | 83,134 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
Refactor cluster/images/etcd-version-monitor to use https://github.com/kubernetes-sigs/legacyflag
**Why is this needed**:
This is part of a refactoring initiative run by @kubernetes/wg-component-standard to address the pain-points of backwards-compatible ComponentConfig migrati... | Refactor cluster/images/etcd-version-monitor to use legacyflags | https://api.github.com/repos/kubernetes/kubernetes/issues/83130/comments | 7 | 2019-09-25T19:43:12Z | 2020-02-29T12:28:24Z | https://github.com/kubernetes/kubernetes/issues/83130 | 498,484,655 | 83,130 |
[
"kubernetes",
"kubernetes"
] | As I was reading this code, I looked into bits that try to rollback the mount operation if `SetVolumeOwnership` fails - https://github.com/kubernetes/kubernetes/pull/62486/files
I am not sure if this is the right thing to do because what could happen is, a volume gets mounted but if `SetVolumeOwnership` fails, the ... | CSI driver should not attempt to rollback mount on ownership change failure | https://api.github.com/repos/kubernetes/kubernetes/issues/83129/comments | 8 | 2019-09-25T19:30:16Z | 2021-06-18T18:14:42Z | https://github.com/kubernetes/kubernetes/issues/83129 | 498,479,075 | 83,129 |
[
"kubernetes",
"kubernetes"
] | with kubeadm moving out of tree (parent issue is here https://github.com/kubernetes/kubernetes/issues/78534)
sig release and sig cluster lifecycle need to make some decisions.
- should the kubeadm binary continue to be packaged as part of the node tarballs.
- what to do with some of the deb/rpm packages that kubea... | decisions about the kubeadm release process | https://api.github.com/repos/kubernetes/kubernetes/issues/83127/comments | 6 | 2019-09-25T17:50:12Z | 2019-12-01T18:36:05Z | https://github.com/kubernetes/kubernetes/issues/83127 | 498,432,675 | 83,127 |
[
"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 received an... | Invalid Error: .container.volumes: hostPath type check failed: "not a directory" | https://api.github.com/repos/kubernetes/kubernetes/issues/83125/comments | 24 | 2019-09-25T17:16:34Z | 2023-05-14T01:46:52Z | https://github.com/kubernetes/kubernetes/issues/83125 | 498,417,263 | 83,125 |
[
"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**:
```
(☸ |k... | unable to 'make' in kubernetes build with go version 1.13 | https://api.github.com/repos/kubernetes/kubernetes/issues/83124/comments | 5 | 2019-09-25T17:15:58Z | 2019-09-25T23:17:37Z | https://github.com/kubernetes/kubernetes/issues/83124 | 498,416,971 | 83,124 |
[
"kubernetes",
"kubernetes"
] | **What happened**: https://github.com/kubernetes/kubernetes/blob/327f53ba57aeaa4b7e7c20b1ef98c42b26b7ea7f/staging/src/k8s.io/apiserver/pkg/server/options/server_run_options.go#L218 has a typo, `/readzy` (should be `/readyz`)
This also shows up in the rendered documentation.
**What you expected to happen**:
Docum... | Typo in API server shutdown-delay-duration help | https://api.github.com/repos/kubernetes/kubernetes/issues/83120/comments | 0 | 2019-09-25T17:00:44Z | 2019-10-07T20:43:11Z | https://github.com/kubernetes/kubernetes/issues/83120 | 498,410,205 | 83,120 |
[
"kubernetes",
"kubernetes"
] | Can k8s support getting cluster name, especially when managing multi cluster | Can k8s support getting cluster name | https://api.github.com/repos/kubernetes/kubernetes/issues/83119/comments | 3 | 2019-09-25T16:45:49Z | 2019-10-09T13:16:35Z | https://github.com/kubernetes/kubernetes/issues/83119 | 498,403,266 | 83,119 |
[
"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 run `mak... | sudo --validate failed | https://api.github.com/repos/kubernetes/kubernetes/issues/83115/comments | 2 | 2019-09-25T15:05:44Z | 2019-09-29T23:47:38Z | https://github.com/kubernetes/kubernetes/issues/83115 | 498,347,626 | 83,115 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
After upgrade kubernetes 1.15 --> v1.16, containers are stuck on `Pending`:
```
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled <unknown> ... | CNI is stopped working after upgrade to v1.16 | https://api.github.com/repos/kubernetes/kubernetes/issues/83114/comments | 4 | 2019-09-25T14:43:12Z | 2019-09-25T20:56:45Z | https://github.com/kubernetes/kubernetes/issues/83114 | 498,333,353 | 83,114 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
I would like startup resources requirements to be added. Now we have `request` and `limits` and I want something like `startup-request` for CPU and RAM.
**Why is this needed**:
Some applications u... | Add startup resource requirements | https://api.github.com/repos/kubernetes/kubernetes/issues/83111/comments | 34 | 2019-09-25T14:04:02Z | 2025-02-12T15:36:29Z | https://github.com/kubernetes/kubernetes/issues/83111 | 498,309,050 | 83,111 |
[
"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 pod that ... | Ephemeral storage doesn't account for deleted files with open handles | https://api.github.com/repos/kubernetes/kubernetes/issues/83107/comments | 35 | 2019-09-25T10:44:17Z | 2025-01-15T02:42:12Z | https://github.com/kubernetes/kubernetes/issues/83107 | 498,202,881 | 83,107 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Creation of dynamic volume failed using Kubernetes plugin.
Volume successfully created and mounted when created by heketi-cli. The problem is most probably on Kubernetes side.
**What you expected to happen**:
Dynamic volume created and bound successfully on Kubernetes.
**How to reproduce i... | glusterfs, heketi: failed to create volume: failed to update endpoint | https://api.github.com/repos/kubernetes/kubernetes/issues/83095/comments | 9 | 2019-09-25T02:23:49Z | 2019-09-28T12:18:18Z | https://github.com/kubernetes/kubernetes/issues/83095 | 498,011,474 | 83,095 |
[
"kubernetes",
"kubernetes"
] | kubectl currently can `wait` on `condition` or `delete`
https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/kubectl/pkg/cmd/wait/wait.go#L110-L111
In addition to the above, can we please add the ability to wait on high level summary that we have `phase`?
https://cs.k8s.io/?q=Phase%20.*json%3A%2... | kubectl wait on arbitrary jsonpath | https://api.github.com/repos/kubernetes/kubernetes/issues/83094/comments | 52 | 2019-09-25T01:22:47Z | 2023-09-21T03:53:36Z | https://github.com/kubernetes/kubernetes/issues/83094 | 497,997,846 | 83,094 |
[
"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 pod wi... | Delete pod with subpath volume shows warning while unmount volume files | https://api.github.com/repos/kubernetes/kubernetes/issues/83089/comments | 5 | 2019-09-24T22:11:00Z | 2019-12-27T13:40:28Z | https://github.com/kubernetes/kubernetes/issues/83089 | 497,948,973 | 83,089 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs -->
**Which jobs are failing**:
pull-kubernetes-node-e2e
**Which test(s) are failing**:
The overall stage is failing in this job.
**Since when has it been failing**:
Started failing today at 13 PDT.
**Test... | [Failing Job] pull-kubernetes-node-e2e is failing | https://api.github.com/repos/kubernetes/kubernetes/issues/83086/comments | 7 | 2019-09-24T21:21:48Z | 2019-09-26T22:47:41Z | https://github.com/kubernetes/kubernetes/issues/83086 | 497,930,890 | 83,086 |
[
"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 attemp... | Azure File Premium Persistent Volume fails due to HTTP 400 error | https://api.github.com/repos/kubernetes/kubernetes/issues/83085/comments | 10 | 2019-09-24T20:57:32Z | 2019-10-22T01:34:18Z | https://github.com/kubernetes/kubernetes/issues/83085 | 497,920,543 | 83,085 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Calling 'make' in release-1.14 and release-1.13 failed due to API rule violation
**What you expected to happen**:
make to complete after cloning the rop
**How to reproduce it (as minimally and precisely as possible)**:
`make` without a `make generated_files UPDATE_API_KNOWN_VIOLATIONS=true`
** ... | Make fails from release branches due to api rule violation | https://api.github.com/repos/kubernetes/kubernetes/issues/83083/comments | 4 | 2019-09-24T19:36:14Z | 2019-11-28T15:49:26Z | https://github.com/kubernetes/kubernetes/issues/83083 | 497,884,152 | 83,083 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
When you are going through [feature gates](https://kubernetes.io/docs/reference/command-line-tools-reference/feature-gates/) link it is not clear where and how you can use it.
**Why is this needed**:... | Feature gates documentation improvement | https://api.github.com/repos/kubernetes/kubernetes/issues/83082/comments | 4 | 2019-09-24T19:22:59Z | 2020-02-21T21:29:43Z | https://github.com/kubernetes/kubernetes/issues/83082 | 497,878,297 | 83,082 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
```yaml
apiVersion: batch/v1
kind: Job
metadata:
labels:
job-name: pi-with-ttl
name: pi-with-ttl
namespace: default
spec:
ttlSecondsAfterFinished: 60
template:
metadata:
labels:
job-name: pi-with-ttl
spec:
containers:
- command:
... | TTLAfterFinished feature does not work in 1.15.2 | https://api.github.com/repos/kubernetes/kubernetes/issues/83081/comments | 4 | 2019-09-24T19:16:05Z | 2019-09-27T19:50:00Z | https://github.com/kubernetes/kubernetes/issues/83081 | 497,875,225 | 83,081 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
There are some race conditions in the leader election code present in the `k8s.io/client-go/tools/leaderelection` package. The race is triggered when contexts used with the LeaderElector are canceled either explicitly or by timeouts. This can lead to undefined behavior during runtime.
**What y... | Data race in leader election | https://api.github.com/repos/kubernetes/kubernetes/issues/83078/comments | 5 | 2019-09-24T18:08:44Z | 2020-02-23T22:17:42Z | https://github.com/kubernetes/kubernetes/issues/83078 | 497,843,850 | 83,078 |
[
"kubernetes",
"kubernetes"
] | Did a fresh pull of k/k, set up a GCP project and ran `make test-e2e-node REMOTE=true` per instructions from https://github.com/kubernetes/community/blob/master/contributors/devel/sig-node/e2e-node-tests.md
Received an error that there was an unknown flag: `--test.timeout`.
```
[1] Sep 24 17:55:24.354: INFO: Par... | Unable to run e2e node tests | https://api.github.com/repos/kubernetes/kubernetes/issues/83076/comments | 4 | 2019-09-24T17:59:01Z | 2020-01-22T22:29:18Z | https://github.com/kubernetes/kubernetes/issues/83076 | 497,839,428 | 83,076 |
[
"kubernetes",
"kubernetes"
] | Hi,
ERROR I am trying to fix:
```the HPA was unable to compute the replica count: unable to get metrics for resource memory: unable to fetch metrics from resource metrics API: the server is currently unable to handle the request (get pods.metrics.k8s.io)```
I have gone through various GitHub issues and installa... | HPA throws unable to handle the request (get pods.metrics.k8s.io) error | https://api.github.com/repos/kubernetes/kubernetes/issues/83074/comments | 7 | 2019-09-24T17:46:05Z | 2020-02-23T03:59:40Z | https://github.com/kubernetes/kubernetes/issues/83074 | 497,833,233 | 83,074 |
[
"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**:
Recently we u... | [Azure] EnsureHostInPool TooManyRequests | https://api.github.com/repos/kubernetes/kubernetes/issues/83073/comments | 11 | 2019-09-24T16:24:50Z | 2020-02-03T08:49:52Z | https://github.com/kubernetes/kubernetes/issues/83073 | 497,794,314 | 83,073 |
[
"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 connec... | Windows: Pod's Source IP address is not preserved when connecting to another pod through a Service Cluster IP | https://api.github.com/repos/kubernetes/kubernetes/issues/83072/comments | 5 | 2019-09-24T15:41:40Z | 2020-03-05T18:32:03Z | https://github.com/kubernetes/kubernetes/issues/83072 | 497,770,611 | 83,072 |
[
"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 load b... | [cloudprovider-aws] AWS legacy cloud provider Load Balancer health check can use non-SSL port with SSL health check | https://api.github.com/repos/kubernetes/kubernetes/issues/83070/comments | 18 | 2019-09-24T15:27:11Z | 2021-02-01T23:49:09Z | https://github.com/kubernetes/kubernetes/issues/83070 | 497,762,190 | 83,070 |
[
"kubernetes",
"kubernetes"
] | @kubernetes/sig-node-bugs @kubernetes/sig-api-machinery-bugs
Hi everyone,
During some maintenance of our kubernetes cluster, I have noticed that there are some pods that have orphaned pod containers; meaning their main Docker containers are running, but there is no corresponding pause container.
Some backgrou... | Pause container got deleted but main container in Pod still run | https://api.github.com/repos/kubernetes/kubernetes/issues/83068/comments | 12 | 2019-09-24T14:57:43Z | 2021-06-08T14:15:09Z | https://github.com/kubernetes/kubernetes/issues/83068 | 497,744,385 | 83,068 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened*:
Pods on 10.244... | iptables rules causing network unreachable | https://api.github.com/repos/kubernetes/kubernetes/issues/83063/comments | 31 | 2019-09-24T13:52:59Z | 2020-09-09T05:02:16Z | https://github.com/kubernetes/kubernetes/issues/83063 | 497,703,822 | 83,063 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
As stated by the error we are not able to change a Container entrypoing in the spec :
```
invalid: spec: Forbidden: pod updates may not change fields other than `spec.containers[*].image
```
... | Allow updating the Spec.Container.Command | https://api.github.com/repos/kubernetes/kubernetes/issues/83059/comments | 7 | 2019-09-24T10:20:20Z | 2020-02-23T22:17:41Z | https://github.com/kubernetes/kubernetes/issues/83059 | 497,596,032 | 83,059 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
Running `ku... | Columns missing from kubectl get events watch | https://api.github.com/repos/kubernetes/kubernetes/issues/83056/comments | 3 | 2019-09-24T09:31:40Z | 2019-09-24T11:02:17Z | https://github.com/kubernetes/kubernetes/issues/83056 | 497,570,553 | 83,056 |
[
"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... | How to use pod overhead in runtimeclass | https://api.github.com/repos/kubernetes/kubernetes/issues/83054/comments | 16 | 2019-09-24T09:15:06Z | 2020-02-25T01:44:17Z | https://github.com/kubernetes/kubernetes/issues/83054 | 497,561,589 | 83,054 |
[
"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 found that... | namespaces status is Terminating,but resources is running,Pod status was running | https://api.github.com/repos/kubernetes/kubernetes/issues/83053/comments | 3 | 2019-09-24T09:11:26Z | 2019-09-24T18:15:56Z | https://github.com/kubernetes/kubernetes/issues/83053 | 497,559,649 | 83,053 |
[
"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 no... | When the time of a node changes to earlier, the pod may be "CreateContainerError" and can't recover itself | https://api.github.com/repos/kubernetes/kubernetes/issues/83050/comments | 10 | 2019-09-24T07:59:12Z | 2020-06-04T09:24:26Z | https://github.com/kubernetes/kubernetes/issues/83050 | 497,522,736 | 83,050 |
[
"kubernetes",
"kubernetes"
] | I have a K8s cluster:
```
NAME STATUS ROLES AGE VERSION
master NotReady master 17m v1.16.0
slave1 NotReady <none> 15m v1.16.0
slave2 NotReady <none> 15m v1.16.0
```
Following are the pods. 2 of the coredns pods are in pending state.
```
NAMESPACE NAME ... | Nodes are in <Not-Ready> state with error FailedNodeAllocatableEnforcement error. | https://api.github.com/repos/kubernetes/kubernetes/issues/83048/comments | 4 | 2019-09-24T06:49:55Z | 2019-09-25T22:53:51Z | https://github.com/kubernetes/kubernetes/issues/83048 | 497,492,984 | 83,048 |
[
"kubernetes",
"kubernetes"
] | The k8s node not Running, I found the kubelet service not running.
@/sig Architecture
@/sig Node
@/sig K8s Infra
KB rss:700KB rss_huge:0KB mapped_file:0KB swap:0KB inactive_anon:0KB active_anon:700KB inactive_file:40KB active_file:36KB unevictable:0KB
Sep 20 15:21:56 ida-lj4700146 kernel: [ pid ] uid tgi... | kubelet service not Runing -- kernel: SLUB: Unable to allocate memory on node -1 (gfp=0x20) | https://api.github.com/repos/kubernetes/kubernetes/issues/83044/comments | 11 | 2019-09-24T06:07:34Z | 2020-05-14T07:42:03Z | https://github.com/kubernetes/kubernetes/issues/83044 | 497,476,481 | 83,044 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Tried bringing up DualStack cluster using kubeadm by setting the "IPv6DualStack: true" feature gate. But it is crashing with "panic: assignment to entry in nil map" error
root@maglev-master-10-64-89-173:/etc/kubernetes/maglev/manifests# kubeadm -v=7 init --ignore-preflight-errors=all --config ... | kubeadm crashes when dualstack feature gate is enabled | https://api.github.com/repos/kubernetes/kubernetes/issues/83041/comments | 9 | 2019-09-24T03:39:01Z | 2019-10-01T18:22:15Z | https://github.com/kubernetes/kubernetes/issues/83041 | 497,435,976 | 83,041 |
Subsets and Splits
Unique Owner-Repo Count
Counts the number of unique owner-repos in the dataset, providing a basic understanding of diverse repositories.