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"
] | /sig scheduling
<!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
A metric that can track the total number of preemption victim pods.
**Why is this needed**:
Currently, kube-scheduler exposes two preemption-related metrics [`pod_preemption_vic... | Scheduler metrics: preemption victim pods count | https://api.github.com/repos/kubernetes/kubernetes/issues/90841/comments | 1 | 2020-05-07T12:50:21Z | 2020-05-09T02:42:55Z | https://github.com/kubernetes/kubernetes/issues/90841 | 614,032,491 | 90,841 |
[
"kubernetes",
"kubernetes"
] | - Create a test pod with kubernetes.io/ingress-bandwidth and kubernetes.io/egress-bandwidth annotations
```
---
apiVersion: v1
kind: Pod
metadata:
name: iperf3
annotations:
kubernetes.io/ingress-bandwidth: 10M
kubernetes.io/egress-bandwidth: 10M
spec:
containers:
- name: iperf3
image: n... | Default bandwidth burst is too large | https://api.github.com/repos/kubernetes/kubernetes/issues/90838/comments | 16 | 2020-05-07T11:40:35Z | 2021-10-05T19:42:06Z | https://github.com/kubernetes/kubernetes/issues/90838 | 613,989,292 | 90,838 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
Add an `AuditEvent` resource (or similar) that can be list-watched via the k8s API.
**Why is this needed**:
It would enable a simple way to pull out the audit events for tools that already know to tal... | Expose audit events as list-watchable k8s API resource | https://api.github.com/repos/kubernetes/kubernetes/issues/90835/comments | 12 | 2020-05-07T10:40:55Z | 2020-10-08T20:28:50Z | https://github.com/kubernetes/kubernetes/issues/90835 | 613,954,171 | 90,835 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
The change in #90806 is temporary - instead of just adding an annotation to every kubemark node to simply increase node objects sizes, we'd like to leverage image preloading (from clusterloader in perf-te... | Leverage image preloading in kubemark tests | https://api.github.com/repos/kubernetes/kubernetes/issues/90833/comments | 49 | 2020-05-07T08:42:24Z | 2021-10-07T14:06:08Z | https://github.com/kubernetes/kubernetes/issues/90833 | 613,880,332 | 90,833 |
[
"kubernetes",
"kubernetes"
] | ## What happened:
I have created a Service Accout which name contains dot character (`.`) and tried to create to pod using this service account. But Pod creation failed with a volume name which doesn't match the regex `[a-z0-9]([-a-z0-9]*[a-z0-9])?`
Output:
```text
serviceaccount/serviceaccount.withdot created
... | Pod Service Account Name can't contain dot character | https://api.github.com/repos/kubernetes/kubernetes/issues/90831/comments | 5 | 2020-05-07T07:37:41Z | 2020-05-07T17:16:11Z | https://github.com/kubernetes/kubernetes/issues/90831 | 613,841,932 | 90,831 |
[
"kubernetes",
"kubernetes"
] | **Which jobs are failing**:
> gce-cos-master-slow (ci-kubernetes-e2e-gci-gce-slow)
**Which test(s) are failing**:
> Overall
>Test
> [sig-apps] StatefulSet [k8s.io] Basic StatefulSet functionality [StatefulSetBasic] Scaling should happen in predictable order and halt if any stateful pod is unhealthy [Slow] [Confo... | [Flaky Test] gce-cos-master-slow (ci-kubernetes-e2e-gci-gce-slow) | https://api.github.com/repos/kubernetes/kubernetes/issues/90830/comments | 13 | 2020-05-07T06:40:30Z | 2020-07-22T18:20:56Z | https://github.com/kubernetes/kubernetes/issues/90830 | 613,811,637 | 90,830 |
[
"kubernetes",
"kubernetes"
] | We set the flag to protect the kernel params are not modified by the kubelet
```
protectKernelDefaults: true
```
But the kubelet cannot be up because of this error
```
Failed to start ContainerManager [Invalid kernel flag: kernel/panic, expected value: 10, actual value: 0, Invalid kernel flag: kernel/panic, expec... | Can we just print the warning instead of failing directly when the node's kernel parameters are not expected in kubelet | https://api.github.com/repos/kubernetes/kubernetes/issues/90829/comments | 5 | 2020-05-07T06:23:46Z | 2020-10-04T09:27:54Z | https://github.com/kubernetes/kubernetes/issues/90829 | 613,803,943 | 90,829 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Using the apiserver `--goaway-chance=0.001` flag resulted in our apiserver load tests reported a 8% reduction in throughput vs a baseline without the flag. One thought was that the GOAWAY operations on a connections were the source of the reduction. So we ran the test with `--goaway-chance=0.0001`. ... | Using apiserver --goaway-chance reduces apiservice request throughput by 8% | https://api.github.com/repos/kubernetes/kubernetes/issues/90821/comments | 10 | 2020-05-06T19:41:28Z | 2020-05-15T22:14:46Z | https://github.com/kubernetes/kubernetes/issues/90821 | 613,565,149 | 90,821 |
[
"kubernetes",
"kubernetes"
] | Tracking work from https://github.com/kubernetes/enhancements/pull/1711
Not all of these are required for GA
- [ ] Update KEP to include new API struct
- [ ] Doc updates, especially around new API changes https://github.com/kubernetes/website/pull/21626
- [ ] Implement new API changes
- [ ] Wire cluster info... | External credential providers KEP follow-ups | https://api.github.com/repos/kubernetes/kubernetes/issues/90817/comments | 11 | 2020-05-06T19:17:22Z | 2021-02-13T21:14:19Z | https://github.com/kubernetes/kubernetes/issues/90817 | 613,551,870 | 90,817 |
[
"kubernetes",
"kubernetes"
] | **Which jobs are flaking**:
pull-kubernetes-bazel-test
**Which test(s) are flaking**:
TestEnsureBackendPoolDeletedConcurrently
**Testgrid link**:
**Reason for failure**:
```
testing.go:853: race detected during execution of test
```
https://prow.k8s.io/view/gcs/kubernetes-jenkins/pr-logs/pull/... | TestEnsureBackendPoolDeletedConcurrently has races | https://api.github.com/repos/kubernetes/kubernetes/issues/90816/comments | 2 | 2020-05-06T18:55:51Z | 2020-05-08T05:21:44Z | https://github.com/kubernetes/kubernetes/issues/90816 | 613,539,536 | 90,816 |
[
"kubernetes",
"kubernetes"
] |
**What happened**:
We are using vsphere cloud provider. Dynamic storage provisioning got very slow after upgrading our K8s clusters from v1.14 to v1.15.
**What you expected to happen**:
We expected `pv`s to be created within seconds as it happens on K8s v1.14 cluster. However depending on the number `pvc`s created... | VSphere Cloud Provider dynamic storage provisioning got very slow after upgrading from v1.14 to v1.15. | https://api.github.com/repos/kubernetes/kubernetes/issues/90814/comments | 19 | 2020-05-06T16:58:46Z | 2021-06-19T22:51:23Z | https://github.com/kubernetes/kubernetes/issues/90814 | 613,470,367 | 90,814 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about flaky tests or jobs (pass or fail with no underlying change in code) in Kubernetes CI -->
**Which jobs are flaking**:
* ci-kubernetes-kind-conformance-parallel
* ci-kubernetes-kind-conformance-ga-only-parallel
* ...
**Which test(s) are flaking**:
... | [Flaky test] [sig-apps] StatefulSet [k8s.io] Basic StatefulSet functionality [StatefulSetBasic] Scaling should happen in predictable order and halt if any stateful pod is unhealthy [Slow] [Conformance] - watch closed before UntilWithoutRetry timeout | https://api.github.com/repos/kubernetes/kubernetes/issues/90813/comments | 16 | 2020-05-06T16:47:42Z | 2020-05-09T21:48:58Z | https://github.com/kubernetes/kubernetes/issues/90813 | 613,463,046 | 90,813 |
[
"kubernetes",
"kubernetes"
] | The test "`Services should be rejected when no endpoints exist`" is flaky. eg, currently on https://testgrid.k8s.io/presubmits-kubernetes-blocking#pull-kubernetes-e2e-gce there are 4 flakes in the last 10 days (or whatever it is):
- https://prow.k8s.io/view/gcs/kubernetes-jenkins/pr-logs/directory/pull-kubernetes-e2... | "Services should be rejected when no endpoints exist" is flaky | https://api.github.com/repos/kubernetes/kubernetes/issues/90810/comments | 16 | 2020-05-06T15:38:36Z | 2020-09-14T12:12:01Z | https://github.com/kubernetes/kubernetes/issues/90810 | 613,417,250 | 90,810 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
**Updated issue description:**
`imagePullPolicy: Always` resolves the image with the registry, and if it resolves to a sha that is not already pulled to the node, pulls the image content. If the resolved sha is already pulled to the node, it uses the already-pulled content. Th... | Clarify behavior of `imagePullPolicy: Always` | https://api.github.com/repos/kubernetes/kubernetes/issues/90809/comments | 6 | 2020-05-06T15:00:21Z | 2020-05-23T15:43:11Z | https://github.com/kubernetes/kubernetes/issues/90809 | 613,389,379 | 90,809 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
A deployment gets way too many pods launched by HPA. But individual pods CPU usage is really low.
foo-deployment Deployment/foo-deployment 89%/90% 14 30 29 205d
But, for those 29 pods the CPU usage is:
112m 64m 91m 99m 133m 75m 115m 86m 76m 128m 98m 102m 13... | Weird HPA behaviour | https://api.github.com/repos/kubernetes/kubernetes/issues/90808/comments | 6 | 2020-05-06T15:00:02Z | 2020-11-10T05:49:52Z | https://github.com/kubernetes/kubernetes/issues/90808 | 613,389,134 | 90,808 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
I downloaded the official ppc64le client binary from the https://kubernetes.io/docs/setup/release/notes/#client-binaries.
When I run `./bin/kubectl`, I get following error:
`cannot execute binary file: Exec format error`
**What you expected to happen**:
The app should work.
**How to... | kubernetes ppc64le client v1.18 binary is mixed up with arm64 client | https://api.github.com/repos/kubernetes/kubernetes/issues/90807/comments | 5 | 2020-05-06T14:01:09Z | 2020-05-11T05:50:17Z | https://github.com/kubernetes/kubernetes/issues/90807 | 613,344,108 | 90,807 |
[
"kubernetes",
"kubernetes"
] | I'm trying to run the init script before the container starts in the pod, for that, I have created a config map from file and mounted as shown in deployment scripts then simply trying to run the `initscript.ps1` but giving error not sure what am I missing.
`initscript-config-script` is a configMap that I have create... | kubernetes: failure in a Windows system call: The system cannot find the path specified | https://api.github.com/repos/kubernetes/kubernetes/issues/90802/comments | 0 | 2020-05-06T12:25:58Z | 2020-05-06T18:31:04Z | https://github.com/kubernetes/kubernetes/issues/90802 | 613,279,778 | 90,802 |
[
"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 bun... | Cronjob controller doesn't honor defined schedules on big clusters | https://api.github.com/repos/kubernetes/kubernetes/issues/90801/comments | 11 | 2020-05-06T12:16:00Z | 2021-04-12T10:17:19Z | https://github.com/kubernetes/kubernetes/issues/90801 | 613,273,891 | 90,801 |
[
"kubernetes",
"kubernetes"
] | Hello guys, I have a problem running hello-minikube in kubernetes.
This is the command -->
run hello-minikube --image=gcr.io/google_containers/echoserver:1.4 --port=8080
This the result -->
error: v1.ReplicationController: ObjectMeta: v1.ObjectMeta: readObjectFieldAsBytes: expect : after object field, parsing ... | Problem with hello-world minikube | https://api.github.com/repos/kubernetes/kubernetes/issues/90798/comments | 2 | 2020-05-06T10:40:38Z | 2020-05-11T10:57:42Z | https://github.com/kubernetes/kubernetes/issues/90798 | 613,220,581 | 90,798 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
kube-controll... | vCenter hostname must be all lower case | https://api.github.com/repos/kubernetes/kubernetes/issues/90795/comments | 2 | 2020-05-06T10:26:47Z | 2020-05-13T04:00:41Z | https://github.com/kubernetes/kubernetes/issues/90795 | 613,212,533 | 90,795 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
A Pod was scheduled for deletion because a taint w/ effect `NoExecute` was observed in the Node the Pod was assigned to, and after the taint is removed from the Node, the Pod scheduled deletion isn't canceled.
After scheduling pod deletion, the *`NoExecuteTaintManager` only cancels pod deletion... | Pods in Node are deleted even if the NoExecute taint that triggered deletion is removed | https://api.github.com/repos/kubernetes/kubernetes/issues/90794/comments | 21 | 2020-05-06T10:00:33Z | 2020-08-10T03:42:20Z | https://github.com/kubernetes/kubernetes/issues/90794 | 613,197,265 | 90,794 |
[
"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**:
Public IP i... | Public IP is not shown on nodes after assigning public IP to Azure VMs | https://api.github.com/repos/kubernetes/kubernetes/issues/90790/comments | 2 | 2020-05-06T07:39:32Z | 2020-05-18T04:16:47Z | https://github.com/kubernetes/kubernetes/issues/90790 | 613,113,886 | 90,790 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
In https://github.com/kubernetes/kubernetes/pull/90697, we're bumping the debian-base image, so new `etcd` and `etcd-empty-dir-cleanup` images need to be pushed to pick up the changes.
**hold on this until https://github.com/kubernetes/kubernetes/pull/90697 merges.**
/area et... | Build and push etcd v3.4.7.1 images | https://api.github.com/repos/kubernetes/kubernetes/issues/90772/comments | 3 | 2020-05-05T19:34:03Z | 2020-05-19T21:57:21Z | https://github.com/kubernetes/kubernetes/issues/90772 | 612,843,699 | 90,772 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
When deleting a PV, the VMDK is deleted but the delete task is called twice. The first task successes but the second task fails because the VMDK is already deleted.
**What you expected to happen**:
Only one delete task should be created.
**How to reproduce it (as minimally and precisely as po... | Double delete of vmdk when PV gets deleted. | https://api.github.com/repos/kubernetes/kubernetes/issues/90770/comments | 16 | 2020-05-05T18:53:18Z | 2021-10-29T18:52:42Z | https://github.com/kubernetes/kubernetes/issues/90770 | 612,820,483 | 90,770 |
[
"kubernetes",
"kubernetes"
] | Currently services/proxy is available in client-go, but pods/proxy resource is not. This requires manual usage via the rest client like
```go
request := client.RESTClient.Get().
Namespace("foo").
Resource("pods").
SubResource("proxy").
Name(name).
Suffix(path)
return request
```
This can be se... | support pods/proxy resource in client-go | https://api.github.com/repos/kubernetes/kubernetes/issues/90768/comments | 1 | 2020-05-05T18:25:05Z | 2020-06-19T18:37:55Z | https://github.com/kubernetes/kubernetes/issues/90768 | 612,804,321 | 90,768 |
[
"kubernetes",
"kubernetes"
] | Using [oidc](https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/client-go/plugin/pkg/client/auth/oidc/oidc.go) with a [DirectClientConfig](https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/client-go/tools/clientcmd/client_config.go#L77) without a [ConfigAccess](https://github.... | /staging/src/k8s.io/client-go/plugin/pkg/client/auth/oidc/ panics if persister is nil | https://api.github.com/repos/kubernetes/kubernetes/issues/90766/comments | 5 | 2020-05-05T17:13:09Z | 2020-10-02T22:54:00Z | https://github.com/kubernetes/kubernetes/issues/90766 | 612,762,491 | 90,766 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
Set information about time in a PDB. For example it can be:
```yaml
spec:
window:
begin: 0 0 13 * 5
duration: 2h
cooldown: 1d
```
- `window`: the moment where a pod can be killed.
- `cooldown` how many times to wait between kills.
**Why is this neede... | time based Pod Disruption Budget | https://api.github.com/repos/kubernetes/kubernetes/issues/90765/comments | 5 | 2020-05-05T15:06:05Z | 2020-10-02T17:48:59Z | https://github.com/kubernetes/kubernetes/issues/90765 | 612,675,693 | 90,765 |
[
"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 ran sonobu... | NodePort service creation e2e test relies on insecure cluster configuration | https://api.github.com/repos/kubernetes/kubernetes/issues/90764/comments | 25 | 2020-05-05T14:46:18Z | 2021-03-09T03:23:00Z | https://github.com/kubernetes/kubernetes/issues/90764 | 612,660,009 | 90,764 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
Remove `go test ./...` example from [testing guide](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-testing/testing.md).
**Why is this needed**:
While trying to get all unit tests to run locally, I tried using this and it doesn't work, at least not fr... | Remove or clarify recommendation about using go test to run unit tests | https://api.github.com/repos/kubernetes/kubernetes/issues/90763/comments | 10 | 2020-05-05T14:19:11Z | 2020-06-16T20:26:05Z | https://github.com/kubernetes/kubernetes/issues/90763 | 612,640,180 | 90,763 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
PR(https://... | azure disk dangling attach issue on VMSS which would cause API throttling | https://api.github.com/repos/kubernetes/kubernetes/issues/90762/comments | 0 | 2020-05-05T13:32:53Z | 2020-05-06T06:43:10Z | https://github.com/kubernetes/kubernetes/issues/90762 | 612,606,019 | 90,762 |
[
"kubernetes",
"kubernetes"
] | **Which jobs are failing**:
> kubeadm-kinder-upgrade-1-18-master (ci-kubernetes-e2e-kubeadm-kinder-upgrade-1-18-master)
**Which test(s) are failing**:
> Overall
> task-06-upgrade
**Since when has it been failing**:
> 05-04 11:52 PDT
**Testgrid link**:
> https://testgrid.k8s.io/sig-release-master-informing... | [Flaky Test] kubeadm-kinder-upgrade-1-18-1-19 (ci-kubernetes-e2e-kubeadm-kinder-upgrade-1-18-1-19) | https://api.github.com/repos/kubernetes/kubernetes/issues/90761/comments | 27 | 2020-05-05T13:15:49Z | 2020-09-23T20:50:05Z | https://github.com/kubernetes/kubernetes/issues/90761 | 612,593,781 | 90,761 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
On an SELinux... | Unexpected MCS levels on containers | https://api.github.com/repos/kubernetes/kubernetes/issues/90759/comments | 16 | 2020-05-05T12:02:15Z | 2021-01-05T11:51:05Z | https://github.com/kubernetes/kubernetes/issues/90759 | 612,549,359 | 90,759 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
When using ... | Partition appears wrong on kubectl describe | https://api.github.com/repos/kubernetes/kubernetes/issues/90758/comments | 4 | 2020-05-05T09:42:23Z | 2020-05-06T15:29:58Z | https://github.com/kubernetes/kubernetes/issues/90758 | 612,472,414 | 90,758 |
[
"kubernetes",
"kubernetes"
] | When reviewing the fix of #88327, I feel that #88331 as well as existing schedulerQueue unit tests are not written in a desired way.
The racing cause of #88327 lies on concurrent access of private fields - those private fields are protected by locks via public functions, but unfortunately directly accessed by the un... | Refine schedulerQueue unit tests | https://api.github.com/repos/kubernetes/kubernetes/issues/90754/comments | 1 | 2020-05-05T07:09:07Z | 2020-05-06T03:03:23Z | https://github.com/kubernetes/kubernetes/issues/90754 | 612,386,193 | 90,754 |
[
"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 test... | CSI ephemeral volumes: idempotent NodeUnpublishVolume | https://api.github.com/repos/kubernetes/kubernetes/issues/90752/comments | 7 | 2020-05-05T06:36:27Z | 2020-11-02T09:41:21Z | https://github.com/kubernetes/kubernetes/issues/90752 | 612,372,148 | 90,752 |
[
"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... | unexpected directory layout: | https://api.github.com/repos/kubernetes/kubernetes/issues/90750/comments | 2 | 2020-05-05T04:17:23Z | 2020-05-11T11:03:10Z | https://github.com/kubernetes/kubernetes/issues/90750 | 612,325,823 | 90,750 |
[
"kubernetes",
"kubernetes"
] | Hello, I'm using the Kubernetes to deploy the Kubeflow Pytorch Operator. No matter how big the ephemeral-storage I set, 20Gi,40..80Gi, I always get the exception "Pod ephemeral local storage usage exceeds the total limit of containers **Gi". Actually, the Node disk is sufficient. Would you please help on that? Great ... | Pod ephemeral local storage usage exceeds the total limit of containers **Gi | https://api.github.com/repos/kubernetes/kubernetes/issues/90748/comments | 8 | 2020-05-05T02:59:15Z | 2021-03-25T04:32:55Z | https://github.com/kubernetes/kubernetes/issues/90748 | 612,290,738 | 90,748 |
[
"kubernetes",
"kubernetes"
] | # Progress <code>[2/6]</code>
- [X] APISnoop org-flow: [deleteCoreV1CollectionNamespacedPodTemplate.org](https://github.com/cncf/apisnoop/blob/master/tickets/k8s/deleteCoreV1CollectionNamespacedPodTemplateTest.org)
- [X] test approval issue: [kubernetes/kubernetes#90746](https://github.com/kubernetes/kubernetes... | Add deleteCoreV1CollectionNamespacedPodTemplate Mock Test - +1 endpoint coverage | https://api.github.com/repos/kubernetes/kubernetes/issues/90746/comments | 6 | 2020-05-05T00:57:29Z | 2020-05-09T21:49:06Z | https://github.com/kubernetes/kubernetes/issues/90746 | 612,260,045 | 90,746 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Deleting a large collection times out (504) and leaks a goroutine that's busy deleting the collection. Calling multiple times in a row makes it worse. There's no indication that apiserver is currently deleting the collection.
**What you expected to happen**:
a) Change delete collection so th... | DELETECOLLECTION doesn't always | https://api.github.com/repos/kubernetes/kubernetes/issues/90743/comments | 35 | 2020-05-04T22:22:56Z | 2024-12-15T14:02:31Z | https://github.com/kubernetes/kubernetes/issues/90743 | 612,207,254 | 90,743 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
`kubectl wait... | kubectl wait fails after successful apply | https://api.github.com/repos/kubernetes/kubernetes/issues/90741/comments | 1 | 2020-05-04T21:08:11Z | 2020-05-04T23:01:13Z | https://github.com/kubernetes/kubernetes/issues/90741 | 612,169,323 | 90,741 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Running `make bazel-test` locally fails with the following error:
```
ERROR: While resolving toolchains for target //build:code_generation_tests_test_1: no matching toolchains found for types @bazel_skylib//toolchains/unittest:toolchain_type
ERROR: Analysis of target '//build:code_generation_test... | Running `make bazel-test` locally fails with toolchain resolution error | https://api.github.com/repos/kubernetes/kubernetes/issues/90739/comments | 5 | 2020-05-04T19:10:55Z | 2020-06-27T22:00:26Z | https://github.com/kubernetes/kubernetes/issues/90739 | 612,102,673 | 90,739 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about flaky tests or jobs (pass or fail with no underlying change in code) in Kubernetes CI -->
**Which jobs are flaking**:
`gce-cos-master-default (ci-kubernetes-e2e-gci-gce)`
**Which test(s) are flaking**:
`[sig-storage] CSI mock volume storage cap... | [Flaky Test] gce-cos-master-default (ci-kubernetes-e2e-gci-gce) | https://api.github.com/repos/kubernetes/kubernetes/issues/90736/comments | 13 | 2020-05-04T17:31:31Z | 2020-07-22T18:17:31Z | https://github.com/kubernetes/kubernetes/issues/90736 | 612,043,828 | 90,736 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about flaky tests or jobs (pass or fail with no underlying change in code) in Kubernetes CI -->
**Which jobs are flaking**:
`node-kubelet-master (ci-kubernetes-node-kubelet)`
**Which test(s) are flaking**:
`Overall`
**Testgrid link**:
https://t... | [Flaky Test] node-kubelet-master (ci-kubernetes-node-kubelet) | https://api.github.com/repos/kubernetes/kubernetes/issues/90735/comments | 2 | 2020-05-04T17:26:23Z | 2020-05-05T13:48:33Z | https://github.com/kubernetes/kubernetes/issues/90735 | 612,040,590 | 90,735 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
TestCmdCompletion unit test fails on freshly cloned repository
**What you expected to happen**:
Unit test should pass when running locally without requiring any manual configuration of the system beforehand.
**How to reproduce it (as minimally and precisely as possible)**:
(Don't have `KUBEA... | TestCmdCompletion unit test fails when run locally | https://api.github.com/repos/kubernetes/kubernetes/issues/90732/comments | 8 | 2020-05-04T16:13:44Z | 2020-05-04T20:04:30Z | https://github.com/kubernetes/kubernetes/issues/90732 | 611,996,292 | 90,732 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
TestKubeletDefault unit test fails when run locally on system that has systemd-resolved active
**What you expected to happen**:
Unit test succeeds
**How to reproduce it (as minimally and precisely as possible)**:
Use ubuntu with systemd-resolved active.
Run `go test ./cmd/kubeadm/app/compon... | TestKubeletDefault unit test fails when run locally on system that has systemd-resolved active | https://api.github.com/repos/kubernetes/kubernetes/issues/90726/comments | 4 | 2020-05-04T15:16:28Z | 2020-05-04T19:16:42Z | https://github.com/kubernetes/kubernetes/issues/90726 | 611,954,931 | 90,726 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
We see an intermittent issue that seems to be related to load where pods stay in `ContainerCreating` state for a long time - sometimes over an hour before they become `Running` . When this happens the Events on the pod show:
```
Warning FailedMount 48s (x21 over 27m) kubelet, 10.94.119.80 Mo... | Kubelet reports configmaps not found even though they do exist | https://api.github.com/repos/kubernetes/kubernetes/issues/90725/comments | 22 | 2020-05-04T15:14:08Z | 2020-10-11T12:14:45Z | https://github.com/kubernetes/kubernetes/issues/90725 | 611,953,170 | 90,725 |
[
"kubernetes",
"kubernetes"
] | /kind cleanup
It doesn't make much sense for Reserve plugins to not have an Unreserve counterpart. Having them separate adds configuration toil.
I propose we merge them in a single interface and a single PluginSet in the configuration. However, we can only do the later in a new version of component config.
/sig ... | Scheduling Framework: Merge Reserve and Unreserve | https://api.github.com/repos/kubernetes/kubernetes/issues/90724/comments | 15 | 2020-05-04T14:56:58Z | 2020-06-26T02:57:32Z | https://github.com/kubernetes/kubernetes/issues/90724 | 611,940,268 | 90,724 |
[
"kubernetes",
"kubernetes"
] | **Which jobs are failing**:
gce-master-scale-performance
**Which test(s) are failing**:
ClusterLoaderV2 - load
**Since when has it been failing**:
2020-05-03
**Testgrid link**:
https://k8s-testgrid.appspot.com/sig-release-master-informing#gce-master-scale-performance
https://prow.k8s.io/view/gcs/kubernete... | [Flaky Test] gce-master-scale-performance: l7-default-backend restarted twice | https://api.github.com/repos/kubernetes/kubernetes/issues/90723/comments | 6 | 2020-05-04T14:42:42Z | 2020-05-07T13:15:42Z | https://github.com/kubernetes/kubernetes/issues/90723 | 611,929,741 | 90,723 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI -->
**Which jobs are failing**:
sig-windows jobs: https://testgrid.k8s.io/sig-windows#aks-engine-azure-windows-master-staging
**Which test(s) are failing**:
[sig-network] Services should be ab... | ExternalName tests are failing on Windows | https://api.github.com/repos/kubernetes/kubernetes/issues/90719/comments | 0 | 2020-05-04T14:07:28Z | 2020-06-10T11:38:38Z | https://github.com/kubernetes/kubernetes/issues/90719 | 611,903,316 | 90,719 |
[
"kubernetes",
"kubernetes"
] | - [Tickets](#sec-1)
- [WIP Endpoints by group](#sec-2)
- [Core](#sec-2-1)
- [Volumes](#sec-2-1-1)
- [ComponentStatus](#sec-2-1-2)
- [Node](#sec-2-1-3)
- [Links and references](#sec-3)
Evaluate and describe which endpoints are not fit for conformance.
# Tickets<a id="sec-1"></a>
- [ ] [API... | Non-conformant endpoints documentation | https://api.github.com/repos/kubernetes/kubernetes/issues/90712/comments | 7 | 2020-05-04T04:31:20Z | 2021-03-17T22:48:48Z | https://github.com/kubernetes/kubernetes/issues/90712 | 611,596,509 | 90,712 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
When deploying kubernetes via kubeadm on Fedora 31+ with cri-o, kubelet fails to start with the following error:
`kubelet.go:1383] Failed to start ContainerManager system validation failed - Following Cgroup subsystem not mounted: [cpu cpuacct cpuset memory]`
Subsequently kubeadm can't finish th... | Kubelet on Fedora 31+ doesn't start without kernel parameter systemd.unified_cgroup_hierarchy = 0 | https://api.github.com/repos/kubernetes/kubernetes/issues/90710/comments | 22 | 2020-05-04T02:46:38Z | 2021-06-04T04:10:46Z | https://github.com/kubernetes/kubernetes/issues/90710 | 611,572,367 | 90,710 |
[
"kubernetes",
"kubernetes"
] | We have some scripts that install docker/containerd etc and are having trouble installing on focal based images as https://download.docker.com/linux does not yet support focal fossa. So in https://github.com/kubernetes/kubernetes/pull/90702 we have a patch that uses `bionic` debs for focal.
Additional context, ple... | Docker repository does not yet support focal fossa | https://api.github.com/repos/kubernetes/kubernetes/issues/90709/comments | 3 | 2020-05-03T20:49:22Z | 2020-06-21T22:28:40Z | https://github.com/kubernetes/kubernetes/issues/90709 | 611,504,407 | 90,709 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Running:
```shell
kubectl run nginx --image=nginx --namespace=tmp --dry-run=client -o yaml
```
produces YAML, which does not contain the line specifying the existing namespace `tmp`.
![snap6809](https://user-images.githubusercontent.com/17828303/80922675-5686d600-8d87-11ea-9357-88613ecbc7ff.p... | kubectl does not generate namespace in yaml for dry run | https://api.github.com/repos/kubernetes/kubernetes/issues/90706/comments | 2 | 2020-05-03T18:58:24Z | 2020-05-03T19:20:39Z | https://github.com/kubernetes/kubernetes/issues/90706 | 611,482,084 | 90,706 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
When a baremetal host node has both an IPv4 address and an IPv6 address, the kubelet's status update will only use the first IP address which matches the _primary_ address family, even when the Dual Stack feature flag is enabled.
**What you expected to happen**:
Both IPv4 and IPv6 addresses ... | DualStack: Baremetal kubelet only sets NodeStatus with a single IP, even in DualStack mode | https://api.github.com/repos/kubernetes/kubernetes/issues/90704/comments | 8 | 2020-05-03T15:55:34Z | 2020-06-30T17:48:21Z | https://github.com/kubernetes/kubernetes/issues/90704 | 611,444,140 | 90,704 |
[
"kubernetes",
"kubernetes"
] | **Which jobs are failing**:
> kind-ipv6-master-parallel (ci-kubernetes-kind-ipv6-e2e-parallel)
**Which test(s) are failing**:
> Overall
> [sig-cli] Kubectl client Simple pod should support inline execution and attach
**Since when has it been failing**:
> 05-03 02:53 PDT
**Testgrid link**:
> https://testgr... | [Failing Test] kind-ipv6-master-parallel (ci-kubernetes-kind-ipv6-e2e-parallel) | https://api.github.com/repos/kubernetes/kubernetes/issues/90701/comments | 6 | 2020-05-03T13:16:24Z | 2020-05-03T13:33:07Z | https://github.com/kubernetes/kubernetes/issues/90701 | 611,412,424 | 90,701 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
Our core/base images should be built and housed on Kubernetes Community Infra.
- `pause`
**Why is this needed**:
We currently depend an extremely small set of Googlers to push these images.
There's minimal public documentation or visibility into this process and it crea... | 'pause' base image updates & building on K8s Infra | https://api.github.com/repos/kubernetes/kubernetes/issues/90698/comments | 9 | 2020-05-03T03:24:48Z | 2021-01-11T22:21:07Z | https://github.com/kubernetes/kubernetes/issues/90698 | 611,322,965 | 90,698 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
```
Service Objects are not getting deleted/cleaned correctly when services are deleted and recreated quickly at scale. This issue is similar to earlier issue https://github.com/kubernetes/kubernetes/issues/77081
```
**What you expected to happen**:
```
Expected to cleanup service objects u... | Garbage Collector does not clean up service objects correctly with "Foreground" propagation policy | https://api.github.com/repos/kubernetes/kubernetes/issues/90692/comments | 7 | 2020-05-02T19:39:04Z | 2021-09-07T21:39:03Z | https://github.com/kubernetes/kubernetes/issues/90692 | 611,259,719 | 90,692 |
[
"kubernetes",
"kubernetes"
] | **Which jobs are failing**:
> capg-conformance-v1alpha3-k8s-master (ci-cluster-api-provider-gcp-make-conformance-v1alpha3-k8s-ci-artifacts)
**Which test(s) are failing**:
> Overall
**Since when has it been failing**:
> 05-01 18:11 PDT
**Testgrid link**:
> https://testgrid.k8s.io/sig-release-master-informi... | [Flaky Test] capg-conformance-v1alpha3-k8s-master (ci-cluster-api-provider-gcp-make-conformance-v1alpha3-k8s-ci-artifacts) | https://api.github.com/repos/kubernetes/kubernetes/issues/90686/comments | 15 | 2020-05-02T09:54:21Z | 2020-06-22T17:30:16Z | https://github.com/kubernetes/kubernetes/issues/90686 | 611,150,095 | 90,686 |
[
"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**:
```
[root@ma... | wait panic | https://api.github.com/repos/kubernetes/kubernetes/issues/90685/comments | 5 | 2020-05-02T04:45:05Z | 2020-05-12T07:46:25Z | https://github.com/kubernetes/kubernetes/issues/90685 | 611,106,659 | 90,685 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
When creating a pod with `PodAffinity` operator `DoesNotExist`, the pod will always land on a node that it should not. (For example, if PodA is on Node1 with the label `foo`, and PodB is created with a Pod Affinity for `DoesNotExist` against label `foo`, PodB will always be scheduled to Node 1)
N... | Pod affinity with operator "DoesNotExist" does not work | https://api.github.com/repos/kubernetes/kubernetes/issues/90679/comments | 20 | 2020-05-01T20:09:19Z | 2020-09-02T21:17:31Z | https://github.com/kubernetes/kubernetes/issues/90679 | 610,943,880 | 90,679 |
[
"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 the e... | AWS: Error creating security policy on load balancer when using custom SSL negotiation policy. | https://api.github.com/repos/kubernetes/kubernetes/issues/90677/comments | 6 | 2020-05-01T17:04:55Z | 2020-12-01T21:18:35Z | https://github.com/kubernetes/kubernetes/issues/90677 | 610,857,874 | 90,677 |
[
"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 with ho... | Pod with hostNetwork cannot updated when replicas equal to nodes and one of nodes notReady | https://api.github.com/repos/kubernetes/kubernetes/issues/90669/comments | 9 | 2020-05-01T11:23:47Z | 2020-06-05T06:07:49Z | https://github.com/kubernetes/kubernetes/issues/90669 | 610,704,237 | 90,669 |
[
"kubernetes",
"kubernetes"
] | **Which jobs are failing**:
> gce-ubuntu-master-default (ci-kubernetes-e2e-ubuntu-gce)
**Which test(s) are failing**:
> Overall
> Up
**Since when has it been failing**:
> 04-30 10:00 PDT
**Testgrid link**:
> https://testgrid.k8s.io/sig-release-master-informing#gce-ubuntu-master-default
**Reason... | [Failing Test] gce-ubuntu-master-default (ci-kubernetes-e2e-ubuntu-gce) | https://api.github.com/repos/kubernetes/kubernetes/issues/90668/comments | 4 | 2020-05-01T09:52:45Z | 2020-05-04T00:36:27Z | https://github.com/kubernetes/kubernetes/issues/90668 | 610,671,375 | 90,668 |
[
"kubernetes",
"kubernetes"
] | **Which jobs are failing**:
> gce-ubuntu-master-containerd (ci-kubernetes-e2e-ubuntu-gce-containerd)
**Which test(s) are failing**:
> Overall
> Up
**Since when has it been failing**:
> 04-30 10:00 PDT
**Testgrid link**:
> https://testgrid.k8s.io/sig-release-master-informing#gce-ubuntu-master-conta... | [Failing Test] gce-ubuntu-master-containerd (ci-kubernetes-e2e-ubuntu-gce-containerd) | https://api.github.com/repos/kubernetes/kubernetes/issues/90667/comments | 3 | 2020-05-01T09:49:26Z | 2020-05-04T00:36:27Z | https://github.com/kubernetes/kubernetes/issues/90667 | 610,670,261 | 90,667 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Kubelet CPU usage on one host becoming crazy. The other node is fine.
**What you expected to happen**:
Nothing, the server wasn't used.
**How to reproduce it (as minimally and precisely as possible)**:
Here is a screenshot of the buggy node
![QYFZ5LNXc8f8RaU83ioiqYJ0B](https://user-images.githu... | Kubelet sending thousands of request and CPU usage 100% | https://api.github.com/repos/kubernetes/kubernetes/issues/90666/comments | 9 | 2020-05-01T08:09:24Z | 2020-10-16T10:09:15Z | https://github.com/kubernetes/kubernetes/issues/90666 | 610,627,092 | 90,666 |
[
"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**:
API server pa... | Kube-apiserver has timeout talking to etcd, probably due to etcd socket leak | https://api.github.com/repos/kubernetes/kubernetes/issues/90664/comments | 8 | 2020-05-01T04:56:05Z | 2020-05-11T23:55:25Z | https://github.com/kubernetes/kubernetes/issues/90664 | 610,562,681 | 90,664 |
[
"kubernetes",
"kubernetes"
] | # Progress <code>[2/6]</code>
- [X] APISnoop org-flow: [deleteCoreV1CollectionNamespacedPodTest.org](https://github.com/cncf/apisnoop/blob/master/tickets/k8s/deleteCoreV1CollectionNamespacedPodTest.org)
- [X] Test approval issue: [kubernetes/kubernetes#90663](https://github.com/kubernetes/kubernetes/issues/9066... | Add deleteCoreV1CollectionNamespacedPod Mock Test - +1 endpoint coverage | https://api.github.com/repos/kubernetes/kubernetes/issues/90663/comments | 4 | 2020-05-01T04:23:47Z | 2020-05-09T21:50:22Z | https://github.com/kubernetes/kubernetes/issues/90663 | 610,552,564 | 90,663 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
ie, when I add "- --v=4" to kube-proxy as flag after "--config" flag, it report an error and forbid this modification, however, it is ok when put it just after kubeproxy. It makes me confused.
does apiserver do this? and which port of a... | Which component guarantees that the modification of the configmap conforms to the configmap format? | https://api.github.com/repos/kubernetes/kubernetes/issues/90661/comments | 5 | 2020-05-01T01:35:47Z | 2020-07-29T12:59:53Z | https://github.com/kubernetes/kubernetes/issues/90661 | 610,501,210 | 90,661 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about flaky tests or jobs (pass or fail with no underlying change in code) in Kubernetes CI -->
**Which jobs are flaking**:
https://prow.k8s.io/view/gcs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_kind/1536/pull-kind-e2e-kubernetes/1255955923654938628
... | flake: [sig-node] RuntimeClass should reject a Pod requesting a RuntimeClass with an unconfigured handler | https://api.github.com/repos/kubernetes/kubernetes/issues/90653/comments | 5 | 2020-04-30T21:02:41Z | 2020-06-11T06:05:45Z | https://github.com/kubernetes/kubernetes/issues/90653 | 610,383,765 | 90,653 |
[
"kubernetes",
"kubernetes"
] | For external cloud provider - Kubelet setting the TaintExternalCloudProvider taint: https://github.com/kubernetes/kubernetes/blob/master/pkg/kubelet/kubelet_node_status.go#L266
The results in calling `initializeNode` function in cloud node-controller:
https://github.com/kubernetes/kubernetes/blob/5c276a451d64d161b2... | Reduce the number of calls to GCE API (for clusters on GCE) coming from cloud node-controller | https://api.github.com/repos/kubernetes/kubernetes/issues/90652/comments | 13 | 2020-04-30T18:51:21Z | 2020-09-22T12:12:24Z | https://github.com/kubernetes/kubernetes/issues/90652 | 610,307,751 | 90,652 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
`testing.Fatal()/FailNow()/SkipNow()/...` can only be used in test goroutine.
`t.Fatal()/Fatalf()/FailNow()` "[must be called from the goroutine running the test or benchmark function, not from other goroutines created during the test.](https://golang.org/pkg/testing/#T.FailNow)"
There are four ... | staging: test.Fatal() can only be used in test goroutine instead of its child | https://api.github.com/repos/kubernetes/kubernetes/issues/90651/comments | 9 | 2020-04-30T16:55:00Z | 2020-11-19T19:34:37Z | https://github.com/kubernetes/kubernetes/issues/90651 | 610,236,514 | 90,651 |
[
"kubernetes",
"kubernetes"
] | https://monitoring.prow.k8s.io/d/d69a91f76d8110d3e72885ee5ce8038e/tide-dashboard?orgId=1&from=now-30d&to=now
https://prow.k8s.io/tide-history?repo=kubernetes%2Fkubernetes&branch=master
Tide is continually retesting PR's but unable to merge them due to flakes or failures. Batches are more likely to encounter them... | Very few PRs have merged in the past few days | https://api.github.com/repos/kubernetes/kubernetes/issues/90647/comments | 11 | 2020-04-30T16:12:37Z | 2020-05-03T20:44:52Z | https://github.com/kubernetes/kubernetes/issues/90647 | 610,200,833 | 90,647 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
kube-proxy bi... | kube-proxy not respecting metricsBindAddress | https://api.github.com/repos/kubernetes/kubernetes/issues/90641/comments | 3 | 2020-04-30T13:11:31Z | 2020-04-30T15:11:30Z | https://github.com/kubernetes/kubernetes/issues/90641 | 609,966,597 | 90,641 |
[
"kubernetes",
"kubernetes"
] | install kubernetes with kubeadm, the version is 1.18.2, kubadm init failed in the master node wth lots of _node "master1" not found_ in /var/log/messages file.
`
● kubelet.service - kubelet: The Kubernetes Node Agent
Loaded: loaded (/etc/systemd/system/kubelet.service; enabled; vendor preset: disabled)
Drop... | kubelet.go:2267] node "master1" not found | https://api.github.com/repos/kubernetes/kubernetes/issues/90637/comments | 7 | 2020-04-30T09:49:53Z | 2020-05-10T12:17:27Z | https://github.com/kubernetes/kubernetes/issues/90637 | 609,770,943 | 90,637 |
[
"kubernetes",
"kubernetes"
] | /kind bug
/sig apps
/sig node
/sig scheduling
**What happened**:
We deployed a job with backofflimit 0, parallelism: 1, completions: 1 and enabled pod preemption and priority. However we found that sometimes when a pod is preempted, the status of the job which owns the preempted pod will be updated to active: 1,... | Job status updated succeeded when pod is preempted | https://api.github.com/repos/kubernetes/kubernetes/issues/90636/comments | 3 | 2020-04-30T07:45:26Z | 2020-05-02T15:32:38Z | https://github.com/kubernetes/kubernetes/issues/90636 | 609,677,652 | 90,636 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
types.go states that Container.SecurityContext applies to a Pod, which can be misleading since we already have PodSecurityContext.
`Security options the pod should run with.`
**What you expected to happen**:
Documentation states that it applies to container
**How to reproduce it (as minima... | Container API: document that SecurityContext applies to the Container instead of Pod | https://api.github.com/repos/kubernetes/kubernetes/issues/90634/comments | 11 | 2020-04-30T07:16:38Z | 2021-01-30T14:38:36Z | https://github.com/kubernetes/kubernetes/issues/90634 | 609,657,576 | 90,634 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
As decribed [here](https://kubernetes.io/docs/concepts/configuration/secret/#projection-of-secret-keys-to-specific-paths) and [here](https://kubernetes.io/docs/concepts/storage/volumes/#configmap), it is possible to present a configMap entry or a secret as a file to the applicati... | Allow to specify char encoding when mounting ConfigMaps as volumes | https://api.github.com/repos/kubernetes/kubernetes/issues/90633/comments | 7 | 2020-04-30T06:58:20Z | 2020-05-02T09:56:04Z | https://github.com/kubernetes/kubernetes/issues/90633 | 609,646,110 | 90,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**:
Working on ot... | Incomplete list of operations for admission webhook | https://api.github.com/repos/kubernetes/kubernetes/issues/90632/comments | 6 | 2020-04-30T04:50:38Z | 2020-05-09T01:27:53Z | https://github.com/kubernetes/kubernetes/issues/90632 | 609,573,786 | 90,632 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about flaky tests or jobs (pass or fail with no underlying change in code) in Kubernetes CI -->
**Which jobs are flaking**:
k8s.io/kubernetes/test/integration/scheduler.TestNominatedNodeCleanUp
**Which test(s) are flaking**:
- https://prow.k8s.io/vie... | TestNominatedNodeCleanUp flakes | https://api.github.com/repos/kubernetes/kubernetes/issues/90627/comments | 10 | 2020-04-30T02:58:47Z | 2020-05-15T09:47:54Z | https://github.com/kubernetes/kubernetes/issues/90627 | 609,529,067 | 90,627 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
PodIP validation for well-formedness was added in 1.16 in https://github.com/kubernetes/kubernetes/commit/54d42e6a658f84ea66593d3107f41db6931a5fbf
However, it was added to the ValidatePod() validation method, which is called for create/update requests to the main pod resource, not status update r... | status.podIP validation is not run during pod/status updates | https://api.github.com/repos/kubernetes/kubernetes/issues/90625/comments | 2 | 2020-04-30T02:48:53Z | 2020-05-01T02:30:08Z | https://github.com/kubernetes/kubernetes/issues/90625 | 609,524,921 | 90,625 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
Currently, PostStart and PreStop hook are not supporting taking arguments and ENV variables like a container does. I'd like to add this functionality into them.
**Why is this needed**:
This feature c... | Add support for using parameters and ENV variables to PostStart/PreStop handler | https://api.github.com/repos/kubernetes/kubernetes/issues/90624/comments | 11 | 2020-04-30T02:01:22Z | 2020-10-06T05:10:41Z | https://github.com/kubernetes/kubernetes/issues/90624 | 609,503,618 | 90,624 |
[
"kubernetes",
"kubernetes"
] | a modifying admission webhook that produces this patch:
```
{
"op": "add",
"path": "/metadata/annotations/foo"
"value": "bar",
}
```
fails when using `kubectl run`
```
kubectl run --generator=run-pod/v1 --attach test-deploy --image=busybox --labels="team=sre,project=datadog" ls
Error from server... | Admission that tries to add an annotation fails when annotations is nil | https://api.github.com/repos/kubernetes/kubernetes/issues/90623/comments | 8 | 2020-04-30T01:29:54Z | 2020-04-30T13:56:39Z | https://github.com/kubernetes/kubernetes/issues/90623 | 609,490,157 | 90,623 |
[
"kubernetes",
"kubernetes"
] | # Progress <code>[2/6]</code>
- [X] APISnoop org-flow: [deleteCoreV1CollectionNamespacedEventTest.org](https://github.com/cncf/apisnoop/blob/master/tickets/k8s/deleteCoreV1CollectionNamespacedEventTest.org)
- [X] Test approval issue: [kubernetes/kubernetes#90619](https://github.com/kubernetes/kubernetes/issues/... | Add deleteCoreV1CollectionNamespacedEvent Test - +1 endpoint coverage | https://api.github.com/repos/kubernetes/kubernetes/issues/90619/comments | 6 | 2020-04-29T23:20:58Z | 2020-05-09T21:51:35Z | https://github.com/kubernetes/kubernetes/issues/90619 | 609,429,667 | 90,619 |
[
"kubernetes",
"kubernetes"
] | When there is not any node fits for an incoming Pod, scheduler firstly tries to [put it to internal unschedulableQ or backoffQ](https://github.com/kubernetes/kubernetes/blob/429aefa2e6e1d41cab892703733cf6fdd9919561/pkg/scheduler/factory.go#L504). And right after that, scheduler [updates the Pod's status as unschedulabl... | Unnecessary scheduling attempt | https://api.github.com/repos/kubernetes/kubernetes/issues/90616/comments | 5 | 2020-04-29T22:44:35Z | 2020-05-17T02:00:07Z | https://github.com/kubernetes/kubernetes/issues/90616 | 609,410,765 | 90,616 |
[
"kubernetes",
"kubernetes"
] | If we want to change make server-side apply the default for `kubectl apply`, we need to minimize the surprise and roadblocks for users. To do that, we need to investigate what the differences between CSA and SSA are and make sure that we have proper testing to detect these differences and prevent new differences from b... | Investigate and test differences between Client-side apply and Server-side apply | https://api.github.com/repos/kubernetes/kubernetes/issues/90614/comments | 9 | 2020-04-29T21:16:26Z | 2020-09-26T23:33:43Z | https://github.com/kubernetes/kubernetes/issues/90614 | 609,365,430 | 90,614 |
[
"kubernetes",
"kubernetes"
] | **What happened**: I have created Azure cluster with the following conf file:
```
{
"cloud":"AzurePublicCloud",
"tenantId":<tenantID>,
"subscriptionId":<subscriptionID>,
"aadClientId":<clientID>,
"aadClientSecret":<clientSecret>,
"resourceGroup":"testCluster-rg",
"location":"eastus",
"vmType":... | Azure LoadBalancer service not accessible due to missing inbound rule in NSG | https://api.github.com/repos/kubernetes/kubernetes/issues/90611/comments | 1 | 2020-04-29T20:33:27Z | 2020-05-01T08:50:30Z | https://github.com/kubernetes/kubernetes/issues/90611 | 609,340,224 | 90,611 |
[
"kubernetes",
"kubernetes"
] | https://github.com/kubedb/issues/issues/739
[`ManagedFieldsEntry. FieldsType`](https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/apimachinery/pkg/apis/meta/v1/types.go#L1123) is not defaulted and can be dropped by pre 1.15 versions of client-go (since the field didn't exist at that time). Unfor... | Updates with client-go dropping ManagedFieldsEntry.FieldsType breaks | https://api.github.com/repos/kubernetes/kubernetes/issues/90610/comments | 14 | 2020-04-29T20:01:07Z | 2021-09-01T20:36:47Z | https://github.com/kubernetes/kubernetes/issues/90610 | 609,321,408 | 90,610 |
[
"kubernetes",
"kubernetes"
] | **What happened**: We attempted to remove a `serviceAccount` from a `StatefulSet` by removing the `serviceAccount` from the `spec.template` of the `StatefulSet`, and by removing the `ServiceAccount` itself.
However, due to the unfixed https://github.com/kubernetes/kubernetes/issues/72519, while the removal of the `S... | StatefulSet continues to try to create pods with old spec even after spec updated | https://api.github.com/repos/kubernetes/kubernetes/issues/90607/comments | 6 | 2020-04-29T19:31:00Z | 2020-07-13T14:56:14Z | https://github.com/kubernetes/kubernetes/issues/90607 | 609,303,913 | 90,607 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
Add a .import-restrictions file to cmd/cloud-controller-manager to prevent new imports to k8s.io/kubernetes.
**Why is this needed**:
As part of https://github.com/kubernetes/cloud-provider/issues/29 and the effort to remove cloud providers, we are moving cmd/cloud-controller-ma... | Add .import-restrictions file to cmd/cloud-controller-manager | https://api.github.com/repos/kubernetes/kubernetes/issues/90600/comments | 3 | 2020-04-29T15:09:26Z | 2020-05-08T00:19:43Z | https://github.com/kubernetes/kubernetes/issues/90600 | 609,134,401 | 90,600 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
We upgraded cert-manager from 0.13 to 0.14 which included moving the CRD version from v1alpha2 to v1alpha3.
At the time, resourcequota_controller picked up the change.
> I0428 13:18:27.284740 1 resource_quota_controller.go:433] syncing resource quota controller with updated resources from di... | Resourcequota not updating due to broken webhook | https://api.github.com/repos/kubernetes/kubernetes/issues/90597/comments | 7 | 2020-04-29T13:48:40Z | 2020-09-27T21:55:55Z | https://github.com/kubernetes/kubernetes/issues/90597 | 609,073,235 | 90,597 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Trying to leverage the inter-pod affinity [concept](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#inter-pod-affinity-and-anti-affinity).
The pod with the affinity property fails almost consistently to collocate with the pod described in the `labelSelector`
**What you e... | Preferred inter-pod affinity rarely collocates pods | https://api.github.com/repos/kubernetes/kubernetes/issues/90595/comments | 2 | 2020-04-29T10:52:16Z | 2020-04-29T12:42:25Z | https://github.com/kubernetes/kubernetes/issues/90595 | 608,959,087 | 90,595 |
[
"kubernetes",
"kubernetes"
] | **What happened**: after a midnight power down, I restarted my cluster's host machine and all of it's nodes. But seems like working nodes WRONGLY tried to reach the master node (and especially the API) through the CNI interface, which was not ready yet. This behavior was even on CNI-plugin pods (I use `kube-router` bec... | Cluster recovering failure | https://api.github.com/repos/kubernetes/kubernetes/issues/90594/comments | 26 | 2020-04-29T10:20:41Z | 2022-10-13T22:51:17Z | https://github.com/kubernetes/kubernetes/issues/90594 | 608,940,728 | 90,594 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
- We had a NFS-server.
- Some pods were using this share
- NFS-server has died
- Pods were removed forcefully (with `--force --grace-period 0`)
- Kubelet was stuck operations for any other pods, eg. when you create new pods they are stuck on `Pending`, if you do `systemctl restart kubelet`, th... | Kubelet is hanging due broken NFS share | https://api.github.com/repos/kubernetes/kubernetes/issues/90593/comments | 22 | 2020-04-29T09:50:23Z | 2022-09-18T12:00:33Z | https://github.com/kubernetes/kubernetes/issues/90593 | 608,922,173 | 90,593 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
I would like the following network policy to be valid:
```
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
name: test-network-policy
namespace: default
spec:
podSelector:
matchLabels:
role: db
policyTypes:
- Ingress
ingress:
- fr... | NetworkPolicy allow traffic from nodes by label | https://api.github.com/repos/kubernetes/kubernetes/issues/90590/comments | 4 | 2020-04-29T08:58:00Z | 2020-04-30T14:28:22Z | https://github.com/kubernetes/kubernetes/issues/90590 | 608,890,143 | 90,590 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
in some of my... | pods in some project recreate every minute randomly | https://api.github.com/repos/kubernetes/kubernetes/issues/90589/comments | 13 | 2020-04-29T08:47:10Z | 2020-10-03T10:04:54Z | https://github.com/kubernetes/kubernetes/issues/90589 | 608,883,571 | 90,589 |
[
"kubernetes",
"kubernetes"
] | https://github.com/kubernetes/kubernetes/blob/0c3c2cd6ac8c9ffefc38f9746034e546331b9cd6/pkg/kubelet/kuberuntime/kuberuntime_manager.go#L434
The comment said 'Needs to create a new sandbox when readySandboxCount > 1 or the ready sandbox is not "the latest one".'
but the sandboxStatus got here is the first one. | Check podSandboxChanged with wrong sandboxStatus | https://api.github.com/repos/kubernetes/kubernetes/issues/90588/comments | 26 | 2020-04-29T08:27:43Z | 2020-12-11T21:12:01Z | https://github.com/kubernetes/kubernetes/issues/90588 | 608,872,218 | 90,588 |
[
"kubernetes",
"kubernetes"
] | **Which jobs are failing**:
> ci-cluster-api-provider-gcp-make-conformance-v1alpha3-k8s-ci-artifacts
**Which test(s) are failing**:
> Overall
**Since when has it been failing**:
> 04-28 13:54 PDT
**Testgrid link**:
https://testgrid.k8s.io/sig-release-master-informing#capg-conformance-v1alpha3-k8s-mas... | [Failing Test] capg-conformance-v1alpha3-k8s-master (ci-cluster-api-provider-gcp-make-conformance-v1alpha3-k8s-ci-artifacts) | https://api.github.com/repos/kubernetes/kubernetes/issues/90587/comments | 3 | 2020-04-29T07:11:31Z | 2020-04-29T12:05:23Z | https://github.com/kubernetes/kubernetes/issues/90587 | 608,829,953 | 90,587 |
[
"kubernetes",
"kubernetes"
] | **Which jobs are failing**:
> gce-cos-master-serial (ci-kubernetes-e2e-gci-gce-serial)
**Which test(s) are failing**:
> Overall
**Since when has it been failing**:
> 04-28 17:07 PDT
**Testgrid link**:
https://testgrid.k8s.io/sig-release-master-informing#gce-cos-master-serial
**Reason for failure**... | [Flaky Test] gce-cos-master-serial (ci-kubernetes-e2e-gci-gce-serial) | https://api.github.com/repos/kubernetes/kubernetes/issues/90586/comments | 17 | 2020-04-29T07:11:28Z | 2020-05-12T12:52:13Z | https://github.com/kubernetes/kubernetes/issues/90586 | 608,829,927 | 90,586 |
[
"kubernetes",
"kubernetes"
] | Hi everyone,
Please help me, I fount this log in kube API server docker container.
Seem to be the api server has been crashed when trying accessing CustomResources of a CRD.
I tried to restart the kube-api-server but it isn't work
```
E0429 05:26:32.479959 1 runtime.go:78] Observed a panic: "invalid memory a... | Kube API Server has been crash, cannot use kubectl | https://api.github.com/repos/kubernetes/kubernetes/issues/90585/comments | 12 | 2020-04-29T05:27:57Z | 2021-10-26T12:33:44Z | https://github.com/kubernetes/kubernetes/issues/90585 | 608,788,016 | 90,585 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
We are using the e2e framework to implement e2e tests for our extensions (device plugins). We noticed that running the tests basically destroys the cluster setup by deleting everything in custom namespaces:
Very basic (single node) cluster setup with node-feature-discovery installed in node-fea... | e2e framework deletes all namespaces | https://api.github.com/repos/kubernetes/kubernetes/issues/90584/comments | 4 | 2020-04-29T04:59:44Z | 2020-04-29T10:38:38Z | https://github.com/kubernetes/kubernetes/issues/90584 | 608,778,610 | 90,584 |
Subsets and Splits
Unique Owner-Repo Count
Counts the number of unique owner-repos in the dataset, providing a basic understanding of diverse repositories.