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"
] | A security issue was discovered in Kubernetes where a user may be able to create a container with subpath volume mounts to access files & directories outside of the volume, including on the host filesystem.
This issue has been rated **High** ([CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H](https://www.first.org/cvss/... | CVE-2021-25741: Symlink Exchange Can Allow Host Filesystem Access | https://api.github.com/repos/kubernetes/kubernetes/issues/104980/comments | 16 | 2021-09-13T20:58:56Z | 2022-06-01T20:25:36Z | https://github.com/kubernetes/kubernetes/issues/104980 | 995,325,596 | 104,980 |
[
"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 are run... | EFS performance degradation eventually leads to nodes being un-responsive | https://api.github.com/repos/kubernetes/kubernetes/issues/104976/comments | 21 | 2021-09-13T19:27:37Z | 2022-02-24T18:28:24Z | https://github.com/kubernetes/kubernetes/issues/104976 | 995,245,335 | 104,976 |
[
"kubernetes",
"kubernetes"
] | It is more of a question since I was trying to find out the reason why runc is vendored in k8s.
Can someone share some thoughts about why runc is vendored in k8s in a bit more detail, since I was not able to find any mention of it in the repo(why to vendor, where it is used, what it is used for?). However, as I went ... | Question: Why to vendor runc in k8s | https://api.github.com/repos/kubernetes/kubernetes/issues/104974/comments | 6 | 2021-09-13T18:52:25Z | 2021-09-14T16:24:09Z | https://github.com/kubernetes/kubernetes/issues/104974 | 995,215,019 | 104,974 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI -->
#### Which jobs are failing:
node-kubelet-serial-containerd
#### Which test(s) are failing:
kubetest.Node Tests
#### Since when has it been failing:
Sep 11 19:47 UTC+05:30
#### T... | [Failing Test][sig-node] node-kubelet-serial-containerd | https://api.github.com/repos/kubernetes/kubernetes/issues/104964/comments | 5 | 2021-09-13T12:51:22Z | 2021-09-13T15:04:30Z | https://github.com/kubernetes/kubernetes/issues/104964 | 994,852,628 | 104,964 |
[
"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/
-->
In my case, I want to run 1 `Job` tha... | Job controller not respect backoffLimit in case of node failure | https://api.github.com/repos/kubernetes/kubernetes/issues/104961/comments | 10 | 2021-09-13T10:49:41Z | 2022-02-25T07:33:22Z | https://github.com/kubernetes/kubernetes/issues/104961 | 994,739,763 | 104,961 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI -->
#### Which jobs are failing:
kubernetes-e2e-gce-stable1-latest-upgrade-master-parallel
#### Which test(s) are failing:
Many test case failed. I noticed that the oidc-discovery failed for a ce... | kubernetes-e2e-gce-stable1-latest-upgrade-master-parallel failed for oidc-discovery-test pod | https://api.github.com/repos/kubernetes/kubernetes/issues/104956/comments | 5 | 2021-09-13T09:51:06Z | 2021-12-13T05:38:06Z | https://github.com/kubernetes/kubernetes/issues/104956 | 994,683,411 | 104,956 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
When I'm coding with a Job Kind, I found the JobSpec has a Suspend field by using command: `kubectl explain job.spec.suspend`, and it show like below:
```sh
KIND: Job
VERSION: batch/v1
FIELD: suspend <boolean>
DESCRIPTION:
Suspend specifies whether the Job controller shou... | JobSpec.Suspend isn't exists at batch/v1 & batch/v1beta1 ... | https://api.github.com/repos/kubernetes/kubernetes/issues/104950/comments | 6 | 2021-09-13T08:11:04Z | 2021-09-13T09:14:57Z | https://github.com/kubernetes/kubernetes/issues/104950 | 994,587,073 | 104,950 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI -->
#### Which jobs are failing:
Kubernetes tests and some of the components using `github.com/json-iterator/go` are failing with golang tip because the [issue](https://github.com/golang/go/issues/4... | Bump github.com/json-iterator/go to v1.1.12 | https://api.github.com/repos/kubernetes/kubernetes/issues/104947/comments | 9 | 2021-09-13T06:56:57Z | 2021-09-16T17:25:46Z | https://github.com/kubernetes/kubernetes/issues/104947 | 994,524,091 | 104,947 |
[
"kubernetes",
"kubernetes"
] | /sig storage
#### What happened:
1. Pod is deleted and volume failed to unmount like [the comment in 53214](https://github.com/kubernetes/kubernetes/issues/54214#issuecomment-341357733), because of node_exporter deployed without mountPropagation (we deployed from rancher.)
2. The new pod is rescheduled to the same... | New pod can't start after the volume failed to unmount. | https://api.github.com/repos/kubernetes/kubernetes/issues/104945/comments | 13 | 2021-09-13T06:16:42Z | 2022-03-27T06:07:31Z | https://github.com/kubernetes/kubernetes/issues/104945 | 994,498,950 | 104,945 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI -->
#### Which jobs are failing:
https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-e2e-gci-gce-ingress/1432573009574498304
#### Which test(s) are failing:
```html
Kubernetes e2e s... | [Flaky test] Kubernetes e2e suite.[sig-network] Loadbalancing: L7 GCE [Slow] [Feature:Ingress] should conform to Ingress spec | https://api.github.com/repos/kubernetes/kubernetes/issues/104941/comments | 4 | 2021-09-12T14:50:50Z | 2021-09-13T00:11:36Z | https://github.com/kubernetes/kubernetes/issues/104941 | 994,179,067 | 104,941 |
[
"kubernetes",
"kubernetes"
] | ### Failure cluster [1b410c50dc9c60031af5](https://go.k8s.io/triage#1b410c50dc9c60031af5)
https://storage.googleapis.com/k8s-triage/index.html?text=prometheus
##### Error text:
**TestRecordOperation**
```
=== RUN TestRecordOperation
--- FAIL: TestRecordOperation (0.00s)
panic: duplicate metrics collector reg... | UT failure: panic: duplicate metrics collector registration attempted | https://api.github.com/repos/kubernetes/kubernetes/issues/104940/comments | 12 | 2021-09-12T09:11:45Z | 2021-11-17T00:36:15Z | https://github.com/kubernetes/kubernetes/issues/104940 | 994,106,606 | 104,940 |
[
"kubernetes",
"kubernetes"
] | ### Failure cluster [7914285bf8bd5294763c](https://go.k8s.io/triage#7914285bf8bd5294763c)
##### Error text:
```
=== RUN TestRestart
E0829 06:18:41.006305 84048 nodeshutdown_manager_linux.go:197] "Ended to watching the node for shutdown events"
==================
WARNING: DATA RACE
Read at 0x00000417c348 by... | UT Failure: TestRestart data race | https://api.github.com/repos/kubernetes/kubernetes/issues/104938/comments | 3 | 2021-09-12T04:48:40Z | 2021-09-21T18:56:31Z | https://github.com/kubernetes/kubernetes/issues/104938 | 994,051,086 | 104,938 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
Helm upgrade fails with the following error:
`UPGRADE FAILED Error: failed to create patch: failed to create two-way merge patch: unable to find api field in struct HorizontalPodAutoscalerSpec for the json field "behavior"`
#### What you expected to happen:
Expected to have the upgrade uninterru... | failed to create patch: failed to create two-way merge patch: unable to find api field in struct HorizontalPodAutoscalerSpec for the json field "behavior" | https://api.github.com/repos/kubernetes/kubernetes/issues/104935/comments | 26 | 2021-09-11T23:09:40Z | 2022-10-01T09:47:08Z | https://github.com/kubernetes/kubernetes/issues/104935 | 993,972,330 | 104,935 |
[
"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:
```bash
$... | Namespace not found, even when created at the earliest | https://api.github.com/repos/kubernetes/kubernetes/issues/104930/comments | 6 | 2021-09-11T06:42:03Z | 2021-09-12T22:01:06Z | https://github.com/kubernetes/kubernetes/issues/104930 | 993,766,233 | 104,930 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
If specify RuntimeClass, it seems to find containerd without using cri-o.
```
Sep 11 02:50:10 k8s-ci-node-05102 kubelet[751]: /run/containerd/s/a613e1e8bdab5137886078fbc47bd0159066e7b7ed19f5f4a6620cb5343dc4aa: connect: connection refused
Sep 11 02:50:10 k8s-ci-node-05102 kubelet[751]: /run/c... | If specify RuntimeClass, it seems to find containerd without using cri-o. | https://api.github.com/repos/kubernetes/kubernetes/issues/104929/comments | 3 | 2021-09-11T03:13:33Z | 2021-09-11T03:26:12Z | https://github.com/kubernetes/kubernetes/issues/104929 | 993,728,803 | 104,929 |
[
"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 looked int... | anti-windup mechanism in queueset is too aggressive | https://api.github.com/repos/kubernetes/kubernetes/issues/104922/comments | 8 | 2021-09-10T21:59:19Z | 2021-09-22T19:58:33Z | https://github.com/kubernetes/kubernetes/issues/104922 | 993,628,637 | 104,922 |
[
"kubernetes",
"kubernetes"
] | How to set elasticsearch JVM
I want set elasticsearch jvm Xms and Xmx。
I edit es-statefulset.yaml as:
resources:
# need more cpu upon initialization, therefore burstable class
limits:
cpu: 1
memory: 3.5Gi
requests:
cpu: 10... | how to set elasticsearch JVM | https://api.github.com/repos/kubernetes/kubernetes/issues/104896/comments | 4 | 2021-09-10T08:51:00Z | 2021-09-10T08:53:43Z | https://github.com/kubernetes/kubernetes/issues/104896 | 993,026,615 | 104,896 |
[
"kubernetes",
"kubernetes"
] | <!-- Feature requests are unlikely to make progress as an issue.
Instead, please suggest enhancements by engaging with SIGs on slack and mailing lists.
A proposal that works through the design along with the implications of the change can be opened as a KEP:
https://git.k8s.io/enhancements/keps#kubernetes-enhanc... | Implement the logic for `RequiredDuringSchedulingRequiredDuringExecution` | https://api.github.com/repos/kubernetes/kubernetes/issues/104895/comments | 3 | 2021-09-10T07:55:42Z | 2021-09-10T13:27:22Z | https://github.com/kubernetes/kubernetes/issues/104895 | 992,984,138 | 104,895 |
[
"kubernetes",
"kubernetes"
] | <!-- Feature requests are unlikely to make progress as an issue.
Instead, please suggest enhancements by engaging with SIGs on slack and mailing lists.
A proposal that works through the design along with the implications of the change can be opened as a KEP:
https://git.k8s.io/enhancements/keps#kubernetes-enhanc... | Refactor `audit_test.go` | https://api.github.com/repos/kubernetes/kubernetes/issues/104893/comments | 9 | 2021-09-10T07:44:27Z | 2022-02-11T22:01:30Z | https://github.com/kubernetes/kubernetes/issues/104893 | 992,976,424 | 104,893 |
[
"kubernetes",
"kubernetes"
] | <!-- Feature requests are unlikely to make progress as an issue.
Instead, please suggest enhancements by engaging with SIGs on slack and mailing lists.
A proposal that works through the design along with the implications of the change can be opened as a KEP:
https://git.k8s.io/enhancements/keps#kubernetes-enhanc... | tracing PRs for promoting pause image to tag 3.6 | https://api.github.com/repos/kubernetes/kubernetes/issues/104890/comments | 4 | 2021-09-10T06:33:40Z | 2021-11-05T16:49:44Z | https://github.com/kubernetes/kubernetes/issues/104890 | 992,932,008 | 104,890 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
I recently upgraded to k8s version 1.22 and made the following observations. I deployed hello-apparmor.yaml example from the kubernetes tutorial on [securing pods with AppArmor](https://kubernetes.io/docs/tutorials/clusters/apparmor/).
hello-apparmor.yaml
```
apiVersion: v1
kind: Pod
metadata:... | kubectl get pods command shows status AppArmor for pod on k8s v1.22 | https://api.github.com/repos/kubernetes/kubernetes/issues/104888/comments | 25 | 2021-09-10T04:06:47Z | 2024-03-06T19:00:13Z | https://github.com/kubernetes/kubernetes/issues/104888 | 992,868,103 | 104,888 |
[
"kubernetes",
"kubernetes"
] | This issue is a bucket placeholder for collaborating on the "Known Issues" additions for the 1.23 Release Notes([example from 1.22 release notes](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.22.md#known-issues)). If you know of issues or API changes that are going out in 1.23, please comme... | 1.23 Release Notes: Known Issues | https://api.github.com/repos/kubernetes/kubernetes/issues/104885/comments | 6 | 2021-09-09T21:53:02Z | 2022-01-10T02:29:14Z | https://github.com/kubernetes/kubernetes/issues/104885 | 992,676,210 | 104,885 |
[
"kubernetes",
"kubernetes"
] | /sig-storage
/assign
[VolumeSourceEnabled](https://github.com/kubernetes/kubernetes/blob/master/test/e2e/storage/testsuites/ephemeral.go#L427) checks for volume sources by creating a pod and seeing if the API server reports the source as valid, and skipping tests if not.
This is an anti-pattern as it could hide ... | VolumeSourceEnabled should not be used to dynamically skip tests | https://api.github.com/repos/kubernetes/kubernetes/issues/104879/comments | 10 | 2021-09-09T21:04:56Z | 2022-05-09T00:34:40Z | https://github.com/kubernetes/kubernetes/issues/104879 | 992,630,717 | 104,879 |
[
"kubernetes",
"kubernetes"
] | In the `KEP-2221: Removing dockershim from kubelet` KEP:
https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/2221-remove-dockershim/README.md
we have a line item that says:
- Document and announce migration guide
We need to have this ready by 1.24, so we should start earlier in 1.23 itself.
... | Document and announce migration guide for Dockershim | https://api.github.com/repos/kubernetes/kubernetes/issues/104878/comments | 32 | 2021-09-09T20:23:02Z | 2022-04-15T16:08:18Z | https://github.com/kubernetes/kubernetes/issues/104878 | 992,600,588 | 104,878 |
[
"kubernetes",
"kubernetes"
] | I observe in node this:
```bash
netstat -antp | grep kube-pr
tcp 0 0 0.0.0.0:26032 0.0.0.0:* LISTEN 949/kube-proxy
tcp 0 0 0.0.0.0:29488 0.0.0.0:* LISTEN 949/kube-proxy
tcp 0 0 0.0.0.0:30000 0.0.0.0:* ... | why kube-proxy LISTEN nodeport? | https://api.github.com/repos/kubernetes/kubernetes/issues/104875/comments | 4 | 2021-09-09T15:03:13Z | 2021-09-09T15:11:35Z | https://github.com/kubernetes/kubernetes/issues/104875 | 992,333,367 | 104,875 |
[
"kubernetes",
"kubernetes"
] | For Structured Logging Migration: [kubernetes/enhancements#1602](https://github.com/kubernetes/enhancements/issues/1602)
[Beta graduation criteria:](https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/1602-structured-logging#beta)
- Migration of Kube-proxy to structured logging
####... | Kube-proxy migration to structured logs | https://api.github.com/repos/kubernetes/kubernetes/issues/104872/comments | 23 | 2021-09-09T14:29:48Z | 2021-10-22T16:00:04Z | https://github.com/kubernetes/kubernetes/issues/104872 | 992,298,673 | 104,872 |
[
"kubernetes",
"kubernetes"
] | Hi.
What environment do the images run in?
Docker? If so, how can you run images in Podman? | k8s Container runtimes | https://api.github.com/repos/kubernetes/kubernetes/issues/104871/comments | 10 | 2021-09-09T14:10:09Z | 2021-09-09T15:39:21Z | https://github.com/kubernetes/kubernetes/issues/104871 | 992,277,686 | 104,871 |
[
"kubernetes",
"kubernetes"
] | Warning FailedMount 23m (x55 over 3h) kubelet, ip-172-31-3-191.us-east-2.compute.internal Unable to attach or mount volumes: unmounted volumes=[mysql-persistent-storage], unattached volumes=[mysql-persistent-storage default-token-6vkr2]: timed out waiting for the condition
Warning FailedMount 4m (x105 over... | attachdetach-controller AttachVolume.NewAttacher failed for volume "pv" :Failed to get AWS Cloud Provider. GetCloudProvider returned <nil> instead | https://api.github.com/repos/kubernetes/kubernetes/issues/104869/comments | 12 | 2021-09-09T13:47:07Z | 2022-02-12T21:15:32Z | https://github.com/kubernetes/kubernetes/issues/104869 | 992,245,895 | 104,869 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
When running the scheduler at `v=2` or greater, the processed component config may be logged as a single line with newline characters inserted, like so:
```
2021-09-09T02:54:17.253985446Z I0909 02:54:17.253914 1 configfile.go:96] "Using component config" config="apiVersion: kubescheduler.co... | Scheduler logged config prints without line breaks | https://api.github.com/repos/kubernetes/kubernetes/issues/104868/comments | 7 | 2021-09-09T12:44:15Z | 2021-11-09T19:28:12Z | https://github.com/kubernetes/kubernetes/issues/104868 | 992,180,440 | 104,868 |
[
"kubernetes",
"kubernetes"
] | i use kubectl to get pod list,then appear a pod name is NAME

i want to deal with,but i dont know
, but `kubelet` rejects with;
```
E0909 06:21:39.503175 376 kuberuntime_manager.go:819] "CreatePodSandbox for pod failed" err="rpc error: code = Unknown desc = failed to create pod network sandbox k8s_mserver-deployment-654bbdc6dc-5zg... | Support CNI v1.0.0 | https://api.github.com/repos/kubernetes/kubernetes/issues/104861/comments | 13 | 2021-09-09T08:45:32Z | 2021-10-30T16:59:47Z | https://github.com/kubernetes/kubernetes/issues/104861 | 991,960,735 | 104,861 |
[
"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:
pull-kubernetes-unit
#### Which test(s) are flaking:
TestDifferentWidths
#### Testgrid link:
https://prow.k8s.io/view/gs/kub... | TestDifferentWidths flakes | https://api.github.com/repos/kubernetes/kubernetes/issues/104860/comments | 3 | 2021-09-09T08:24:02Z | 2021-09-10T02:49:59Z | https://github.com/kubernetes/kubernetes/issues/104860 | 991,941,919 | 104,860 |
[
"kubernetes",
"kubernetes"
] | I created a pv with nfs storage and next created a pvc bound to this pv. The pv reclaim policy is recycle. I noticed that the NFS path was set with a nonexistent volume by mistake. Then I deleted the pvc and pv. I found that a recycler pod was launched for recycling data in this pv. This was expected. But this pod was... | Recycler pod status keep on ContainerCreating forever | https://api.github.com/repos/kubernetes/kubernetes/issues/104855/comments | 8 | 2021-09-09T07:41:23Z | 2022-02-06T10:20:54Z | https://github.com/kubernetes/kubernetes/issues/104855 | 991,905,413 | 104,855 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
`flowschemas` resource is currently skipped by `TestApplyResetFields` test.
https://github.com/kubernetes/kubernetes/blob/master/test/integration/apiserver/apply/reset_fields_test.go#L70-L74
```
var resetFieldsSkippedResources = map[string]struct{}{
// TODO: flowschemas is flaking,
// poss... | flowschemas resource is currently skipped by TestApplyResetFields test. | https://api.github.com/repos/kubernetes/kubernetes/issues/104842/comments | 13 | 2021-09-08T14:26:48Z | 2022-10-08T12:01:32Z | https://github.com/kubernetes/kubernetes/issues/104842 | 991,202,506 | 104,842 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
#### What happened: I am using K8... | Cluster Service name is not responding sig/multicluster | https://api.github.com/repos/kubernetes/kubernetes/issues/104839/comments | 2 | 2021-09-08T08:28:59Z | 2021-09-08T08:30:11Z | https://github.com/kubernetes/kubernetes/issues/104839 | 990,855,931 | 104,839 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
#### What happened: I am using K8... | Cluster Service name is not responding | https://api.github.com/repos/kubernetes/kubernetes/issues/104838/comments | 6 | 2021-09-08T07:58:37Z | 2021-09-16T20:22:09Z | https://github.com/kubernetes/kubernetes/issues/104838 | 990,830,335 | 104,838 |
[
"kubernetes",
"kubernetes"
] | Hello all,
I'm have a website running on k8s below is architecture with issue of mixed content http loaded on https :
```
kubernetes version : 1.21
traefik : v2.5
Nginx : v1.17
```
`Client -----> Cloudflare SSL -----> Traefik SSL (letsencrypt) ---> Nginx Pods (No SSL) `
it will be impossible to ins... | Mixed content issue , http content loaded over https | https://api.github.com/repos/kubernetes/kubernetes/issues/104834/comments | 5 | 2021-09-08T04:38:15Z | 2021-09-09T07:53:10Z | https://github.com/kubernetes/kubernetes/issues/104834 | 990,707,719 | 104,834 |
[
"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:
This is noth... | Potential loss of precision in progress meter in queueSet | https://api.github.com/repos/kubernetes/kubernetes/issues/104831/comments | 9 | 2021-09-08T01:26:55Z | 2021-10-12T19:39:42Z | https://github.com/kubernetes/kubernetes/issues/104831 | 990,534,629 | 104,831 |
[
"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 you try a... | "Input contains a loop" on vendoring new dependencies that depend on staging projects | https://api.github.com/repos/kubernetes/kubernetes/issues/104827/comments | 5 | 2021-09-07T23:33:34Z | 2021-09-08T11:38:29Z | https://github.com/kubernetes/kubernetes/issues/104827 | 990,430,077 | 104,827 |
[
"kubernetes",
"kubernetes"
] | A pod can be created, allocated unique resources on a node (such as a volume, an isolated CPU, or a device), and then force deleted. Force deletion however happens independent of the state of the Kubelet - the pod could still be running or not have completed termination (termination takes a non-zero amount of time fro... | Pods that are terminating but force deleted must still be accounted for in admission | https://api.github.com/repos/kubernetes/kubernetes/issues/104824/comments | 15 | 2021-09-07T17:52:20Z | 2024-12-18T18:52:51Z | https://github.com/kubernetes/kubernetes/issues/104824 | 990,215,532 | 104,824 |
[
"kubernetes",
"kubernetes"
] | I propose that we try to limit the use of go-cmp/cmp primarily to tests.
The comparisons themselves are less efficient, and referencing the cmp package may allocate some static structures.
Where we can't easily avoid calling cmp, I propose we limit its usage. If we are calling it from a V(4) log statement (for e... | Use go-cmp/cmp only in tests | https://api.github.com/repos/kubernetes/kubernetes/issues/104821/comments | 44 | 2021-09-07T17:30:38Z | 2025-03-06T16:14:23Z | https://github.com/kubernetes/kubernetes/issues/104821 | 990,199,271 | 104,821 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
Calling `strategicpatch.CreateThreeWayMergePatch` results in `{"metadata":{"creationTimestamp":null}}`, but expected `{}` instead.
code example:
```go
package main
import (
"fmt"
"k8s.io/apimachinery/pkg/runtime/schema"
"k8s.io/apimachinery/pkg/util/strategicpatch"
k8sscheme "k8s.io... | Wrong strategic ThreeWayMergePatch because of "creationTimestamp":null | https://api.github.com/repos/kubernetes/kubernetes/issues/104820/comments | 12 | 2021-09-07T17:28:40Z | 2022-02-09T01:38:37Z | https://github.com/kubernetes/kubernetes/issues/104820 | 990,197,958 | 104,820 |
[
"kubernetes",
"kubernetes"
] | We have the following environment:
kubernetes 1.22.0
containerd: 1.5.2-0ubuntu1~20.04.2
calico: v3.19.1
OS: ubuntu 20.04
The problem is that when pods are running, we experience random "interrupted system call" issues. What could be the problem? What additional data is needed to figure out what's wrong?
One... | Random "interrupted system call" issues | https://api.github.com/repos/kubernetes/kubernetes/issues/104815/comments | 10 | 2021-09-07T11:50:07Z | 2021-09-22T17:57:50Z | https://github.com/kubernetes/kubernetes/issues/104815 | 989,900,028 | 104,815 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI -->
#### Which jobs are failing:
ci-cgroup-systemd-containerd-node-e2e
#### Which test(s) are failing:
- e2e.go: Node Tests expand_more
#### Since when has it been failing:
since #103692
... | ci-cgroup-systemd-containerd-node-e2e failed for golang version | https://api.github.com/repos/kubernetes/kubernetes/issues/104813/comments | 4 | 2021-09-07T09:04:19Z | 2021-09-08T05:29:41Z | https://github.com/kubernetes/kubernetes/issues/104813 | 989,761,073 | 104,813 |
[
"kubernetes",
"kubernetes"
] | #### Which jobs are flaking:
Two flakes recently:
* https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-e2e-gce-scale-performance/1434924831014391808
* https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-e2e-gce-scale-performance/1432025635122843648
They fail with error like:
```
:0
... | ci-kubernetes-e2e-gce-scale-performance flakes with slow POST/PATCH jobs requests | https://api.github.com/repos/kubernetes/kubernetes/issues/104811/comments | 17 | 2021-09-07T08:47:20Z | 2021-09-09T15:18:31Z | https://github.com/kubernetes/kubernetes/issues/104811 | 989,745,138 | 104,811 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
#### What happened:
In the last ... | Scalability tests are using exempt priority levels for all calls | https://api.github.com/repos/kubernetes/kubernetes/issues/104809/comments | 10 | 2021-09-07T08:22:30Z | 2023-05-10T11:15:01Z | https://github.com/kubernetes/kubernetes/issues/104809 | 989,724,097 | 104,809 |
[
"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 Nginx ser... | The pod of another node cannot be accessed | https://api.github.com/repos/kubernetes/kubernetes/issues/104804/comments | 9 | 2021-09-07T02:39:57Z | 2021-09-07T15:29:47Z | https://github.com/kubernetes/kubernetes/issues/104804 | 989,539,468 | 104,804 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
#### What happened:
The dockerd ... | Dockerd process leaking handles in K8s Windows worker nodes | https://api.github.com/repos/kubernetes/kubernetes/issues/104789/comments | 19 | 2021-09-06T06:15:37Z | 2022-08-16T00:53:15Z | https://github.com/kubernetes/kubernetes/issues/104789 | 988,806,464 | 104,789 |
[
"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 testing... | Improve tests for ReleaseControllerRevision | https://api.github.com/repos/kubernetes/kubernetes/issues/104787/comments | 6 | 2021-09-06T04:29:12Z | 2022-02-03T05:58:01Z | https://github.com/kubernetes/kubernetes/issues/104787 | 988,753,844 | 104,787 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
#### What happened:
The liveness... | kube-apiserver pod livenessProbe: why is kube-apiserver pod still `running` status when etcd healthz check failed | https://api.github.com/repos/kubernetes/kubernetes/issues/104786/comments | 8 | 2021-09-06T02:36:20Z | 2022-02-04T21:13:50Z | https://github.com/kubernetes/kubernetes/issues/104786 | 988,684,602 | 104,786 |
[
"kubernetes",
"kubernetes"
] | #### What happened
kubelet log:
`nestedpendingoperations.go:301] Operation for "{volumeName:kubernetes.io/rbd/k8s-data:kubernetes-dynamic-pvc-b3e3f5a1-6a72-4c1b-b491-21879df40d07 podName: nodeName:}" failed. No retries permitted until 2021-09-06 06:24:03.085198835 +0800 CST m=+4045740.475184549 (durationBeforeRe... | rbd: unmap failed: (16) Device or resource busy | https://api.github.com/repos/kubernetes/kubernetes/issues/104785/comments | 7 | 2021-09-06T02:07:39Z | 2022-02-06T03:17:56Z | https://github.com/kubernetes/kubernetes/issues/104785 | 988,673,330 | 104,785 |
[
"kubernetes",
"kubernetes"
] | 
How to solve the problem that the old endpoint cannot be deleted from the kubernetes service | This is a error on the kube-apiserver | https://api.github.com/repos/kubernetes/kubernetes/issues/104784/comments | 4 | 2021-09-06T02:06:00Z | 2021-09-06T03:15:19Z | https://github.com/kubernetes/kubernetes/issues/104784 | 988,672,262 | 104,784 |
[
"kubernetes",
"kubernetes"
] | There are a few mock files [1] in the codebase today that are generated by mockery. However, these files are not autogenerated by any scripts today. This should be fixed by phasing out `mockery` then re implement the mock files using `mockgen` and `go:generate`, also the newly generated files using `mockgen` should be... | Automate code generated by mockery using hack/update-mocks.sh and hack/verify-mocks.sh scripts | https://api.github.com/repos/kubernetes/kubernetes/issues/104771/comments | 2 | 2021-09-04T15:36:10Z | 2021-10-01T01:33:22Z | https://github.com/kubernetes/kubernetes/issues/104771 | 988,316,268 | 104,771 |
[
"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:
Service clus... | Servcie cluster ip leaks | https://api.github.com/repos/kubernetes/kubernetes/issues/104769/comments | 5 | 2021-09-04T12:41:57Z | 2021-09-05T23:07:19Z | https://github.com/kubernetes/kubernetes/issues/104769 | 988,285,955 | 104,769 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI -->
#### Which jobs are failing:
#### Which test(s) are failing:
#### Since when has it been failing:
#### Testgrid link:
#### Reason for failure:
#### Anything else we need to know:
| openAPIConfig.GetDefinitions | https://api.github.com/repos/kubernetes/kubernetes/issues/104768/comments | 2 | 2021-09-04T11:14:36Z | 2021-09-04T11:15:06Z | https://github.com/kubernetes/kubernetes/issues/104768 | 988,271,101 | 104,768 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
#### What happened:
When a node ... | Kubernetes Problems Creating Pods in Out of Network Nodes | https://api.github.com/repos/kubernetes/kubernetes/issues/104766/comments | 10 | 2021-09-04T04:52:04Z | 2021-10-28T20:48:37Z | https://github.com/kubernetes/kubernetes/issues/104766 | 988,210,268 | 104,766 |
[
"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 tried to... | Failed to mount PVC to pods in GKE cluster: timed out waiting for the condition | https://api.github.com/repos/kubernetes/kubernetes/issues/104764/comments | 3 | 2021-09-03T23:09:07Z | 2021-09-07T19:56:52Z | https://github.com/kubernetes/kubernetes/issues/104764 | 988,146,807 | 104,764 |
[
"kubernetes",
"kubernetes"
] | GA volume storage-provisioner annotation is added in this PR: https://github.com/kubernetes/kubernetes/pull/104590
At the same time, beta annotation is deprecated. This issue is to track the beta annotation removal after the deprecation period.
/sig storage
/cc @jsafrane @msau42
/triage accepted | Remove beta volume storage-provisioner annotation | https://api.github.com/repos/kubernetes/kubernetes/issues/104760/comments | 19 | 2021-09-03T17:57:13Z | 2024-10-29T08:51:56Z | https://github.com/kubernetes/kubernetes/issues/104760 | 987,991,678 | 104,760 |
[
"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:
ipvs mode di... | ipvs mode doesn't preserve client IP for NodePort Service with protocol SCTP and ExternalTrafficPolicy Local | https://api.github.com/repos/kubernetes/kubernetes/issues/104755/comments | 2 | 2021-09-03T15:08:43Z | 2021-09-09T22:34:56Z | https://github.com/kubernetes/kubernetes/issues/104755 | 987,870,277 | 104,755 |
[
"kubernetes",
"kubernetes"
] | #### Which jobs are flaking:
https://testgrid.k8s.io/sig-release-master-informing#node-kubelet-serial-containerd
Summary:
2 of 9 (22.2%) recent columns passed
#### Which test(s) are flaking:
kubetest.Node Tests
#### Testgrid link:
https://testgrid.k8s.io/sig-release-master-informing#node-kubelet-serial-con... | Flaky test: node-kubelet-serial-containerd | https://api.github.com/repos/kubernetes/kubernetes/issues/104754/comments | 9 | 2021-09-03T14:23:54Z | 2022-01-17T11:56:39Z | https://github.com/kubernetes/kubernetes/issues/104754 | 987,822,998 | 104,754 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
#### What happened:
I set up a k... | kubemark cluster can't work normally | https://api.github.com/repos/kubernetes/kubernetes/issues/104746/comments | 9 | 2021-09-03T06:44:53Z | 2022-01-31T14:38:30Z | https://github.com/kubernetes/kubernetes/issues/104746 | 987,452,999 | 104,746 |
[
"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:
(1) he... | helm uninstall chart , but ReplicaSet and Pod is exists on k8s | https://api.github.com/repos/kubernetes/kubernetes/issues/104745/comments | 7 | 2021-09-03T06:35:10Z | 2021-09-20T16:43:45Z | https://github.com/kubernetes/kubernetes/issues/104745 | 987,447,172 | 104,745 |
[
"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 can't crea... | Problem initializing cluster, "User "system:kube-controller-manager" cannot get resource "leases" in API group "coordination.k8s.io" in the namespace "kube-system"" | https://api.github.com/repos/kubernetes/kubernetes/issues/104738/comments | 15 | 2021-09-02T18:58:08Z | 2021-11-12T09:52:51Z | https://github.com/kubernetes/kubernetes/issues/104738 | 987,061,219 | 104,738 |
[
"kubernetes",
"kubernetes"
] | Is it possible to change request only without pod restart? I know about #24913. But requests seems to me to be safe to change
Example of usage:
We have blue green deployment. When new pods are starting they need few resources. When they switched to production poods need more resources (request only). After deploy... | pod updates:how to change the fields of spec.containers[].resources.request.cpu(memory) | https://api.github.com/repos/kubernetes/kubernetes/issues/104737/comments | 5 | 2021-09-02T18:12:56Z | 2021-09-05T23:13:55Z | https://github.com/kubernetes/kubernetes/issues/104737 | 987,026,130 | 104,737 |
[
"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 `kube-api... | kube-apiserver: Liveness probe failed: HTTP probe failed with statuscode: 401 | https://api.github.com/repos/kubernetes/kubernetes/issues/104731/comments | 7 | 2021-09-02T10:58:04Z | 2021-09-03T07:45:17Z | https://github.com/kubernetes/kubernetes/issues/104731 | 986,548,713 | 104,731 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about flaky tests or jobs (pass or fail with no underlying change in code) in Kubernetes CI -->
#### Which jobs are flaking:
https://prow.k8s.io/job-history/gs/kubernetes-jenkins/pr-logs/directory/pull-kubernetes-unit
#### Which test(s) are flaking:
... | pull-kubernetes-unit flake TestEnsurePIPTagged | https://api.github.com/repos/kubernetes/kubernetes/issues/104730/comments | 5 | 2021-09-02T10:37:01Z | 2021-09-03T07:15:50Z | https://github.com/kubernetes/kubernetes/issues/104730 | 986,525,953 | 104,730 |
[
"kubernetes",
"kubernetes"
] | how can i closed pod's FQDN when i was created pod by statefulset | close pod's FQDN | https://api.github.com/repos/kubernetes/kubernetes/issues/104724/comments | 4 | 2021-09-02T02:46:37Z | 2021-09-16T20:36:10Z | https://github.com/kubernetes/kubernetes/issues/104724 | 986,015,590 | 104,724 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
#### What happened:
While workin... | TestWatchBookmarksWithCorrectResourceVersion uses `*testing.T` in forked goroutine | https://api.github.com/repos/kubernetes/kubernetes/issues/104721/comments | 11 | 2021-09-01T22:14:35Z | 2022-07-03T16:50:26Z | https://github.com/kubernetes/kubernetes/issues/104721 | 985,759,914 | 104,721 |
[
"kubernetes",
"kubernetes"
] | A security issue was discovered in Kubernetes where actors that control the responses of MutatingWebhookConfiguration or ValidatingWebhookConfiguration requests are able to redirect kube-apiserver requests to private networks of the apiserver. If that user can view kube-apiserver logs when the log level is set to 10, t... | CVE-2020-8561: Webhook redirect in kube-apiserver | https://api.github.com/repos/kubernetes/kubernetes/issues/104720/comments | 17 | 2021-09-01T20:18:50Z | 2024-10-30T15:47:32Z | https://github.com/kubernetes/kubernetes/issues/104720 | 985,625,732 | 104,720 |
[
"kubernetes",
"kubernetes"
] | This came from discussions in - https://github.com/kubernetes/enhancements/pull/2914
And we should consider renaming the label to something more meaningful and a current proposed alternative is `volume_fsgroup_apply`.
/sig storage
| Rename volume_fsgroup_recursive_apply labe for volume operations to volume_fsgroup_apply | https://api.github.com/repos/kubernetes/kubernetes/issues/104717/comments | 4 | 2021-09-01T19:24:29Z | 2021-11-17T12:06:20Z | https://github.com/kubernetes/kubernetes/issues/104717 | 985,544,776 | 104,717 |
[
"kubernetes",
"kubernetes"
] | #### What would you like to be added:
Make node affinity and tolerations mutable for Jobs.
#### Why is this needed:
In https://github.com/kubernetes/kubernetes/issues/97170 we added a new flag to allow suspending jobs to control when the Pods of a Job get created by controller-manager. We proposed this as a p... | Make scheduling directives mutable for Jobs | https://api.github.com/repos/kubernetes/kubernetes/issues/104714/comments | 34 | 2021-09-01T14:52:57Z | 2025-02-20T23:02:37Z | https://github.com/kubernetes/kubernetes/issues/104714 | 985,253,828 | 104,714 |
[
"kubernetes",
"kubernetes"
] | <img width="350" alt="1" src="https://user-images.githubusercontent.com/89909933/131661632-4660f2fc-7d34-42a2-a144-a3ec03f46c27.PNG">
<img width="525" alt="2" src="https://user-images.githubusercontent.com/89909933/131661638-7c9bc799-6f66-4d53-bfc5-8aeeab3f301e.PNG">
<img width="550" alt="3" src="https://user-images.... | issue while installing Kubernetes cluster: | https://api.github.com/repos/kubernetes/kubernetes/issues/104710/comments | 8 | 2021-09-01T11:12:25Z | 2021-09-06T12:07:42Z | https://github.com/kubernetes/kubernetes/issues/104710 | 985,022,310 | 104,710 |
[
"kubernetes",
"kubernetes"
] |
#### What happened:
In a three-node cluster, we have Statefulset with replica-3. Each node in the cluster has a PV/PVC created in order to make sure one statefulset-pod to schedule on each node.
Initially all things are working good. But as part of our testing, we have hard-rebooted all three boxes with a ~60sec... | PV and PVC exists for POD but Scheduler still complains volume/node affinity | https://api.github.com/repos/kubernetes/kubernetes/issues/104709/comments | 10 | 2021-09-01T10:49:17Z | 2022-06-25T19:15:36Z | https://github.com/kubernetes/kubernetes/issues/104709 | 984,998,983 | 104,709 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
no explanation for metadata filed of NodeMetrics/PodMetrics, code:
https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/metrics/pkg/apis/metrics/v1beta1/types.go#L33
https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/metrics/pkg/apis/metrics/v1beta1/types.... | no explanation for metadata filed of NodeMetrics/PodMetrics | https://api.github.com/repos/kubernetes/kubernetes/issues/104707/comments | 2 | 2021-09-01T07:13:07Z | 2021-09-16T18:35:26Z | https://github.com/kubernetes/kubernetes/issues/104707 | 984,789,883 | 104,707 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
#### What happened:
I have a p... | Pod running on windows node with containerd runtime stuck at PodInitializing | https://api.github.com/repos/kubernetes/kubernetes/issues/104702/comments | 6 | 2021-09-01T02:04:01Z | 2022-01-04T03:02:34Z | https://github.com/kubernetes/kubernetes/issues/104702 | 984,518,796 | 104,702 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
We are developing a new k8s controller and decided to use SSA completely. We ran into an issue when I marked a field empty in the configuration for an existing object. I have a custom resource with field called 'prop1' and it is not a required field (see snippet below).
Scenario 1:
Using SSA... | Invalid value: "null" when field is empty in configuration and SSA is used to apply | https://api.github.com/repos/kubernetes/kubernetes/issues/104694/comments | 14 | 2021-08-31T20:11:24Z | 2024-05-23T17:33:45Z | https://github.com/kubernetes/kubernetes/issues/104694 | 984,270,728 | 104,694 |
[
"kubernetes",
"kubernetes"
] | #### Which jobs are flaking:
`pull-kubernetes-unit`
#### Which test(s) are flaking:
`TestApfExecuteWatchRequestsWithInitializationSignal`
#### Testgrid link:
Testgrid doesn't load kubernetes/test-infra#23425
#### Reason for failure:
From: https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/... | Data race in TestApfExecuteWatchRequestsWithInitializationSignal | https://api.github.com/repos/kubernetes/kubernetes/issues/104692/comments | 2 | 2021-08-31T19:53:58Z | 2021-09-03T15:35:49Z | https://github.com/kubernetes/kubernetes/issues/104692 | 984,248,249 | 104,692 |
[
"kubernetes",
"kubernetes"
] | *Disclaimer:* This is something that seems highly useful for users and simple to implement. I intend to complete this myself.
#### What would you like to be added:
When looking at the e2e test results you see stack traces like:
```
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/... | E2E test output should provide more useful stack traces | https://api.github.com/repos/kubernetes/kubernetes/issues/104685/comments | 8 | 2021-08-31T13:51:25Z | 2022-04-07T17:08:30Z | https://github.com/kubernetes/kubernetes/issues/104685 | 983,888,338 | 104,685 |
[
"kubernetes",
"kubernetes"
] | <!-- Feature requests are unlikely to make progress as an issue.
Instead, please suggest enhancements by engaging with SIGs on slack and mailing lists.
A proposal that works through the design along with the implications of the change can be opened as a KEP:
https://git.k8s.io/enhancements/keps#kubernetes-enhanc... | Default Scheduler Enhancement: add pods scheduling tracker metrics as a feature gate to track a pod scheduling lifecycle | https://api.github.com/repos/kubernetes/kubernetes/issues/104684/comments | 6 | 2021-08-31T12:58:06Z | 2021-09-09T11:53:30Z | https://github.com/kubernetes/kubernetes/issues/104684 | 983,832,032 | 104,684 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI -->
#### Which jobs are failing:
https://testgrid.k8s.io/sig-windows-networking#ltsc2019-containerd-flannel-sdnoverlay-master
#### Which test(s) are failing:
[Feature:Windows] SecurityContext ... | RunAsUsername Windows test fails with containerD master | https://api.github.com/repos/kubernetes/kubernetes/issues/104683/comments | 7 | 2021-08-31T12:49:51Z | 2021-09-01T16:37:23Z | https://github.com/kubernetes/kubernetes/issues/104683 | 983,824,449 | 104,683 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
Setup:
1. 3 Master nodes and 2 Worker Nodes.
2. Kubernetes Version: v1.22.0-rc.0+5c2f7cd
3. Configuring Memory Manager on Kubernetes Version (v1.22.0-rc.0+5c2f7cd) and Nodes configured with Hugepages of size 2M on 2 Worker nodes.
4. Each Worker node having 2 Numa Nodes (numa node0 and numa n... | Memory Manager allows Guaranteed QoS Pod with hugepages requested is exactly equal to the left over Hugepages | https://api.github.com/repos/kubernetes/kubernetes/issues/104682/comments | 2 | 2021-08-31T12:31:10Z | 2021-10-05T13:47:09Z | https://github.com/kubernetes/kubernetes/issues/104682 | 983,808,119 | 104,682 |
[
"kubernetes",
"kubernetes"
] | #### What would you like to be added:
The idea is to support CPU and memory profile creation via `runtime/pprof` for binaries like the kubelet. This allows to collect profiles over the complete lifetime of a binary, for example when running them in test suites or for debugging purposes.
#### Why is this needed:
... | Add `runtime/pprof` support to binaries like the kubelet | https://api.github.com/repos/kubernetes/kubernetes/issues/104681/comments | 9 | 2021-08-31T12:30:51Z | 2022-03-13T09:42:42Z | https://github.com/kubernetes/kubernetes/issues/104681 | 983,807,799 | 104,681 |
[
"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:
Nodes w... | Nodes become NotReady after adding ExternalIPs in ClusterIP or NodePort service | https://api.github.com/repos/kubernetes/kubernetes/issues/104679/comments | 7 | 2021-08-31T10:31:48Z | 2021-09-07T05:50:27Z | https://github.com/kubernetes/kubernetes/issues/104679 | 983,703,174 | 104,679 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
#### What happened:
When I cre... | Secrets bug | https://api.github.com/repos/kubernetes/kubernetes/issues/104678/comments | 13 | 2021-08-31T10:24:45Z | 2021-09-09T20:14:54Z | https://github.com/kubernetes/kubernetes/issues/104678 | 983,697,190 | 104,678 |
[
"kubernetes",
"kubernetes"
] |
#### What happened:
Although the `Strict` mode (i.e. what should disallow unknown and duplicate fields) is enabled in the `json.Serializer`; unknown fields in serialized data doesn't yield any error when specifying the `into` parameter of the `Decode(` function.
#### What you expected to happen:
Disallowing ... | Disallowing unknown fields doesn't work when decoding into an object in the JSON serializer | https://api.github.com/repos/kubernetes/kubernetes/issues/104661/comments | 12 | 2021-08-30T13:44:25Z | 2022-01-25T14:40:05Z | https://github.com/kubernetes/kubernetes/issues/104661 | 982,810,465 | 104,661 |
[
"kubernetes",
"kubernetes"
] |
#### What happened:
sessionAffinity based on ClientIP, is not maintained for a new UDP request followed by TCP request coming from same client.
Lets take two independent Kubernetes clusters **Cluster 1 & Cluster 2** , Each of them has two replicas of same application Pod. Like
**Cluster 1 : Pod A & Pod B**
... | sessionAffinity based on ClientIP, is not maintained for a new UDP request followed by TCP request from same client | https://api.github.com/repos/kubernetes/kubernetes/issues/104659/comments | 13 | 2021-08-30T11:34:55Z | 2021-09-05T23:19:36Z | https://github.com/kubernetes/kubernetes/issues/104659 | 982,695,089 | 104,659 |
[
"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://k8s-testgrid.appspot.com/sig-scalability-gce#gce-master-scale-performance
#### Which test(s) are flaking:
`gce-master-scale... | gce-master-scale-performance is failing | https://api.github.com/repos/kubernetes/kubernetes/issues/104657/comments | 5 | 2021-08-30T09:17:03Z | 2021-11-11T11:10:13Z | https://github.com/kubernetes/kubernetes/issues/104657 | 982,578,207 | 104,657 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
* Started a 1.22 cluster
* Added a static pod manifest
* Observed the pod run successfully
* Removed and recreated the pod manifest
* Observed the pod enter an error state and never restart successfully
#### What you expected to happen:
For the pod to be re-run successfully (as in previ... | 1.22 regression: removing and recreating static pod manifest leaves pod in error state | https://api.github.com/repos/kubernetes/kubernetes/issues/104648/comments | 31 | 2021-08-29T01:34:12Z | 2021-09-20T20:59:41Z | https://github.com/kubernetes/kubernetes/issues/104648 | 981,968,741 | 104,648 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
#### What happened:
The metric... | High cardinality on container_network_* metrics with hostNetwork | https://api.github.com/repos/kubernetes/kubernetes/issues/104647/comments | 8 | 2021-08-28T19:08:29Z | 2022-02-22T08:51:07Z | https://github.com/kubernetes/kubernetes/issues/104647 | 981,907,461 | 104,647 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
Pod DNS look ups fail
#### What you expected to happen:
DNS lookups work
#### How to reproduce it (as minimally and precisely as possible):
There are 3 nodes (IPs in brackets): k-m-001 (10.7.50.11), k-w-001 (10.7.60.11), k-w-001 (10.7.60.12). This is a /16 network.
I installed Kubernetes o... | Pod DNS failure | https://api.github.com/repos/kubernetes/kubernetes/issues/104645/comments | 5 | 2021-08-28T07:10:21Z | 2021-09-05T21:12:23Z | https://github.com/kubernetes/kubernetes/issues/104645 | 981,759,007 | 104,645 |
[
"kubernetes",
"kubernetes"
] | my problem is summarized [here](https://stackoverflow.com/questions/68958322/how-to-use-kubernetes-indexed-job).
I have no idea why this doesn't works.
| Kubernetes 'Indexed-Job' does not works | https://api.github.com/repos/kubernetes/kubernetes/issues/104644/comments | 4 | 2021-08-28T06:57:38Z | 2021-08-28T16:55:44Z | https://github.com/kubernetes/kubernetes/issues/104644 | 981,756,293 | 104,644 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI -->
#### Which jobs are failing:
after restart network nodeport cannot access,or telnet ip:nodeport failure
CentOS Linux release 7.5.1804 (Core),GitVersion:"v1.13.3
claas/kube-proxy:v1.13.3
!... | after restart network nodeport cannot access,or telnet ip:nodeport failure | https://api.github.com/repos/kubernetes/kubernetes/issues/104643/comments | 6 | 2021-08-28T04:39:06Z | 2021-09-16T20:36:20Z | https://github.com/kubernetes/kubernetes/issues/104643 | 981,726,679 | 104,643 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
The order of `initContainers` is significant, but when using `kubectl apply --server-side` to change this field, the intended order is not preserved.
#### What you expected to happen:
I expected the order of `initContainers` to match my submitted intent.
#### How to reproduce it (as mini... | Incorrect initContainers order when using server-side apply | https://api.github.com/repos/kubernetes/kubernetes/issues/104641/comments | 20 | 2021-08-28T02:11:32Z | 2022-01-14T20:32:26Z | https://github.com/kubernetes/kubernetes/issues/104641 | 981,698,631 | 104,641 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
#### What happened:
RateLimitedQ... | Node Lifecycle RateLimitedQueue QPS issue | https://api.github.com/repos/kubernetes/kubernetes/issues/104639/comments | 13 | 2021-08-27T21:43:12Z | 2022-11-26T05:26:07Z | https://github.com/kubernetes/kubernetes/issues/104639 | 981,616,846 | 104,639 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
Details here: https://github.com/kubernetes/kubernetes/issues/98278
#### What you expected to happen:
NLB should not delete SG rules added manually during LB reconcile.
#### How to reproduce it (as minimally and precisely as possible):
Details here: https://github.com/kubernetes/kubernetes... | Kubernetes Service Document Update for AWS | https://api.github.com/repos/kubernetes/kubernetes/issues/104638/comments | 7 | 2021-08-27T21:42:21Z | 2022-01-29T22:18:48Z | https://github.com/kubernetes/kubernetes/issues/104638 | 981,616,473 | 104,638 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
```bash
➜ k auth can-i --as=dmitry --as-group=system:master get pods -n argo-cd
Error from server: impersonation request has been denied, group header "system:master" value is not allowed in roles
➜ k get clusterrolebinding system:master -o yaml
apiVersion: rbac.authorization.k8s.io/v1
kin... | kubernetes auth error: impersonation request has been denied, group header value is not allowed in roles | https://api.github.com/repos/kubernetes/kubernetes/issues/104637/comments | 5 | 2021-08-27T20:59:15Z | 2021-09-01T12:31:46Z | https://github.com/kubernetes/kubernetes/issues/104637 | 981,592,620 | 104,637 |
[
"kubernetes",
"kubernetes"
] | <!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI -->
#### Which jobs are failing:
ci-kubernetes-e2e-aks-engine-azure-master-windows-containerd-nightly
#### Which test(s) are failing:
Kubernetes e2e suite.[sig-windows] [Feature:Windows] Securit... | Pods that fail to create podsandbox due to errors don't mark the pods as failed | https://api.github.com/repos/kubernetes/kubernetes/issues/104635/comments | 8 | 2021-08-27T19:56:16Z | 2021-10-28T21:22:01Z | https://github.com/kubernetes/kubernetes/issues/104635 | 981,552,692 | 104,635 |
[
"kubernetes",
"kubernetes"
] | #### What happened:
I have a deployment where each pod has 1 initContainer and 3 regular containers. These pods usually work as expected, however I have observed several times now that occasionally they manage to fall into a state where the 3 regular containers are working and serving traffic, _while the initContainer... | Init Container in CrashLoop while regular containers are running | https://api.github.com/repos/kubernetes/kubernetes/issues/104629/comments | 15 | 2021-08-27T12:14:06Z | 2022-03-29T11:18:25Z | https://github.com/kubernetes/kubernetes/issues/104629 | 981,189,460 | 104,629 |
[
"kubernetes",
"kubernetes"
] | I am trying to preserve unknown fields dropped in CRD version v1 by default. I tried adding `preserveUnknownFields=true` in the CRD_OPTIONS as shown below:
`CRD_OPTIONS?="crd:trivialVersions=true,crdVersions=v1beta1,preserveUnknownFields=true" `However, once I added this and applied the changes, I get the followin... | Preserving unknown fields in CRD version v1 | https://api.github.com/repos/kubernetes/kubernetes/issues/104628/comments | 5 | 2021-08-27T11:24:25Z | 2021-08-31T20:23:18Z | https://github.com/kubernetes/kubernetes/issues/104628 | 981,151,115 | 104,628 |
Subsets and Splits
Unique Owner-Repo Count
Counts the number of unique owner-repos in the dataset, providing a basic understanding of diverse repositories.