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"
] | # Identifying an untested feature Using APISnoop
According to this APIsnoop query, there are still some remaining Service endpoints which are untested.
```sql-mode
SELECT
operation_id,
-- k8s_action,
-- path,
-- description,
kind
FROM untested_stable_core_endpoints
where path not like '%volu... | Add ServiceStatus resource lifecycle test - +2 endpoint coverage | https://api.github.com/repos/kubernetes/kubernetes/issues/89135/comments | 5 | 2020-03-16T00:38:03Z | 2020-05-09T21:56:01Z | https://github.com/kubernetes/kubernetes/issues/89135 | 581,895,901 | 89,135 |
[
"kubernetes",
"kubernetes"
] | **Which jobs are failing**:
`aks-engine-azure-1-18-windows (ci-kubernetes-e2e-aks-engine-azure-1-18-windows )`
**Which test(s) are failing**:
`[sig-windows] [Feature:Windows] Cpu Resources Container limits should not be exceeded after waiting 2 minutes`
**Since when has it been failing**:
`14th March 14:14 PDT... | [Failing Test] aks-engine-azure-1-18-windows (ci-kubernetes-e2e-aks-engine-azure-1-18-windows ) | https://api.github.com/repos/kubernetes/kubernetes/issues/89134/comments | 10 | 2020-03-15T17:16:12Z | 2020-03-27T11:35:49Z | https://github.com/kubernetes/kubernetes/issues/89134 | 581,750,060 | 89,134 |
[
"kubernetes",
"kubernetes"
] | when installed k8s v1.16.7,I checked pods and the result is as follow:
**kubectl logs kube-controller-manager-node1 -n kube-system**
I0315 09:28:28.488397 1 shared_informer.go:197] Waiting for caches to sync for garbage collector
I0315 09:28:28.570006 1 shared_informer.go:204] Caches are synced for ce... | Failed to update statusUpdateNeeded field in actual state of world: Failed to set statusUpdateNeeded to needed true, because nodeName=" | https://api.github.com/repos/kubernetes/kubernetes/issues/89132/comments | 5 | 2020-03-15T10:38:41Z | 2020-04-12T21:42:50Z | https://github.com/kubernetes/kubernetes/issues/89132 | 581,617,418 | 89,132 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
I'd like the team to publish a security bulletin when a vulnerability is found.
I need information such as below.
- CVSS v3 score or Severity <= This is what I want most.
- Affected versions
- Patched... | Create Security Bulletins page | https://api.github.com/repos/kubernetes/kubernetes/issues/89130/comments | 3 | 2020-03-15T03:09:01Z | 2020-03-24T14:02:54Z | https://github.com/kubernetes/kubernetes/issues/89130 | 581,483,568 | 89,130 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
Create or replace if exist, for a configmap.
To preserve backward compatibility, a new flag can be added (with default being same behavior as now)
**Why is this needed**:
Seems basic, but I need it s... | [Feature] [kubectl] create or replace configmap | https://api.github.com/repos/kubernetes/kubernetes/issues/89129/comments | 3 | 2020-03-15T01:37:46Z | 2020-04-20T18:36:55Z | https://github.com/kubernetes/kubernetes/issues/89129 | 581,456,570 | 89,129 |
[
"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**:
```
Moun... | Kubernetes thinks that a file is not a file | https://api.github.com/repos/kubernetes/kubernetes/issues/89127/comments | 8 | 2020-03-14T23:09:35Z | 2020-08-14T16:42:07Z | https://github.com/kubernetes/kubernetes/issues/89127 | 581,411,609 | 89,127 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
IPVS dont work in EKS 1.14
**What you expected to happen**:
I've deployed kube-proxy with --proxy-mode=ipvs flag, but kube-proxy keeps running with iptables.
Here the snippet of kube-proxy daemonset yaml, i use kube-proxy:v1.12.6 image
> containers:
- command:
- /bin/sh
... | IPVS dont work in EKS 1.14 | https://api.github.com/repos/kubernetes/kubernetes/issues/89126/comments | 3 | 2020-03-14T21:21:25Z | 2020-03-14T22:59:37Z | https://github.com/kubernetes/kubernetes/issues/89126 | 581,377,232 | 89,126 |
[
"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 ro... | `kubectl rollout history` command not showing `kubectl apply` history | https://api.github.com/repos/kubernetes/kubernetes/issues/89125/comments | 9 | 2020-03-14T18:34:46Z | 2021-01-23T18:04:22Z | https://github.com/kubernetes/kubernetes/issues/89125 | 581,320,321 | 89,125 |
[
"kubernetes",
"kubernetes"
] | So I don't forget.
kubernetes/client-go#155
windmilleng/tilt#2702
* Check how many authenticators are created.
* Maybe look at interactive login. | Verify behavior of exec auth plugin when credentials expire | https://api.github.com/repos/kubernetes/kubernetes/issues/89114/comments | 7 | 2020-03-13T18:36:11Z | 2020-11-15T04:45:34Z | https://github.com/kubernetes/kubernetes/issues/89114 | 580,775,294 | 89,114 |
[
"kubernetes",
"kubernetes"
] | When a pod is deleted before nodePublish is done, but after nodeStage is done, it will not be unmounted by kubelet. This causes stale mounts on host to be left around. | Stale mounts are left if pod is deleted before nodePublish is completed | https://api.github.com/repos/kubernetes/kubernetes/issues/89112/comments | 13 | 2020-03-13T17:25:37Z | 2020-08-14T23:48:25Z | https://github.com/kubernetes/kubernetes/issues/89112 | 580,742,058 | 89,112 |
[
"kubernetes",
"kubernetes"
] | I was trying to copy files from pod to my host machine using 'kubectl cp' command and figured out that when we run the copy command it zips the files using 'tar' utility first and then copy them to host machine. In one of use case I found a bug here, where tar process started but the copy didn't finished. Here I wrote... | unwanted tar process getting created inside a pod and consuming lot of CPU | https://api.github.com/repos/kubernetes/kubernetes/issues/89110/comments | 6 | 2020-03-13T14:58:00Z | 2020-09-26T15:25:41Z | https://github.com/kubernetes/kubernetes/issues/89110 | 580,655,165 | 89,110 |
[
"kubernetes",
"kubernetes"
] | As suggested by @dims in #sig-network Slack channel, ipvs was extracted out of docker/libnetwork package to its own repo in https://github.com/moby/ipvs and it should be replaced also in the parts of code using ipvs to the new library location.
The idea is to replace the parts using the IPVS library to use github.co... | Migrate ipvs library from docker/libnetwork/ipvs to moby/ipvs | https://api.github.com/repos/kubernetes/kubernetes/issues/89109/comments | 3 | 2020-03-13T14:07:06Z | 2020-03-30T22:50:41Z | https://github.com/kubernetes/kubernetes/issues/89109 | 580,623,458 | 89,109 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
During a cluster upgrade from `v1.17.2` to `v1.17.4`, the following misleading non-fatal warning was emitted:
`[upgrade/etcd] Non fatal issue encountered during upgrade: the desired etcd version for this Kubernetes version "v1.17.4" is "3.4.3-0", but the current etcd version is "3.4.3". Won't dow... | [kubeadm upgrade] Misleading component version warning | https://api.github.com/repos/kubernetes/kubernetes/issues/89108/comments | 4 | 2020-03-13T12:14:14Z | 2020-03-13T18:03:35Z | https://github.com/kubernetes/kubernetes/issues/89108 | 580,563,137 | 89,108 |
[
"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!
/sig cli
/kind bug
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happe... | error: unexpected error when reading response body. | https://api.github.com/repos/kubernetes/kubernetes/issues/89107/comments | 8 | 2020-03-13T10:27:15Z | 2024-05-31T06:36:54Z | https://github.com/kubernetes/kubernetes/issues/89107 | 580,507,554 | 89,107 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
Some instrumentation on tests or on the reporting tools that allow identifying stack traces on the logs.
**Why is this needed**:
Stack traces are meaningful for developers but meaningless for oper... | Stack Traces detector for tests | https://api.github.com/repos/kubernetes/kubernetes/issues/89103/comments | 7 | 2020-03-13T08:26:15Z | 2020-08-21T18:25:59Z | https://github.com/kubernetes/kubernetes/issues/89103 | 580,445,345 | 89,103 |
[
"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/
-->
I'm applying yaml for pods deployme... | Pods not updating after deployment. Kubectl rollout status not showing any status | https://api.github.com/repos/kubernetes/kubernetes/issues/89102/comments | 4 | 2020-03-13T07:53:54Z | 2020-03-13T23:04:21Z | https://github.com/kubernetes/kubernetes/issues/89102 | 580,431,139 | 89,102 |
[
"kubernetes",
"kubernetes"
] | I'm applying yaml for pods deployment. And after that applying "kubectl rollout status" to monitor rollout but somehow it's not showing ay status and finishing the deployment script.
Previously it's used to work.
So, because of the above reason, my pods are not getting updated with the latest changes. | Pods not updating after deployment. Kubectl rollout status not showing any status | https://api.github.com/repos/kubernetes/kubernetes/issues/89101/comments | 7 | 2020-03-13T07:40:48Z | 2020-04-12T21:42:23Z | https://github.com/kubernetes/kubernetes/issues/89101 | 580,425,475 | 89,101 |
[
"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/
-->
without internet
image:xxx:latest
... | imagePullPolicy not work,always try pull from repository | https://api.github.com/repos/kubernetes/kubernetes/issues/89100/comments | 5 | 2020-03-13T04:22:43Z | 2021-09-07T16:03:40Z | https://github.com/kubernetes/kubernetes/issues/89100 | 580,361,874 | 89,100 |
[
"kubernetes",
"kubernetes"
] | Container in a Deployment exits on error
apiVersion: v1
kind: Pod
metadata:
name: init-container
spec:
containers:
- name: application-container
image: alpine
command: ['sh', '-c', 'if [ -f /work/sharedfile.txt ]; then sleep 99999; else exit; fi']
volumeMounts:
- name: workdir-volume... | Initcontainer-exit on error | https://api.github.com/repos/kubernetes/kubernetes/issues/89099/comments | 3 | 2020-03-13T02:47:20Z | 2020-03-15T16:37:51Z | https://github.com/kubernetes/kubernetes/issues/89099 | 580,336,463 | 89,099 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
After deleting a namespace, the related ClusterRoleBinding didn't get deleted as well.
**What you expected to happen**:
I expected that related ClusterRoleBinding should be deleted after deleting a namespace.
**How to reproduce it (as minimally and precisely as possible)**:
1. Create a... | Deleting a namespace doesn't delete related ClusterRoleBinding | https://api.github.com/repos/kubernetes/kubernetes/issues/89098/comments | 3 | 2020-03-13T01:22:31Z | 2020-03-13T15:17:57Z | https://github.com/kubernetes/kubernetes/issues/89098 | 580,313,830 | 89,098 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
Migrate the content currently at https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#resources to a new URL inside https://k8s.io/docs/reference/
... | Migrate API conventions to https://k8s.io/docs/reference/ | https://api.github.com/repos/kubernetes/kubernetes/issues/89094/comments | 17 | 2020-03-12T19:24:54Z | 2021-05-07T20:01:47Z | https://github.com/kubernetes/kubernetes/issues/89094 | 580,168,245 | 89,094 |
[
"kubernetes",
"kubernetes"
] | The scheduler does not properly calculate pod requests for a resource as `max(max(initContainers),sum(containers))` - it ignores init containers completely in `ResourceAllocationPriority`. This would allow a workload to get "free" scheduling above the limit of containers (mitigated by quota, which calculates this prop... | Init container resource usage not properly prioritized in scheduler | https://api.github.com/repos/kubernetes/kubernetes/issues/89092/comments | 9 | 2020-03-12T18:28:50Z | 2020-09-14T05:25:05Z | https://github.com/kubernetes/kubernetes/issues/89092 | 580,139,105 | 89,092 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
Hi all,
When binding a volume, whether it is a hostPath or a volume with Pvc, we can express a subPathExpr under it such as (source https://kubernetes.io/docs/concepts/storage/volumes/#using-subpath):
```
apiVersion: v1
kind: Pod
metad... | Add subPath(Expr) under volume for dynamic volume | https://api.github.com/repos/kubernetes/kubernetes/issues/89091/comments | 6 | 2020-03-12T18:26:06Z | 2020-08-10T10:02:29Z | https://github.com/kubernetes/kubernetes/issues/89091 | 580,137,072 | 89,091 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**With CPU Manager feature enabled, if a POD/Container is launched, there should be a to identify which CPU IDs have been assigned to that container so that processes inside the container can use pthread_setaffinity() calls**:
**pthreads o... | CPUManager feature: processes inside the containers should get the exact list of CPUs allocated | https://api.github.com/repos/kubernetes/kubernetes/issues/89087/comments | 8 | 2020-03-12T14:53:14Z | 2020-08-27T17:46:39Z | https://github.com/kubernetes/kubernetes/issues/89087 | 579,996,771 | 89,087 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
After movin... | kubectl patch fails to update node's spec.providerId | https://api.github.com/repos/kubernetes/kubernetes/issues/89085/comments | 1 | 2020-03-12T13:59:28Z | 2020-03-12T14:37:58Z | https://github.com/kubernetes/kubernetes/issues/89085 | 579,958,899 | 89,085 |
[
"kubernetes",
"kubernetes"
] | My Gateway file is as
apiVersion: networking.istio.io/v1alpha3
kind: Gateway
metadata:
name: my-gateway-secure
namespace: myapp
spec:
selector:
istio: ingressgateway # use istio default controller
servers:
- port:
number: 443
name: https
protocol: HTTPS
tls:
mod... | You're speaking plain HTTP to an SSL-enabled server port. | https://api.github.com/repos/kubernetes/kubernetes/issues/89084/comments | 2 | 2020-03-12T13:55:57Z | 2020-04-02T18:26:25Z | https://github.com/kubernetes/kubernetes/issues/89084 | 579,956,484 | 89,084 |
[
"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**:
Using [GetV... | IntStr GetValueFromIntOrPercent assumes all strings are percentages | https://api.github.com/repos/kubernetes/kubernetes/issues/89082/comments | 18 | 2020-03-12T12:06:33Z | 2020-10-06T03:00:20Z | https://github.com/kubernetes/kubernetes/issues/89082 | 579,893,010 | 89,082 |
[
"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... | Massive managedFields in yaml file | https://api.github.com/repos/kubernetes/kubernetes/issues/89080/comments | 11 | 2020-03-12T10:40:33Z | 2020-05-11T04:16:47Z | https://github.com/kubernetes/kubernetes/issues/89080 | 579,846,185 | 89,080 |
[
"kubernetes",
"kubernetes"
] | **Which jobs are flaking**:
pull-kubernetes-e2e-kind
**Which test(s) are flaking**:
should never report success for a pending container
**Testgrid link**:
https://prow.k8s.io/view/gcs/kubernetes-jenkins/pr-logs/pull/88849/pull-kubernetes-e2e-kind/1237903275018162177
**Reason for failure**:
```
Mar 12 01:1... | 'Pod Container Status should never report success for a pending container' is flaky | https://api.github.com/repos/kubernetes/kubernetes/issues/89077/comments | 2 | 2020-03-12T01:29:56Z | 2020-03-12T04:24:53Z | https://github.com/kubernetes/kubernetes/issues/89077 | 579,636,107 | 89,077 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
It would be great to give k8s administrator more control over TLS settings - TLS timeout in particular - by making these parameters configurable, for:
* api -> etcd communication https://github.com/k... | Make TLS timeout configurable for `kubelet->api` and `api->etcd` communications | https://api.github.com/repos/kubernetes/kubernetes/issues/89076/comments | 11 | 2020-03-11T22:52:15Z | 2020-11-28T19:05:29Z | https://github.com/kubernetes/kubernetes/issues/89076 | 579,589,468 | 89,076 |
[
"kubernetes",
"kubernetes"
] | Deployed the below yaml file.
```
apiVersion: apps/v1
kind: Deployment
metadata:
name: test
namespace: test
spec:
replicas: 1
selector:
matchLabels:
app: container
template:
metadata:
labels:
app: container
spec:
containers:
- name: image1
... | Deployed image in the container status does not match with image in spec | https://api.github.com/repos/kubernetes/kubernetes/issues/89075/comments | 6 | 2020-03-11T22:44:34Z | 2020-08-09T04:33:29Z | https://github.com/kubernetes/kubernetes/issues/89075 | 579,586,725 | 89,075 |
[
"kubernetes",
"kubernetes"
] | - [x] [mock ticket](#)
- [x] [issue created](https://github.com/kubernetes/kubernetes/issues/89071)
- [x] [PR created](https://github.com/kubernetes/kubernetes/pull/90193)
- [ ] Promotion created
# Identifying an untested feature Using APISnoop
According to this APIsnoop query, there are still some remaining S... | Write CoreV1ServiceAccount resource lifecycle test+promote - +3 | https://api.github.com/repos/kubernetes/kubernetes/issues/89071/comments | 6 | 2020-03-11T22:10:41Z | 2020-05-09T21:41:52Z | https://github.com/kubernetes/kubernetes/issues/89071 | 579,574,399 | 89,071 |
[
"kubernetes",
"kubernetes"
] | There is no mechanism today to prevent abusive eviction loops (controller recreates a pod that was just evicted). #89067 seems to indicate that the kubelet and the controller will just fight until the controller stops. It seems reasonable that an eviction decision should perform some rate limit on subsequent pods fro... | Kubelet has no rate controls after a pod was evicted | https://api.github.com/repos/kubernetes/kubernetes/issues/89068/comments | 11 | 2020-03-11T20:30:12Z | 2024-12-18T18:55:56Z | https://github.com/kubernetes/kubernetes/issues/89068 | 579,527,734 | 89,068 |
[
"kubernetes",
"kubernetes"
] | The SS controller appears to go into a very tight loop when the `Should recreate evicted statefulset` e2e test runs. The controller should go into backoff after an eviction for that pod instead of hammering the node.
```
I0311 16:27:00.916503 1968 kubelet.go:1913] SyncLoop (ADD, "api"): "ss-0_e2e-statefulset-1... | Stateful set controller does not appear to backoff when pods are evicted | https://api.github.com/repos/kubernetes/kubernetes/issues/89067/comments | 13 | 2020-03-11T20:24:39Z | 2023-04-06T05:38:34Z | https://github.com/kubernetes/kubernetes/issues/89067 | 579,525,002 | 89,067 |
[
"kubernetes",
"kubernetes"
] | **Which jobs are flaking**:
* pull-kubernetes-e2e-kind
* pull-kubernetes-e2e-kind-ipv6
**Which test(s) are flaking**:
* [sig-storage] In-tree Volumes [Driver: emptydir] [Testpattern: Inline-volume (default fs)] subPath should support non-existent path
* [sig-storage] In-tree Volumes [Driver: hostPathSymlink] [... | failed to create containerd task: failed to start io pipe copy: unable to copy pipes: containerd-shim: opening w/o fifo | https://api.github.com/repos/kubernetes/kubernetes/issues/89064/comments | 9 | 2020-03-11T19:26:26Z | 2021-02-16T14:18:16Z | https://github.com/kubernetes/kubernetes/issues/89064 | 579,493,352 | 89,064 |
[
"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 cannot c... | Cannot set the eventTime field when creating/updating Events | https://api.github.com/repos/kubernetes/kubernetes/issues/89062/comments | 13 | 2020-03-11T18:57:30Z | 2025-03-04T21:22:05Z | https://github.com/kubernetes/kubernetes/issues/89062 | 579,478,841 | 89,062 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Create a new cluster with auto-resize, then follow steps to configure autoscale for a pod : https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough/
Then trigger load on that pod :
```
gcloud container clusters create example-cluster --zone northamerica-northeast... | Cluster does not autoscale to minSize after autoscaleUp | https://api.github.com/repos/kubernetes/kubernetes/issues/89058/comments | 6 | 2020-03-11T18:00:32Z | 2020-08-09T14:43:28Z | https://github.com/kubernetes/kubernetes/issues/89058 | 579,447,589 | 89,058 |
[
"kubernetes",
"kubernetes"
] | **Which jobs are failing**:
`verify-1.18 (ci-kubernetes-verify-beta)`
**Since when has it been failing**:
`11 March 00:56 PDT`
**Testgrid link**:
https://testgrid.k8s.io/sig-release-1.18-blocking#verify-1.18
**Reason for failure**:
see https://prow.k8s.io/view/gcs/kubernetes-jenkins/logs/ci-kubernetes-veri... | [Flaking Test] verify-1.18 (ci-kubernetes-verify-beta) | https://api.github.com/repos/kubernetes/kubernetes/issues/89052/comments | 9 | 2020-03-11T14:48:22Z | 2020-03-27T11:43:26Z | https://github.com/kubernetes/kubernetes/issues/89052 | 579,320,198 | 89,052 |
[
"kubernetes",
"kubernetes"
] | **Which jobs are failing**:
`gce-cos-1.18-scalability-100 (ci-kubernetes-e2e-gci-gce-scalability-beta )`
**Since when has it been failing**:
`10th March 05:01 PDT`
**Testgrid link**:
https://testgrid.k8s.io/sig-release-1.18-blocking#gce-cos-1.18-scalability-100
**Reason for failure**:
see https://prow.k8s.... | [Failing Test] gce-cos-.*-scalability tests are failing since 03/06 | https://api.github.com/repos/kubernetes/kubernetes/issues/89051/comments | 14 | 2020-03-11T14:43:52Z | 2020-04-14T08:01:12Z | https://github.com/kubernetes/kubernetes/issues/89051 | 579,316,910 | 89,051 |
[
"kubernetes",
"kubernetes"
] | **Which jobs are failing**:
`build-packages-rpms (ci-release-build-packages-rpms)`
**Since when has it been failing**:
`10th March 19:44 PDT`
**Testgrid link**:
https://testgrid.k8s.io/sig-release-master-informing#build-packages-rpms
**Reason for failure**:
```console
time="2020-03-11T10:46:41Z" level=in... | [Failing Test] build-packages-rpms (ci-release-build-packages-rpms) | https://api.github.com/repos/kubernetes/kubernetes/issues/89050/comments | 5 | 2020-03-11T14:36:38Z | 2020-03-11T23:19:47Z | https://github.com/kubernetes/kubernetes/issues/89050 | 579,311,631 | 89,050 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
nodelocaldns pod does not work properly on m5.12xlarge instance. it does work on m4.4xlarge.
the logs of the pod:
[ERROR] plugin/errors: 2 xxxx.ec2.internal. A: dial tcp 10.0.0.2:53: i/o timeout
[ERROR] plugin/errors: 2 xxxx.ec2.internal. A: dial tcp 10.0.0.2:53: i/o timeout
[ERROR] plugin/... | nodelocaldns does not work on m5.12xlarge aws instances | https://api.github.com/repos/kubernetes/kubernetes/issues/89049/comments | 5 | 2020-03-11T14:18:35Z | 2020-08-09T11:40:27Z | https://github.com/kubernetes/kubernetes/issues/89049 | 579,298,809 | 89,049 |
[
"kubernetes",
"kubernetes"
] | **THIS IS THE THIRD TIME FOR CREATING THIS ISSUE!
The two previous ones:
https://github.com/kubernetes/kubernetes/issues/73140
https://github.com/kubernetes/kubernetes/issues/32987**
**What happened**:
I created a service for my microservice in helm. It is a NodePort type. I specified the nodePort, but after I... | Adding an already deleted node port to service shows already acquired error | https://api.github.com/repos/kubernetes/kubernetes/issues/89042/comments | 4 | 2020-03-11T12:48:40Z | 2020-03-12T04:43:12Z | https://github.com/kubernetes/kubernetes/issues/89042 | 579,239,803 | 89,042 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
* If a pod's priority is lowest(e.g. there is three priroites in cluster: 10, 20 and 30, and the pod's priority is 10), it could not preempt any other pods, then we could skip trying preemption for it, ... | Optimization for scheduler preemption | https://api.github.com/repos/kubernetes/kubernetes/issues/89036/comments | 47 | 2020-03-11T09:23:59Z | 2022-07-02T02:37:20Z | https://github.com/kubernetes/kubernetes/issues/89036 | 579,118,820 | 89,036 |
[
"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**:
Parameters, a... | changes in config.yaml for kubelet have no effect | https://api.github.com/repos/kubernetes/kubernetes/issues/89035/comments | 11 | 2020-03-11T09:09:35Z | 2020-03-16T22:36:23Z | https://github.com/kubernetes/kubernetes/issues/89035 | 579,110,548 | 89,035 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Pluralization logic in the client generator in api/machinery is too simplistic. For an example CRD `FabricGateway` the pluralised generated client is `FabricGatewaies` whereas the actual is `FabricGateways`.
**What you expected to happen**:
To be able to specify the plural name for the client ge... | RESTMapper Pluralization Logic Is Too Limited | https://api.github.com/repos/kubernetes/kubernetes/issues/89034/comments | 5 | 2020-03-11T08:42:07Z | 2020-08-09T15:44:27Z | https://github.com/kubernetes/kubernetes/issues/89034 | 579,095,615 | 89,034 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
When I use `env` command inside a container of a certain namespace I get all env variables concerning IP address and services of all containers in this namespace.
**What you expected to happen**:
`env` command should return only variables of my pod.
**How to reproduce it (as minimally and precise... | Env variables are shared between pods on the same namespace | https://api.github.com/repos/kubernetes/kubernetes/issues/89033/comments | 2 | 2020-03-11T08:23:36Z | 2020-03-11T16:30:40Z | https://github.com/kubernetes/kubernetes/issues/89033 | 579,086,750 | 89,033 |
[
"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 executed a ... | Process remained in container after Kubectl exec being killed | https://api.github.com/repos/kubernetes/kubernetes/issues/89031/comments | 6 | 2020-03-11T07:15:55Z | 2020-08-12T03:42:49Z | https://github.com/kubernetes/kubernetes/issues/89031 | 579,056,079 | 89,031 |
[
"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**:
try to use po... | document is not line up on podpreset | https://api.github.com/repos/kubernetes/kubernetes/issues/89030/comments | 4 | 2020-03-11T07:13:36Z | 2020-03-12T13:26:50Z | https://github.com/kubernetes/kubernetes/issues/89030 | 579,055,116 | 89,030 |
[
"kubernetes",
"kubernetes"
] | I deployed TF-serving model and now I want to know how to monitor service and resource used ? | How to monitor services dead and resource used ? | https://api.github.com/repos/kubernetes/kubernetes/issues/89029/comments | 3 | 2020-03-11T06:48:11Z | 2020-04-12T21:41:37Z | https://github.com/kubernetes/kubernetes/issues/89029 | 579,045,202 | 89,029 |
[
"kubernetes",
"kubernetes"
] | Is there a way to implement kubernetes authentication at application level. I would like to know is there a way to implement something like Google-Login in kubernetes which should be able to authenticate application users via kubernetes plugins or api calls. I am aware of ABAC, RBAC and Node level authentication, but t... | Kubernetes Authentication At Application Level | https://api.github.com/repos/kubernetes/kubernetes/issues/89028/comments | 4 | 2020-03-11T06:32:51Z | 2020-07-15T09:57:01Z | https://github.com/kubernetes/kubernetes/issues/89028 | 579,039,708 | 89,028 |
[
"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**:
Controller ma... | Azure: Many invalid VMSS update calls due to incorrect VMSS cache | https://api.github.com/repos/kubernetes/kubernetes/issues/89025/comments | 1 | 2020-03-11T03:13:32Z | 2020-03-11T07:23:36Z | https://github.com/kubernetes/kubernetes/issues/89025 | 578,980,550 | 89,025 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
I have 6 node... | nodeSelector doesn't seem to be working reliably on EKS | https://api.github.com/repos/kubernetes/kubernetes/issues/89024/comments | 3 | 2020-03-11T02:49:06Z | 2020-03-11T16:35:11Z | https://github.com/kubernetes/kubernetes/issues/89024 | 578,973,951 | 89,024 |
[
"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 get statu... | The status of Node is ready before deployment NetworkPolicy(calico) | https://api.github.com/repos/kubernetes/kubernetes/issues/89022/comments | 3 | 2020-03-11T02:00:44Z | 2020-04-10T09:01:44Z | https://github.com/kubernetes/kubernetes/issues/89022 | 578,960,653 | 89,022 |
[
"kubernetes",
"kubernetes"
] | **Which jobs are flaking**:
pull-kubernetes-integration
**Which test(s) are flaking**:
TestStressingCascadingDeletion
**Testgrid link**:
https://prow.k8s.io/view/gcs/kubernetes-jenkins/pr-logs/pull/89019/pull-kubernetes-integration/1237494932579553283
**Reason for failure**:
Maybe related:
```
garbag... | TestStressingCascadingDeletion is flaky | https://api.github.com/repos/kubernetes/kubernetes/issues/89021/comments | 8 | 2020-03-10T22:22:36Z | 2020-03-19T13:07:16Z | https://github.com/kubernetes/kubernetes/issues/89021 | 578,895,925 | 89,021 |
[
"kubernetes",
"kubernetes"
] | /kind cleanup
/sig instrumentation
What happened:
SIG Instrumentation has published logging conventions for use in Kubernetes.
https://github.com/kubernetes/community/blob/master/contributors/devel/sig-instrumentation/logging.md
The existing code has calls in the range 0 to 10 and still remains to be normalized ... | apimachinery: Use log levels that match logging conventions | https://api.github.com/repos/kubernetes/kubernetes/issues/89020/comments | 6 | 2020-03-10T22:01:41Z | 2020-08-16T21:33:26Z | https://github.com/kubernetes/kubernetes/issues/89020 | 578,886,534 | 89,020 |
[
"kubernetes",
"kubernetes"
] | Resubmitting from https://github.com/kubernetes/apimachinery/issues/80
There's a service I'm looking at which uses client-go that produces race conditions in the k8s libs under a certain scenario. See these tests:
```
func TestSubscribeK8SAPIParallel(t *testing.T) {
var exp []exporters.Exporter
exp = []exporte... | Race conditions when making shared informers in parallel | https://api.github.com/repos/kubernetes/kubernetes/issues/89017/comments | 8 | 2020-03-10T21:25:15Z | 2020-03-19T21:14:13Z | https://github.com/kubernetes/kubernetes/issues/89017 | 578,870,764 | 89,017 |
[
"kubernetes",
"kubernetes"
] |
**What happened**:
When calling `NewDocumentDecoder` the token size for the buffer is the default which is NOT changable. Larger documents (which is likely when using a yaml separator) causes a `bufio.Scanner: token too long`
This was uncovered using kudo... the issue is https://github.com/kudobuilder/kudo/issu... | NewDocumentDecoder fails with bufio.Scanner: token too long | https://api.github.com/repos/kubernetes/kubernetes/issues/89016/comments | 8 | 2020-03-10T20:32:03Z | 2020-04-10T05:27:48Z | https://github.com/kubernetes/kubernetes/issues/89016 | 578,843,834 | 89,016 |
[
"kubernetes",
"kubernetes"
] | E.g. https://github.com/kubernetes/apimachinery, https://github.com/kubernetes/client-go, etc
People file issues there because it's logical, but we (api machinery) don't include them in our triage meeting.
We should either adjust our query, change our process in some other way (like tag issues when we've looked a... | Issues in published repos are not very visible | https://api.github.com/repos/kubernetes/kubernetes/issues/89015/comments | 9 | 2020-03-10T20:30:14Z | 2020-08-17T16:39:30Z | https://github.com/kubernetes/kubernetes/issues/89015 | 578,842,855 | 89,015 |
[
"kubernetes",
"kubernetes"
] | We know that when node is in unknown state, node-lifecycle-controller will add "node.kubernetes.io/unreachable NoExecute" and "node.kubernetes.io/unreachable NoSchedule" taints on node. While, i found that after deleting these two taints, "node.kubernetes.io/unreachable NoSchedule" will be added again soon, but "node.k... | Controller doesn't taint NoExecute | https://api.github.com/repos/kubernetes/kubernetes/issues/89012/comments | 2 | 2020-03-10T17:40:58Z | 2020-04-03T04:36:55Z | https://github.com/kubernetes/kubernetes/issues/89012 | 578,752,252 | 89,012 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
An error code... | kubectl cordon returns wrong error code if you don't have permissions | https://api.github.com/repos/kubernetes/kubernetes/issues/89008/comments | 12 | 2020-03-10T16:40:23Z | 2021-03-06T15:22:20Z | https://github.com/kubernetes/kubernetes/issues/89008 | 578,715,403 | 89,008 |
[
"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 user cre... | kube-controller-manager creates continuously pods in OutOfcpu state | https://api.github.com/repos/kubernetes/kubernetes/issues/89007/comments | 27 | 2020-03-10T16:33:08Z | 2023-01-03T11:23:55Z | https://github.com/kubernetes/kubernetes/issues/89007 | 578,710,570 | 89,007 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
We see nil dereference panics in the scheduler:
```
runtime.go:78] Observed a panic: \"invalid memory address or nil pointer dereference\" (runtime error: invalid memory address or nil pointer dereference)
{"log":"goroutine 1531102 [running]:
{"log":"k8s.io/kubernetes/vendor/k8s.io/apimachinery/... | Nil dereference panic in generic scheduler | https://api.github.com/repos/kubernetes/kubernetes/issues/89006/comments | 9 | 2020-03-10T16:08:49Z | 2020-04-01T23:37:54Z | https://github.com/kubernetes/kubernetes/issues/89006 | 578,694,741 | 89,006 |
[
"kubernetes",
"kubernetes"
] | Documentations for topologyKey at [kubernetes.io/docs/.../assign-pod-node/](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#an-example-of-a-pod-that-uses-pod-affinity) says:
> For `preferredDuringSchedulingIgnoredDuringExecution` pod anti-affinity, empty `topologyKey` is interpreted as “all topolo... | Documentation about empty affinity topologyKey | https://api.github.com/repos/kubernetes/kubernetes/issues/89000/comments | 2 | 2020-03-10T09:27:44Z | 2020-03-16T06:00:36Z | https://github.com/kubernetes/kubernetes/issues/89000 | 578,443,673 | 89,000 |
[
"kubernetes",
"kubernetes"
] | Here is the error message of kube-proxy :
E0303 07:46:14.241529 1 reflector.go:307] k8s.io/client-go/informers/factory.go:135: Failed to watch *v1.Service: Get https://192.168.205.60:6443/api/v1/services?allowWatchBookmarks=true&labelSelector=%21service.kubernetes.io%2Fheadless%2C%21service.kubernetes.io%2Fser... | kube-proxy logs show errors， however the stautus of pod is RUNNING | https://api.github.com/repos/kubernetes/kubernetes/issues/88999/comments | 4 | 2020-03-10T08:16:41Z | 2020-06-23T10:50:35Z | https://github.com/kubernetes/kubernetes/issues/88999 | 578,407,150 | 88,999 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
Extended `device plugin API` and `Node` API, some designs as follows:
```golang
// E.g:
// struct Device {
// ID: "GPU-fef8089b-4820-abfc-e83e-94318197576e",
// Health: "Healthy",
// Pr... | Extended device plugin api to expose more device information | https://api.github.com/repos/kubernetes/kubernetes/issues/88997/comments | 2 | 2020-03-10T08:03:51Z | 2020-06-10T03:10:56Z | https://github.com/kubernetes/kubernetes/issues/88997 | 578,401,526 | 88,997 |
[
"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://storage.googleapis.com/k8s-gubernator/triage/index.html?ci=0&pr=1&test=Kubectl%20logs%20should%20be%20able%20to%20retrieve%2... | [Flaky Test] [sig-cli] Kubectl client Kubectl logs should be able to retrieve and filter logs [Conformance] | https://api.github.com/repos/kubernetes/kubernetes/issues/88996/comments | 5 | 2020-03-10T07:42:20Z | 2020-08-06T12:20:33Z | https://github.com/kubernetes/kubernetes/issues/88996 | 578,391,906 | 88,996 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
Newest glusterfs client in hyperkube image.
**Why is this needed**:
To allow using [glusterfs](https://kubernetes.io/docs/concepts/storage/volumes/#glusterfs) volume with newer versions of server.
... | Upgrade glusterfs client in hyperkube image to latest stable version. | https://api.github.com/repos/kubernetes/kubernetes/issues/88994/comments | 1 | 2020-03-10T06:57:21Z | 2020-04-13T06:27:37Z | https://github.com/kubernetes/kubernetes/issues/88994 | 578,374,637 | 88,994 |
[
"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**:
From a comput... | Bare Metal K8S 63 Second Service Routing Delay - when accessing service via ClusterIP, or ExternalIP | https://api.github.com/repos/kubernetes/kubernetes/issues/88986/comments | 113 | 2020-03-09T21:19:51Z | 2021-04-08T16:03:51Z | https://github.com/kubernetes/kubernetes/issues/88986 | 578,197,782 | 88,986 |
[
"kubernetes",
"kubernetes"
] | This issue tracking the sub-resource tracking issue in server-side apply, reported in:
- https://github.com/kubernetes/kubernetes/issues/88901
- https://github.com/kubernetes/kubernetes/issues/82046
/sig api-machinery
/wg apply
/assign @apelisse | Server-side Apply: Ownership not tracked for sub-resources | https://api.github.com/repos/kubernetes/kubernetes/issues/88981/comments | 10 | 2020-03-09T19:31:59Z | 2021-06-28T11:43:25Z | https://github.com/kubernetes/kubernetes/issues/88981 | 578,141,448 | 88,981 |
[
"kubernetes",
"kubernetes"
] | Currently the content type for using ssa is `application/apply-patch+yaml`, while ssa explicitly accepts both yaml and json.
This can be confusing for users.
Our current plan to approach is this is:
- [x] Clarify the documentation (@kwiesmueller)
- [x] ~~Add a new content type that is clearer~~
/sig api-mac... | Server Side Apply patch type only mentions yaml | https://api.github.com/repos/kubernetes/kubernetes/issues/88975/comments | 6 | 2020-03-09T16:54:25Z | 2020-03-31T18:21:59Z | https://github.com/kubernetes/kubernetes/issues/88975 | 578,049,370 | 88,975 |
[
"kubernetes",
"kubernetes"
] | **Which jobs are failing**:
`gce-windows-1909-master (ci-kubernetes-e2e-windows-gce-1909)`
**Since when has it been failing**:
`5th March`
**Testgrid link**:
https://testgrid.k8s.io/sig-release-master-informing#gce-windows-1909-master
**Reason for failure**:
Many test cases are stale and others are failing... | [Failing Test] gce-windows-1909-master (ci-kubernetes-e2e-windows-gce-1909) | https://api.github.com/repos/kubernetes/kubernetes/issues/88974/comments | 37 | 2020-03-09T15:57:48Z | 2021-04-26T19:04:47Z | https://github.com/kubernetes/kubernetes/issues/88974 | 578,012,935 | 88,974 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI -->
Tl;DR every single e2e job that runs on GKE is either broken or shows up intestgrid with no results because the e2e job has already been removed but testgrid config has not been updated.
**Whic... | Cleanup or replace GKE-based e2e jobs | https://api.github.com/repos/kubernetes/kubernetes/issues/88971/comments | 2 | 2020-03-09T15:28:56Z | 2020-04-29T19:22:31Z | https://github.com/kubernetes/kubernetes/issues/88971 | 577,992,238 | 88,971 |
[
"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**:
k8s 1.17.2
c... | kubelet always print error log: Failed to get system container stats for "/docker" when set cgroupsPerQOS: false | https://api.github.com/repos/kubernetes/kubernetes/issues/88969/comments | 1 | 2020-03-09T14:33:06Z | 2020-04-14T18:04:14Z | https://github.com/kubernetes/kubernetes/issues/88969 | 577,952,540 | 88,969 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
When passed the argument `--max-resource-write-bytes` as shown in the tests of the PR #73805.
I received an error: `Request entity too large: limit is 3145728` on creating a big binary `ConfigMap` file
I got the error that there is no argument in `kube-apiserver`.
```
minikube start --extra-co... | Missing flag to changing MaxRequestBodyBytes | https://api.github.com/repos/kubernetes/kubernetes/issues/88968/comments | 3 | 2020-03-09T14:22:00Z | 2020-03-09T17:31:10Z | https://github.com/kubernetes/kubernetes/issues/88968 | 577,945,045 | 88,968 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
@lavalamp suggested in https://github.com/kubernetes/kubernetes/pull/88579#issuecomment-592102136 adding a global rate limit.
In that PR we decided to use different approach (adding a constant delay) a... | Add global rate limit to endpoints/endpointslices controller | https://api.github.com/repos/kubernetes/kubernetes/issues/88967/comments | 27 | 2020-03-09T14:20:30Z | 2024-05-22T12:41:31Z | https://github.com/kubernetes/kubernetes/issues/88967 | 577,944,028 | 88,967 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Q1：
1. kubectl get pod -A -oyaml , shows all pods condition.Ready:true on node1
2. I0308 09:32:15 ifdown enp8s0f1 on node1
3. I0308 09:33:27 NodeNotReady status on node1 -> Added NoSchedule Taint -> pod condition.Ready: false
I0308 09:33:32 Added NoExecuteTaint
4. I0308 09... | After ifdown and ifup, pod condition.Ready on node never become true | https://api.github.com/repos/kubernetes/kubernetes/issues/88964/comments | 26 | 2020-03-09T12:45:32Z | 2020-08-31T05:07:40Z | https://github.com/kubernetes/kubernetes/issues/88964 | 577,883,301 | 88,964 |
[
"kubernetes",
"kubernetes"
] | The follow is my config info:
```
[root@localhost app]# cat home-pvc.yaml
kind: PersistentVolumeClaim
apiVersion: v1
metadata:
name: appupload
namespace: auth
spec:
storageClassName: alicloud-disk-efficiency
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 100Gi
[ro... | Unable to mount volumes for pod | https://api.github.com/repos/kubernetes/kubernetes/issues/88961/comments | 3 | 2020-03-09T11:04:11Z | 2020-03-10T03:33:04Z | https://github.com/kubernetes/kubernetes/issues/88961 | 577,825,283 | 88,961 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
Support adding extra metrics for framework plugins
**Why is this needed**:
/sig scheduling | Enhancement Request: Support adding extra metrics for framework plugins | https://api.github.com/repos/kubernetes/kubernetes/issues/88960/comments | 1 | 2020-03-09T10:57:09Z | 2020-04-08T11:25:44Z | https://github.com/kubernetes/kubernetes/issues/88960 | 577,821,678 | 88,960 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
kubernetes v1.17.3 sonobuoy e2e test failed for AdmissionWebhook
```
[root@master01 ~]# sonobuoy results $results
Plugin: e2e
Status: failed
Total: 4843
Passed: 258
Failed: 20
Skipped: 4565
Failed tests:
[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should honor timeout ... | e2e test failed for kubernetes v1.17.3 | https://api.github.com/repos/kubernetes/kubernetes/issues/88958/comments | 10 | 2020-03-09T08:02:25Z | 2020-07-23T03:36:10Z | https://github.com/kubernetes/kubernetes/issues/88958 | 577,722,426 | 88,958 |
[
"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 ... | unable to fetch pod metrics for pod default/mypod: no metrics known for pod | https://api.github.com/repos/kubernetes/kubernetes/issues/88957/comments | 6 | 2020-03-09T06:12:04Z | 2020-04-12T21:41:46Z | https://github.com/kubernetes/kubernetes/issues/88957 | 577,681,805 | 88,957 |
[
"kubernetes",
"kubernetes"
] | we are using kubernetes 1.17 and we implemented Startup Probes ... And reduced the failure Threshold of readiness and liveness probes ... after that the pods are going to crashed state ... is it the expected behaviour?
we saw that the startup probe is useful during the slow start of the containers..
we thought that... | About Startup Probes - need more information about starting time of startup probes | https://api.github.com/repos/kubernetes/kubernetes/issues/88956/comments | 5 | 2020-03-09T05:54:47Z | 2020-08-06T07:26:08Z | https://github.com/kubernetes/kubernetes/issues/88956 | 577,676,429 | 88,956 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
kubeadm init fail
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
I0308 19:17:00.605906 2726 round_trippers.go:423] curl -k -v -XGET -H "User-Agent: kubeadm/v1.17.3 (linux/arm64) kuber... | Install Kubernetes on Ubuntu 16.04 ARM64 environment with qemu kube-apiserver pod crash and Rejected connection in ETCD logs | https://api.github.com/repos/kubernetes/kubernetes/issues/88947/comments | 29 | 2020-03-08T11:25:26Z | 2020-09-10T06:09:03Z | https://github.com/kubernetes/kubernetes/issues/88947 | 577,485,600 | 88,947 |
[
"kubernetes",
"kubernetes"
] | ```
Mar 8 15:11:48 k8s-master02 kube-apiserver: I0308 15:11:48.529082 16626 flags.go:33] FLAG: --v="2"
Mar 8 15:11:48 k8s-master02 kube-apiserver: I0308 15:11:48.529086 16626 flags.go:33] FLAG: --version="false"
Mar 8 15:11:48 k8s-master02 kube-apiserver: I0308 15:11:48.529092 16626 flags.go:33] FLAG: --vmo... | kube-apiserver v1.18.0-beta.1 panic: runtime error: invalid memory address or nil pointer dereference | https://api.github.com/repos/kubernetes/kubernetes/issues/88946/comments | 2 | 2020-03-08T07:23:22Z | 2020-03-08T07:47:14Z | https://github.com/kubernetes/kubernetes/issues/88946 | 577,458,440 | 88,946 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
My CRD definition with a [`Free-Form Object`](https://swagger.io/docs/specification/data-models/data-types/) attribute does not work as expected.
Having the following CRD:
```yaml
apiVersion: apiextensions.k8s.io/v1
kind: CustomResourceDefinition
metadata:
name: users.grafana.k8spin.cl... | CRD: Free-Form Object (openAPIV3Schema) | https://api.github.com/repos/kubernetes/kubernetes/issues/88944/comments | 4 | 2020-03-07T19:53:32Z | 2020-03-08T00:19:47Z | https://github.com/kubernetes/kubernetes/issues/88944 | 577,391,512 | 88,944 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
I have followed the guidelines from... | Unable to start Pods on Windows nodes (Failed to create pod sandbox) | https://api.github.com/repos/kubernetes/kubernetes/issues/88942/comments | 6 | 2020-03-07T18:31:15Z | 2020-08-07T23:11:01Z | https://github.com/kubernetes/kubernetes/issues/88942 | 577,381,210 | 88,942 |
[
"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**:
CpuManager, K... | k8s 1.15.5 cpumanager/kubelet changed the cpu_sets of containers in Guaranteed Qos Pods | https://api.github.com/repos/kubernetes/kubernetes/issues/88939/comments | 9 | 2020-03-07T07:32:44Z | 2020-08-31T00:02:45Z | https://github.com/kubernetes/kubernetes/issues/88939 | 577,294,494 | 88,939 |
[
"kubernetes",
"kubernetes"
] | I have deployed kubernetes cluster on AWS EC2 Ubuntu Nodes, one master node and one worker node. Its a free tier t2.micro machine with 1 CPU.
I installed and configured everything and on day 1 everything works fine. kubectl get nodes command was responding without any delay and i was able to create MYSQL deployment.... | kubectl get nodes command giving The connection to the server <ip>:6443 was refused - did you specify the right host or port? | https://api.github.com/repos/kubernetes/kubernetes/issues/88938/comments | 6 | 2020-03-07T05:06:59Z | 2020-03-13T02:46:29Z | https://github.com/kubernetes/kubernetes/issues/88938 | 577,279,743 | 88,938 |
[
"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**:
Denied a CSR ... | certificatesigningrequest.certificates.k8s.io wrong output upon certificate deny | https://api.github.com/repos/kubernetes/kubernetes/issues/88937/comments | 3 | 2020-03-07T02:23:27Z | 2020-03-07T18:09:01Z | https://github.com/kubernetes/kubernetes/issues/88937 | 577,261,601 | 88,937 |
[
"kubernetes",
"kubernetes"
] | No matter what the used network size or the index is, GetIndexedIP() always returns an error.
For example when used with the network `fd:11:b2:be::/64` and index `1`. It fails with the error
```
can't generate IP with index 1 from subnet. subnet too small. subnet: "fd:11:b2:be::/64"
```
It works well with IPv4... | k8s.io/utils/net.GetIndexedIP() always fails with IPv6 networks | https://api.github.com/repos/kubernetes/kubernetes/issues/88933/comments | 17 | 2020-03-06T23:22:17Z | 2020-03-23T08:44:17Z | https://github.com/kubernetes/kubernetes/issues/88933 | 577,226,116 | 88,933 |
[
"kubernetes",
"kubernetes"
] | JSONPath wildcard and filter support works correctly for arrays but does not work for objects.
When I use an expression like ...
```
kubectl get pod my-pod -o=jsonpath={.metadata.labels[*]}
```
I get the error ...
```
Error executing template: map[string]interface {} is not array or slice.
```
Similarly wh... | jsonpath wildcard and filter support is not working with objects | https://api.github.com/repos/kubernetes/kubernetes/issues/88928/comments | 10 | 2020-03-06T21:48:26Z | 2020-09-23T04:04:39Z | https://github.com/kubernetes/kubernetes/issues/88928 | 577,193,395 | 88,928 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
Add a sanitization function (perhaps similar to, or using the same mechanism as #76794) that is _enabled by default_ for kube-apiserver audit log messages for `secret` resources. "Sanitization" in this... | Audit log: sanitize requestObject of Secret resources by default | https://api.github.com/repos/kubernetes/kubernetes/issues/88926/comments | 8 | 2020-03-06T21:28:48Z | 2020-12-02T02:23:35Z | https://github.com/kubernetes/kubernetes/issues/88926 | 577,185,286 | 88,926 |
[
"kubernetes",
"kubernetes"
] |
**What would you like to be added**:
How can i get the pod name (in my code) where my service is running
**Why is this needed**:
In our current project we are running 100 pods i just want to have a monitor on logs, if we know which pod it is running. i can create a dashboard which gives information total request... | Getting Pod Name | https://api.github.com/repos/kubernetes/kubernetes/issues/88922/comments | 6 | 2020-03-06T20:56:21Z | 2020-08-06T09:28:10Z | https://github.com/kubernetes/kubernetes/issues/88922 | 577,171,145 | 88,922 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
The example given in the conformance README consists of
```
/*
Release : v1.13
Testname: Kubelet, log output, default
Description: By default the stdout and stderr from the process being executed in a pod MUST be sent to the pod's logs.
*/
framework.ConformanceIt("should print the ... | Conformance test header: Inconsistency between Name and Testname | https://api.github.com/repos/kubernetes/kubernetes/issues/88921/comments | 2 | 2020-03-06T20:51:08Z | 2020-06-02T20:58:38Z | https://github.com/kubernetes/kubernetes/issues/88921 | 577,168,965 | 88,921 |
[
"kubernetes",
"kubernetes"
] | /sig scheduling
/sig docs
/wg component-standard
/kind feature
kube-scheduler has 2 APIs that can be used to configure it at start up:
- [kubescheduler.config.k8s.io/v1.Policy](https://github.com/kubernetes/kubernetes/blob/c649666b4addcb9cbef3ca5ca1d6d572e252f551/staging/src/k8s.io/kube-scheduler/config/v1/reg... | Add swagger docs for kube-scheduler APIs | https://api.github.com/repos/kubernetes/kubernetes/issues/88919/comments | 20 | 2020-03-06T20:26:57Z | 2020-12-30T22:40:00Z | https://github.com/kubernetes/kubernetes/issues/88919 | 577,158,220 | 88,919 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
The conformance.yaml file captures comments not intended to be part of the "Description" section in the Description section.
For example: https://github.com/kubernetes/kubernetes/blob/master/test/e2e/common/docker_containers.go#L66-L67 should not be captured, but is populated in the Description... | conformance.yaml capturing comments not intended for conformance data | https://api.github.com/repos/kubernetes/kubernetes/issues/88918/comments | 1 | 2020-03-06T19:32:59Z | 2020-03-17T23:22:05Z | https://github.com/kubernetes/kubernetes/issues/88918 | 577,132,074 | 88,918 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
We should add a quorum check against etcd in a readiness health check for the kube-apiserver, since we don't want to route traffic to the kube-apiserver if etcd is perceived unhealthy by the apiserver.
/sig api-machinery
/assign @logicalhan
| Add etcd quorum check to readyz for kube-apiserver | https://api.github.com/repos/kubernetes/kubernetes/issues/88914/comments | 8 | 2020-03-06T17:25:48Z | 2020-08-21T20:28:01Z | https://github.com/kubernetes/kubernetes/issues/88914 | 577,072,985 | 88,914 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
Pods will n... | Pods not starting on Windows nodes | https://api.github.com/repos/kubernetes/kubernetes/issues/88913/comments | 11 | 2020-03-06T17:23:46Z | 2020-03-16T16:50:01Z | https://github.com/kubernetes/kubernetes/issues/88913 | 577,071,997 | 88,913 |
[
"kubernetes",
"kubernetes"
] | Fully described in https://github.com/kubernetes/kubernetes/pull/87865#discussion_r384736714, `VisitPodSecretNames` and `VisitPodConfigmapNames` will visit these fields for all containers, regardless of whether they're hidden behind a feature gate (e.g. `EphemeralContainers`).
This is usually correct, these methods ... | Visitors of Configmaps and Secrets should specify which containers to visit | https://api.github.com/repos/kubernetes/kubernetes/issues/88909/comments | 4 | 2020-03-06T16:08:44Z | 2020-03-20T16:20:37Z | https://github.com/kubernetes/kubernetes/issues/88909 | 577,028,748 | 88,909 |
[
"kubernetes",
"kubernetes"
] | On going through https://godoc.org/k8s.io/apimachinery/pkg/apis/meta/v1/unstructured I found at that there is no support for GetGroupVersionResource.
It would be good if we have something like
``` GroupVersionResource: v1.GroupVersionResource{
Group: obj.GroupVersionResource().Group,
Version:... | package unstructured does not provide GetGroupVersionResource() | https://api.github.com/repos/kubernetes/kubernetes/issues/88908/comments | 3 | 2020-03-06T15:43:34Z | 2020-03-12T17:36:32Z | https://github.com/kubernetes/kubernetes/issues/88908 | 577,012,844 | 88,908 |
[
"kubernetes",
"kubernetes"
] | **Which jobs are flaking**:
`pull-kubernetes-e2e-gce-alpha-features`
**Which test(s) are flaking**:
```
[sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)] provisioning should provision storage with snapshot data source [Feature:VolumeSnapshotDataSource]
``... | [Flaky Test] pull-kubernetes-e2e-gce-alpha-features | https://api.github.com/repos/kubernetes/kubernetes/issues/88907/comments | 4 | 2020-03-06T15:32:12Z | 2020-03-11T23:22:18Z | https://github.com/kubernetes/kubernetes/issues/88907 | 577,006,263 | 88,907 |
Subsets and Splits
Unique Owner-Repo Count
Counts the number of unique owner-repos in the dataset, providing a basic understanding of diverse repositories.