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"
] | ### Failure cluster [744a4b0836673f8abb50](https://go.k8s.io/triage#744a4b0836673f8abb50)
##### Error text:
```
test/e2e_node/critical_pod_test.go:47
Unexpected error:
<*fmt.wrapError | 0xc000e0a360>: {
msg: "error while waiting for pod critical-pod-test-1603/static-critical-pod to be running and re... | Failure cluster [744a4b08...]: test/e2e_node/critical_pod_test.go:47 | https://api.github.com/repos/kubernetes/kubernetes/issues/109883/comments | 2 | 2022-05-07T07:34:29Z | 2022-05-07T07:36:03Z | https://github.com/kubernetes/kubernetes/issues/109883 | 1,228,557,077 | 109,883 |
[
"kubernetes",
"kubernetes"
] | ### Failure cluster [16ae3f774c3255733716](https://go.k8s.io/triage#16ae3f774c3255733716)
##### Error text:
```
test/e2e/common/node/downwardapi.go:295
May 4 11:36:57.292: Feature gate checking is not enabled, don't use SkipUnlessFeatureGateEnabled(DownwardAPIHugePages). Instead use the Feature tag.
test/e2e/co... | Failing test: Feature gate checking is not enabled | https://api.github.com/repos/kubernetes/kubernetes/issues/109882/comments | 10 | 2022-05-07T07:31:54Z | 2022-05-13T06:36:33Z | https://github.com/kubernetes/kubernetes/issues/109882 | 1,228,556,556 | 109,882 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
ci-benchmark-scheduler-perf-master
### Which tests are failing?
- BenchmarkPerfScheduling/PreemptionBasic/5000Nodes
- BenchmarkPerfScheduling/PreemptionPVs/5000Nodes
### Since when has it been failing?
Unclear. It seems to be failing for a while, consistently.
### Testgrid link
https... | [sched-perf] PreemptionBasic/5000Nodes and PreemptionPVs/5000Nodes failures | https://api.github.com/repos/kubernetes/kubernetes/issues/109881/comments | 6 | 2022-05-07T05:48:39Z | 2022-10-05T03:16:43Z | https://github.com/kubernetes/kubernetes/issues/109881 | 1,228,536,180 | 109,881 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
How does efk integrate with LDAP in k8s
efk在k8s里怎么和ldap集成
### What did you expect to happen?
Efk login with LDAP user
efk用ldap用户登录
### How can we reproduce it (as minimally and precisely as possible)?
Efk login with LDAP user
### Anything else we need to know?
_No response_
### Ku... | How does efk integrate with LDAP in k8s | https://api.github.com/repos/kubernetes/kubernetes/issues/109878/comments | 6 | 2022-05-07T02:38:16Z | 2022-05-10T10:30:41Z | https://github.com/kubernetes/kubernetes/issues/109878 | 1,228,499,263 | 109,878 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
Similar to #109475
Today, in the scheduler volumebinding plugin, the bound PV node affinity check is done during `Filter` stage which means that all nodes are considered.
For the case of bound **local** PV, the PV node affinity spec looks like
```yaml
nodeAffinity:
... | scheduler volumebinding: leverage PreFilterResult for Bound local PersistentVolumes | https://api.github.com/repos/kubernetes/kubernetes/issues/109876/comments | 9 | 2022-05-06T23:59:13Z | 2022-12-13T22:54:01Z | https://github.com/kubernetes/kubernetes/issues/109876 | 1,228,465,102 | 109,876 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
* Related to https://github.com/kubernetes/kubernetes/pull/109031
Seeing the following errors in kube-apiserver logs when CRDs are applied:
```
W0505 23:04:14.625582 55 merge.go:121] Should not happen: OpenAPI V3 merge schema conflict on io.k8s.apimachinery.pkg.apis.meta.v1.FieldsV1
W0... | `Should not happen: OpenAPI V3 merge schema conflict` when applying CRDs | https://api.github.com/repos/kubernetes/kubernetes/issues/109871/comments | 5 | 2022-05-06T18:38:08Z | 2022-05-13T22:31:55Z | https://github.com/kubernetes/kubernetes/issues/109871 | 1,228,272,035 | 109,871 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Currently, the number of retries is calculated in two ways:
1. The number of Pods with `.status.phase = "Failed"`.
2. When using `restartPolicy = "OnFailure"`, the number of retries in all the containers of Pods with `.status.phase` equal to `Pending` or `Running`.
Only the first number is r... | When restartPolicy=OnFailure the calculation for number of retries is not accurate | https://api.github.com/repos/kubernetes/kubernetes/issues/109870/comments | 3 | 2022-05-06T18:20:52Z | 2022-06-13T13:34:13Z | https://github.com/kubernetes/kubernetes/issues/109870 | 1,228,226,785 | 109,870 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are flaking?
pull-kubernetes-conformance-kind-ga-only-parallel
### Which tests are flaking?
Kubernetes e2e suite: [sig-node] ConfigMap should be consumable via the environment [NodeConformance] [Conformance]
### Since when has it been flaking?
unknown
### Testgrid link
https://tes... | [Flaking test] Kubernetes e2e suite: [sig-node] ConfigMap should be consumable via the environment [NodeConformance] [Conformance] | https://api.github.com/repos/kubernetes/kubernetes/issues/109864/comments | 5 | 2022-05-06T15:23:02Z | 2022-10-06T09:34:31Z | https://github.com/kubernetes/kubernetes/issues/109864 | 1,228,001,374 | 109,864 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are flaking?
pull-kubernetes-conformance-kind-ga-only-parallel
### Which tests are flaking?
Kubernetes e2e suite: [sig-storage] Projected secret optional updates should be reflected in volume [NodeConformance] [Conformance]
### Since when has it been flaking?
unknown
### Testgrid link
https://t... | [Flaking test] Kubernetes e2e suite: [sig-storage] Projected secret optional updates should be reflected in volume [NodeConformance] [Conformance] | https://api.github.com/repos/kubernetes/kubernetes/issues/109863/comments | 5 | 2022-05-06T15:20:15Z | 2022-10-03T17:04:09Z | https://github.com/kubernetes/kubernetes/issues/109863 | 1,227,997,971 | 109,863 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I'm deploying addon manager v9.1.6:
```
...
- command:
- /bin/bash
- -c
- exec /opt/kube-addons-main.sh
env:
- name: ADDON_CHECK_INTERVAL_SEC
value: "180"
- name: ADDON_PATH
value: /var/kubernetes/addons/
image... | kube-addon-manager seems to ignore ADDON_CHECK_INTERVAL_SEC var | https://api.github.com/repos/kubernetes/kubernetes/issues/109862/comments | 5 | 2022-05-06T14:43:17Z | 2022-05-10T10:04:05Z | https://github.com/kubernetes/kubernetes/issues/109862 | 1,227,958,488 | 109,862 |
[
"kubernetes",
"kubernetes"
] | ### Failure cluster [3aba724e4e525dc8072c](https://go.k8s.io/triage#3aba724e4e525dc8072c)
##### Error text:
```
=== RUN TestStaticPodExclusion
pod_workers_test.go:865: unexpected status for pod 5: &kubelet.podSyncStatus{ctx:context.Context(nil), cancelFn:(context.CancelFunc)(nil), working:false, fullname:"p... | Failure cluster [3aba724e...] TestStaticPodExclusion flake | https://api.github.com/repos/kubernetes/kubernetes/issues/109851/comments | 3 | 2022-05-06T07:42:31Z | 2022-07-29T20:17:44Z | https://github.com/kubernetes/kubernetes/issues/109851 | 1,227,527,639 | 109,851 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are flaking?
pull-kubernetes-unit
### Which tests are flaking?
Test_managerImpl_processShutdownEvent
### Since when has it been flaking?
?
### Testgrid link
https://testgrid.k8s.io/presubmits-kubernetes-blocking#pull-kubernetes-unit&include-filter-by-regex=Test_managerImpl_processShutdownEvent
##... | Flaky Test_managerImpl_processShutdownEvent unit test | https://api.github.com/repos/kubernetes/kubernetes/issues/109848/comments | 8 | 2022-05-06T04:36:08Z | 2022-12-16T07:57:22Z | https://github.com/kubernetes/kubernetes/issues/109848 | 1,227,410,323 | 109,848 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are flaking?
pull-kubernetes-integration
### Which tests are flaking?
TestNamespaceAuthorization
### Since when has it been flaking?
unknown
### Testgrid link
https://testgrid.k8s.io/presubmits-kubernetes-blocking#pull-kubernetes-integration&include-filter-by-regex=TestNamespaceAuthorization
### ... | Flaky TestNamespaceAuthorization integration test | https://api.github.com/repos/kubernetes/kubernetes/issues/109847/comments | 8 | 2022-05-06T04:26:54Z | 2022-09-12T16:17:48Z | https://github.com/kubernetes/kubernetes/issues/109847 | 1,227,405,736 | 109,847 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
While working on the code, I noticed a bug: apiserver_flowcontrol_read_vs_write_request_count_samples is a histogram of _ratios_, but when API Priority and Fairness is used the denominator is left defaulted to 1.0 rather than set to something meaning like what is done when the max-in-flight filters ... | Denominator not set for apiserver_flowcontrol_read_vs_write_request_count_samples | https://api.github.com/repos/kubernetes/kubernetes/issues/109846/comments | 4 | 2022-05-05T21:59:41Z | 2022-07-25T20:32:35Z | https://github.com/kubernetes/kubernetes/issues/109846 | 1,227,216,724 | 109,846 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
https://github.com/kubernetes/apimachinery uses versions starting with 0, so v0.24.0 for example. That makes it impossible to use multiple versions (for example for kubernetes 1.20 and 1.23) in one project.
I understand that just mirroring the kubernetes version (so using v1.24) is not desirable ... | Current versioning scheme for golang code makes it impossible to use multiple versions in one project | https://api.github.com/repos/kubernetes/kubernetes/issues/109842/comments | 12 | 2022-05-05T20:46:55Z | 2022-09-22T08:34:45Z | https://github.com/kubernetes/kubernetes/issues/109842 | 1,227,161,184 | 109,842 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
We found that the the serialization specification for the `Quantity` type does not conform to the real implementation of parse function. The serialization specification is found here in the documentation https://github.com/kubernetes/kubernetes/blob/f02682c628c530219966a00ae002d799f0d813dc/staging/s... | Quantity type's validation does not conform to its serialization specification | https://api.github.com/repos/kubernetes/kubernetes/issues/109839/comments | 14 | 2022-05-05T19:56:20Z | 2025-03-04T21:29:26Z | https://github.com/kubernetes/kubernetes/issues/109839 | 1,227,116,197 | 109,839 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
Expose network packet stats in kubelet Summary API:
- RxPackets: Cumulative count of packets received
- RxDropped: Cumulative count of packets dropped while receiving
- TxPackets: Cumulative count of packets transmitted
- TxDropped: Cumulative count of packets dropped whil... | Add network packet stats in kubelet Summary API | https://api.github.com/repos/kubernetes/kubernetes/issues/109837/comments | 10 | 2022-05-05T19:48:19Z | 2023-01-15T11:04:46Z | https://github.com/kubernetes/kubernetes/issues/109837 | 1,227,109,175 | 109,837 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
Today, unit-level tests only exist for `*etcd3.store{}`, and cannot be run against any other implementation of `storage.Interface`. In general, these tests define what it means to be a correct implementation of `storage.Interface`, and only use exported functionality. We aim to r... | apiserver/storage: test caching and indexing layers at the unit level | https://api.github.com/repos/kubernetes/kubernetes/issues/109831/comments | 26 | 2022-05-05T15:31:54Z | 2025-03-04T21:26:53Z | https://github.com/kubernetes/kubernetes/issues/109831 | 1,226,837,233 | 109,831 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
Follow-up to https://github.com/kubernetes/kubernetes/pull/105126. Discussed in https://github.com/kubernetes/kubernetes/pull/105126#discussion_r783142176.
As part of kubelet tracing beta, we should add tracing support to the kubelet's read-only endpoint, which currently does n... | Add Tracing to the kubelet's read-only endpoint | https://api.github.com/repos/kubernetes/kubernetes/issues/109829/comments | 19 | 2022-05-05T14:59:56Z | 2024-04-18T06:59:35Z | https://github.com/kubernetes/kubernetes/issues/109829 | 1,226,793,890 | 109,829 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
Windows GCE jobs:
https://testgrid.k8s.io/sig-windows-gce#gce-windows-2019-containerd-master
https://testgrid.k8s.io/sig-windows-gce#gce-windows-20h2-containerd-master
### Which tests are failing?
[sig-windows] [Feature:WindowsHostProcessContainers] [MinimumKubeletVersion:1.22] Host... | Windows HostProcessContainer jobs fail due to mismatching COMPUTERNAME | https://api.github.com/repos/kubernetes/kubernetes/issues/109821/comments | 3 | 2022-05-05T13:08:01Z | 2022-05-05T16:38:55Z | https://github.com/kubernetes/kubernetes/issues/109821 | 1,226,650,890 | 109,821 |
[
"kubernetes",
"kubernetes"
] | May 05 17:01:38 master-01 kubelet[127119]: I0505 17:01:38.612023 127119 kuberuntime_manager.go:222] "Container runtime initialized" containerRuntime="docker" version="20.10.14" apiVersion="1.41.0"
May 05 17:01:44 master-01 kubelet[127119]: E0505 17:01:44.749930 127119 aws_credentials.go:77] while getting AWS credent... | faild to start kubelet | https://api.github.com/repos/kubernetes/kubernetes/issues/109817/comments | 8 | 2022-05-05T09:55:29Z | 2022-10-02T14:55:09Z | https://github.com/kubernetes/kubernetes/issues/109817 | 1,226,455,052 | 109,817 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
.:53
2021-12-24T10:19:33.706Z [INFO] CoreDNS-1.2.6
2021-12-24T10:19:33.706Z [INFO] linux/amd64, go1.11.2, 756749c
CoreDNS-1.2.6
linux/amd64, go1.11.2, 756749c
[INFO] plugin/reload: Running configuration MD5 = 64abacc4c5a9834ab518a99b06d65a7d
E0411 11:27:17.278584 1 str... | coredns pod logs error info | https://api.github.com/repos/kubernetes/kubernetes/issues/109815/comments | 8 | 2022-05-05T09:12:13Z | 2022-06-09T13:33:59Z | https://github.com/kubernetes/kubernetes/issues/109815 | 1,226,410,920 | 109,815 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
In dual stack cluster , all the pods have both Ipv6 and Ipv4 interfaces. However there would be scenarios where user does not to enable dual stack for all the pods . So basically the ask is to restrict IP families to certain POD. We should be able to specify certain pods to opera... | As a user I want to be able to restrict IP families to some pods | https://api.github.com/repos/kubernetes/kubernetes/issues/109814/comments | 48 | 2022-05-05T09:08:59Z | 2024-06-07T20:01:54Z | https://github.com/kubernetes/kubernetes/issues/109814 | 1,226,407,587 | 109,814 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I doubt whether the API configuration is wrong, because the created serviceaccount does not seem to be mounted in the pod container
```
[root@testwithsa /run/secrets/kubernetes.io/serviceaccount]$ curl --cacert ./ca.crt -H "Authorization: Bearer $(cat ./token)" https://10.1.1.100:6443/namespace/$(... | new invalid bearer token, square/go-jose: error in cryptographic primitive | https://api.github.com/repos/kubernetes/kubernetes/issues/109812/comments | 13 | 2022-05-05T08:28:58Z | 2022-09-12T16:23:25Z | https://github.com/kubernetes/kubernetes/issues/109812 | 1,226,360,010 | 109,812 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
The iptables is upgraded from 1.4.21 to v1.8.6 (nf_tables) when os is upgraded.
I have followed the document in [https://github.com/kubernetes-sigs/iptables-wrappers](url) and added iptables-wrappers in kube-proxy pod.
But rules in iptables-legacy is not clear. If some pods were rebuild, then ... | when upgrade iptables from 1.4.21 to v1.8.6 (nf_tables), rules in iptables-legacy is not clear. | https://api.github.com/repos/kubernetes/kubernetes/issues/109811/comments | 4 | 2022-05-05T07:45:54Z | 2022-05-26T14:40:32Z | https://github.com/kubernetes/kubernetes/issues/109811 | 1,226,308,969 | 109,811 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I made myself a shiny new Ubuntu 22.04 VM and tricked it out for building Kubernetes. But `hack/local-up-cluster.sh` repeatedly failed with a bogus complaint from the linker about not being able to open some files due to "cannot allocate memory". This VM has 24 GiB of memory and 4 vCPUs. I moni... | make fails on second and subsequent runs, with "...go/pkg/tool/linux_amd64/link: cannot open file ... cannot allocate memory" | https://api.github.com/repos/kubernetes/kubernetes/issues/109808/comments | 9 | 2022-05-05T05:20:35Z | 2022-10-02T07:55:08Z | https://github.com/kubernetes/kubernetes/issues/109808 | 1,226,209,358 | 109,808 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
After running for a period of time, the ip cannot be obtained in the pod, hang while executing ipconfig command
### What did you expect to happen?
The container ip can be obtained normally
### How can we reproduce it (as minimally and precisely as possible)?
- start pod
- set pod use hostNetwor... | windows pod exec ipconfig hang，can not get ip | https://api.github.com/repos/kubernetes/kubernetes/issues/109807/comments | 7 | 2022-05-05T04:02:25Z | 2022-05-13T16:58:03Z | https://github.com/kubernetes/kubernetes/issues/109807 | 1,226,175,226 | 109,807 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When I configured a Pod with startupProbe but without a readinessProbe, the pod will take extra time (40-60 seconds) to be ready.
For example, if the startupProbe is configured as below, and readinessProbe is not configured at all
```
startupProbe:
exec:
command:
- echo
- st... | When a Pod is configured with startupProbe but without readinessProbe, the Pod will take extra time to be ready | https://api.github.com/repos/kubernetes/kubernetes/issues/109802/comments | 7 | 2022-05-04T21:11:17Z | 2022-05-05T15:10:44Z | https://github.com/kubernetes/kubernetes/issues/109802 | 1,225,974,748 | 109,802 |
[
"kubernetes",
"kubernetes"
] | I have a custom resource `Foo` which is automatically created by a controller whenever there are events from a kubernetes resource `Bar`.
`Foo`'s deletion should be allowed only when `Bar` is deleted. It should be possible to add watches in the controller and re-create `Foo` in case it was deleted accidentally, but ... | Is there a way to prevent a CustomResource from being deleted if it is still needed | https://api.github.com/repos/kubernetes/kubernetes/issues/109801/comments | 6 | 2022-05-04T20:58:20Z | 2022-05-10T10:21:18Z | https://github.com/kubernetes/kubernetes/issues/109801 | 1,225,963,946 | 109,801 |
[
"kubernetes",
"kubernetes"
] | Let's assume this scenario:
- linux node, zone A, tainted
- windows node, zone B, untainted
In a multizone cluster, while trying to run the generic ephemeral volume tests in Windows nodes it might be possible that a volume that's supposed to be for a Windows node is created in the zone for the Linux node instead... | Generic ephemeral volume e2e tests may fail in a multizone cluster | https://api.github.com/repos/kubernetes/kubernetes/issues/109800/comments | 10 | 2022-05-04T20:39:47Z | 2023-01-31T00:20:51Z | https://github.com/kubernetes/kubernetes/issues/109800 | 1,225,949,850 | 109,800 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
once the we hit a beta release, we can reset the default value for strict handling to false to prep for 1.25. It will likely be introduced in https://github.com/kubernetes/kubernetes/pull/108797
/kind bug
/priority important-soon
/milestone v1.25
https://github.com/orgs/kubernetes/teams/sig-... | reset deleted_kinds strictRemovedHandlingInAlpha to false after beta | https://api.github.com/repos/kubernetes/kubernetes/issues/109799/comments | 4 | 2022-05-04T19:44:45Z | 2022-08-10T14:52:33Z | https://github.com/kubernetes/kubernetes/issues/109799 | 1,225,833,642 | 109,799 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
If there is a connection failure when updating the Pod status, we don't retry.
Furthermore, due to #108761, we won't have another chance until much later.
The problem is that if we don't mark the Pod as Unschedulable, other controllers (such as cluster-autoscaler) wouldn't react to these pods.... | Unschedulable Pod might take a long time to get the condition set | https://api.github.com/repos/kubernetes/kubernetes/issues/109796/comments | 5 | 2022-05-04T18:10:13Z | 2022-07-19T02:52:06Z | https://github.com/kubernetes/kubernetes/issues/109796 | 1,225,712,514 | 109,796 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I am reproducing this in OpenShift using the OpenStack cloud provider, but nothing here is specific to either OpenShift or OpenStack.
When migrating a cluster which uses in-tree cloud provider to use external cloud-provider, we use the following process:
1. Disable cloud controllers in KCM
... | Enabling external CCM causes Node.Addresses to flap | https://api.github.com/repos/kubernetes/kubernetes/issues/109793/comments | 6 | 2022-05-04T16:46:38Z | 2022-07-14T21:36:40Z | https://github.com/kubernetes/kubernetes/issues/109793 | 1,225,625,850 | 109,793 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are flaking?
pull-kubernetes-unit
### Which tests are flaking?
TestStatefulSetControlOnDeleteUpdate
### Since when has it been flaking?
Maybe May 4th
### Testgrid link
https://testgrid.k8s.io/presubmits-kubernetes-blocking#pull-kubernetes-unit&include-filter-by-regex=TestStatefulSetControlOnDelete... | Flaky unit test TestStatefulSetControlOnDeleteUpdate | https://api.github.com/repos/kubernetes/kubernetes/issues/109791/comments | 5 | 2022-05-04T16:07:50Z | 2022-10-01T17:47:07Z | https://github.com/kubernetes/kubernetes/issues/109791 | 1,225,585,969 | 109,791 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are flaking?
pull-kubernetes-integration
### Which tests are flaking?
Test_ServiceLoadBalancerDisableAllocateNodePorts
### Since when has it been flaking?
unknown
### Testgrid link
https://testgrid.k8s.io/presubmits-kubernetes-blocking#pull-kubernetes-integration&include-filter-by-regex=Test_Servi... | Flaky Test_ServiceLoadBalancerDisableAllocateNodePorts integration test | https://api.github.com/repos/kubernetes/kubernetes/issues/109785/comments | 7 | 2022-05-04T14:32:31Z | 2022-05-26T16:01:44Z | https://github.com/kubernetes/kubernetes/issues/109785 | 1,225,457,266 | 109,785 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I start traefik through the pod container
pod is running
pod log error：
```
"Provider connection error: could not retrieve server version: the server has asked for the client to provide credentials; retrying in 1.127867932s","providerName":"kubernetes","time":"2022-05-04T13:52:32Z"}
```
I thin... | invalid bearer token, square/go-jose: error in cryptographic primitive | https://api.github.com/repos/kubernetes/kubernetes/issues/109784/comments | 7 | 2022-05-04T14:05:02Z | 2022-10-02T06:55:08Z | https://github.com/kubernetes/kubernetes/issues/109784 | 1,225,422,219 | 109,784 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are flaking?
pull-kubernetes-integration
### Which tests are flaking?
TestSchedulerInformers, TestPodTopologySpreadFilter, TestTaintNodeByCondition
### Since when has it been flaking?
Unknown
### Testgrid link
https://testgrid.k8s.io/presubmits-kubernetes-blocking#pull-kubernetes-int... | Flaky scheduler integration tests | https://api.github.com/repos/kubernetes/kubernetes/issues/109783/comments | 20 | 2022-05-04T13:34:23Z | 2022-05-09T06:10:28Z | https://github.com/kubernetes/kubernetes/issues/109783 | 1,225,381,899 | 109,783 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When creating a service of type `LoadBalancer` with `externalTrafficPolicy` set to `Local`, kube-proxy on Windows does not seem to create a LoadBalancer via the HNS on the Windows node to route the traffic to the internal service endpoints, while kube-proxy on Linux does create the IPTables rules ... | Windows node does not route traffic to internal service IP | https://api.github.com/repos/kubernetes/kubernetes/issues/109780/comments | 33 | 2022-05-04T11:44:57Z | 2023-01-07T14:39:24Z | https://github.com/kubernetes/kubernetes/issues/109780 | 1,225,258,749 | 109,780 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
* Some external controller deleted node object while kubelet was alive
* Due to ignoring errors in kubelet's lease logic, it created lease without ownerReference set
### What did you expect to happen?
* Kubelet doesn't create lease without ownerReference set in any case, even pathological one
##... | Kubelet creates leases without ownerReference set if node doesn't exist | https://api.github.com/repos/kubernetes/kubernetes/issues/109777/comments | 10 | 2022-05-04T09:34:28Z | 2023-08-21T18:09:25Z | https://github.com/kubernetes/kubernetes/issues/109777 | 1,225,134,115 | 109,777 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.24.md has some broken links. These are relative links that work OK in the release blog article but need to be absolute hyperlinks in the release notes.
### What did you expect to happen?
Links in release notes work.
### Ho... | Broken links in release notes | https://api.github.com/repos/kubernetes/kubernetes/issues/109771/comments | 3 | 2022-05-03T23:08:10Z | 2022-05-05T15:14:27Z | https://github.com/kubernetes/kubernetes/issues/109771 | 1,224,754,067 | 109,771 |
[
"kubernetes",
"kubernetes"
] | [Here](https://kubernetes.io/docs/reference/kubernetes-api/workload-resources/pod-v1/#Container) the text of the **name** specification contains:
> Name of the container specified as a DNS_LABEL.
However the documentation for [Object Names and IDs](https://kubernetes.io/docs/concepts/overview/working-with-objects... | Improve PodSpec Container name documentation | https://api.github.com/repos/kubernetes/kubernetes/issues/109769/comments | 12 | 2022-05-03T13:47:37Z | 2022-09-30T23:45:07Z | https://github.com/kubernetes/kubernetes/issues/109769 | 1,224,176,631 | 109,769 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
I am trying to configure the NUMA Affinity in kubernets cluster. We have configured Hugepage as well CPU Pinning and same has been passed to Kubelet of Workernode.
### Which tests are failing?
29867 cpu_manager.go:158] "Detected CPU topology" topology=&{NumCPUs:8 NumCores:4 NumSoc... | NUMA Affinity Configuration | https://api.github.com/repos/kubernetes/kubernetes/issues/109766/comments | 12 | 2022-05-03T08:23:45Z | 2022-11-05T18:45:32Z | https://github.com/kubernetes/kubernetes/issues/109766 | 1,223,814,366 | 109,766 |
[
"kubernetes",
"kubernetes"
] | Is there a similar parameter that I can quickly get to a default kube-api or con-manager systemd configuration file ? | kubeadm config print can get default kubeadm config, but if use binary install, i need to get every parameter meaning | https://api.github.com/repos/kubernetes/kubernetes/issues/109765/comments | 4 | 2022-05-03T06:13:08Z | 2022-05-03T07:50:44Z | https://github.com/kubernetes/kubernetes/issues/109765 | 1,223,728,609 | 109,765 |
[
"kubernetes",
"kubernetes"
] | # Progress <code>[6/6]</code>
- [x] APISnoop org-flow: [CoreV1NamespaceStatusTest.org](https://github.com/apisnoop/ticket-writing/blob/master/CoreV1NamespacedStatusTest.org)
- [x] test approval issue : #109762
- [x] test pr : #109763 109763
- [x] two weeks soak start date : [testgrid](https://testgrid.k8s.io/sig-... | Write NamespaceStatus endpoints test +3 Endpoints | https://api.github.com/repos/kubernetes/kubernetes/issues/109762/comments | 3 | 2022-05-02T23:37:14Z | 2022-08-02T19:47:55Z | https://github.com/kubernetes/kubernetes/issues/109762 | 1,223,466,594 | 109,762 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
This is a very minor good first issue for conformance understandability... esp in terms of Distruptive conformance tests which i think folks need to understand for production clusters.
I think the logging messages for "why" were tainting the node, and why were removing the taint, etc... could b... | [minor] improve the "tainting node" log message to be easier to understand | https://api.github.com/repos/kubernetes/kubernetes/issues/109754/comments | 10 | 2022-05-02T14:27:47Z | 2022-09-15T20:36:50Z | https://github.com/kubernetes/kubernetes/issues/109754 | 1,222,958,812 | 109,754 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
1. We have an object X that has ownerReference set to Y
2. garbage collector is down (for whatever reason)
3. Something deletes Y
4. garbage collector starts
5. garbage collector never attempts to delete X (despite its ownerReference is dangling), as the code isn't verifying if objects added as ... | GC doesn't delete already orphaned objects after startup | https://api.github.com/repos/kubernetes/kubernetes/issues/109748/comments | 7 | 2022-05-02T09:14:13Z | 2022-05-04T08:21:31Z | https://github.com/kubernetes/kubernetes/issues/109748 | 1,222,661,627 | 109,748 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Here is a list of TODOs that could be fixed for Ginkgo migration from v1 to v2.
* [x] Lost the validation on the SIGDescribe: https://github.com/kubernetes/kubernetes/issues/109724
* [x] Ginkgo V2 currently cannot get the number of specs that will run in `BeforeSuite`, this might be fixed in... | Umbrella issue for Ginkgo Migration | https://api.github.com/repos/kubernetes/kubernetes/issues/109744/comments | 28 | 2022-05-02T06:36:29Z | 2023-01-12T13:58:27Z | https://github.com/kubernetes/kubernetes/issues/109744 | 1,222,538,099 | 109,744 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I my cluster, I want to install two scheduler extenders. They have different managedResources and therefore different logic of binding. The configuration is as follows:
```
{
"apiVersion": "kubescheduler.config.k8s.io/v1beta2",
"kind": "KubeSchedulerConfiguration",
"... | kube-scheduler does not allow two extenders implementing bindVerb(the two extenders have different managedResources) | https://api.github.com/repos/kubernetes/kubernetes/issues/109739/comments | 16 | 2022-05-01T09:44:30Z | 2023-02-19T15:56:49Z | https://github.com/kubernetes/kubernetes/issues/109739 | 1,222,093,239 | 109,739 |
[
"kubernetes",
"kubernetes"
] | `wait.Poll` treats any error returned by the condition as terminal, but `e2epod.WaitForPodCondition` silently ignores any errors that aren't returned along with `done=true`. We should change WaitForPodCondition to behave like `wait.Poll`.
/sig testing
/area e2e-test-framework | E2E framework/pod WaitForPodCondition silently ignores condition errors. | https://api.github.com/repos/kubernetes/kubernetes/issues/109732/comments | 4 | 2022-04-30T00:42:54Z | 2022-09-20T07:05:21Z | https://github.com/kubernetes/kubernetes/issues/109732 | 1,221,675,935 | 109,732 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
The static pods that kubeadm generates contains two labels, `component` and `tier`. The code that adds these labels is here https://github.com/kubernetes/kubernetes/blob/e7a2ce75e5df96ba6ea51d904bf2735397b3e203/cmd/kubeadm/app/util/staticpod/utils.go#L67-L69
### What did you expect to happen?
... | Kubeadm static pods missing recommended labels | https://api.github.com/repos/kubernetes/kubernetes/issues/109731/comments | 10 | 2022-04-29T22:20:03Z | 2022-08-03T05:30:20Z | https://github.com/kubernetes/kubernetes/issues/109731 | 1,221,627,494 | 109,731 |
[
"kubernetes",
"kubernetes"
] | obfuscated deletable | Obfuscated ... deletable | https://api.github.com/repos/kubernetes/kubernetes/issues/109726/comments | 6 | 2022-04-29T17:29:28Z | 2022-05-03T20:09:44Z | https://github.com/kubernetes/kubernetes/issues/109726 | 1,221,321,646 | 109,726 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Because the test spec in Ginkgo V2 don't the `stacktrace` available, the script in `verify-e2e-test-ownership.sh` which is used to validate `SIGDescribe` in the `stacktrace` is not possible anymore.
The rules are:
> - tests MUST use top-level SIGDescribe
> - tests MUST NOT use nested SIGDescr... | Ginkgo V2: Lost the validation on the `SIGDescribe` | https://api.github.com/repos/kubernetes/kubernetes/issues/109724/comments | 4 | 2022-04-29T14:28:31Z | 2022-07-29T02:13:40Z | https://github.com/kubernetes/kubernetes/issues/109724 | 1,220,957,990 | 109,724 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
[ci-crio-cgroupv1-node-e2e-conformance](https://testgrid.k8s.io/sig-release-master-informing#ci-crio-cgroupv1-node-e2e-conformance)
### Which tests are failing?
- ci-crio-cgroupv1-node-e2e-conformance.Overall
- kubetest.Node Tests
### Since when has it been failing?
04-29 00:... | [Failing test] ci-crio-cgroupv1-node-e2e-conformance | https://api.github.com/repos/kubernetes/kubernetes/issues/109723/comments | 4 | 2022-04-29T12:35:23Z | 2022-05-03T13:21:21Z | https://github.com/kubernetes/kubernetes/issues/109723 | 1,220,715,634 | 109,723 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Hello! After upgrading our k8s-cluster to v1.21.11 we start to see a lot of warnings in kube-apiserver logs:
`Auditing failed of request: encoding failed: no kind "Scale" is registered for version "apps/v1" in scheme "k8s.io/kubernetes/pkg/api/legacyscheme/scheme.go:30"`
Probably these warnings c... | [kube-apiserver] Auditing failed of request: encoding failed no kind "Scale" is registered for version "apps/v1" | https://api.github.com/repos/kubernetes/kubernetes/issues/109720/comments | 11 | 2022-04-29T09:24:32Z | 2022-10-02T20:55:10Z | https://github.com/kubernetes/kubernetes/issues/109720 | 1,220,335,234 | 109,720 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
On our GKE cluster (using preemptible nodes), pods are correctly marked as "terminated", but are still showing as "ready" in the endpoints list, causing traffic to route to them.
Deleting the Terminated pods removes them from the endpoints list.
The Terminated pods reappear after a node preemp... | "Terminated" pod on shutdown node listed in service edpoints. | https://api.github.com/repos/kubernetes/kubernetes/issues/109718/comments | 36 | 2022-04-29T09:18:11Z | 2022-10-24T02:30:26Z | https://github.com/kubernetes/kubernetes/issues/109718 | 1,220,322,600 | 109,718 |
[
"kubernetes",
"kubernetes"
] | There is a strong and growing consensus in sig-node about the need of increasing the test coverage in the kubelet, improving the current testsuite about coverage and reliability. See for example the [April 26 sig-node meeting notes](https://docs.google.com/document/d/1Ne57gvidMEWXR70OxxnRkYquAoMpt56o75oZtg-OeBg/edit#he... | tracker: improve the kubelet test coverage | https://api.github.com/repos/kubernetes/kubernetes/issues/109717/comments | 37 | 2022-04-29T06:51:28Z | 2024-10-03T16:16:02Z | https://github.com/kubernetes/kubernetes/issues/109717 | 1,220,027,649 | 109,717 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Kubernetes scheduler may preempt lower priority pods during deployment rollout. I suspect https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/#higher-priority-pods-are-preempted-before-lower-priority-pods partially explains why.
### What did you expect to happen?
... | Kubernetes scheduler may preempt lower priority pods during deployment rollout | https://api.github.com/repos/kubernetes/kubernetes/issues/109714/comments | 16 | 2022-04-28T19:21:29Z | 2024-01-19T10:16:11Z | https://github.com/kubernetes/kubernetes/issues/109714 | 1,219,170,450 | 109,714 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
A mode of operation for Jobs with `.spec.completionMode="Indexed` that allows every index to execute.
Currently this is not possible because when a job reaches its `.spec.backoffLimit`, active pods will be deleted; moreover, the job is declared failed and so no new pods are cre... | An Indexed Job mode that allows every index to execute | https://api.github.com/repos/kubernetes/kubernetes/issues/109712/comments | 34 | 2022-04-28T16:03:28Z | 2024-01-22T14:03:48Z | https://github.com/kubernetes/kubernetes/issues/109712 | 1,218,949,078 | 109,712 |
[
"kubernetes",
"kubernetes"
] | Since golang 1.12 https://github.com/golang/go/commit/ee55f0856a3f1fed5d8c15af54c40e4799c2d32f
the standard library httputil.ReverseProxy supports automatic upgrade to websockets and other protocols, in a much cleaner implementation that we have today in `staging/src/k8s.io/apimachinery/pkg/util/proxy/upgradeaware.go`... | upgradeaware proxy and golang httputil.ReverseProxy | https://api.github.com/repos/kubernetes/kubernetes/issues/109710/comments | 6 | 2022-04-28T11:34:36Z | 2023-08-06T21:26:10Z | https://github.com/kubernetes/kubernetes/issues/109710 | 1,218,596,101 | 109,710 |
[
"kubernetes",
"kubernetes"
] | Please publish 3.5.4-0 image and update to [etcd v3.5.4](https://github.com/etcd-io/etcd/releases/tag/v3.5.4) to benefit from fix https://github.com/etcd-io/etcd/pull/13950 for https://github.com/etcd-io/etcd/issues/13948, while still keeping v3.5.3 critical correctness fixes (https://github.com/etcd-io/etcd/issues/137... | etcd: Update to v3.5.4 | https://api.github.com/repos/kubernetes/kubernetes/issues/109707/comments | 7 | 2022-04-28T09:42:06Z | 2022-08-02T12:51:34Z | https://github.com/kubernetes/kubernetes/issues/109707 | 1,218,470,299 | 109,707 |
[
"kubernetes",
"kubernetes"
] | `FilterNonRestartablePods` (and the corresponding `isNotRestartAlwaysMirrorPod`) are confusing functions. Either these are buggy, or they need to be renamed with much more descriptive comments.
1. Should non-mirror pods with a `RestartPolicy=Never` be considered non-restartable?
2. What does this mean: `pods that w... | [E2E] Review FilterNonRestartablePods | https://api.github.com/repos/kubernetes/kubernetes/issues/109703/comments | 9 | 2022-04-28T00:02:19Z | 2024-08-04T15:16:55Z | https://github.com/kubernetes/kubernetes/issues/109703 | 1,218,002,086 | 109,703 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Kubernetes fails to clean up AWS resources it created when creating a Service which leads to a build-up of resources, inability to delete the environment this happens within without manual intervention, etc.
I'm using EKS and creating a Service. When I create service:
- Kubernetes creates an... | ELB Security Group references not cleaned up after deleting service | https://api.github.com/repos/kubernetes/kubernetes/issues/109698/comments | 16 | 2022-04-27T17:40:52Z | 2025-03-09T06:44:04Z | https://github.com/kubernetes/kubernetes/issues/109698 | 1,217,683,875 | 109,698 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
https://testgrid.k8s.io/sig-testing-canaries#ci-kubernetes-coverage-conformance
https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-coverage-conformance/1519348158935601152
> pkg/util/coverage/coverage.go:84: not enough arguments in call to testing.MainStart
### What did you exp... | e2e coverage is broken | https://api.github.com/repos/kubernetes/kubernetes/issues/109695/comments | 10 | 2022-04-27T16:37:29Z | 2022-12-16T19:12:18Z | https://github.com/kubernetes/kubernetes/issues/109695 | 1,217,607,619 | 109,695 |
[
"kubernetes",
"kubernetes"
] | Currently, when a scheduling profile is configured, the `schedulerName` field [1] is used to map the profile to a pod. In cases where the same profile is shared between control plane pods [2] and user workload pods, this may become cumbersome when there's a demand on having different scheduling configuration for the wo... | [RFE] scheduling profiles restricted by a list of namespaces | https://api.github.com/repos/kubernetes/kubernetes/issues/109693/comments | 9 | 2022-04-27T11:07:05Z | 2022-10-03T16:04:10Z | https://github.com/kubernetes/kubernetes/issues/109693 | 1,217,195,563 | 109,693 |
[
"kubernetes",
"kubernetes"
] | A principle of writing a scheduler PreFilter/PreScore plugin is to iterate all nodes **when necessay**. If it's just a good-to-have, we usually delay the O(n) operator to Filter()/Score() on each node.
Two valid examples for this is InterPodAffinity and PodTopologySpread's PreFilter(), which **need** to calculate th... | Optimize a O(n) operation in volumerestrictions#PreFilter | https://api.github.com/repos/kubernetes/kubernetes/issues/109687/comments | 5 | 2022-04-27T01:20:56Z | 2022-05-04T13:49:51Z | https://github.com/kubernetes/kubernetes/issues/109687 | 1,216,659,332 | 109,687 |
[
"kubernetes",
"kubernetes"
] | # Progress <code>[6/6]</code>
- [x] APISnoop org-flow: [CoreV1ResourceQuotaTest.org](https://github.com/apisnoop/ticket-writing/blob/master/CoreV1ResourceQuotaTest.org)
- [x] test approval issue : #109682
- [x] test pr : #109683
- [X] two weeks soak start date : [Testgid](https://testgrid.k8s.io/sig-release-maste... | Write List, Patch & DeleteCollection ResourceQuota test - +3 endpoint coverage | https://api.github.com/repos/kubernetes/kubernetes/issues/109682/comments | 3 | 2022-04-26T22:53:46Z | 2022-07-21T21:25:40Z | https://github.com/kubernetes/kubernetes/issues/109682 | 1,216,559,524 | 109,682 |
[
"kubernetes",
"kubernetes"
] | **This is a Bug Report**
<!-- Thanks for filing an issue! Before submitting, please fill in the following information. -->
<!-- See https://kubernetes.io/docs/contribute/start/ for guidance on writing an actionable issue description. -->
<!--Required Information-->
**Problem:**
As a user upgrading to Kuberne... | Document CNI version-related breaking change | https://api.github.com/repos/kubernetes/kubernetes/issues/109686/comments | 29 | 2022-04-26T22:40:57Z | 2022-04-28T10:23:09Z | https://github.com/kubernetes/kubernetes/issues/109686 | 1,216,623,918 | 109,686 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
As described in [#1009](https://github.com/kubernetes-sigs/metrics-server/pull/1009), When the pod start or stop, negative metrics generated.
```
# HELP container_start_time_seconds [ALPHA] Start time of the container since unix epoch in seconds
# TYPE container_start_time_seconds gauge
cont... | Incorrect metrics of container might be generated when pod start or stop | https://api.github.com/repos/kubernetes/kubernetes/issues/109679/comments | 7 | 2022-04-26T20:35:45Z | 2022-07-15T08:04:36Z | https://github.com/kubernetes/kubernetes/issues/109679 | 1,216,450,618 | 109,679 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I have a pod that is made up of two containers. One called backend and one called notification-service. Both are written in haskell and both communicate via websockets. The backend is running on port 3000 and the notification has no port exposed. There is an ALB in front of the backend and the... | Websocket connection drops between two containers in same pod | https://api.github.com/repos/kubernetes/kubernetes/issues/109678/comments | 18 | 2022-04-26T19:38:16Z | 2022-10-11T08:54:08Z | https://github.com/kubernetes/kubernetes/issues/109678 | 1,216,396,317 | 109,678 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
For certain storage classes (ex;- smb volume, hostpath (manual) volume), when i query /stats/summary kubelet end point( k8s version 1.23.5), I dont see the below metrics for some of my above volume, though they are mounted and used .
"volume": [
{
"time": "2022-04-26T02:52:55Z",
"availableByte... | volume usage metrics missing in /stats/summary kubelet endpoint for certain volumes | https://api.github.com/repos/kubernetes/kubernetes/issues/109677/comments | 15 | 2022-04-26T18:01:16Z | 2023-02-26T18:05:23Z | https://github.com/kubernetes/kubernetes/issues/109677 | 1,216,299,383 | 109,677 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
```
kubectl apply -f pod-0.yaml
```
where `pod-0.yaml` is as follows:
```
apiVersion: apps/v1
kind: Deployment
metadata:
name: pod-0
spec:
selector:
matchLabels:
run: pod-0
replicas: 1
template:
metadata:
labels:
run: pod-0
spec:
c... | `imagePullPolicy` issue. | https://api.github.com/repos/kubernetes/kubernetes/issues/109673/comments | 11 | 2022-04-26T14:46:12Z | 2022-04-28T02:47:08Z | https://github.com/kubernetes/kubernetes/issues/109673 | 1,216,069,825 | 109,673 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
An accept rule should be installed before the conntrack rule exempt local traffic such as requests to localhost:10248/healthz
```
...
-N KUBE-SERVICES
-A INPUT -m comment --comment "kubernetes health check service ports" -j KUBE-NODEPORTS
-A INPUT -m conntrack --ctstate NEW ... | Kube-proxy should exempt local traffic from going through conntrack | https://api.github.com/repos/kubernetes/kubernetes/issues/109672/comments | 22 | 2022-04-26T12:56:41Z | 2024-10-24T19:15:18Z | https://github.com/kubernetes/kubernetes/issues/109672 | 1,215,918,822 | 109,672 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
Create an unix domain socket endpoint (i.e. /var/lib/kubelet/kubelet.sock) for Kubelet's http services (e.g. /healthz)
### Why is this needed?
Some requests to Kubelet only travel within a host. Relying on a unix domain socket can bypass `netfilter`, which sometimes is not workin... | Create unix socket endpoint for Kubelet | https://api.github.com/repos/kubernetes/kubernetes/issues/109671/comments | 9 | 2022-04-26T12:49:00Z | 2022-09-23T16:23:43Z | https://github.com/kubernetes/kubernetes/issues/109671 | 1,215,909,308 | 109,671 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
`cobra.Command.RunE ` does not print errors in the file or console if errors occur.
e.g.:
https://github.com/kubernetes/kubernetes/blob/a83cc51a19d1b5f2b2d3fb75574b04f587ec0054/cmd/kube-scheduler/app/server.go#L85-L87
If `runCommand` return err, No error printing in console.
Why not use `k... | `cobra.Command.RunE ` does not print errors if errors occur | https://api.github.com/repos/kubernetes/kubernetes/issues/109670/comments | 4 | 2022-04-26T10:54:15Z | 2022-04-27T06:09:59Z | https://github.com/kubernetes/kubernetes/issues/109670 | 1,215,775,322 | 109,670 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
According to the [release notes](https://github.com/kubernetes/kubernetes/blob/a83cc51a19d1b5f2b2d3fb75574b04f587ec0054/CHANGELOG/CHANGELOG-1.23.md?plain=1#L950) the `kubeadm` flag `--patches` is no longer allowed in a mixture with the flag `--config`.
However, that is not the case as someone can s... | Error in CHANGELOG-1.23 | https://api.github.com/repos/kubernetes/kubernetes/issues/109669/comments | 4 | 2022-04-26T10:41:00Z | 2022-04-26T11:49:12Z | https://github.com/kubernetes/kubernetes/issues/109669 | 1,215,760,923 | 109,669 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
This issue is very similar to #97970 but limited to the `LabelSelector` type. A smallish reproducer can be found [in this gist](https://gist.github.com/jan--f/870b5f7a231245bba0ac870ae6206af7).
Same as in #97970, if a user and an operator both modify a `LabelSelector` such that they both either s... | Server Side Apply: metav1 `LabelSelector` members `MatchLabels` and `MatchExpressions` are not atomic | https://api.github.com/repos/kubernetes/kubernetes/issues/109668/comments | 7 | 2022-04-26T09:23:04Z | 2022-04-27T09:10:48Z | https://github.com/kubernetes/kubernetes/issues/109668 | 1,215,662,120 | 109,668 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
The apiserver accepts sharding parameters in LIST requests. This can be utilized by controllers performing list-watch.
A request can be separated into `n` shards by passing `shard: i, numShards: n` in the `ListOptions`, then the apiserver only responds with the list of objects w... | Sharding list requests | https://api.github.com/repos/kubernetes/kubernetes/issues/109667/comments | 7 | 2022-04-26T08:18:51Z | 2022-04-29T16:47:03Z | https://github.com/kubernetes/kubernetes/issues/109667 | 1,215,583,241 | 109,667 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
Wanted to check whether FIPS can enabled in Kubernetes
### Why is this needed?
To validate security compliance | Is enabling FIPS is supported in kubernetes | https://api.github.com/repos/kubernetes/kubernetes/issues/109666/comments | 3 | 2022-04-26T07:36:28Z | 2022-04-26T12:08:56Z | https://github.com/kubernetes/kubernetes/issues/109666 | 1,215,532,723 | 109,666 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Using calico as a network plugin,Creating other pods before the calico node is successfully started,Even if calico returns to normal,other pods might stuck on ContainerCreating and K8s does not retry that.
According to the kubelet log, the following error is reported when the kubelet is running:
... | some pod stuck on ContainerCreating | https://api.github.com/repos/kubernetes/kubernetes/issues/109665/comments | 12 | 2022-04-26T07:07:46Z | 2022-05-08T13:19:27Z | https://github.com/kubernetes/kubernetes/issues/109665 | 1,215,501,194 | 109,665 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
We run DaemonSet on worker node, worker node loses connection to master node due to network issue. The DaemonSet container is continuing to running on worker, this is expected. But then I reboot worker node, we found there is no any container running on the worker. Is this a bug ?
### What di... | DaemonSet not restart after worker reboot when lose connection to master | https://api.github.com/repos/kubernetes/kubernetes/issues/109664/comments | 10 | 2022-04-26T06:40:07Z | 2023-09-01T07:54:24Z | https://github.com/kubernetes/kubernetes/issues/109664 | 1,215,474,486 | 109,664 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
pod status is NodeAffinity,
```[root@node-1 ~]# kubectl get pod -n ceph -o wide | grep ceph-rgw
ceph-rgw-548fdf5fc5-2whgg 1/1 Running 0 4h25m 10.232.1.28 node-5 <none> <none>
ceph-rgw-548fdf5fc5-86gkn 1/1 Running 0 4h25m ... | 1:20: Pods stuck as failed with "Pod Predicate NodeAffinity failed" | https://api.github.com/repos/kubernetes/kubernetes/issues/109663/comments | 16 | 2022-04-26T06:13:07Z | 2022-10-14T09:09:48Z | https://github.com/kubernetes/kubernetes/issues/109663 | 1,215,450,286 | 109,663 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When scheduling pod, we encountered the following event `FailedScheduling`, then the scheduler will backoff to reschedule again, but this add more waiting time.
```
Events:
Type Reason Age From Message
---- ------ ---- ---- -----... | PVC update conflict on scheduler-binding pod volumes | https://api.github.com/repos/kubernetes/kubernetes/issues/109661/comments | 7 | 2022-04-26T05:40:07Z | 2022-10-18T18:29:20Z | https://github.com/kubernetes/kubernetes/issues/109661 | 1,215,424,549 | 109,661 |
[
"kubernetes",
"kubernetes"
] | testgrid shows not a single recent run has been green:
https://testgrid.k8s.io/google-gce-upgrade
the aggreated test report confirms this :
https://storage.googleapis.com/k8s-triage/index.html?pr=1&job=stable&xjob=windows&xtest=gcepd
Looking at where these jobs are defined:
https://cs.k8s.io/?q=google-gce-up... | Need owners or cleanup for google-gce-upgrade in testgrid | https://api.github.com/repos/kubernetes/kubernetes/issues/109655/comments | 7 | 2022-04-25T19:07:31Z | 2022-10-08T17:58:18Z | https://github.com/kubernetes/kubernetes/issues/109655 | 1,214,921,863 | 109,655 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
The current process to test a CSI driver in Windows nodepools is:
- Create a cluster with a Windows nodepool, by default the Window nodes are tainted with `NoSchedule`
- Install a CSI Driver, assume it has a node component that can run in Windows
- Untaint the Windows nodes an... | Update storage e2e test suite running in Windows to add a nodeSelector for Window nodes | https://api.github.com/repos/kubernetes/kubernetes/issues/109654/comments | 9 | 2022-04-25T18:36:37Z | 2023-02-25T18:56:21Z | https://github.com/kubernetes/kubernetes/issues/109654 | 1,214,892,418 | 109,654 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
When configuring klog, the ValidateAndApply function in the component-base logs package is required for the configuration to take effect. This is not very friendly, it is recommended to be divided into validate and apply functions
### Why is this needed?
Some scenarios may requir... | Split the ValidateAndApply function in the component-base logs package into validate and apply | https://api.github.com/repos/kubernetes/kubernetes/issues/109650/comments | 9 | 2022-04-25T11:51:25Z | 2022-05-05T18:49:29Z | https://github.com/kubernetes/kubernetes/issues/109650 | 1,214,392,569 | 109,650 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
The E2E framework has SkipUnlessFeatureGateEnabled which tricks developers into thinking that they can write tests that only run when a feature gate is enabled. That doesn't work:
- the e2e.test binary has no way of checking which feature gates are enabled in the Kubernetes cluste... | remove SkipUnlessFeatureGateEnabled | https://api.github.com/repos/kubernetes/kubernetes/issues/109648/comments | 8 | 2022-04-25T09:11:27Z | 2022-05-04T09:35:19Z | https://github.com/kubernetes/kubernetes/issues/109648 | 1,214,206,063 | 109,648 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
ci-kubernetes-e2e-gce-iscsi-serial and ci-kubernetes-e2e-gce-iscsi
### Which tests are failing?
I guess it is create cluster step not tests
```
W0424 13:35:17.146] -----------------------------------------------------
W0424 13:35:17.147] * Expire in 0 ms for 6 (transfer 0x558db7d1b0f0)... | ci-kubernetes-e2e-gce-iscsi and ci-kubernetes-e2e-gce-iscsi-serial are failing | https://api.github.com/repos/kubernetes/kubernetes/issues/109645/comments | 3 | 2022-04-25T08:09:10Z | 2022-04-28T02:46:55Z | https://github.com/kubernetes/kubernetes/issues/109645 | 1,214,132,339 | 109,645 |
[
"kubernetes",
"kubernetes"
] | Please see https://testgrid.k8s.io/google-windows, jobs are in various states of disrepair. We need to find owners or clean them up.
Also see https://storage.googleapis.com/k8s-triage/index.html?pr=1&job=windows
- [ci-kubernetes-e2e-windows-containerd-gce](https://cs.k8s.io/?q=ci-kubernetes-e2e-windows-container... | Need Owner for abandoned(?) google-windows CI jobs | https://api.github.com/repos/kubernetes/kubernetes/issues/109641/comments | 8 | 2022-04-24T23:35:17Z | 2022-09-28T17:12:42Z | https://github.com/kubernetes/kubernetes/issues/109641 | 1,213,801,188 | 109,641 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
Add a check for CRI service to localhost healthz endpoint in `kubelet` (i.e. localhost:10248/healthz and localhost:10248/healthz/cri).
### Why is this needed?
CRI service is usually a separate process in the system (Containerd, for example). So it requires a health check to make... | Add CRI check to localhost healthz endpoint | https://api.github.com/repos/kubernetes/kubernetes/issues/109640/comments | 13 | 2022-04-24T14:22:56Z | 2023-04-26T21:39:51Z | https://github.com/kubernetes/kubernetes/issues/109640 | 1,213,668,796 | 109,640 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Custom resource definitions are created using kubectl apply of the CRD yaml file or via the REST API. We do not see the service account field being part of the CRD spec. Does one require cluster role privileges to register the CRD into the k8s api server ? If not via service account, how is the user... | CustomResourceDefinition spec does not have serviceAccount field. | https://api.github.com/repos/kubernetes/kubernetes/issues/109638/comments | 8 | 2022-04-24T11:42:24Z | 2022-04-27T12:48:59Z | https://github.com/kubernetes/kubernetes/issues/109638 | 1,213,630,492 | 109,638 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
There was pod, scheduled to node, and all unusual it had was pvc, provided by rook-ceph.
During pod start kubelet shown logs about that pod's container start:
```
Apr 22 13:31:01 worker-node.company.tld crio[1469]: time="2022-04-22 13:31:01.859500599Z" level=info msg="Creating container: eco-chec... | 1.20.0: kubelet crashing with concurrent map writes | https://api.github.com/repos/kubernetes/kubernetes/issues/109636/comments | 5 | 2022-04-24T10:07:41Z | 2022-04-27T19:08:02Z | https://github.com/kubernetes/kubernetes/issues/109636 | 1,213,608,846 | 109,636 |
[
"kubernetes",
"kubernetes"
] | service uses any backend pods that match labels specified under the selector.
Since service, pods are both namespaced resources, why service is allowed to select any pods across namespaces?
wouldn't that be better to include a namespace selector to confine the selection to the current namespace or use any namespace ... | why no namespace selector in service selector | https://api.github.com/repos/kubernetes/kubernetes/issues/109630/comments | 14 | 2022-04-23T22:19:09Z | 2022-05-26T15:29:57Z | https://github.com/kubernetes/kubernetes/issues/109630 | 1,213,467,101 | 109,630 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Created a service using named `targetPort` (namely `http`), but it didn't work. Checked the endpoint for the service, the endpoint is empty but the endpointslice is not:
```
$ kubectl -n test get ep,endpointslice,deploy
NAME ENDPOINTS AGE
endpoints/svc <none> 20s
NAME ... | Named target port is not working | https://api.github.com/repos/kubernetes/kubernetes/issues/109627/comments | 3 | 2022-04-22T22:53:32Z | 2022-04-24T20:19:50Z | https://github.com/kubernetes/kubernetes/issues/109627 | 1,212,906,018 | 109,627 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are flaking?
ci-cri-containerd-e2e-cos-gce
### Which tests are flaking?
Kubernetes e2e suite: [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] [Flaky] kubectl explain works for CR with the same resource name as built-in object.
Kubernetes e2e suite: [sig-storage] NFS... | e2e-cos test is flaky | https://api.github.com/repos/kubernetes/kubernetes/issues/109621/comments | 31 | 2022-04-22T17:43:02Z | 2024-06-12T08:02:45Z | https://github.com/kubernetes/kubernetes/issues/109621 | 1,212,621,892 | 109,621 |
[
"kubernetes",
"kubernetes"
] | ### Issue Details
A security issue was discovered in [ingress-nginx](https://github.com/kubernetes/ingress-nginx) where a user that can create or update ingress objects can use `.metadata.annotations` in an Ingress object (in the `networking.k8s.io` or `extensions` API group) to obtain the credentials of the ingress-n... | CVE-2021-25746: Ingress-nginx directive injection via annotations | https://api.github.com/repos/kubernetes/kubernetes/issues/126813/comments | 12 | 2022-04-22T16:18:27Z | 2024-08-20T13:25:18Z | https://github.com/kubernetes/kubernetes/issues/126813 | 2,475,631,555 | 126,813 |
[
"kubernetes",
"kubernetes"
] | ### Issue Details
A security issue was discovered in [ingress-nginx](https://github.com/kubernetes/ingress-nginx) where a user that can create or update ingress objects can use the `spec.rules[].http.paths[].path` field of an Ingress object (in the `networking.k8s.io` or `extensions` API group) to obtain the credentia... | CVE-2021-25745: Ingress-nginx `path` can be pointed to service account token file | https://api.github.com/repos/kubernetes/kubernetes/issues/126812/comments | 14 | 2022-04-22T16:18:21Z | 2024-08-20T13:25:11Z | https://github.com/kubernetes/kubernetes/issues/126812 | 2,475,629,788 | 126,812 |
[
"kubernetes",
"kubernetes"
] | Hello, team. I was using apiserver to implement my webhook server, but found these is no flag used to set `always-allow-groups`, but there is a flag to set `authorization-always-allow-paths`:
https://github.com/kubernetes/apiserver/blob/ac613d389acee636c827a241b1eba448e6b15f3a/pkg/server/options/authorization.go#L1... | Should we add `authorization-always-allow-groups` flag as well? | https://api.github.com/repos/kubernetes/kubernetes/issues/110345/comments | 14 | 2022-04-22T01:05:00Z | 2024-05-16T16:40:47Z | https://github.com/kubernetes/kubernetes/issues/110345 | 1,258,119,583 | 110,345 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
`kubectl drain $node_name --ignore-daemonsets=true`
failed because it requires to list daemonsets
### What did you expect to happen?
it working without that permissions
### How can we reproduce it (as minimally and precisely as possible)?
see above
### Anything else we need to know?
this is a... | kubectl drain should not require permissions to list daemonsets | https://api.github.com/repos/kubernetes/kubernetes/issues/109605/comments | 12 | 2022-04-21T22:13:23Z | 2022-12-08T17:43:22Z | https://github.com/kubernetes/kubernetes/issues/109605 | 1,211,603,553 | 109,605 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
In one of our multi tenant cluster, we've observed that all kubelet requests (under `system-nodes` flow schema) eventually started timing out or aborted due to secret watch request occupying all `system` priority level concurrency share. It happened due to our KMS provider was quite latent (& some... | cacher watch timeout not handled when it is not ready | https://api.github.com/repos/kubernetes/kubernetes/issues/109603/comments | 14 | 2022-04-21T20:40:54Z | 2023-02-28T11:23:18Z | https://github.com/kubernetes/kubernetes/issues/109603 | 1,211,530,745 | 109,603 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
This was previously tracked in https://github.com/kubernetes/kubernetes/issues/34059 (created in 2016, closed in 2020 after several tests were enhanced).
I'm starting to wonder whether the problem is getting worse again because we still don't catch new tests that use this anti-p... | prevent the "Expect(err).NotTo(HaveOccurred())" and "ExpectNoError(err)" anti-pattern in e2e tests | https://api.github.com/repos/kubernetes/kubernetes/issues/109600/comments | 18 | 2022-04-21T19:17:37Z | 2023-01-30T16:18:01Z | https://github.com/kubernetes/kubernetes/issues/109600 | 1,211,454,981 | 109,600 |
Subsets and Splits
Unique Owner-Repo Count
Counts the number of unique owner-repos in the dataset, providing a basic understanding of diverse repositories.