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"
] | **Describe**:
- Docker Version
- 17.03.2-ce
- Kubernetes Version
- v1.11.6
**Pod status**:
`Terminating `
**Pod Events**:
`Killing container with id docker://xxx:Need to kill Pod`
When exec docker ps in node host, app container status is running, also view the logs using docker logs.
But ... | envents Killing container with id docker://xxx:Need to kill Pod | https://api.github.com/repos/kubernetes/kubernetes/issues/91094/comments | 5 | 2020-05-14T07:57:53Z | 2020-12-24T15:11:14Z | https://github.com/kubernetes/kubernetes/issues/91094 | 618,010,710 | 91,094 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
I wanted to l... | Improve ClientConfigLoadingRules#Load documentation | https://api.github.com/repos/kubernetes/kubernetes/issues/91092/comments | 6 | 2020-05-14T06:57:42Z | 2020-10-12T19:45:55Z | https://github.com/kubernetes/kubernetes/issues/91092 | 617,975,006 | 91,092 |
[
"kubernetes",
"kubernetes"
] | **What happened**: I am trying to create a service type load balancer by mentioning the annotation **service.beta.kubernetes.io/aws-load-balancer-security-groups** with a security group id but it is throwing error
CONFIG:
![image](https://user-images.githubusercontent.com/51995628/81902170-44602f80-95f2-11ea-9520-c... | Not able to use the desired Security group when creating loadbalancer from kubernetes | https://api.github.com/repos/kubernetes/kubernetes/issues/91091/comments | 5 | 2020-05-14T06:54:04Z | 2020-10-26T18:11:42Z | https://github.com/kubernetes/kubernetes/issues/91091 | 617,972,999 | 91,091 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
I have a fanout ingress for host pytest-beta.com with paths /payment and /product. Kubernetes does not print the detailed output when I use kubectl get ingress command. Please have a look at expected output section.
current output:
**oc get ingress**
NAME HOSTS ... | Print more details like path, termination to "kubectl get ingress" output | https://api.github.com/repos/kubernetes/kubernetes/issues/91090/comments | 16 | 2020-05-14T05:43:38Z | 2020-07-16T17:26:11Z | https://github.com/kubernetes/kubernetes/issues/91090 | 617,941,137 | 91,090 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
k8 pod does not detect newly added volumes/disks. can we have a mechanism to add newly added disk/volume to be visible in pod without restarting pod?
**Why is this needed**:
the application may require ... | using new storage device/volumes to pods without restarting pods | https://api.github.com/repos/kubernetes/kubernetes/issues/91089/comments | 6 | 2020-05-14T04:51:56Z | 2020-10-11T07:09:43Z | https://github.com/kubernetes/kubernetes/issues/91089 | 617,922,439 | 91,089 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
···
if len(g... | kubectl create deploy‘’s code‘s logic has problem’ | https://api.github.com/repos/kubernetes/kubernetes/issues/91088/comments | 2 | 2020-05-14T04:30:19Z | 2020-05-15T04:46:21Z | https://github.com/kubernetes/kubernetes/issues/91088 | 617,915,291 | 91,088 |
[
"kubernetes",
"kubernetes"
] | Hi team,
we are having 1000's of pods running for our application. due to some reason we need to restart 100's of pods. is there any way we can do it in kubernetes using kubectl or any other tool. Please advice. it should be pure pod restart | How to restart 100's of pods at a time | https://api.github.com/repos/kubernetes/kubernetes/issues/91087/comments | 4 | 2020-05-14T04:05:00Z | 2020-06-22T11:42:56Z | https://github.com/kubernetes/kubernetes/issues/91087 | 617,907,343 | 91,087 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Pods won't go into a Ready state when there's a readiness probe configured with intialDelaySeconds and timeoutSeconds (default 1s) is shorter than the startup delay of the pod.
**What you expected to happen**:
Pod should go into ready state with the specified initial delay.
**How to reproduce... | Probe timeout should take startup delay into account | https://api.github.com/repos/kubernetes/kubernetes/issues/91076/comments | 3 | 2020-05-13T21:37:19Z | 2020-06-10T19:35:22Z | https://github.com/kubernetes/kubernetes/issues/91076 | 617,771,223 | 91,076 |
[
"kubernetes",
"kubernetes"
] | **Which jobs are flaking**:
test/integration is flaking. For example - https://prow.k8s.io/view/gcs/kubernetes-jenkins/pr-logs/pull/90907/pull-kubernetes-integration/1260640250275827716
**Which test(s) are flaking**:
--- FAIL: TestMaxResourceSize/StrategicMergePatchType_should_handle_a_patch_just_under... | TestMaxResourceSize integration test being flaky | https://api.github.com/repos/kubernetes/kubernetes/issues/91075/comments | 9 | 2020-05-13T20:39:22Z | 2020-07-31T17:56:40Z | https://github.com/kubernetes/kubernetes/issues/91075 | 617,739,891 | 91,075 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
A way (through a `Plan` kind?) to save a list of changes to be applied later, with
the guarantee to not cause any additional conflicts/resource addition/resource deletion.
The workflow would look like:
- Generate a `Plan` with `kubectl diff --recursive --server-side -oyaml... | Add a `Plan` kind | https://api.github.com/repos/kubernetes/kubernetes/issues/91074/comments | 14 | 2020-05-13T20:38:45Z | 2022-01-12T08:48:15Z | https://github.com/kubernetes/kubernetes/issues/91074 | 617,739,531 | 91,074 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
I have discon... | Kubelet gets "Timeout: Too large resource version" error from the API server after network outage | https://api.github.com/repos/kubernetes/kubernetes/issues/91073/comments | 29 | 2020-05-13T19:54:28Z | 2021-04-01T07:56:10Z | https://github.com/kubernetes/kubernetes/issues/91073 | 617,713,553 | 91,073 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
When a Service selector is removed, the corresponding Endpoints and EndpointSlice resources are not removed by their controllers.
**What you expected to happen**:
The corresponding Endpoints and EndpointSlice resources to be removed by their controllers.
**How to reproduce it (as minimally an... | Endpoints, EndpointSlice, and EndpointSliceMirroring controllers do not clean up resources when Service selector is removed | https://api.github.com/repos/kubernetes/kubernetes/issues/91072/comments | 36 | 2020-05-13T19:33:14Z | 2022-01-30T22:30:26Z | https://github.com/kubernetes/kubernetes/issues/91072 | 617,701,327 | 91,072 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
After rotating the SA public and private keys, the API server is unable to validate tokens minted off the old private key.
**What you expected to happen**:
Based on the documentation and the notes in [34029](https://github.com/kubernetes/kubernetes/pull/34029) and [20165](https://github.co... | Service account key rotation is not well documented | https://api.github.com/repos/kubernetes/kubernetes/issues/91070/comments | 13 | 2020-05-13T18:37:28Z | 2021-02-16T13:40:03Z | https://github.com/kubernetes/kubernetes/issues/91070 | 617,667,762 | 91,070 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Since Kubernetes 1.18 the `kubectl run` command is not creating deployments anymore, but pods. Furthermore, some flags (e.g. [--replicas](https://github.com/kubernetes/kubernetes/issues/89651)) have also been deprecated.
I stumbled upon a few places where the docs do not reflect that:
- https:... | Some docs do not reflect the changes to kubectl run command since 1.18 | https://api.github.com/repos/kubernetes/kubernetes/issues/91064/comments | 8 | 2020-05-13T14:24:12Z | 2021-01-18T05:48:15Z | https://github.com/kubernetes/kubernetes/issues/91064 | 617,493,260 | 91,064 |
[
"kubernetes",
"kubernetes"
] | /kind bug
/sig api-machinery
take quota's DELETECOLLECTION openapi schema as example:
```
"/api/v1/namespaces/{namespace}/resourcequotas": {
...
"description": "delete collection of ResourceQuota",
"operationId": "deleteCollectionNamespacedResourceQuota",
"parameters": [
... | Watch-related options ("watch"/"allowWatchBookmarks") should be pruned from DELETECOLLECTION's openapi parameter | https://api.github.com/repos/kubernetes/kubernetes/issues/91063/comments | 2 | 2020-05-13T14:02:01Z | 2020-05-21T12:35:58Z | https://github.com/kubernetes/kubernetes/issues/91063 | 617,475,831 | 91,063 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
The scheduler framework now has a new pod wrapper type named PodInfo which we can use to decorate the pod with pre-processed information. This issue is focused on processed affinity terms, which are expensive to do frequently especially when evaluating the anti affinity terms of ex... | Pre-calculate affinity terms in PodInfo | https://api.github.com/repos/kubernetes/kubernetes/issues/91058/comments | 4 | 2020-05-13T13:03:36Z | 2020-08-11T18:19:19Z | https://github.com/kubernetes/kubernetes/issues/91058 | 617,430,697 | 91,058 |
[
"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**:
Then load b... | Increase log level for TLS handshake error logs for kube-apiserver | https://api.github.com/repos/kubernetes/kubernetes/issues/91050/comments | 5 | 2020-05-13T09:06:12Z | 2020-07-11T21:12:18Z | https://github.com/kubernetes/kubernetes/issues/91050 | 617,277,945 | 91,050 |
[
"kubernetes",
"kubernetes"
] |
**What happened**:
When I execute the command to run the service case, the console always prints the timeout, and the pod is not running
`network-perf-1259 iperf-e2e-pod-0 0/1 Completed 0 3h41m
network-perf-1259 iperf-e2e-pod-1 0/1 Completed ... | kubetest --ginkgo.focus=Service timed out waiting for the condition | https://api.github.com/repos/kubernetes/kubernetes/issues/91047/comments | 7 | 2020-05-13T08:17:11Z | 2020-12-21T09:55:11Z | https://github.com/kubernetes/kubernetes/issues/91047 | 617,243,032 | 91,047 |
[
"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... | create svc externalname --tcp has no effect | https://api.github.com/repos/kubernetes/kubernetes/issues/91043/comments | 8 | 2020-05-13T05:57:57Z | 2020-12-24T15:11:16Z | https://github.com/kubernetes/kubernetes/issues/91043 | 617,165,278 | 91,043 |
[
"kubernetes",
"kubernetes"
] | An integration test should be added to confirm that the node authorizer interacts correctly with the `SelfSubjectRulesReview` API.
Test the 4 permutations of node authorizer=on/off with identity isNode=true/false.
xref: #90975 #91030 | Add test coverage for SelfSubjectRulesReview and node authorizer | https://api.github.com/repos/kubernetes/kubernetes/issues/91042/comments | 17 | 2020-05-13T02:27:25Z | 2021-02-13T21:14:18Z | https://github.com/kubernetes/kubernetes/issues/91042 | 617,090,988 | 91,042 |
[
"kubernetes",
"kubernetes"
] | ## Background
Per discussion in the [draft design doc](https://docs.google.com/document/d/1lBZOA-vjo2m52242q4dZ1L1W-RrNyr14F63PfQ5YUr8/view) and [brainstorming issue](https://github.com/kubernetes/kubernetes/issues/90025), we've come out with a good shape on how scheduler preemption logic can be refactored into.
... | [Umbrella] scheduler PostFilter extension point | https://api.github.com/repos/kubernetes/kubernetes/issues/91038/comments | 12 | 2020-05-12T22:31:07Z | 2020-10-05T17:05:15Z | https://github.com/kubernetes/kubernetes/issues/91038 | 617,005,435 | 91,038 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
The ability to set the Linux kernel hostname field ([the nodename field of struct utsname](http://man7.org/linux/man-pages/man2/uname.2.html)) of a pod to its fully qualified domain name (FQDN). Currently, when a pod is configured to have FQDN (e.g., foo.subdomain.namespace.svc.c... | Allow setting FQDN as hostname of pods. | https://api.github.com/repos/kubernetes/kubernetes/issues/91036/comments | 18 | 2020-05-12T19:43:13Z | 2020-10-13T18:58:27Z | https://github.com/kubernetes/kubernetes/issues/91036 | 616,911,916 | 91,036 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
`make` should check if dockerd has experimental features enabled and warn the user if they do not
**Why is this needed**:
I was trying to get e2e tests running locally, and when kubetest ran `make qui... | make should warn if experimental docker features are not enabled before attempting to use them | https://api.github.com/repos/kubernetes/kubernetes/issues/91031/comments | 5 | 2020-05-12T17:53:43Z | 2020-05-19T04:15:16Z | https://github.com/kubernetes/kubernetes/issues/91031 | 616,846,404 | 91,031 |
[
"kubernetes",
"kubernetes"
] | Split the scheduler framework into an interface pkg and an implementation pkg.
We can keep the interface files (interface.go, types.go, listers.go and cyclestate.go) under ```scheduler/framework/v1alpha1``` and move the implementation to ```scheduler/framework/runtime```.
Ideally plugins should only depend on t... | Split scheduler framework implementation into a separate pkg | https://api.github.com/repos/kubernetes/kubernetes/issues/91029/comments | 11 | 2020-05-12T17:36:36Z | 2020-10-31T06:03:59Z | https://github.com/kubernetes/kubernetes/issues/91029 | 616,836,056 | 91,029 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
Please offer more links for quickly jumping back and forth between logs for a pod, and exec to a pod.
**Why is this needed**:
The user currently has to find the pod all over again in the main pod list. It really slows you down when troubleshooting.
Also, extra page loads... | Awkward navigation from logs <-> exec | https://api.github.com/repos/kubernetes/kubernetes/issues/91028/comments | 2 | 2020-05-12T14:27:16Z | 2020-05-12T22:44:06Z | https://github.com/kubernetes/kubernetes/issues/91028 | 616,701,767 | 91,028 |
[
"kubernetes",
"kubernetes"
] | The Web browsing user has no control over whether log hyperlink opens in the current tab vs. a new tab. | Dashboard logs forcibly open in new tab | https://api.github.com/repos/kubernetes/kubernetes/issues/91027/comments | 4 | 2020-05-12T14:23:59Z | 2020-05-12T22:43:07Z | https://github.com/kubernetes/kubernetes/issues/91027 | 616,699,365 | 91,027 |
[
"kubernetes",
"kubernetes"
] | There are tooltips for the download button, the font buttons. No tooltip for whatever the clock button does. | No tooltip for the weird clock button above logs in dashboard | https://api.github.com/repos/kubernetes/kubernetes/issues/91026/comments | 3 | 2020-05-12T14:21:48Z | 2020-05-12T22:42:06Z | https://github.com/kubernetes/kubernetes/issues/91026 | 616,697,711 | 91,026 |
[
"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**:
Sometimes w... | kubelet "failed to initialize top level QOS containers" on cgroup mount leaks | https://api.github.com/repos/kubernetes/kubernetes/issues/91023/comments | 17 | 2020-05-12T13:43:05Z | 2020-11-05T10:12:41Z | https://github.com/kubernetes/kubernetes/issues/91023 | 616,667,983 | 91,023 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
More debug information for kubeadm when doing "kubeadm upgrade plan" and get this message:
invalid configuration: kind and apiVersion is mandatory information that needs to be specified
**Why is this ... | Add debug for kubeadm | https://api.github.com/repos/kubernetes/kubernetes/issues/91022/comments | 3 | 2020-05-12T12:29:08Z | 2020-05-12T17:04:16Z | https://github.com/kubernetes/kubernetes/issues/91022 | 616,616,849 | 91,022 |
[
"kubernetes",
"kubernetes"
] | Cobra 1.0.0 release was released a month ago:
https://github.com/spf13/cobra/releases/tag/v1.0.0
We should bump our vendor to use that (instead of 0.5 version we currently use).
As a bonus - in 0.6 version, support for "Context" was added, which would help me with cleaning up UnitWithoutRetry - see https://githu... | Bump spf13/cobra dependency to 1.0.0 version | https://api.github.com/repos/kubernetes/kubernetes/issues/91021/comments | 3 | 2020-05-12T12:27:06Z | 2020-05-15T09:48:49Z | https://github.com/kubernetes/kubernetes/issues/91021 | 616,615,626 | 91,021 |
[
"kubernetes",
"kubernetes"
] | <!--
STOP -- PLEASE READ!
GitHub is not the right place for support requests.
If you're looking for help, check [Stack Overflow](https://stackoverflow.com/questions/tagged/kubernetes) and the [troubleshooting guide](https://kubernetes.io/docs/tasks/debug-application-cluster/troubleshooting/).
You can also pos... | can I use dlv with k8s in linux unit file | https://api.github.com/repos/kubernetes/kubernetes/issues/91017/comments | 4 | 2020-05-12T10:14:43Z | 2020-07-14T16:08:13Z | https://github.com/kubernetes/kubernetes/issues/91017 | 616,535,157 | 91,017 |
[
"kubernetes",
"kubernetes"
] | This problem relates to k8s.io/utils/mount utility, please refer to
issue: https://github.com/kubernetes/utils/issues/163
PR: https://github.com/kubernetes/utils/pull/164
1. In K8s cluster with docker in /var/lib/docker and kubelet in /var/lib/kublet, create two pods as follows:
- pod p1
```
cat <<EOF | kub... | use lazy umount to avoid pod terminating problems caused by volume mounting dir accessed by other pods | https://api.github.com/repos/kubernetes/kubernetes/issues/91015/comments | 5 | 2020-05-12T09:32:02Z | 2020-09-16T07:45:13Z | https://github.com/kubernetes/kubernetes/issues/91015 | 616,507,135 | 91,015 |
[
"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... | error compile | https://api.github.com/repos/kubernetes/kubernetes/issues/91011/comments | 1 | 2020-05-12T08:24:17Z | 2020-05-12T08:58:33Z | https://github.com/kubernetes/kubernetes/issues/91011 | 616,461,170 | 91,011 |
[
"kubernetes",
"kubernetes"
] |
**What happened**:
1. following https://kubernetes.io/docs/tasks/access-kubernetes-api/custom-resources/custom-resource-definitions/#create-a-customresourcedefinition to create a CRD named `crontabs.stable.example.com` and then following https://kubernetes.io/docs/tasks/access-kubernetes-api/custom-resources/custo... | Error updating managedFields in custom resource: failed to update ManagedFields: failed to convert old object | https://api.github.com/repos/kubernetes/kubernetes/issues/91006/comments | 19 | 2020-05-12T05:59:59Z | 2020-06-10T00:31:55Z | https://github.com/kubernetes/kubernetes/issues/91006 | 616,383,089 | 91,006 |
[
"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**:
Kubemark pr... | Kubemark pre-existing e2e skipping all tests | https://api.github.com/repos/kubernetes/kubernetes/issues/91003/comments | 3 | 2020-05-12T04:56:57Z | 2020-05-13T06:11:49Z | https://github.com/kubernetes/kubernetes/issues/91003 | 616,358,807 | 91,003 |
[
"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**:
**Which test(s) are flaking**:
[sig-storage] CSI mock volume CSI volume limit information using mock driver should report attach li... | Test flake: [sig-storage] CSI mock volume CSI volume limit information using mock driver should report attach limit when limit is bigger than 0 [ | https://api.github.com/repos/kubernetes/kubernetes/issues/91001/comments | 19 | 2020-05-12T02:10:59Z | 2021-07-17T23:15:43Z | https://github.com/kubernetes/kubernetes/issues/91001 | 616,304,569 | 91,001 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Currently when the mirror pod is deleted, it is deleted without grace period.
When static pod yaml was removed from the manifests directory, @sjenning observed
```
Jul 29 20:54:44 master-2 hyperkube[1526]: I0729 20:54:44.122924 1526 kubelet.go:1904] SyncLoop (REMOVE, "file"): "kube-apiserver... | Mirror pod deletion should respect grace period | https://api.github.com/repos/kubernetes/kubernetes/issues/90999/comments | 20 | 2020-05-11T23:37:31Z | 2020-07-11T00:49:24Z | https://github.com/kubernetes/kubernetes/issues/90999 | 616,255,863 | 90,999 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
When I deploy... | Internal error occurred: failed calling webhook "mutations.agones.dev": Post https://agones-controller-service.agones-system.svc:443/mutate?timeout=30s: dial tcp 10.96.195.169:443: connect: connection refused | https://api.github.com/repos/kubernetes/kubernetes/issues/90997/comments | 22 | 2020-05-11T21:08:21Z | 2022-07-30T16:54:12Z | https://github.com/kubernetes/kubernetes/issues/90997 | 616,188,933 | 90,997 |
[
"kubernetes",
"kubernetes"
] | I have a 4 node cluster which runs in HA mode ie 3 masters and 1 worker nodes. I am trying to test nic failure on a node and to simulate that I ran `ifdown eth0` which is the public nic on which k8s is running on node 2.
I was expecting the node to be marked not ready and pods to evict and failover to other nodes. H... | Testing nic failure on bare-metal kubernetes cluster | https://api.github.com/repos/kubernetes/kubernetes/issues/90996/comments | 15 | 2020-05-11T20:48:16Z | 2020-12-10T20:53:32Z | https://github.com/kubernetes/kubernetes/issues/90996 | 616,177,042 | 90,996 |
[
"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 followed the kubectl debug exam... | I don't see a prompt in kubectl alpha debug | https://api.github.com/repos/kubernetes/kubernetes/issues/90993/comments | 1 | 2020-05-11T19:52:27Z | 2020-06-07T21:59:06Z | https://github.com/kubernetes/kubernetes/issues/90993 | 616,140,603 | 90,993 |
[
"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 making c... | Golang errors in Dockershim don't stop Kube Proxy from building | https://api.github.com/repos/kubernetes/kubernetes/issues/90991/comments | 5 | 2020-05-11T18:54:13Z | 2020-05-12T00:49:14Z | https://github.com/kubernetes/kubernetes/issues/90991 | 616,105,876 | 90,991 |
[
"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**:
Same symtoms ... | Azure disk detach/attach failure - due to deleted node (vmss) | https://api.github.com/repos/kubernetes/kubernetes/issues/90986/comments | 18 | 2020-05-11T16:21:41Z | 2020-10-02T06:37:19Z | https://github.com/kubernetes/kubernetes/issues/90986 | 616,011,450 | 90,986 |
[
"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 created... | kubeadm-flags.env not properly downloaded from master when joining cluster from worker node | https://api.github.com/repos/kubernetes/kubernetes/issues/90984/comments | 4 | 2020-05-11T15:44:51Z | 2020-05-12T13:50:39Z | https://github.com/kubernetes/kubernetes/issues/90984 | 615,986,331 | 90,984 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
The issue stems from use cases were 1 initiator is used for multiple LUNs. Because of this, all of the LUNs are discovered and mapped on a node when it does its initial discovery / login via AttachDisk[1]. Because a pod never mounts the device on any of the other nodes, it is never removed.
[1] h... | Automatic session scanning discovers all iSCSI devices during login and can cause LUN assignment issues | https://api.github.com/repos/kubernetes/kubernetes/issues/90982/comments | 2 | 2020-05-11T15:19:01Z | 2020-05-20T23:45:16Z | https://github.com/kubernetes/kubernetes/issues/90982 | 615,967,680 | 90,982 |
[
"kubernetes",
"kubernetes"
] | **Which jobs are failing**:
ci-kubernetes-kubemark-500-gce-stable3
**Which test(s) are failing**:
load test
**Since when has it been failing**:
2020-05-06
**Testgrid link**:
https://k8s-testgrid.appspot.com/sig-scalability-kubemark#kubemark-1.15-500
**Reason for failure**:
`[measurement call NetworkProgramming... | [Failing test] kubemark-500 failing due to no NetworkProgrammingLatency samples | https://api.github.com/repos/kubernetes/kubernetes/issues/90981/comments | 4 | 2020-05-11T15:10:19Z | 2020-05-12T12:36:23Z | https://github.com/kubernetes/kubernetes/issues/90981 | 615,961,278 | 90,981 |
[
"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 the pod ... | Single instance deployment will be unavailable during eviction | https://api.github.com/repos/kubernetes/kubernetes/issues/90977/comments | 12 | 2020-05-11T13:12:31Z | 2024-10-27T15:03:21Z | https://github.com/kubernetes/kubernetes/issues/90977 | 615,874,055 | 90,977 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
I checked if kubelet (`/var/lib/kubelet/pki/kubelet-client-current.pem`) has permissions for `get pods`
with Selfsubject**Access**Reviews and I saw that it has.
But when I checked its permissions with Selfsubject**Rules**Reviews it didn't show it.
**What you expected to happen**:
I expe... | SelfsubjectRulesReviews does not indicate results are incomplete for kubelets with Node authorizer | https://api.github.com/repos/kubernetes/kubernetes/issues/90975/comments | 8 | 2020-05-11T12:33:43Z | 2020-05-13T07:19:23Z | https://github.com/kubernetes/kubernetes/issues/90975 | 615,849,539 | 90,975 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
Provide a Kubernetes mechanism to allow certain pods (maybe with RBAC controls on which ones) to override the `oom_score_adj` values which are currently set based on QoS heuristics. This would allow Pos... | Allow override of oom_score_adj values | https://api.github.com/repos/kubernetes/kubernetes/issues/90973/comments | 30 | 2020-05-11T10:54:41Z | 2024-03-22T21:30:59Z | https://github.com/kubernetes/kubernetes/issues/90973 | 615,791,234 | 90,973 |
[
"kubernetes",
"kubernetes"
] |
**What happened**:
When updating a namespace with an invalid namespace via `kubectl apply --force`
the resources within the namespace are deleted
**What you expected to happen**:
Even with the force flag specified I would not expect an invalid annotation
to result in deletion of resources from a namespace.
... | Namespace Resources deleted when invalid annotation applied with force flag | https://api.github.com/repos/kubernetes/kubernetes/issues/90968/comments | 15 | 2020-05-11T08:07:05Z | 2020-11-13T21:14:39Z | https://github.com/kubernetes/kubernetes/issues/90968 | 615,678,654 | 90,968 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
Once volume binding logic is implemented as a VolumeBinding scheduler plugin (#83726), the following improvements can be done:
- [x] Revert assumed volume cache in `Unreserve` extension point (https://github.com/kubernetes/kubernetes/pull/... | VolumeBinding improvements track issue | https://api.github.com/repos/kubernetes/kubernetes/issues/90962/comments | 11 | 2020-05-11T03:23:13Z | 2020-12-01T01:28:27Z | https://github.com/kubernetes/kubernetes/issues/90962 | 615,559,762 | 90,962 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
my kubernetes... | IPv4 kubernetes pod mount volume failed , errors is: pod try to connect openstack IPv6 endpoint ( cinder) | https://api.github.com/repos/kubernetes/kubernetes/issues/90961/comments | 11 | 2020-05-11T03:21:42Z | 2020-06-21T09:05:20Z | https://github.com/kubernetes/kubernetes/issues/90961 | 615,559,243 | 90,961 |
[
"kubernetes",
"kubernetes"
] | `KubeSchedulerConfiguration.BindTimeoutSeconds` configures volume bind timeout for `VolumeBinding` plugin. It is not necessary after #83726.
- [x] Add versioned counterparts of `VolumeBindingArgs` and tests in `pkg/scheduler/apis/config/scheme/` https://github.com/kubernetes/kubernetes/issues/91139
- [ ] Eliminate ... | Remove BindTimeoutSeconds from KubeSchedulerConfiguration | https://api.github.com/repos/kubernetes/kubernetes/issues/90958/comments | 10 | 2020-05-11T01:59:24Z | 2020-06-05T15:45:46Z | https://github.com/kubernetes/kubernetes/issues/90958 | 615,535,731 | 90,958 |
[
"kubernetes",
"kubernetes"
] | * [Ticket status](#sec-1)
* [Current problem](#sec-2)
* [Proposed solution](#sec-3)
This Issue replace #90574
# Ticket status
* [ ] [K8s watch events test tooling #323](https://github.com/cncf/apisnoop/pull/323)
* [ ] [Watch event test verification tooling #90574](https://github.com/kubernetes/kubernetes/is... | Watch event test verification tooling | https://api.github.com/repos/kubernetes/kubernetes/issues/90957/comments | 10 | 2020-05-10T21:45:26Z | 2020-07-23T20:54:24Z | https://github.com/kubernetes/kubernetes/issues/90957 | 615,482,941 | 90,957 |
[
"kubernetes",
"kubernetes"
] | **Which jobs are failing**:
>gce-master-scale-correctness (ci-kubernetes-e2e-gce-scale-correctness)
**Which test(s) are failing**:
> - Test
> - [sig-storage] In-tree Volumes [Driver: gcepd] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] should access to two volumes with the same volume mode and reta... | [Flaky Test] gce-master-scale-correctness (ci-kubernetes-e2e-gce-scale-correctness) | https://api.github.com/repos/kubernetes/kubernetes/issues/90955/comments | 14 | 2020-05-10T16:39:28Z | 2020-07-22T18:43:13Z | https://github.com/kubernetes/kubernetes/issues/90955 | 615,429,128 | 90,955 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
We use the `leaderelection` package downstream in Knative (currently 1.16.x libs), and virtually any unit testing I try with the `LeaderElector` fails under `-race` due to assorted data races.
For example:
```
==================
WARNING: DATA RACE
Write at 0x00c00045d528 by goroutine 23:
... | Package leaderelection has data races | https://api.github.com/repos/kubernetes/kubernetes/issues/90952/comments | 11 | 2020-05-10T14:59:17Z | 2020-10-30T02:35:16Z | https://github.com/kubernetes/kubernetes/issues/90952 | 615,409,277 | 90,952 |
[
"kubernetes",
"kubernetes"
] | Hugepages: Pod deleting stuck
Created a pod with following configuration:
###### nginx-hugepages.yml
```yaml
apiVersion: v1
kind: Pod
metadata:
name: nginx1
spec:
containers:
- name: nginx1
image: nginx:1.7.9
ports:
- containerPort: 80
volumeMounts:
- mountPath: /hugepag... | Pod with hugepage get stuck in terminating state on deletion | https://api.github.com/repos/kubernetes/kubernetes/issues/90950/comments | 11 | 2020-05-10T14:09:02Z | 2020-10-11T18:20:44Z | https://github.com/kubernetes/kubernetes/issues/90950 | 615,399,476 | 90,950 |
[
"kubernetes",
"kubernetes"
] | **Which jobs are failing**:
> gce-device-plugin-gpu-master (ci-kubernetes-e2e-gce-device-plugin-gpu)
**Which test(s) are failing**:
>BeforeSuite
>Overall
>Test
**Since when has it been failing**:
> 05-09 00:30 PDT
**Testgrid link**:
> https://testgrid.k8s.io/sig-release-master-blocking#gce-device-plugin-... | [Failing Test] gce-device-plugin-gpu-master (ci-kubernetes-e2e-gce-device-plugin-gpu) | https://api.github.com/repos/kubernetes/kubernetes/issues/90947/comments | 21 | 2020-05-10T07:56:58Z | 2020-05-12T07:08:22Z | https://github.com/kubernetes/kubernetes/issues/90947 | 615,338,866 | 90,947 |
[
"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**:
```
Error: r... | kubectl create secret docker-registry --from-file=docker shows error | https://api.github.com/repos/kubernetes/kubernetes/issues/90945/comments | 3 | 2020-05-10T03:55:27Z | 2020-05-12T07:45:20Z | https://github.com/kubernetes/kubernetes/issues/90945 | 615,310,409 | 90,945 |
[
"kubernetes",
"kubernetes"
] | # Progress `[6/6]`
* [x] Original approval issue: #89071
* [x] Test approval issue: [kubernetes/kubernetes#90937](https://github.com/kubernetes/kubernetes/issues/90937)
* [x] Test pr: [PR](https://github.com/kubernetes/kubernetes/pull/90193)
* [x] Two weeks soak start date: [testgrid-link](https://testgrid.k8s.i... | Write CoreV1ServiceAccount resource lifecycle test+promote - +3 endpoint coverage | https://api.github.com/repos/kubernetes/kubernetes/issues/90937/comments | 2 | 2020-05-09T21:37:30Z | 2020-05-21T01:30:25Z | https://github.com/kubernetes/kubernetes/issues/90937 | 615,264,846 | 90,937 |
[
"kubernetes",
"kubernetes"
] | # Progress `[8/8]`
* [x] Original approval issue: #88545
* [x] Test approval issue: [kubernetes/kubernetes#90936](https://github.com/kubernetes/kubernetes/issues/90936)
* [x] [APISnoop PR](https://github.com/cncf/apisnoop/pull/290)
* [x] Test pr: [PR](https://github.com/kubernetes/kubernetes/pull/90942) - Revert... | Write CoreV1Pod and CoreV1PodStatus lifecycle test - +4 coverage | https://api.github.com/repos/kubernetes/kubernetes/issues/90936/comments | 8 | 2020-05-09T21:27:47Z | 2020-11-23T19:44:39Z | https://github.com/kubernetes/kubernetes/issues/90936 | 615,263,317 | 90,936 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**: when i run `ku... | kubectl deprecate message has typo | https://api.github.com/repos/kubernetes/kubernetes/issues/90935/comments | 5 | 2020-05-09T18:08:04Z | 2020-05-12T22:26:31Z | https://github.com/kubernetes/kubernetes/issues/90935 | 615,230,977 | 90,935 |
[
"kubernetes",
"kubernetes"
] | **What would you like to be added**:
With the introduction of `managedFields` in object meta `-o yaml` output is harder to read. I would like to propose that command `-o yaml | json` commands by default hide the `managedFields` from output and show it if user passes a flag like `--show-managed-fields`.
**Why is thi... | kubectl get -o yaml | json should not show managedFields by default | https://api.github.com/repos/kubernetes/kubernetes/issues/90933/comments | 1 | 2020-05-09T15:33:40Z | 2020-05-09T17:15:54Z | https://github.com/kubernetes/kubernetes/issues/90933 | 615,201,018 | 90,933 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
A resource is not replaced (deleted and recreated) when passing the `--force`
flag to `kubectl apply --server-side` and the change cannot be applied.
**What you expected to happen**:
I expected the service to be replaced.
**How to reproduce it (as minimally and precisely as possible)**:
... | `kubectl apply --server-side` doesn't honor `--force` flag | https://api.github.com/repos/kubernetes/kubernetes/issues/90931/comments | 14 | 2020-05-09T11:26:26Z | 2020-07-07T03:37:59Z | https://github.com/kubernetes/kubernetes/issues/90931 | 615,154,915 | 90,931 |
[
"kubernetes",
"kubernetes"
] | <!--
STOP -- PLEASE READ!
GitHub is not the right place for support requests.
If you're looking for help, check [Stack Overflow](https://stackoverflow.com/questions/tagged/kubernetes) and the [troubleshooting guide](https://kubernetes.io/docs/tasks/debug-application-cluster/troubleshooting/).
You can also pos... | Kubernetes - Building - IPv4/IPv6 dual stack cluster | https://api.github.com/repos/kubernetes/kubernetes/issues/90930/comments | 4 | 2020-05-09T11:24:07Z | 2020-05-09T14:58:44Z | https://github.com/kubernetes/kubernetes/issues/90930 | 615,154,517 | 90,930 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
APIs to show recent revisions of configMap.
**Why is this needed**:
Reversion history of configMap is useful for troubleshooting and rollback. | APIs to show recent revisions of configMap | https://api.github.com/repos/kubernetes/kubernetes/issues/90929/comments | 2 | 2020-05-09T10:12:49Z | 2020-05-09T14:57:46Z | https://github.com/kubernetes/kubernetes/issues/90929 | 615,141,643 | 90,929 |
[
"kubernetes",
"kubernetes"
] | kubenete 1.17.3
With one master and three workers
Two wokers are edge node which is just an arm64 router which has one wan port and 8 lan port.
Master(x86)
Worker1(Arm64)
eth0 192.168.100.59
br0 192.168.188.1
lan0-lan8 Ethernet ports with PoE function.
lan3 attach a IP camera with IP 192.168.188.232.
Deplo... | Expose IP camera as service in edge node | https://api.github.com/repos/kubernetes/kubernetes/issues/90928/comments | 8 | 2020-05-09T10:00:11Z | 2020-05-25T08:45:50Z | https://github.com/kubernetes/kubernetes/issues/90928 | 615,139,385 | 90,928 |
[
"kubernetes",
"kubernetes"
] | newly kubeadm init, and found following error in `kubectl cluster-info dump`
k8s.io/client-go/informers/factory.go:132: Failed to list *v1.ReplicationController: replicationcontrollers is forbidden: User "system:kube-scheduler" cannot list resource "replicationcontrollers" in API group "" at the cluster scope
Wha... | User "system:kube-scheduler" cannot list resource "replicationcontrollers" in API group "" at the cluster scope | https://api.github.com/repos/kubernetes/kubernetes/issues/90924/comments | 6 | 2020-05-09T03:22:33Z | 2020-10-09T03:19:00Z | https://github.com/kubernetes/kubernetes/issues/90924 | 615,079,916 | 90,924 |
[
"kubernetes",
"kubernetes"
] | # Progress `[7/7]`
* [x] Original approval issue: #87762
* [x] Test approval issue: [kubernetes/kubernetes#90923](https://github.com/kubernetes/kubernetes/issues/90923)
* [x] Test pr: [PR](https://github.com/kubernetes/kubernetes/pull/88778)
* [x] Two weeks soak start date: [testgrid-link](https://testgrid.k8s.i... | Write CoreV1Endpoints test - +4 coverage | https://api.github.com/repos/kubernetes/kubernetes/issues/90923/comments | 2 | 2020-05-09T02:35:51Z | 2020-07-28T23:31:48Z | https://github.com/kubernetes/kubernetes/issues/90923 | 615,072,882 | 90,923 |
[
"kubernetes",
"kubernetes"
] | - cluster cidr is 192.168.0.0/16
- set --node-cidr-mask-size 24
- add two nodes podCIDR will be 192.168.0.0/24 and 192.168.1.0/24
- set --node-cidr-mask-size 23 and restart controller-manager
- delete node 192.168.1.0/24
- add a node pod CIDR will be 192.168.0.0/23
- 192.168.0.0/24 and 192.168.0.0/23 overlap
... | support variable sized pod-CIDRs for different-sized node (was: Allow --node-cidr-mask-size to change: make NodeIPAM controller support variable sized CIDRs) | https://api.github.com/repos/kubernetes/kubernetes/issues/90922/comments | 39 | 2020-05-09T02:34:32Z | 2022-04-21T00:27:13Z | https://github.com/kubernetes/kubernetes/issues/90922 | 615,072,686 | 90,922 |
[
"kubernetes",
"kubernetes"
] | # Progress `[6/7]`
* [x] Original approval issue: #87120
* [x] Test approval issue: [kubernetes/kubernetes#90921](https://github.com/kubernetes/kubernetes/issues/90921)
* [x] Test pr: [PR](https://github.com/kubernetes/kubernetes/pull/87212)
* [x] Two weeks soak start date: 24 April 2020 [testgrid-link](https://... | Write CoreV1ConfigMap test - +2 endpoint Coverage | https://api.github.com/repos/kubernetes/kubernetes/issues/90921/comments | 6 | 2020-05-09T01:22:13Z | 2020-07-15T22:28:49Z | https://github.com/kubernetes/kubernetes/issues/90921 | 615,061,190 | 90,921 |
[
"kubernetes",
"kubernetes"
] | In k8s 17, i created a pod which configured raw block device by local volume. Then, I created lvm in the pod based on this raw device, I found I can create pv and vg correctly, but I can’t create lv.
I had given privilege authorization.
| How can create lvm in Pod? | https://api.github.com/repos/kubernetes/kubernetes/issues/90920/comments | 6 | 2020-05-09T01:17:38Z | 2020-10-17T08:30:56Z | https://github.com/kubernetes/kubernetes/issues/90920 | 615,060,416 | 90,920 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
Kubeadm tool ... | kubeadm don't pull arm64 images | https://api.github.com/repos/kubernetes/kubernetes/issues/90919/comments | 3 | 2020-05-09T01:02:48Z | 2020-05-09T08:55:10Z | https://github.com/kubernetes/kubernetes/issues/90919 | 615,057,798 | 90,919 |
[
"kubernetes",
"kubernetes"
] | # Progress `[2/6]`
* [x] Original approval issue: #89135
* [x] Test approval issue: [kubernetes/kubernetes#90918](https://github.com/kubernetes/kubernetes/issues/90918)
* [ ] Test pr: ?
* [ ] Two weeks soak start date: testgrid-link
* [ ] Two weeks soak end date:
* [ ] Test promotion pr: ?
This issue is c... | Write ServiceStatus resource lifecycle test - +2 endpoint coverage | https://api.github.com/repos/kubernetes/kubernetes/issues/90918/comments | 4 | 2020-05-09T00:50:58Z | 2020-09-17T22:39:52Z | https://github.com/kubernetes/kubernetes/issues/90918 | 615,055,683 | 90,918 |
[
"kubernetes",
"kubernetes"
] | # Progress `[2/6]`
* [x] Original approval issue: #88358
* [x] Test approval issue: [kubernetes/kubernetes#90917](https://github.com/kubernetes/kubernetes/issues/90917)
* [ ] Test pr: ?
* [ ] Two weeks soak start date: testgrid-link
* [ ] Two weeks soak end date:
* [ ] Test promotion pr: ?
This issue is c... | Write CoreV1NodeStatus test+promote - +2 endpoint coverage | https://api.github.com/repos/kubernetes/kubernetes/issues/90917/comments | 9 | 2020-05-09T00:29:04Z | 2021-02-16T17:36:29Z | https://github.com/kubernetes/kubernetes/issues/90917 | 615,051,253 | 90,917 |
[
"kubernetes",
"kubernetes"
] | # Progress `[7/7]`
* [x] Original approval issue: #89340
* [x] Test approval issue: [kubernetes/kubernetes#90916](https://github.com/kubernetes/kubernetes/issues/90916)
* [x] Test pr: #92589
* [x] Two weeks soak start date: 5 Nov 2020 [testgrid-link](https://testgrid.k8s.io/sig-apps#gce&include-filter-by-regex=D... | Write AppsV1Deployment resource lifecycle test - +6 endpoint coverage | https://api.github.com/repos/kubernetes/kubernetes/issues/90916/comments | 13 | 2020-05-09T00:10:06Z | 2020-11-20T01:11:13Z | https://github.com/kubernetes/kubernetes/issues/90916 | 615,046,940 | 90,916 |
[
"kubernetes",
"kubernetes"
] | # Progress `[7/7]`
* [x] Original approval issue: #90619
* [x] APISnoop org-flow: [deleteCoreV1CollectionNamespacedEventTest.org](https://github.com/cncf/apisnoop/blob/master/tickets/k8s/deleteCoreV1CollectionNamespacedEventTest.org)
* [x] Test approval issue: [kubernetes/kubernetes#90914](https://github.com/kuber... | Write deleteCoreV1CollectionNamespacedEvent test+promote - +1 endpoint coverage | https://api.github.com/repos/kubernetes/kubernetes/issues/90914/comments | 6 | 2020-05-08T23:49:42Z | 2020-07-16T02:16:35Z | https://github.com/kubernetes/kubernetes/issues/90914 | 615,041,752 | 90,914 |
[
"kubernetes",
"kubernetes"
] | # Progress `[7/7]`
* [x] Original approval issue: #90663
* [x] APISnoop org-flow: [deleteCoreV1CollectionNamespacedPodTest.org](https://github.com/cncf/apisnoop/blob/master/tickets/k8s/deleteCoreV1CollectionNamespacedPodTest.org)
* [x] Test approval issue: [kubernetes/kubernetes#90913](https://github.com/kubernete... | Write deleteCoreV1CollectionNamespacedPod test - +1 endpoint coverage | https://api.github.com/repos/kubernetes/kubernetes/issues/90913/comments | 11 | 2020-05-08T23:32:21Z | 2020-07-29T16:47:36Z | https://github.com/kubernetes/kubernetes/issues/90913 | 615,037,488 | 90,913 |
[
"kubernetes",
"kubernetes"
] | # Progress `[7/7]`
* [x] Original approval issue: #90746
* [x] APISnoop org-flow: [deleteCoreV1CollectionNamespacedPodTemplate.org](https://github.com/cncf/apisnoop/blob/master/tickets/k8s/deleteCoreV1CollectionNamespacedPodTemplateTest.org)
* [x] test approval issue: [kubernetes/kubernetes#90912](https://github.c... | Write deleteCoreV1CollectionNamespacedPodTemplate test+promote - +1 endpoint coverage | https://api.github.com/repos/kubernetes/kubernetes/issues/90912/comments | 9 | 2020-05-08T23:07:52Z | 2020-07-10T22:43:02Z | https://github.com/kubernetes/kubernetes/issues/90912 | 615,030,743 | 90,912 |
[
"kubernetes",
"kubernetes"
] | Currently we don't have an easy way of determining what number of requests are apiserver self-requests. This has historically bitten us, since we used to have a 50(?) QPS limit on apiserver self-requests (which thus has been removed). Even so, it would be a good idea to know this generally, since this may be helpful in... | Add a metric for apiserver self-requests | https://api.github.com/repos/kubernetes/kubernetes/issues/90908/comments | 3 | 2020-05-08T20:08:58Z | 2020-09-24T23:53:12Z | https://github.com/kubernetes/kubernetes/issues/90908 | 614,959,730 | 90,908 |
[
"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**:
Trying to a... | Incorrect parsing of YAML strings | https://api.github.com/repos/kubernetes/kubernetes/issues/90905/comments | 3 | 2020-05-08T19:38:44Z | 2020-05-08T19:49:42Z | https://github.com/kubernetes/kubernetes/issues/90905 | 614,944,310 | 90,905 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
FieldManager errors were encountered in an Update API request (xref https://github.com/openfaas/faas-netes/issues/630#issuecomment-625440515):
```
Unexpected status: 500, message: failed to update object (Update for openfaas.com/v1, Kind=Function) managed fields: failed to convert live object to... | fieldManager errors can fail create/update/non-apply-patch API calls | https://api.github.com/repos/kubernetes/kubernetes/issues/90904/comments | 13 | 2020-05-08T15:34:35Z | 2020-06-19T20:11:41Z | https://github.com/kubernetes/kubernetes/issues/90904 | 614,817,561 | 90,904 |
[
"kubernetes",
"kubernetes"
] | Hi Team,
We have the below nodepools which are dedicated for the individual client. As part of cost reduction exercise can you kindly let me know how can we reduce cost for the nodes at the same time ensure optimum performance?
```
// max_pods_per_node
// We set this to control the CIDR subnetwork allocated, w... | Reduce cost for Kubernetes nodes | https://api.github.com/repos/kubernetes/kubernetes/issues/90903/comments | 5 | 2020-05-08T14:33:30Z | 2020-05-14T21:13:54Z | https://github.com/kubernetes/kubernetes/issues/90903 | 614,780,878 | 90,903 |
[
"kubernetes",
"kubernetes"
] | extracted from https://github.com/kubernetes/kubernetes/issues/85127#issuecomment-605890538
```yaml
apiVersion: apiextensions.k8s.io/v1beta1
kind: CustomResourceDefinition
metadata:
name: intorstrings.stable.example.com
spec:
group: stable.example.com
versions:
- name: v1
served: true
stora... | "error building openapi models" error logged serving CRD containing x-kubernetes-int-or-string | https://api.github.com/repos/kubernetes/kubernetes/issues/90902/comments | 9 | 2020-05-08T14:33:24Z | 2021-01-14T16:10:20Z | https://github.com/kubernetes/kubernetes/issues/90902 | 614,780,820 | 90,902 |
[
"kubernetes",
"kubernetes"
] | Can we please add a label when we update the status(es) from prow jobs that are required have failed?
Reviewers can look for things to be lgtm-ed can use say : `label:approved -label:do-not-merge:required-jobs-failed"`
Approvers can rely on reviewers lgtm use say : `label:lgtm -label:do-not-merge:required-jobs-fail... | Need a new label "do-not-merge:required-jobs-failed" | https://api.github.com/repos/kubernetes/kubernetes/issues/90899/comments | 5 | 2020-05-08T14:00:59Z | 2020-05-08T23:21:05Z | https://github.com/kubernetes/kubernetes/issues/90899 | 614,761,631 | 90,899 |
[
"kubernetes",
"kubernetes"
] | Read-only NFS based PV PVC allowing writes to the underlying filesystem, when I made the changes by exec'ing into the pods (mounting those pvc based volumes)
**How to reproduce it (as minimally and precisely as possible)**:
```
Storage EC2 - 10.0.40.220
sudo apt-get update
sudo apt-get install nfs-kernel-ser... | Read-only NFS based PV PVC allowing writes to the filesystem | https://api.github.com/repos/kubernetes/kubernetes/issues/90885/comments | 9 | 2020-05-08T07:14:08Z | 2022-04-20T13:49:41Z | https://github.com/kubernetes/kubernetes/issues/90885 | 614,555,251 | 90,885 |
[
"kubernetes",
"kubernetes"
] | **What happened**: when one attempts to run the tests in pkg/kubelet/oom inside an unprivileged container, the `TestStartingWatcher` test case fails because `/dev/kmsg` doesn't exist:
```
--- FAIL: TestStartingWatcher (0.00s) ... | unit test pkg/kubelet/oom TestStartingWatcher fails when run in an unprivileged container | https://api.github.com/repos/kubernetes/kubernetes/issues/90883/comments | 7 | 2020-05-08T04:35:34Z | 2020-05-12T01:21:45Z | https://github.com/kubernetes/kubernetes/issues/90883 | 614,496,767 | 90,883 |
[
"kubernetes",
"kubernetes"
] | # Progress `[8/8]`
* [x] Original approval issue: #88302
* [x] [APISnoop mock ticket](https://github.com/cncf/apisnoop/pull/289)
* [x] test approval issue: [kubernetes/kubernetes#88588](https://github.com/kubernetes/kubernetes/issues/88588)
* [x] [update and improve](https://github.com/kubernetes/kubernetes/pu... | Write CoreV1ReplicationController lifecycle test+promote - +7 coverage | https://api.github.com/repos/kubernetes/kubernetes/issues/90881/comments | 6 | 2020-05-08T03:34:48Z | 2020-10-23T05:16:59Z | https://github.com/kubernetes/kubernetes/issues/90881 | 614,479,888 | 90,881 |
[
"kubernetes",
"kubernetes"
] | - [X] Original approval issue: #89637
- [ ] test pr : ?
- [ ] two weeks soak start date : testgrid-link ?
- [ ] two weeks soak end date :
- [ ] test promotion pr : ?
This issue is created to allow edit by @Riaankl
/wip
/hold
# Identifying an untested feature Using APISnoop
According to this APIsnoop ... | Write AppsV1DaemonSet resource lifecycle test - +5 endpoint coverage | https://api.github.com/repos/kubernetes/kubernetes/issues/90877/comments | 17 | 2020-05-08T02:43:44Z | 2021-03-22T01:28:21Z | https://github.com/kubernetes/kubernetes/issues/90877 | 614,464,020 | 90,877 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting enhancement requests -->
**What would you like to be added**:
AWS release [Local Zones] (https://aws.amazon.com/about-aws/whats-new/2020/03/aws-customers-enable-aws-local-zones-themselves/). One user enable local zones, using us-west-2 as an example, there's `us-... | AWS doesn't support local zone availability zones | https://api.github.com/repos/kubernetes/kubernetes/issues/90873/comments | 2 | 2020-05-08T00:58:56Z | 2020-06-10T11:38:53Z | https://github.com/kubernetes/kubernetes/issues/90873 | 614,432,691 | 90,873 |
[
"kubernetes",
"kubernetes"
] | ## What would you like to be added?
Explicitly state in this repo's [`CONTRIBUTING.md`](https://git.k8s.io/kubernetes/CONTRIBUTING.md) that contributors must sign the [CLA](https://git.k8s.io/community/CLA.md).
## Why is this needed?
The CNCF received a user complaint that the CLA requirement is non-obvious un... | CLA requirement isn't obvious to first time contributors | https://api.github.com/repos/kubernetes/kubernetes/issues/90869/comments | 1 | 2020-05-07T23:49:34Z | 2020-05-12T01:08:22Z | https://github.com/kubernetes/kubernetes/issues/90869 | 614,412,225 | 90,869 |
[
"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 running kub... | ephemeral test suites encounter flag redefine error | https://api.github.com/repos/kubernetes/kubernetes/issues/90868/comments | 22 | 2020-05-07T23:39:04Z | 2021-05-05T18:09:40Z | https://github.com/kubernetes/kubernetes/issues/90868 | 614,408,856 | 90,868 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI -->
**Which test(s) are failing**:
https://github.com/kubernetes/kubernetes/blob/master/test/e2e/storage/testsuites/volume_expand.go
These tests are hardcoding PVC size to 1Mi and expanding the PVC... | Volume expansion tests are not taking into account supported driver sizes | https://api.github.com/repos/kubernetes/kubernetes/issues/90866/comments | 5 | 2020-05-07T22:52:44Z | 2020-10-05T00:43:01Z | https://github.com/kubernetes/kubernetes/issues/90866 | 614,392,886 | 90,866 |
[
"kubernetes",
"kubernetes"
] | Hi,
I want to have two secrets mounted at the same path, e.g:
```
/var/tmp/secret_one
/var/tmp/secret_two
```
I've tried doing this by using:
```
apiVersion: v1
kind: Pod
metadata:
name: [redacted]
spec:
containers:
- name: [redacted]
image: [redacted]
ports:
- containerPort: 389
... | Cannot have two secrets mounted at same path | https://api.github.com/repos/kubernetes/kubernetes/issues/90862/comments | 2 | 2020-05-07T21:16:20Z | 2020-05-07T23:27:39Z | https://github.com/kubernetes/kubernetes/issues/90862 | 614,348,937 | 90,862 |
[
"kubernetes",
"kubernetes"
] | A long time ago we removed conformance for a similar HostPath test in:
https://github.com/kubernetes/kubernetes/pull/22380
At that time a policy was added [that said](https://github.com/kubernetes/kubernetes/pull/22379/files):
```
A conformance test cannot rely on any particular non-standard file system permissio... | Remove [Conformance] from "HostPath should give a volume the correct mode" test | https://api.github.com/repos/kubernetes/kubernetes/issues/90860/comments | 3 | 2020-05-07T20:46:32Z | 2020-05-16T14:36:41Z | https://github.com/kubernetes/kubernetes/issues/90860 | 614,333,383 | 90,860 |
[
"kubernetes",
"kubernetes"
] | Follow up to #87784
The validation is currently done in each plugin, which makes sense to keep some independence of the plugins.
However, since the types are API types, it also makes sense to have them in the validation package (and call the functions from the plugins)
Note that validation is only imported in `c... | Move scheduler Plugin args validation to apis/config/validation | https://api.github.com/repos/kubernetes/kubernetes/issues/90859/comments | 15 | 2020-05-07T19:52:44Z | 2020-09-16T14:35:06Z | https://github.com/kubernetes/kubernetes/issues/90859 | 614,304,292 | 90,859 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
I am trying to create a pod in ... | pod fails to pull image from private docker registry | https://api.github.com/repos/kubernetes/kubernetes/issues/90858/comments | 3 | 2020-05-07T19:11:51Z | 2020-05-08T01:59:35Z | https://github.com/kubernetes/kubernetes/issues/90858 | 614,281,695 | 90,858 |
[
"kubernetes",
"kubernetes"
] |
**What would you like to be added**:
Remove the need to call remote KMS for every new Secret.
**Why is this needed**:
Due to the serial processing of List requests, the initialization of informers may take significant time due to the large number of consecutive trips to KMS. For example, assuming a 40 millisecon... | Improve readiness times for clusters that use envelope encryption and create large numbers of secrets. | https://api.github.com/repos/kubernetes/kubernetes/issues/90856/comments | 13 | 2020-05-07T18:50:45Z | 2023-03-14T17:40:30Z | https://github.com/kubernetes/kubernetes/issues/90856 | 614,270,125 | 90,856 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
We run `kube-proxy` in `ipvs` mode on `RHEL 8.1`. Upgrading from kubernetes `1.15.3` to `1.18.1` introduces an additional 1 second of latency when making an HTTP call from `host -> service IP -> pod`, when the pod is running on a different host than the host where the call is made. **No** addition... | Additional 1s latency in `host -> service IP -> pod` when upgrading from `1.15.3 -> 1.18.1` on RHEL 8.1 | https://api.github.com/repos/kubernetes/kubernetes/issues/90854/comments | 14 | 2020-05-07T18:14:34Z | 2020-07-20T18:13:06Z | https://github.com/kubernetes/kubernetes/issues/90854 | 614,249,583 | 90,854 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
Pods get stuck in terminating state, as kubelet failed to unmount volume:
nodev on /var/lib/kubelet/pods/b3220985-120c-45c4-aeac-9f49adb29d17/volumes/kubernetes.io~empty-dir/hugepage type hugetlbfs (rw,relatime,pagesize=**2Mi**)
`Error: "UnmountVolume.TearDown failed for volume \"hugepage\" (Uni... | UnmountVolume.TearDown failed for volume of type hugetlbfs, error getting page size from 'pagesize=2Mi' mount option: unable to parse quantity's suffix". Resulting pod status in terminated forever. | https://api.github.com/repos/kubernetes/kubernetes/issues/90851/comments | 10 | 2020-05-07T16:36:17Z | 2020-09-02T16:17:24Z | https://github.com/kubernetes/kubernetes/issues/90851 | 614,193,080 | 90,851 |
[
"kubernetes",
"kubernetes"
] | **What happened**:
When the password is changed in the vSphere secret for the user that is configured for the cluster, storage can still be provisioned despite having a password that is no longer valid.
**What you expected to happen**:
PVC provisioning should fail with "Cannot complete login due to an incorr... | PVCs can still be provisioned after the password has been changed vSphere | https://api.github.com/repos/kubernetes/kubernetes/issues/90844/comments | 2 | 2020-05-07T13:57:52Z | 2020-06-19T02:03:40Z | https://github.com/kubernetes/kubernetes/issues/90844 | 614,079,544 | 90,844 |
Subsets and Splits
Unique Owner-Repo Count
Counts the number of unique owner-repos in the dataset, providing a basic understanding of diverse repositories.