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"
] | **What happened**:
On 2019-02-22 https://github.com/kubernetes/kubernetes/pull/74065 was merged with an indication that the mondo test tarball noted as deprecated as per https://git.k8s.io/enhancements/keps/sig-testing/20190118-breaking-apart-the-kubernetes-test-tarball.md. But it did not include a timeline for event... | Deprecated mondo test tarball needs removed | https://api.github.com/repos/kubernetes/kubernetes/issues/82767/comments | 2 | 2019-09-17T00:19:57Z | 2019-09-25T20:52:26Z | https://github.com/kubernetes/kubernetes/issues/82767 | 494,338,530 | 82,767 |
[
"kubernetes",
"kubernetes"
] | **How to reproduce it (as minimally and precisely as possible)**:
- Follow https://github.com/kubernetes/website/blob/dev-1.16/content/en/docs/concepts/services-networking/dual-stack.md
- After that, disable 'IPv6DualStack', i.e., deploy the same cluster without the options followed in the previous step.
- Notice `k... | [v1.16.1] kube-controller-manager v1.16.0-rc.2 panics when restarting after disabling alpha feature 'IPv6DualStack' | https://api.github.com/repos/kubernetes/kubernetes/issues/82765/comments | 22 | 2019-09-16T21:28:11Z | 2020-02-11T17:58:59Z | https://github.com/kubernetes/kubernetes/issues/82765 | 494,286,021 | 82,765 |
[
"kubernetes",
"kubernetes"
] | Hi Team,
I am new to k8s.
i am installed k8s cluster successfully and i am able to access k8s Dashboard.
But i am unable to access other apps from outside.
i am getting below error.
Kindly suggest me.
```
root@k8s-master:~# kubectl get svc --all-namespaces
NAMESPACE NAME TY... | Nameserver limits were exceeded, some nameservers have been omitted, the applied nameserver | https://api.github.com/repos/kubernetes/kubernetes/issues/82756/comments | 28 | 2019-09-16T14:39:26Z | 2024-08-08T19:56:54Z | https://github.com/kubernetes/kubernetes/issues/82756 | 494,093,323 | 82,756 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
During I tr... | Dynamically created pv may be bound to wrong pvc | https://api.github.com/repos/kubernetes/kubernetes/issues/82755/comments | 10 | 2019-09-16T14:20:11Z | 2020-02-17T13:49:39Z | https://github.com/kubernetes/kubernetes/issues/82755 | 494,081,663 | 82,755 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
Pod sandbox b... | Pod sandbox be killed and re-created when pull image failed | https://api.github.com/repos/kubernetes/kubernetes/issues/82754/comments | 17 | 2019-09-16T13:39:40Z | 2020-02-17T03:39:47Z | https://github.com/kubernetes/kubernetes/issues/82754 | 494,056,266 | 82,754 |
[
"kubernetes",
"kubernetes"
] | **This is not a _duplicate_ of #37957, but rather a "the problem seems to have re-appeared."**
**What happened**:
I have a weekly cronjob that last week failed in a way that made me delete the spawned job. The specific failure was caused by a bug in our code, and as such is not a problem for Kubernetes. This week... | CronJob reports active job even when that job was deleted | https://api.github.com/repos/kubernetes/kubernetes/issues/82753/comments | 11 | 2019-09-16T13:06:04Z | 2020-03-06T15:54:22Z | https://github.com/kubernetes/kubernetes/issues/82753 | 494,037,807 | 82,753 |
[
"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-13, green otherwise
**Testgrid link**:
https://k8s-testgrid.appspot.com/sig-scalability-gce#gce-master-scale-performance
**Reason for failure**:
> W0913 19:... | [Failing Test] GCE 5K Performance - transient etcd failures | https://api.github.com/repos/kubernetes/kubernetes/issues/82751/comments | 3 | 2019-09-16T12:25:39Z | 2019-10-11T12:39:59Z | https://github.com/kubernetes/kubernetes/issues/82751 | 494,017,276 | 82,751 |
[
"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**:
StartupProbe [Serial] [Disruptive] [NodeFeature:StartupProbe]
**Since when has it been failing**:
**Testg... | [Failing Test] [sig-node] startup_probe_test.go | https://api.github.com/repos/kubernetes/kubernetes/issues/82747/comments | 6 | 2019-09-16T09:55:58Z | 2019-12-10T17:43:11Z | https://github.com/kubernetes/kubernetes/issues/82747 | 493,951,758 | 82,747 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
With Statefullsets, podManagementPolicy=OrderedReady should garantee that PODs are never started in parallel.
**Why is this needed**:
When PODs in a Statefullset fail in an certain order or are delete... | Have podManagementPolicy=OrderedReady garantee that restarts are executed in series | https://api.github.com/repos/kubernetes/kubernetes/issues/82746/comments | 5 | 2019-09-16T09:42:51Z | 2020-03-15T19:27:39Z | https://github.com/kubernetes/kubernetes/issues/82746 | 493,945,469 | 82,746 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**: Have an option to pass in cluster service IP for the apiserver. Currently the first IP of the ServiceClusterIPRange is used as the cluster IP for the apiserver where ServiceClusterIPRange can be changed us... | Have option to pass in cluster service IP for apiserver | https://api.github.com/repos/kubernetes/kubernetes/issues/82743/comments | 26 | 2019-09-16T07:44:58Z | 2020-12-28T20:51:13Z | https://github.com/kubernetes/kubernetes/issues/82743 | 493,894,267 | 82,743 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
There are two Pods behind a K8s clusterIP service. It's expected only one Pod to carry the traffic. Hence label corresponding to the "selector" of the service is attached to first Pod. There are two client Pods scheduled on different worker nodes of the K8s cluster. TCP connection from those two c... | conntrack shows wrong IP after changing the backend Pod of K8s ClusterIP service | https://api.github.com/repos/kubernetes/kubernetes/issues/82727/comments | 4 | 2019-09-15T09:34:48Z | 2021-12-04T14:46:13Z | https://github.com/kubernetes/kubernetes/issues/82727 | 493,716,125 | 82,727 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
@kubernetes/sig-cli-feature-requests
**What would you like to be added**:
Support for passing environment variables in `create secret` command:
`kubectl create secret generic mysecret --from-literal=username=sudouser --from-literal=passw... | Environment variables support - kubectl create secret --from-literal | https://api.github.com/repos/kubernetes/kubernetes/issues/82724/comments | 8 | 2019-09-14T19:45:58Z | 2020-02-22T23:55:43Z | https://github.com/kubernetes/kubernetes/issues/82724 | 493,659,619 | 82,724 |
[
"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**:
Most of the... | kubectl run change default restart policy due to generator depreciation | https://api.github.com/repos/kubernetes/kubernetes/issues/82723/comments | 6 | 2019-09-14T18:28:43Z | 2020-04-06T02:45:50Z | https://github.com/kubernetes/kubernetes/issues/82723 | 493,652,651 | 82,723 |
[
"kubernetes",
"kubernetes"
] |
**What would you like to be added**:
Write equivalent Plugins for all currently supported priorities and predicates. Those plugins should only call the existing predicates/priorities logic
/sig scheduling
/assign | Migrate Predicates to plugins | https://api.github.com/repos/kubernetes/kubernetes/issues/82715/comments | 4 | 2019-09-14T03:24:42Z | 2019-10-10T14:00:30Z | https://github.com/kubernetes/kubernetes/issues/82715 | 493,577,262 | 82,715 |
[
"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... | should not delete an azure disk when that disk is being attached | https://api.github.com/repos/kubernetes/kubernetes/issues/82714/comments | 0 | 2019-09-14T02:06:15Z | 2019-11-09T02:44:48Z | https://github.com/kubernetes/kubernetes/issues/82714 | 493,571,083 | 82,714 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
The `readyz` ... | Readyz and livez do not match healthz | https://api.github.com/repos/kubernetes/kubernetes/issues/82712/comments | 2 | 2019-09-13T21:06:19Z | 2019-09-16T15:16:41Z | https://github.com/kubernetes/kubernetes/issues/82712 | 493,516,962 | 82,712 |
[
"kubernetes",
"kubernetes"
] | Windows + containerd
When creating a pod, the expectation is that all containers have the hostname properly set to the name of the pod.
However when using Windows nodes + containerd as a runtime, only the pause container in the pod has the hostname properly set, not the work container.
**How to reproduce it (... | Wrong hostname in pod work container for Windows nodes with containerd runtime | https://api.github.com/repos/kubernetes/kubernetes/issues/82711/comments | 20 | 2019-09-13T21:02:56Z | 2020-02-24T00:19:40Z | https://github.com/kubernetes/kubernetes/issues/82711 | 493,515,852 | 82,711 |
[
"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 using cA... | cAdvisor network metrics missing with cri-o | https://api.github.com/repos/kubernetes/kubernetes/issues/82709/comments | 2 | 2019-09-13T20:04:53Z | 2019-09-13T20:26:14Z | https://github.com/kubernetes/kubernetes/issues/82709 | 493,495,743 | 82,709 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
A way to configure future default plugins, and translation between [Predicate/Priority Policy](https://github.com/kubernetes/kubernetes/blob/926bd4ddbbee7afbb52e15afd890fccb6e1e69cf/pkg/scheduler/api/types.go#L49-L57) and [component config Plugins](https://github.com/kubernetes/kub... | [migration] Translate predicates/priorities config to Plugin configuration | https://api.github.com/repos/kubernetes/kubernetes/issues/82708/comments | 5 | 2019-09-13T16:49:05Z | 2019-10-07T00:44:45Z | https://github.com/kubernetes/kubernetes/issues/82708 | 493,422,899 | 82,708 |
[
"kubernetes",
"kubernetes"
] |
**What happened**:
When I run kubectl kustomize <dire> the result is different between runs. I have the problem right now with services. The base service.yaml has no node-ports assigned but the overlay "development" does. When I run kubectl kustomize development I sometimes get the nodeports added, sometimes not... | kubectl kustomize gives random result | https://api.github.com/repos/kubernetes/kubernetes/issues/82706/comments | 7 | 2019-09-13T15:34:22Z | 2019-09-16T08:06:41Z | https://github.com/kubernetes/kubernetes/issues/82706 | 493,390,627 | 82,706 |
[
"kubernetes",
"kubernetes"
] | /sig scheduling
/cc @k82cn @ahg-g
/assign
This feature has been in Beta since 1.12, we can now graduate it to GA in 1.17.
- [x] KEP for graduating schedule daemonset pods https://github.com/kubernetes/enhancements/pull/1299
- [x] Performance concern before the graduation of ScheduleDaemonSetPods #83829
- [x... | Graduate ScheduleDaemonSet to GA | https://api.github.com/repos/kubernetes/kubernetes/issues/82702/comments | 6 | 2019-09-13T14:58:53Z | 2020-02-04T11:51:05Z | https://github.com/kubernetes/kubernetes/issues/82702 | 493,372,474 | 82,702 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
When running the command "kubectl get all -A" no ingress resources are shown.
**Why is this needed**: Particularly new users of kubernetes are confused why a valid resource type is not shown in a command that has a flag called -all. All should encompass all resource types.
| Kubectl get all does not include ingress resources | https://api.github.com/repos/kubernetes/kubernetes/issues/82701/comments | 4 | 2019-09-13T13:49:30Z | 2019-09-13T14:43:51Z | https://github.com/kubernetes/kubernetes/issues/82701 | 493,336,317 | 82,701 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs -->
**Which jobs are failing**: ci-kubernetes-e2e-gce-scale-correctness
**Which test(s) are failing**: [sig-network] Loadbalancing: L7 [Slow] Nginx should conform to Ingress spec
**Since when has it been failing... | [Failing Test] ci-kubernetes-e2e-gce-scale-correctness | https://api.github.com/repos/kubernetes/kubernetes/issues/82695/comments | 8 | 2019-09-13T07:46:01Z | 2019-10-07T09:50:59Z | https://github.com/kubernetes/kubernetes/issues/82695 | 493,183,008 | 82,695 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs -->
**Which jobs are failing**:
pull-kubernetes-integration
**Which test(s) are failing**:
https://prow.k8s.io/view/gcs/kubernetes-jenkins/pr-logs/directory/pull-kubernetes-integration/1172176898202013696
... | flake: TestWebhookAdmission | https://api.github.com/repos/kubernetes/kubernetes/issues/82694/comments | 3 | 2019-09-13T06:54:12Z | 2019-11-08T14:04:28Z | https://github.com/kubernetes/kubernetes/issues/82694 | 493,165,552 | 82,694 |
[
"kubernetes",
"kubernetes"
] | **Which jobs are failing**:
**Which test(s) are failing**:
https://prow.k8s.io/view/gcs/kubernetes-jenkins/pr-logs/directory/pull-kubernetes-integration/1172262471734398978
https://prow.k8s.io/view/gcs/kubernetes-jenkins/pr-logs/directory/pull-kubernetes-integration/1172263738850414593
https://prow.k8s.io/v... | flake: TestWebhookReinvocationPolicy | https://api.github.com/repos/kubernetes/kubernetes/issues/82693/comments | 5 | 2019-09-13T06:52:16Z | 2019-09-20T08:33:21Z | https://github.com/kubernetes/kubernetes/issues/82693 | 493,164,940 | 82,693 |
[
"kubernetes",
"kubernetes"
] | **Which jobs are failing**:
**Which test(s) are failing**:
```
--- FAIL: TestAggregatedAPIServer (13.36s)
apiserver_test.go:222: open /tmp/test-integration-wardle-server747867932/apiserver.crt: no such file or directory
apiserver_test.go:222: open /tmp/test-integration-wardle-server747867932/apiserver.... | flake: TestAggregatedAPIServer: Discovery call expected to return failed unavailable service | https://api.github.com/repos/kubernetes/kubernetes/issues/82692/comments | 4 | 2019-09-13T06:47:57Z | 2019-12-10T17:48:58Z | https://github.com/kubernetes/kubernetes/issues/82692 | 493,163,606 | 82,692 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
`RunAsUsername` was added for Windows and is passing tests in Kubernetes 1.16 with Docker. In ContainerD, it seems to be ignored since a container can start with an invalid username. Setting a valid username is ignored too - the container default user is still used.
_[sig-windows] [Feature:Window... | RunAsUsername does not work with ContainerD on Windows | https://api.github.com/repos/kubernetes/kubernetes/issues/82679/comments | 8 | 2019-09-12T22:41:04Z | 2019-12-05T23:55:02Z | https://github.com/kubernetes/kubernetes/issues/82679 | 493,061,709 | 82,679 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs -->
**Which jobs are failing**:
pull-kubernetes-kubemark-e2e-gce-big
**Since when has it been failing**:
As per triage, https://storage.googleapis.com/k8s-gubernator/triage/index.html?ci=0&pr=1&job=pull-kuberne... | [Failing Job] pull-kubernetes-kubemark-e2e-gce-big | https://api.github.com/repos/kubernetes/kubernetes/issues/82676/comments | 9 | 2019-09-12T22:25:22Z | 2019-09-16T00:46:34Z | https://github.com/kubernetes/kubernetes/issues/82676 | 493,057,354 | 82,676 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
When we run csi hostpath driver e2e tests on a multi-node cluster some tests failed because they assume that volumes are node independent but this is not the case for some drivers like hostpath.
Related PR; https://github.com/kubernetes-csi/external-provisioner/pull/339
**What you expected to ... | Skip e2e tests that run on multi node cluster and require node independent volume for the drivers that does not support node independent volumes | https://api.github.com/repos/kubernetes/kubernetes/issues/82675/comments | 0 | 2019-09-12T22:19:22Z | 2019-09-13T21:18:30Z | https://github.com/kubernetes/kubernetes/issues/82675 | 493,055,688 | 82,675 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
In 1.16 CI testing we came across integration tests failing on liveness and readiness probes with payloads of 50KB (the max is 10KB).
```
Warning Unhealthy 94s (x9 over 2m54s) kubelet, [snip].ec2.internal Liveness probe errored: the read limit is reached
Warning Unhealthy 86s (x12 ov... | Regression in Kubelet Status Calls | https://api.github.com/repos/kubernetes/kubernetes/issues/82671/comments | 5 | 2019-09-12T21:02:03Z | 2019-09-13T15:27:41Z | https://github.com/kubernetes/kubernetes/issues/82671 | 493,028,134 | 82,671 |
[
"kubernetes",
"kubernetes"
] | Right now only real drivers are supported in the translation library, this makes unit testing especially difficult. If we add a mock driver we should be able to unit test external provisioner (and maybe other components) better | Add Mock Driver to csi translation library to support unit testing | https://api.github.com/repos/kubernetes/kubernetes/issues/82670/comments | 2 | 2019-09-12T20:53:53Z | 2019-09-29T17:11:38Z | https://github.com/kubernetes/kubernetes/issues/82670 | 493,024,500 | 82,670 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
Ability to inject additional Container to a running K8s POD
**Why is this needed**:
This is needed to define/monitor certain aspects of the running POD which can be turned on/off on demand basis. | Injecting Additional Container to a Running POD | https://api.github.com/repos/kubernetes/kubernetes/issues/82668/comments | 14 | 2019-09-12T20:19:14Z | 2020-08-02T04:49:56Z | https://github.com/kubernetes/kubernetes/issues/82668 | 493,009,162 | 82,668 |
[
"kubernetes",
"kubernetes"
] | Now that the scheduler is migrated to new Events API, we can migrate the kubelet to emit events against the new API
This is part of #76674
List of the files that needs to be migrated:
```
./pkg/kubelet/kubelet.go
./pkg/kubelet/prober/prober.go
./pkg/kubelet/kubelet_pods.go
./pkg/kubelet/config/config.go
./p... | Migrate kubelet to use v1beta1 Events | https://api.github.com/repos/kubernetes/kubernetes/issues/82665/comments | 5 | 2019-09-12T19:38:07Z | 2021-06-25T18:13:37Z | https://github.com/kubernetes/kubernetes/issues/82665 | 492,991,783 | 82,665 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Ran a conformance test run (using Sonobuoy) on v1.16.0.beta.3
One of the taint based tests added a NoExecute taint to a node which evicted all workloads including the Sonobuoy workload itself. If this had been a prod workload, numerous prod workloads could have been impacted.
**What you expect... | Some taint tests will evict non-test workloads as a result and missing [Disruptive] | https://api.github.com/repos/kubernetes/kubernetes/issues/82663/comments | 2 | 2019-09-12T19:36:47Z | 2019-09-25T18:06:29Z | https://github.com/kubernetes/kubernetes/issues/82663 | 492,991,193 | 82,663 |
[
"kubernetes",
"kubernetes"
] | Raising per discussion in sig-arch on Sep 12. What are the obstacles here? How can we make progress? | Drive CronJob from Beta to GA | https://api.github.com/repos/kubernetes/kubernetes/issues/82659/comments | 17 | 2019-09-12T18:49:19Z | 2021-06-02T13:48:45Z | https://github.com/kubernetes/kubernetes/issues/82659 | 492,970,399 | 82,659 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
When running `kubectl drain node --dry-run` the pods to be deleted and any blockers should be listed.
**Why is this needed**:
To make more informed `kubectl drain node` calls. | kubectl drain node --dry-run should list pods, warnings, errors | https://api.github.com/repos/kubernetes/kubernetes/issues/82657/comments | 2 | 2019-09-12T18:39:12Z | 2019-09-14T15:01:45Z | https://github.com/kubernetes/kubernetes/issues/82657 | 492,965,998 | 82,657 |
[
"kubernetes",
"kubernetes"
] | Filing issue for the discussion I brought up in SIG scalability meeting today, as I couldn't find one for it already.
**Background**:
Currently all our informers, which use reflectors underneath, list from apiserver's watch cache. This was a decision made quite some time ago to use watch cache instead of etcd - to ... | Reconsider using etcd+chunking for reflector lists | https://api.github.com/repos/kubernetes/kubernetes/issues/82655/comments | 11 | 2019-09-12T18:20:38Z | 2022-01-31T08:39:38Z | https://github.com/kubernetes/kubernetes/issues/82655 | 492,957,872 | 82,655 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
1. Created a non-structural CRD
```yaml
apiVersion: apiextensions.k8s.io/v1beta1
kind: CustomResourceDefinition
metadata:
name: examples.example.com
spec:
conversion:
strategy: None
group: example.com
names:
kind: Example
listKind: ExampleList
plural: example... | 1.16 publishes openapi for non-structural schemas | https://api.github.com/repos/kubernetes/kubernetes/issues/82651/comments | 1 | 2019-09-12T17:05:59Z | 2019-09-13T15:52:02Z | https://github.com/kubernetes/kubernetes/issues/82651 | 492,926,019 | 82,651 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
Apply the following security best practices for dashboard add-on:
Low hanging fruit:
- [x] Run as non-root (& disallow privilege escalation)
- [x] Run with the default seccomp profile (i.e. `runt... | Harden dashboard addon | https://api.github.com/repos/kubernetes/kubernetes/issues/82647/comments | 29 | 2019-09-12T15:17:34Z | 2022-08-24T18:30:47Z | https://github.com/kubernetes/kubernetes/issues/82647 | 492,872,492 | 82,647 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
a validation error is returned when trying to parse a liveness probe port represented as a string.
exact error:
```
spec.containers[1].livenessProbe.httpGet.port: Invalid value: \"48888\": must contain at least one letter or number (a-z, 0-9)
```
**What you expected to happen**:
it should be... | liveness probe validation error when port represented as string (golang lib) | https://api.github.com/repos/kubernetes/kubernetes/issues/82642/comments | 4 | 2019-09-12T14:26:19Z | 2019-09-12T16:45:51Z | https://github.com/kubernetes/kubernetes/issues/82642 | 492,841,083 | 82,642 |
[
"kubernetes",
"kubernetes"
] | follow the same pattern that we updated to 3.3.15:
- client side changes needs to be vendored in (similar to https://github.com/kubernetes/kubernetes/pull/81434)
- update default etcd server (similar to https://github.com/kubernetes/kubernetes/pull/82199) | Update to etcd 3.4 in Kubernetes 1.17 release | https://api.github.com/repos/kubernetes/kubernetes/issues/82641/comments | 12 | 2019-09-12T14:25:24Z | 2019-10-30T09:30:53Z | https://github.com/kubernetes/kubernetes/issues/82641 | 492,840,498 | 82,641 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
Can't downgrade... | Can't downgrade number of worker nodes on VMWARE cloud provider. | https://api.github.com/repos/kubernetes/kubernetes/issues/82636/comments | 7 | 2019-09-12T12:33:52Z | 2020-02-09T16:44:47Z | https://github.com/kubernetes/kubernetes/issues/82636 | 492,776,399 | 82,636 |
[
"kubernetes",
"kubernetes"
] | This feature has been in Beta since 1.12, we can now graduate it to GA.
/sig scheduling
/cc @k82cn | Graduate TaintNodesByCondition to GA
| https://api.github.com/repos/kubernetes/kubernetes/issues/82635/comments | 5 | 2019-09-12T12:19:40Z | 2019-11-08T13:10:14Z | https://github.com/kubernetes/kubernetes/issues/82635 | 492,769,553 | 82,635 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
Containerd ... | Containerd doesn't report additional POD IPs | https://api.github.com/repos/kubernetes/kubernetes/issues/82634/comments | 7 | 2019-09-12T12:14:39Z | 2019-09-20T04:53:09Z | https://github.com/kubernetes/kubernetes/issues/82634 | 492,767,259 | 82,634 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
We stored lots of secrets into etcd / k8s (about 750.000) and it is very slow to fetch them. A simple "kubectl get all secrets" takes up to 6 minutes! Also, we see lots of errors during the request:
**etcd**
```
ERROR: 2019/09/12 10:45:27 grpc: server failed to encode response: rpc error: ... | apiserver received an error that is not an metav1.Status: grpc: message too large | https://api.github.com/repos/kubernetes/kubernetes/issues/82633/comments | 9 | 2019-09-12T12:04:16Z | 2019-10-14T14:02:47Z | https://github.com/kubernetes/kubernetes/issues/82633 | 492,762,418 | 82,633 |
[
"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**:
Logs from pod... | Pod logs arriving asynchronously | https://api.github.com/repos/kubernetes/kubernetes/issues/82628/comments | 8 | 2019-09-12T09:15:57Z | 2020-02-09T20:48:46Z | https://github.com/kubernetes/kubernetes/issues/82628 | 492,683,958 | 82,628 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
Apply security best practices for both kube-dns and core-dns.
### kube-dns
Low hanging fruit:
- [x] Run as non-root & disallow privilege escalation
- [x] Run with the default seccomp profile (i.e... | Harden Addons: Kube-dns and Core-Dns | https://api.github.com/repos/kubernetes/kubernetes/issues/82623/comments | 1 | 2019-09-12T07:41:48Z | 2019-09-25T18:05:00Z | https://github.com/kubernetes/kubernetes/issues/82623 | 492,639,438 | 82,623 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
If a node with ... | Azure disk detach fails if node no longer exists | https://api.github.com/repos/kubernetes/kubernetes/issues/82617/comments | 0 | 2019-09-12T07:19:43Z | 2019-09-14T09:46:41Z | https://github.com/kubernetes/kubernetes/issues/82617 | 492,630,206 | 82,617 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
I create a ... | The statefulset have duplicate revision after resource was updated. | https://api.github.com/repos/kubernetes/kubernetes/issues/82613/comments | 5 | 2019-09-12T06:17:04Z | 2019-09-26T03:09:05Z | https://github.com/kubernetes/kubernetes/issues/82613 | 492,607,082 | 82,613 |
[
"kubernetes",
"kubernetes"
] | <!--
STOP -- PLEASE READ!
GitHub is not the right place for support requests.
If you're looking for help, check [Stack Overflow](https://stackoverflow.com/questions/tagged/kubernetes) and the [troubleshooting guide](https://kubernetes.io/docs/tasks/debug-application-cluster/troubleshooting/).
You can also pos... | can not get the statefulset rollout history details | https://api.github.com/repos/kubernetes/kubernetes/issues/82612/comments | 19 | 2019-09-12T06:12:25Z | 2020-09-24T16:43:50Z | https://github.com/kubernetes/kubernetes/issues/82612 | 492,605,540 | 82,612 |
[
"kubernetes",
"kubernetes"
] | /sig node
/kind feature
<!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
add pod UID, NameSpace and Name to deviceplugin AllocateRequest
for API Specification:
```
message AllocateRequest {
repeated string devicesIDs = 1;
string podUI... | add pod information to deviceplugin allocate request | https://api.github.com/repos/kubernetes/kubernetes/issues/82606/comments | 3 | 2019-09-12T03:20:38Z | 2019-12-11T08:31:30Z | https://github.com/kubernetes/kubernetes/issues/82606 | 492,563,269 | 82,606 |
[
"kubernetes",
"kubernetes"
] | When I make test, It just can not pass.
Some of the error message is:
```
--- FAIL: TestEncryptionProviderFlag/ENCRYPTION_PROVIDER_CONFIG_is_set (0.09s)
configure_helper_test.go:133: Start kubernetes api-server
WARNING: ALL of ETCD_APISERVER_CA_KEY, ETCD_APISERVER_CA_CERT, ETCD_APISERVER_SE... | local: -n: invalid option when make test "kubernetes 1.16". Requires bash version >= 4.3 | https://api.github.com/repos/kubernetes/kubernetes/issues/82605/comments | 6 | 2019-09-12T02:56:44Z | 2020-02-21T22:34:56Z | https://github.com/kubernetes/kubernetes/issues/82605 | 492,559,612 | 82,605 |
[
"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 clone ... | `make test` failed | https://api.github.com/repos/kubernetes/kubernetes/issues/82604/comments | 5 | 2019-09-12T02:15:35Z | 2020-02-09T04:32:49Z | https://github.com/kubernetes/kubernetes/issues/82604 | 492,548,228 | 82,604 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
Code for hand... | AWS: Network Load Balancer ignores annotations upon creation | https://api.github.com/repos/kubernetes/kubernetes/issues/82595/comments | 20 | 2019-09-11T18:01:07Z | 2020-11-07T03:46:02Z | https://github.com/kubernetes/kubernetes/issues/82595 | 492,384,699 | 82,595 |
[
"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**:
CoreDNS add-o... | kubeadm: CoreDNS creation fails | https://api.github.com/repos/kubernetes/kubernetes/issues/82592/comments | 20 | 2019-09-11T16:37:40Z | 2019-12-13T14:36:14Z | https://github.com/kubernetes/kubernetes/issues/82592 | 492,346,264 | 82,592 |
[
"kubernetes",
"kubernetes"
] | The kube-aggregator uses Golang's reverse proxy code to forward requests to aggregated API server. Whenever such a connection is uncleanly closed, the Golang code panics. The panic is passed through the handler chain down to the panic handler which prints it.
This leads to main panic stack traces in the kube-apiserv... | Cut off connections from kube-aggregator to aggregated apiserver lead to panic in the logs | https://api.github.com/repos/kubernetes/kubernetes/issues/82591/comments | 3 | 2019-09-11T15:43:51Z | 2019-09-12T05:54:00Z | https://github.com/kubernetes/kubernetes/issues/82591 | 492,319,088 | 82,591 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
I like to use `k8s.io/kubernetes/pkg/registry/core/service/portallocator` in my project but Go modules cannot add Kubernetes core as dependency without pinning versions.
**Why is this needed**:
Port allocations may be a common need in custom controllers and Kubernetes already h... | Expose portallocator as a component | https://api.github.com/repos/kubernetes/kubernetes/issues/82590/comments | 15 | 2019-09-11T15:33:51Z | 2020-03-12T15:13:16Z | https://github.com/kubernetes/kubernetes/issues/82590 | 492,313,694 | 82,590 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Running `hack/local-up-cluster.sh`, kube-proxy never succeeds calling `iptables-restore --noflush --counters`:
```
I0911 14:30:08.104508 1022 proxier.go:1420] Restoring iptables rules: *filter
:KUBE-SERVICES - [0:0]
:KUBE-EXTERNAL-SERVICES - [0:0]
:KUBE-FORWARD - [0:0]
-A KUBE-FORWARD -m ... | kube-proxy fails to restore iptable rules | https://api.github.com/repos/kubernetes/kubernetes/issues/82587/comments | 7 | 2019-09-11T14:49:50Z | 2019-09-20T21:00:02Z | https://github.com/kubernetes/kubernetes/issues/82587 | 492,287,458 | 82,587 |
[
"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**:
Hostpath vo... | HostPath: pvc having selector bounded with unmatched pv label | https://api.github.com/repos/kubernetes/kubernetes/issues/82584/comments | 6 | 2019-09-11T13:47:18Z | 2020-02-08T20:24:45Z | https://github.com/kubernetes/kubernetes/issues/82584 | 492,249,421 | 82,584 |
[
"kubernetes",
"kubernetes"
] | **Is this a BUG REPORT or FEATURE REQUEST?**:
/kind api-change
/sig storage
/sig node
/milestone v1.17
**Description:**
This is the issue that is used to upgrade VolumeSubpathEnvExpansion feature gate to GA.
Related Issues:
Beta Upgrade: https://github.com/kubernetes/kubernetes/pull/76546
Feature Request: ... | Promote VolumeSubpathEnvExpansion to GA | https://api.github.com/repos/kubernetes/kubernetes/issues/82577/comments | 9 | 2019-09-11T11:55:59Z | 2019-12-13T11:32:58Z | https://github.com/kubernetes/kubernetes/issues/82577 | 492,191,292 | 82,577 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Mounting `projected` `serviceAccountTokens` into a container always sets the mode of the mounted token files to `0600`. This is hardcoded in the source code:
https://github.com/kubernetes/kubernetes/blob/cf76868b3430be015cc1e8443a216bf863a9b9f7/pkg/volume/projected/projected.go#L357
**What you... | Projected serviceAccountToken has mode of mounted file hardcoded to 0600 | https://api.github.com/repos/kubernetes/kubernetes/issues/82573/comments | 14 | 2019-09-11T09:28:13Z | 2020-09-16T18:59:23Z | https://github.com/kubernetes/kubernetes/issues/82573 | 492,120,759 | 82,573 |
[
"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 deployme... | cleanupDeployment should sort ReplicaSet with revision rather than createTimeStamp | https://api.github.com/repos/kubernetes/kubernetes/issues/82570/comments | 14 | 2019-09-11T08:37:38Z | 2021-01-19T09:15:19Z | https://github.com/kubernetes/kubernetes/issues/82570 | 492,095,346 | 82,570 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs -->
**Which jobs are failing**:
pull-kubernetes-verify
pull-kubernetes-e2e-gce
**Which test(s) are failing**:
pull-kubernetes-verify
pull-kubernetes-e2e-gce
**Since when has it been failing**:
Unexpecte... | Help me confirm why it test failed | https://api.github.com/repos/kubernetes/kubernetes/issues/82566/comments | 3 | 2019-09-11T06:02:54Z | 2019-09-11T17:05:46Z | https://github.com/kubernetes/kubernetes/issues/82566 | 492,034,520 | 82,566 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs -->
**Which jobs are failing**:
pull-kubernetes-verify
pull-kubernetes-e2e-gce
**Which test(s) are failing**:
pull-kubernetes-verify
pull-kubernetes-e2e-gce
**Since when has it been failing**:
Unexpecte... | Help me confirm why it test failed | https://api.github.com/repos/kubernetes/kubernetes/issues/82564/comments | 5 | 2019-09-11T05:12:42Z | 2019-09-11T05:59:16Z | https://github.com/kubernetes/kubernetes/issues/82564 | 492,020,567 | 82,564 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
During developing our CSI driver/provisioner, we found if create a PV using fieldSelector to match Node, then the kubelet will failed to setup Volume with the error `No matching NodeSelectorTerms`.
The error code exist in: https://github.com/kubernetes/kubernetes/blob/master/pkg/volume/util/uti... | kubelet check PV nodeAffinity failed if PV use fieldSelector | https://api.github.com/repos/kubernetes/kubernetes/issues/82562/comments | 5 | 2019-09-11T04:30:44Z | 2019-09-11T05:40:45Z | https://github.com/kubernetes/kubernetes/issues/82562 | 492,011,008 | 82,562 |
[
"kubernetes",
"kubernetes"
] | Under Umbrella issue: #82312
hostPID will be a bit different on Windows nodes.
/area conformance
/sig testing | PodSpec endpoints - hostPID test | https://api.github.com/repos/kubernetes/kubernetes/issues/82547/comments | 6 | 2019-09-10T21:05:29Z | 2020-02-14T04:29:34Z | https://github.com/kubernetes/kubernetes/issues/82547 | 491,898,022 | 82,547 |
[
"kubernetes",
"kubernetes"
] | Umbrella issue: #82312
/area conformance
/sig testing | PodSpec - new priorityClassName test | https://api.github.com/repos/kubernetes/kubernetes/issues/82545/comments | 5 | 2019-09-10T20:58:36Z | 2020-02-11T20:55:54Z | https://github.com/kubernetes/kubernetes/issues/82545 | 491,894,719 | 82,545 |
[
"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**:
Node failed t... | Error when joining the node to the cluster, when using both 1GB and 2MB huge-page sizes are enabled on the node | https://api.github.com/repos/kubernetes/kubernetes/issues/82544/comments | 5 | 2019-09-10T20:50:12Z | 2020-02-10T17:08:52Z | https://github.com/kubernetes/kubernetes/issues/82544 | 491,890,697 | 82,544 |
[
"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**:
Last week we'... | Cronjobs stopped starting after Kube upgrade from `1.13` to `1.14` | https://api.github.com/repos/kubernetes/kubernetes/issues/82539/comments | 6 | 2019-09-10T17:50:35Z | 2019-09-12T13:21:34Z | https://github.com/kubernetes/kubernetes/issues/82539 | 491,813,294 | 82,539 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs -->
**Which jobs are failing**:
ci-kubernetes-e2e-gce-scale-performance
**Which test(s) are failing**:
testing/load/config.yaml
ClusterLoaderV2
**Since when has it been failing**:
09/09/2019
**Testgrid... | [Failing Test] testing/load/config.yaml | https://api.github.com/repos/kubernetes/kubernetes/issues/82538/comments | 7 | 2019-09-10T16:08:08Z | 2019-09-12T13:42:54Z | https://github.com/kubernetes/kubernetes/issues/82538 | 491,767,822 | 82,538 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
I used kubectl to apply an Ingress resource with an annotation, whose value was accidentally an integer (instead of a string). The Kubernetes API server accepted the resource, but silently removed all annotations (also valid ones).
**What you expected to happen**:
I expected, that the server... | Unexpected handling of invalid ingress annotation | https://api.github.com/repos/kubernetes/kubernetes/issues/82536/comments | 3 | 2019-09-10T15:02:10Z | 2019-09-11T04:43:29Z | https://github.com/kubernetes/kubernetes/issues/82536 | 491,730,639 | 82,536 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
When dockers are running on the server, the following errors are generated by dmesg.
```
[319003.331580] SLUB: Unable to allocate memory on node -1 (gfp=0x2088020)
[319003.331587] cache: mnt_cache(9946:ea4c61d01895b46bf04a9b8c54602a4a6fff12ca7341b3b21f879414c120da79), object size: 384, buffer s... | SLUB: Unable to allocate memory on node -1 | https://api.github.com/repos/kubernetes/kubernetes/issues/82534/comments | 6 | 2019-09-10T14:57:18Z | 2021-09-26T05:23:52Z | https://github.com/kubernetes/kubernetes/issues/82534 | 491,727,635 | 82,534 |
[
"kubernetes",
"kubernetes"
] | Since yesterday, we have been seeing multiple CI jobs fail for a variety of reasons.
Many of the jobs fail at the `overall` stage with an error message such as the one in https://prow.k8s.io/view/gcs/kubernetes-jenkins/logs/ci-kubernetes-e2e-gce-master-new-gci-kubectl-skew/1171375532827217930#0:build-log.txt%3A4097
... | Multiple jobs flaking in CI | https://api.github.com/repos/kubernetes/kubernetes/issues/82533/comments | 9 | 2019-09-10T14:34:39Z | 2019-09-12T13:34:38Z | https://github.com/kubernetes/kubernetes/issues/82533 | 491,713,644 | 82,533 |
[
"kubernetes",
"kubernetes"
] | had a discussion with @timothysc about this yesterday.
this is a tracking issue for replacing the pending PR and release blocking jobs based on kube-up with Cluster API (CAPI) provider alternatives over time.
ideally:
- the replacement jobs should co-existing in parallel with the kube-up jobs.
- once the replac... | replace the existing PR and release blocking kube-up based jobs with CAPI jobs | https://api.github.com/repos/kubernetes/kubernetes/issues/82532/comments | 44 | 2019-09-10T14:14:47Z | 2023-06-21T11:59:15Z | https://github.com/kubernetes/kubernetes/issues/82532 | 491,700,946 | 82,532 |
[
"kubernetes",
"kubernetes"
] | Tasks to move to go1.13:
- [x] resolve https://github.com/kubernetes/kubernetes/issues/82506 / https://github.com/heketi/heketi/issues/1648 (fixed upstream https://github.com/heketi/heketi/pull/1649)
- fixed in k8s in #82805
- [x] update gofmt-formatted source to be compatible with 1.12 and 1.13
- https://git... | switch build scripts to use go modules, stop requiring $GOPATH | https://api.github.com/repos/kubernetes/kubernetes/issues/82531/comments | 64 | 2019-09-10T13:50:36Z | 2024-06-07T15:21:40Z | https://github.com/kubernetes/kubernetes/issues/82531 | 491,685,879 | 82,531 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
An automated, straightforward procedure for cluster tenants to collect core dumps of failing containers.
**Why is this needed**:
So that segmentation faults can be diagnosed at scale without exposing unnecessary privileges to k8ts tenants. | Procedure for tenants to collect core dumps of failing containers | https://api.github.com/repos/kubernetes/kubernetes/issues/82530/comments | 10 | 2019-09-10T13:49:37Z | 2020-03-28T20:32:23Z | https://github.com/kubernetes/kubernetes/issues/82530 | 491,685,293 | 82,530 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
We have a Statefullset with `podManagementPolicy=OrderedReady`. For testing I throw away all PODs using `kubectl delete --force --grace-period=0`. Kubernetes restarts the PODs all at the same time, i.e. in parallel.
**What you expected to happen**:
The PODs should be restarted one by one. ... | Statefullset does not honor podManagementPolicy=OrderedReady when restarting failed pods | https://api.github.com/repos/kubernetes/kubernetes/issues/82529/comments | 15 | 2019-09-10T13:12:03Z | 2020-02-13T12:13:55Z | https://github.com/kubernetes/kubernetes/issues/82529 | 491,663,972 | 82,529 |
[
"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'm creatin... | Two similar entries in deployment "volumes" section cause pod start stuck | https://api.github.com/repos/kubernetes/kubernetes/issues/82526/comments | 5 | 2019-09-10T10:45:32Z | 2020-02-07T12:53:36Z | https://github.com/kubernetes/kubernetes/issues/82526 | 491,594,873 | 82,526 |
[
"kubernetes",
"kubernetes"
] | Per #72519, serviceAccountName (and serviceAccount) are not removed when they are deleted from a resource spec. which is then passed to `kubectl apply`.
I hit this exact bug, and there is nothing in the docs at https://kubernetes.io/docs/concepts/cluster-administration/manage-deployment/#kubectl-apply to warn about ... | Document that some specific properties may not be removed when using kubectl apply | https://api.github.com/repos/kubernetes/kubernetes/issues/82525/comments | 47 | 2019-09-10T10:22:12Z | 2025-02-03T16:14:26Z | https://github.com/kubernetes/kubernetes/issues/82525 | 491,584,148 | 82,525 |
[
"kubernetes",
"kubernetes"
] | From the doc here, https://kubernetes.io/docs/concepts/workloads/pods/init-containers/#pod-restart-reasons
```
A user updates the Pod specification, causing the init container image to change. Any changes to the init container image restarts the Pod. App container image changes only restart the app container.
```
I... | Pods are not restarted when changing the init container's image | https://api.github.com/repos/kubernetes/kubernetes/issues/82523/comments | 11 | 2019-09-10T10:07:43Z | 2020-07-29T06:18:29Z | https://github.com/kubernetes/kubernetes/issues/82523 | 491,577,069 | 82,523 |
[
"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**:
Collect hos... | The kubelet /stats/summary is too expensive on windows | https://api.github.com/repos/kubernetes/kubernetes/issues/82522/comments | 14 | 2019-09-10T09:32:22Z | 2020-03-02T18:56:29Z | https://github.com/kubernetes/kubernetes/issues/82522 | 491,558,523 | 82,522 |
[
"kubernetes",
"kubernetes"
] | Hello,
Can someone inform what means exit code : 3 ?
Also if somebody know, please explain a little what means every code when the pod is terminated ?
I've searched on internet what means code :3, but without success .
Example :
State: Running
Started: Sun, 08 Sep 2019 21:53:04 +0... | Exit codes for terminated pods | https://api.github.com/repos/kubernetes/kubernetes/issues/82519/comments | 7 | 2019-09-10T08:09:13Z | 2022-04-07T09:50:44Z | https://github.com/kubernetes/kubernetes/issues/82519 | 491,516,858 | 82,519 |
[
"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, my p... | pod's cpu usage on matser2 node higher than other node | https://api.github.com/repos/kubernetes/kubernetes/issues/82518/comments | 6 | 2019-09-10T07:48:02Z | 2019-09-13T07:31:22Z | https://github.com/kubernetes/kubernetes/issues/82518 | 491,507,411 | 82,518 |
[
"kubernetes",
"kubernetes"
] | when ommkill happened，the third party librar installed by user can‘t be recovered。Is there any way to solve this problem？
community/question | Is there any way not to kill container when exceed memory limit，but to stop the process inside the container？ | https://api.github.com/repos/kubernetes/kubernetes/issues/82516/comments | 8 | 2019-09-10T07:21:50Z | 2020-02-07T09:51:03Z | https://github.com/kubernetes/kubernetes/issues/82516 | 491,496,602 | 82,516 |
[
"kubernetes",
"kubernetes"
] | On a multi-tenent k8s environment how we make sure that no one create duplicate entry on common ingress controller.
I have common ingress controller manage all ingress rule where multiple application team create their rules. How to avoid one app overwrite other app ingress rules.
| How to avoid duplicate entry on ingress on a multi-tenent environment? | https://api.github.com/repos/kubernetes/kubernetes/issues/82515/comments | 14 | 2019-09-10T06:45:24Z | 2020-05-21T19:38:42Z | https://github.com/kubernetes/kubernetes/issues/82515 | 491,482,220 | 82,515 |
[
"kubernetes",
"kubernetes"
] | It happened usually on static pods.
Here we have kube-controller-manager.manifest under the dir /etc/kubernetes/manifest where kubelet will watch.
When we update the file kube-controller-manager.manifest, the container will be running, but the pod will be in CrashLoopBackOff, and kubelet will create new container. B... | The new pod is stuck in CrashLoopBackOff | https://api.github.com/repos/kubernetes/kubernetes/issues/82512/comments | 13 | 2019-09-10T02:47:31Z | 2021-03-30T06:26:29Z | https://github.com/kubernetes/kubernetes/issues/82512 | 491,420,473 | 82,512 |
[
"kubernetes",
"kubernetes"
] | To get metrics stability into Beta, we will make it illegal to directly import prometheus methods in Kubernetes components. This will insure that all new metrics are instantiated using the correct wrapper methods. To do this, we need to provide wrappers for the direct prometheus method calls (namely, prometheus.Bucket ... | Remove direct references to prometheus methods | https://api.github.com/repos/kubernetes/kubernetes/issues/82510/comments | 6 | 2019-09-09T23:54:46Z | 2019-12-20T01:03:49Z | https://github.com/kubernetes/kubernetes/issues/82510 | 491,379,955 | 82,510 |
[
"kubernetes",
"kubernetes"
] | Currently custom prometheus collectors are ingested into metrics stability framework without any stability metadata. We need some mechanism for wrapping custom prometheus collectors so that we can annotate them with stability metadata.
/sig instrumentation | Provide a mechanism for custom collectors to use the metrics stability framework | https://api.github.com/repos/kubernetes/kubernetes/issues/82509/comments | 6 | 2019-09-09T23:48:44Z | 2019-11-06T10:23:52Z | https://github.com/kubernetes/kubernetes/issues/82509 | 491,378,604 | 82,509 |
[
"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**:
v1alpha1 St... | Drop `VolumeLifecycleModes` field from `CSIDriver` API before GA | https://api.github.com/repos/kubernetes/kubernetes/issues/82507/comments | 9 | 2019-09-09T23:26:50Z | 2020-02-28T21:27:55Z | https://github.com/kubernetes/kubernetes/issues/82507 | 491,373,089 | 82,507 |
[
"kubernetes",
"kubernetes"
] | https://github.com/golang/go/wiki/Modules#how-to-prepare-for-a-release specifies that we should run `go mod tidy` before a release to ensure our `go.mod` file is limited to the set of imports we actually need.
However this currently fails:
```console
$ go mod tidy
warning: ignoring symlink /usr/local/google/home/... | go mod tidy fails in kubernetes/kubernetes on go1.13 | https://api.github.com/repos/kubernetes/kubernetes/issues/82506/comments | 11 | 2019-09-09T22:54:15Z | 2019-09-17T23:55:28Z | https://github.com/kubernetes/kubernetes/issues/82506 | 491,364,589 | 82,506 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
**What you ... | ImagePullBackOff gcr | https://api.github.com/repos/kubernetes/kubernetes/issues/82505/comments | 1 | 2019-09-09T21:07:30Z | 2019-09-09T21:07:48Z | https://github.com/kubernetes/kubernetes/issues/82505 | 491,327,191 | 82,505 |
[
"kubernetes",
"kubernetes"
] | Seen in https://prow.k8s.io/view/gcs/kubernetes-jenkins/pr-logs/pull/69821/pull-kubernetes-integration/1170241808647589890
Serialization using `WithVersionEncoder#Encode` (the default for output) mutates objects. More details in https://github.com/kubernetes/kubernetes/pull/117174
https://github.com/kubernetes/ku... | panic encoding the same object from multiple goroutines concurrently | https://api.github.com/repos/kubernetes/kubernetes/issues/82497/comments | 6 | 2019-09-09T15:58:43Z | 2023-09-07T20:52:02Z | https://github.com/kubernetes/kubernetes/issues/82497 | 491,184,721 | 82,497 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
We had a major network issue on our cluster where nodes were not able to contact each others and master(api,scheduler). Services endpoint were cleaned but when the network was back online some services endpoints remains blank while there were pods running for the services, i guess the controller sho... | Service endpoints status is wrong / not updated | https://api.github.com/repos/kubernetes/kubernetes/issues/82494/comments | 25 | 2019-09-09T14:47:53Z | 2020-04-12T21:54:51Z | https://github.com/kubernetes/kubernetes/issues/82494 | 491,143,613 | 82,494 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs -->
**Which jobs are failing**:
UP - cluster creation
**Which test(s) are failing**:
gce-master-scale-correctness
**Since when has it been failing**:
on 09/07 only, next run has passed (hence this is not urg... | [Failing Test] gce-master-scale-correctness on 09/07 | https://api.github.com/repos/kubernetes/kubernetes/issues/82488/comments | 4 | 2019-09-09T11:48:53Z | 2019-12-09T09:14:31Z | https://github.com/kubernetes/kubernetes/issues/82488 | 491,047,700 | 82,488 |
[
"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 using ... | AppArmor loader reports "No new profiles found" | https://api.github.com/repos/kubernetes/kubernetes/issues/82487/comments | 1 | 2019-09-09T11:38:46Z | 2019-09-23T13:03:31Z | https://github.com/kubernetes/kubernetes/issues/82487 | 491,043,361 | 82,487 |
[
"kubernetes",
"kubernetes"
] | I was recently looking into pprof graphs from our tests, and found out that we're spending a lot of time in `defaultConvert` function (e.g. this run:
https://gcsweb.k8s.io/gcs/kubernetes-jenkins/logs/ci-kubernetes-e2e-gce-scale-performance/1169656830515744771/artifacts/?marker=logs%2fci-kubernetes-e2e-gce-scale-perfor... | No (auto)generated conversions for apimachinery and apiserver objects | https://api.github.com/repos/kubernetes/kubernetes/issues/82484/comments | 18 | 2019-09-09T11:08:47Z | 2019-11-08T07:59:06Z | https://github.com/kubernetes/kubernetes/issues/82484 | 491,030,671 | 82,484 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
I had the issue mentioned here: https://github.com/kubernetes/kubernetes/issues/37450
My applications take some time to be ready for serving traffic after creation, and I thought `readinessProbe` must ... | Initial check for container being ready in a pod | https://api.github.com/repos/kubernetes/kubernetes/issues/82482/comments | 14 | 2019-09-09T10:46:10Z | 2020-05-20T12:07:40Z | https://github.com/kubernetes/kubernetes/issues/82482 | 491,020,907 | 82,482 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
/sig scheduling
/kind feature
**What would you like to be added**:
Graduate ResourceQuotaScopeSelectors from beta to GA
- [x] Relax namespace restriction for critical pods #76310
- [x] Graduate ResourceQuotaScopeSelectors API to GA h... | [Umbrella] Graduate ResourceQuotaScopeSelectors from beta to GA | https://api.github.com/repos/kubernetes/kubernetes/issues/82480/comments | 1 | 2019-09-09T09:09:38Z | 2019-12-12T10:04:03Z | https://github.com/kubernetes/kubernetes/issues/82480 | 490,974,558 | 82,480 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:a timeout mechanism for bind
**Why is this needed**:if kube-schduler already pick a suggest-host for pod,it
call bind() function ,if it didn`t return fail then put result in cache .And in cache cleanup... | Should we give bind a timeout mechanism? | https://api.github.com/repos/kubernetes/kubernetes/issues/82476/comments | 5 | 2019-09-09T03:50:55Z | 2020-01-07T11:18:57Z | https://github.com/kubernetes/kubernetes/issues/82476 | 490,862,217 | 82,476 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
See #66754.
Assuming the `--requestheader-group-headers` flag is set to `X-Remote-Group` the API server should accept both the following header(s) to apply the groups A,B,C to the user:
```http
X-Remote-Group: A
X-Remote-Group: B
X-Remote-Group: C
```
```http
X-Remote... | Kubernetes API Authentication Proxy Request Headers | https://api.github.com/repos/kubernetes/kubernetes/issues/82468/comments | 22 | 2019-09-08T14:47:42Z | 2024-04-22T17:48:11Z | https://github.com/kubernetes/kubernetes/issues/82468 | 490,763,265 | 82,468 |
Subsets and Splits
Unique Owner-Repo Count
Counts the number of unique owner-repos in the dataset, providing a basic understanding of diverse repositories.