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 [d01efc01be08953f1a7a](https://go.k8s.io/triage#d01efc01be08953f1a7a)
##### Error text:
```
[FAILED] Failed to get successful response from /configz: timed out waiting for the condition
In [It] at: test/e2e_node/kubeletconfig/kubeletconfig.go:185 @ 06/17/23 00:07:48.306
```
#### Recent fai... | Failure cluster [d01efc01...] without SRIOV devices in the system with disabled KubeletPodResourcesGetAllocatable feature gate should return the expected error with the feature gate disabled | https://api.github.com/repos/kubernetes/kubernetes/issues/118851/comments | 11 | 2023-06-25T04:46:31Z | 2024-05-14T08:37:17Z | https://github.com/kubernetes/kubernetes/issues/118851 | 1,773,055,191 | 118,851 |
[
"kubernetes",
"kubernetes"
] | ### Failure cluster [a91fc79ba237afb3fb87](https://go.k8s.io/triage#a91fc79ba237afb3fb87)
##### Error text:
```
[FAILED] Failed to get successful response from /configz: timed out waiting for the condition
In [It] at: test/e2e_node/kubeletconfig/kubeletconfig.go:185 @ 06/17/23 00:07:35.481
```
#### Recent fai... | Failure cluster [a91fc79b...] a pod without init containers should report all conditions set in expected order after the pod is up | https://api.github.com/repos/kubernetes/kubernetes/issues/118847/comments | 4 | 2023-06-24T10:06:53Z | 2023-07-24T10:20:39Z | https://github.com/kubernetes/kubernetes/issues/118847 | 1,772,587,778 | 118,847 |
[
"kubernetes",
"kubernetes"
] | null | Mark KMS v1beta1 as deprecated with no further fixes | https://api.github.com/repos/kubernetes/kubernetes/issues/118839/comments | 7 | 2023-06-23T20:43:56Z | 2023-07-06T20:39:06Z | https://github.com/kubernetes/kubernetes/issues/118839 | 1,772,123,795 | 118,839 |
[
"kubernetes",
"kubernetes"
] | ref: https://github.com/kubernetes/kubernetes/issues/118831
/sig auth
/triage accepted
/assign @aramase @enj
/milestone v1.28 | [KMSv2] update KEP with the crypto changes | https://api.github.com/repos/kubernetes/kubernetes/issues/118837/comments | 5 | 2023-06-23T18:53:32Z | 2023-09-20T17:28:03Z | https://github.com/kubernetes/kubernetes/issues/118837 | 1,771,937,225 | 118,837 |
[
"kubernetes",
"kubernetes"
] | This issue refers to the `Marshal` and `Unmarshal` code:
https://github.com/kubernetes/kubernetes/blob/c2fb8057b2b9ad0b278c8f7412a3ec50787dd7e4/staging/src/k8s.io/apiserver/pkg/storage/value/encrypt/envelope/kmsv2/envelope.go#L251-L257
We will likely need a struct the encapsulates `proto.NewBuffer` and `Encrypted... | kmsv2: use gRPC decoding buffer for encrypted object | https://api.github.com/repos/kubernetes/kubernetes/issues/118835/comments | 5 | 2023-06-23T17:59:52Z | 2024-04-23T19:52:09Z | https://github.com/kubernetes/kubernetes/issues/118835 | 1,771,862,198 | 118,835 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
On Kubernetes 1.22.x successfulJobsHistoryLimit and failedJobsHistoryLimit, so the parameter ttlSecondsAfterFinished doesn't exist. On any newer version, every pods are keep even if the job is deleted.
I know there a note on the documentation, but I still think that was a bug.
### What did y... | successfulJobsHistoryLimit and failedJobsHistoryLimit make pods orphan | https://api.github.com/repos/kubernetes/kubernetes/issues/118834/comments | 7 | 2023-06-23T17:33:26Z | 2024-03-26T02:03:39Z | https://github.com/kubernetes/kubernetes/issues/118834 | 1,771,825,578 | 118,834 |
[
"kubernetes",
"kubernetes"
] | /sig auth
/assign @aramase
/triage accepted
/milestone v1.28 | Wire feature flag and to authn config struct | https://api.github.com/repos/kubernetes/kubernetes/issues/118833/comments | 6 | 2023-06-23T17:21:14Z | 2023-09-05T20:08:53Z | https://github.com/kubernetes/kubernetes/issues/118833 | 1,771,806,441 | 118,833 |
[
"kubernetes",
"kubernetes"
] | /sig auth
/assign @aramase
/triage accepted
/milestone v1.28 | Create struct for authn config and re-wire OIDC flags to use it | https://api.github.com/repos/kubernetes/kubernetes/issues/118832/comments | 5 | 2023-06-23T17:10:31Z | 2023-08-25T18:52:57Z | https://github.com/kubernetes/kubernetes/issues/118832 | 1,771,790,329 | 118,832 |
[
"kubernetes",
"kubernetes"
] | xref: https://hackmd.io/@enj/SyiXCABZn | kmsv2: fix limitations caused by counter based nonce | https://api.github.com/repos/kubernetes/kubernetes/issues/118831/comments | 5 | 2023-06-23T16:12:57Z | 2023-07-21T23:10:21Z | https://github.com/kubernetes/kubernetes/issues/118831 | 1,771,715,632 | 118,831 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Created a validating webhook to validate the configmap during updates.
When tried to cancel the request while applying the update to the configmap, webhook is considering it as failOpen due to context canceled.
### What did you expect to happen?
We expect not to consider this case as fail... | Canceling the request to webhook while processing the request, webhook emits failOpen metric. | https://api.github.com/repos/kubernetes/kubernetes/issues/118829/comments | 9 | 2023-06-23T15:14:36Z | 2024-03-24T01:47:32Z | https://github.com/kubernetes/kubernetes/issues/118829 | 1,771,634,289 | 118,829 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
We should enhance the podgc_controller_test.go to verify that adding `DisruptionCondition` is unit-testable.
We originally thought that this would only be possible with finalizers but there looks to be other options.
We could follow examples from https://github.com/kubernet... | PodGC unit tests do not actually test addition of any conditions. | https://api.github.com/repos/kubernetes/kubernetes/issues/118826/comments | 16 | 2023-06-23T13:26:59Z | 2023-09-05T10:19:51Z | https://github.com/kubernetes/kubernetes/issues/118826 | 1,771,465,031 | 118,826 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
We created a kubernetes cluster on azure rhel 8.8 VMs. I exec inside a pod and do nslookup google.com, sometimes it works but sometimes it shows `"connection timed out; no servers could be reached"`
![image](https://github.com/kubernetes/kubernetes/assets/110471490/973fd611-b121-4cf4-a602-f9198e13f... | Kubernetes COREDNS Timeout | https://api.github.com/repos/kubernetes/kubernetes/issues/118824/comments | 4 | 2023-06-23T10:05:04Z | 2023-06-25T14:20:34Z | https://github.com/kubernetes/kubernetes/issues/118824 | 1,771,182,784 | 118,824 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I have a daemonset with the rolling update strategy. I have `maxSurge` parameter set to a non zero value [which means](https://github.com/openshift/kubernetes/blob/cb4b47e5ddfbaf7844237b2e2eb2b0acfed5f1b5/pkg/apis/apps/validation/validation.go#L394-L402) that the `maxUnavailable` parameter is set ... | DaemonSet fails to scale down during the rolling update when `maxUnavailable=0` | https://api.github.com/repos/kubernetes/kubernetes/issues/118823/comments | 12 | 2023-06-23T08:08:02Z | 2023-09-19T23:50:18Z | https://github.com/kubernetes/kubernetes/issues/118823 | 1,771,016,313 | 118,823 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
**What happened:**
When using the following Kubernetes settings:
```yaml
apiVersion: v1
kind: Pod
metadata:
name: privilege_escalation_test
namespace: default
spec:
containers:
- name: centos
image: arthsouza/privilege_escalation_test
command: ['sh', '-c', 'sleep 99... | Inconsistency in' securityContext.privileged and allowPrivilegeEscalation behaviors | https://api.github.com/repos/kubernetes/kubernetes/issues/118822/comments | 11 | 2023-06-22T22:18:31Z | 2025-01-17T18:22:15Z | https://github.com/kubernetes/kubernetes/issues/118822 | 1,770,466,710 | 118,822 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
**Below pod yaml file was deployed. From probe logs we see probe is getting scheduled more than once in 30 sec duration of perodSeconds configured for readinessProbe. At times it gets scheduled twice within 5 seconds though 30 sec is configured as periodSeconds**
<code>
apiVersion: v1
kind: Pod... | readiness probe is not scheduled as configured periodSeconds | https://api.github.com/repos/kubernetes/kubernetes/issues/118815/comments | 22 | 2023-06-22T12:34:22Z | 2024-10-23T01:20:55Z | https://github.com/kubernetes/kubernetes/issues/118815 | 1,769,586,746 | 118,815 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
We have NBI traffic impact on worker node after node reboot. TCP Conntrack entries remain in stale after rebooting worker node hosting backend NBI POD.
### What did you expect to happen?
Initial analysis indicating there is some issue with kube-proxy/conntrack handling when endpoint IP chang... | TCP Conntrack entries remain in stale after rebooting worker node | https://api.github.com/repos/kubernetes/kubernetes/issues/118814/comments | 24 | 2023-06-22T12:18:52Z | 2023-06-27T04:26:49Z | https://github.com/kubernetes/kubernetes/issues/118814 | 1,769,563,303 | 118,814 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Kubernetes needs to be updated with the cadvisor version that has the fix for https://github.com/google/cadvisor/pull/3301
### What did you expect to happen?
cadvisor with the fix https://github.com/google/cadvisor/pull/3301 is vendored in
### How can we reproduce it (as minimally and precisely a... | Bump cadvisor to include https://github.com/google/cadvisor/pull/3301 | https://api.github.com/repos/kubernetes/kubernetes/issues/118796/comments | 3 | 2023-06-21T13:31:43Z | 2023-07-10T13:53:10Z | https://github.com/kubernetes/kubernetes/issues/118796 | 1,767,614,013 | 118,796 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Pointing out the existing issue looks like mine [here](https://github.com/oracle/docker-images/issues/1154)
I was trying to host my application in the kubernetes and my issue is similar to above issue. However he resolved that issue by uploading the image in the docker hub repo. I don't want to d... | errImageNeverPull error when try to run the pod using the image of the local machines docker | https://api.github.com/repos/kubernetes/kubernetes/issues/118795/comments | 5 | 2023-06-21T13:20:45Z | 2023-07-18T04:39:51Z | https://github.com/kubernetes/kubernetes/issues/118795 | 1,767,593,254 | 118,795 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Ive started to use the `kubectl debug` command recently and i found that trying to debug in a Pod Security Admission cluster/namespace, where `restricted` profile is labeled, the `kubectl debug` command dont return an ephemeral container with propper security context set, when using flag `profile=... | kubectl debug --profile=restricted do not set AllowPrivilegeEscalation or SeccompProfile for EphemeralContainer | https://api.github.com/repos/kubernetes/kubernetes/issues/118791/comments | 8 | 2023-06-21T11:53:35Z | 2023-06-22T10:22:52Z | https://github.com/kubernetes/kubernetes/issues/118791 | 1,767,430,346 | 118,791 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
The leader election of client-go cannot be terminated, even if I use ctx.done() or the cancel function in context.WithCancel(context.Background()), the running elector.Run(ctx) will never be stopped
### What did you expect to happen?
After I use ctx.Done() or the cancel function, the elected Run()... | client-go leader election can not be cancel | https://api.github.com/repos/kubernetes/kubernetes/issues/118790/comments | 16 | 2023-06-21T10:40:42Z | 2024-09-16T08:15:00Z | https://github.com/kubernetes/kubernetes/issues/118790 | 1,767,299,890 | 118,790 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Paraphrasing this https://github.com/canonical/microk8s/issues/3908
concurrencyPolicy:Forbid and scheduling interval smaller than job actual runtime leads to lots of events sent by control plane (ending up clogging logs on observability side of things)
For example for a job with a once per 55 ... | Excessive Logging from CronJob | https://api.github.com/repos/kubernetes/kubernetes/issues/118789/comments | 27 | 2023-06-21T10:34:46Z | 2024-06-27T13:54:05Z | https://github.com/kubernetes/kubernetes/issues/118789 | 1,767,291,010 | 118,789 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
A jitter should be added when requeuing HPA objects.
### Why is this needed?
Currently HPA controller list pods for each HPA object every 15s by default. These calls are always made at the same second. These calls always require quorum read from etcd.
As a consequence, API... | Add a jitter when requeuing HPA objects | https://api.github.com/repos/kubernetes/kubernetes/issues/118788/comments | 16 | 2023-06-21T09:20:50Z | 2024-06-22T06:07:01Z | https://github.com/kubernetes/kubernetes/issues/118788 | 1,767,163,287 | 118,788 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
The `containerRuntimeEndpoint` setting is supposed to make the `--container-runtime-endpoint` CLI option unnecessary when running `kubelet --config=/path/to/config`, but the value is ignored, so that the CLI option is still necessary.
### What did you expect to happen?
The `containerRuntimeE... | Value of containerRuntimeEndpoint in configuration file ignored by kubelet | https://api.github.com/repos/kubernetes/kubernetes/issues/118787/comments | 12 | 2023-06-21T09:19:49Z | 2023-06-25T07:29:38Z | https://github.com/kubernetes/kubernetes/issues/118787 | 1,767,161,687 | 118,787 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
Hello.
I think in would be useful to introduce an annotation for the Service resource, which will make possible to override the IPVS scheduler configured into kube-proxy configuration for individual Service resource.
Something like:
```yaml
apiVersion: v1
kind: Service
metada... | [kube-proxy/ipvs] Make a scheduler configurable for each Service | https://api.github.com/repos/kubernetes/kubernetes/issues/118784/comments | 15 | 2023-06-21T07:52:51Z | 2023-06-27T04:50:19Z | https://github.com/kubernetes/kubernetes/issues/118784 | 1,766,981,259 | 118,784 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
scheduler panic when use SnapshotSharedLister().NodeInfos().Get in binding cycle
### What did you expect to happen?
not panic
### How can we reproduce it (as minimally and precisely as possible)?
- add a custom bind plugin, use SnapshotSharedLister().NodeInfos().Get(name) in its prebin... | use SnapshotSharedLister().NodeInfos().Get(name) in binding cycle may cause scheduler panic | https://api.github.com/repos/kubernetes/kubernetes/issues/118783/comments | 3 | 2023-06-21T07:00:36Z | 2023-06-26T01:43:29Z | https://github.com/kubernetes/kubernetes/issues/118783 | 1,766,891,957 | 118,783 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
In thinking about evolution scenarios, I realized that `digestConfigObjects` at https://github.com/kubernetes/apiserver/blob/2b176f025d6c5ce699f7361fe8fc04ce4b3cb2d3/pkg/util/flowcontrol/apf_controller.go#L541 should cast a skeptical eye --- that is, filter by validity --- the given objects. It is ... | digestConfigObjects is not critical of the given objects | https://api.github.com/repos/kubernetes/kubernetes/issues/118780/comments | 6 | 2023-06-21T01:55:31Z | 2024-07-03T18:18:18Z | https://github.com/kubernetes/kubernetes/issues/118780 | 1,766,531,380 | 118,780 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I think that https://github.com/kubernetes/kubernetes/issues/115804 via https://github.com/kubernetes/kubernetes/pull/116685 have introduced a regression for HA Kubernetes API server configurations behind a proxy and/or load balancer. Such configurations may only have a single Kubernetes API server... | Restore Kubernetes API service endpoint during HA rolling restarts | https://api.github.com/repos/kubernetes/kubernetes/issues/118777/comments | 23 | 2023-06-20T21:20:41Z | 2023-08-10T16:56:18Z | https://github.com/kubernetes/kubernetes/issues/118777 | 1,766,207,993 | 118,777 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
cluster became unaccessible due to etcd OOM killed and API server FullListIfExpired triggered by periodic etcd compaction
According to client-go list design, if the data is expired, it will fall-back to full-list
https://github.com/kubernetes/client-go/blob/v0.24.6/tools/pager/pager.go#L98
... | cluster unaccessible due to etcd OOM killed and API server FullListIfExpired | https://api.github.com/repos/kubernetes/kubernetes/issues/118776/comments | 13 | 2023-06-20T19:52:33Z | 2024-12-10T01:21:54Z | https://github.com/kubernetes/kubernetes/issues/118776 | 1,766,056,013 | 118,776 |
[
"kubernetes",
"kubernetes"
] | https://github.com/kubernetes/kubernetes/issues/118725 illustrates some surprising behavior with `kubectl apply`. I have found, repeatedly, that humans are bad at predicting what apply will do (made worse by client-side and server-side being different).
From talking to a lot of people, the `apply` action feels like... | Idea: EOL "apply" in favor of more descriptive verbs | https://api.github.com/repos/kubernetes/kubernetes/issues/118775/comments | 7 | 2023-06-20T19:29:24Z | 2024-07-18T18:35:43Z | https://github.com/kubernetes/kubernetes/issues/118775 | 1,766,024,003 | 118,775 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I am working on [kubectl-validate](https://github.com/kubernetes-sigs/kubectl-validate/) and see that the populated defaults for many fields don't themselves pass validation in the OpenAPI published by k8s used by the tool. This means when users leave the fields unspecified the document fails val... | Generated OpenAPI Defaults often do not fit type | https://api.github.com/repos/kubernetes/kubernetes/issues/118771/comments | 4 | 2023-06-20T17:45:35Z | 2023-10-19T20:53:34Z | https://github.com/kubernetes/kubernetes/issues/118771 | 1,765,866,666 | 118,771 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are flaking?
[capz-windows-master](https://testgrid.k8s.io/sig-windows-signal#capz-windows-master)
### Which tests are flaking?
Tests which are using the agnhost image. We've observed the failure on the following tests:
[sig-storage] Downward API volume should provide container's memory lim... | Windows: agnhost start flake | https://api.github.com/repos/kubernetes/kubernetes/issues/118769/comments | 3 | 2023-06-20T16:36:51Z | 2023-08-10T16:53:44Z | https://github.com/kubernetes/kubernetes/issues/118769 | 1,765,761,835 | 118,769 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I use api crate dependent deploy and set ownerReferences,and is worked.when I change dependent image tag and delete owner deploy ,the slave deploy not gc
### What did you expect to happen?
I delete owner deploy and dependent delete
### How can we reproduce it (as minimally and precisely as possib... | set ownerReferences,change dependent deploy image tag, delete owner deploy and dependent not deleted | https://api.github.com/repos/kubernetes/kubernetes/issues/118758/comments | 2 | 2023-06-20T08:04:50Z | 2023-06-20T08:07:49Z | https://github.com/kubernetes/kubernetes/issues/118758 | 1,764,875,366 | 118,758 |
[
"kubernetes",
"kubernetes"
] | ### Failure cluster [3d2a4cbd3657e98000ed](https://go.k8s.io/triage#3d2a4cbd3657e98000ed)
##### Error text:
```
[FAILED] Timed out after 60.001s.
Expected
<string>: KubeletMetrics
to match keys: {
."kubelet_cpu_manager_pinning_requests_total"[]:
Expected
<string>: Sample
to match fields: {
.His... | Failure cluster [3d2a4cbd...]: should report zero pinning counters after a fresh restart | https://api.github.com/repos/kubernetes/kubernetes/issues/118757/comments | 4 | 2023-06-20T08:04:02Z | 2023-06-23T06:37:04Z | https://github.com/kubernetes/kubernetes/issues/118757 | 1,764,874,108 | 118,757 |
[
"kubernetes",
"kubernetes"
] | **Cluster information:**
Kubernetes version: 1.27.2
Cloud being used: baremetal
Installation method: kubeadm
Host OS: Ubuntu 20.04.4 LTS
CNI and version: calico v3.26.0
CRI and version: containerd v1.6.2
**Dummy NGINX Deployment**
```
apiVersion: apps/v1
kind: Deployment
metadata:
name: nginx-deployme... | Replicaset and Pods not deleted after Deployment has been deleted | https://api.github.com/repos/kubernetes/kubernetes/issues/118753/comments | 19 | 2023-06-20T06:07:36Z | 2023-06-21T12:22:32Z | https://github.com/kubernetes/kubernetes/issues/118753 | 1,764,709,791 | 118,753 |
[
"kubernetes",
"kubernetes"
] | There's been a quite a few failures across jobs that query node metrics.
* https://testgrid.k8s.io/sig-node-containerd#cos-cgroupv1-containerd-node-features
* https://testgrid.k8s.io/sig-node-containerd#cos-cgroupv1-containerd-node-e2e-serial
* https://testgrid.k8s.io/sig-node-containerd#cos-cgroupv2-containerd... | e2e node test failures due to unexpected metric | https://api.github.com/repos/kubernetes/kubernetes/issues/118751/comments | 6 | 2023-06-20T04:37:29Z | 2023-06-22T03:25:40Z | https://github.com/kubernetes/kubernetes/issues/118751 | 1,764,620,752 | 118,751 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
I desperately need a way to spread similar prods from different namespaces evenly across clusters nodes.
Right now official docummentation for topologySpreadConstraints explicitly states this:
> Only the Pods holding the same namespace as the incoming Pod can be matching cand... | topologySpreadConstraint spanning multiple namespaces | https://api.github.com/repos/kubernetes/kubernetes/issues/118749/comments | 14 | 2023-06-20T03:17:50Z | 2024-03-27T10:24:22Z | https://github.com/kubernetes/kubernetes/issues/118749 | 1,764,545,667 | 118,749 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
The currently available debug endpoints for APF are for dump_priority_levels, dump_queues, and dump_requests. These commands provide useful information primarily about the state of APF queues, including the the FlowDistinguisher, ArriveTime, UserName, Verb, and APIPath of requests ... | Debug endpoint to dump currently executing requests | https://api.github.com/repos/kubernetes/kubernetes/issues/118746/comments | 7 | 2023-06-19T18:44:05Z | 2023-07-18T20:44:20Z | https://github.com/kubernetes/kubernetes/issues/118746 | 1,764,031,023 | 118,746 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
We have a pod with the following port mapping:
```yaml
- containerPort: 8443
name: virt-api
protocol: TCP
- containerPort: 8443
name: metrics
protocol: TCP
```
When a node becomes unavailable, the pod does not get del... | Feature gate PodDisruptionConditions sometimes silently breaks delete operations on pods when node becomes unavailable | https://api.github.com/repos/kubernetes/kubernetes/issues/118741/comments | 6 | 2023-06-19T09:29:22Z | 2023-06-19T13:03:58Z | https://github.com/kubernetes/kubernetes/issues/118741 | 1,763,131,173 | 118,741 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I have a cluster of three Node nodes:
For i1/i2/i3, the Pod corresponding to the ingress Controller runs on the i1 node, and the listening port of the NodePort of the Service is 32757
Among the three nodes, it is normal to add port 32757 through their own intranet IP
However, it is not possible... | External access svc nodeport mode TCP status is SYN_RECV | https://api.github.com/repos/kubernetes/kubernetes/issues/118739/comments | 6 | 2023-06-19T08:09:28Z | 2023-06-20T06:51:06Z | https://github.com/kubernetes/kubernetes/issues/118739 | 1,762,992,688 | 118,739 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
create sts Error reporting “is invalid: spec: Forbidden: updates to statefulset spec for fields other than 'replicas', 'template', and 'updateStrategy' are forbidden”
### What did you expect to happen?
Normal creation
### How can we reproduce it (as minimally and precisely as possible)?
apiVersi... | Failed to create STS | https://api.github.com/repos/kubernetes/kubernetes/issues/118734/comments | 7 | 2023-06-19T01:09:40Z | 2023-06-23T07:07:23Z | https://github.com/kubernetes/kubernetes/issues/118734 | 1,762,549,508 | 118,734 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are flaking?
master-informing:
- periodic-conformance-main-k8s-main
### Which tests are flaking?
`Kubernetes e2e suite.[It] [sig-network] Networking Granular Checks: Pods should function for intra-pod communication: http [NodeConformance] [Conformance]`
### Since when has it been flaking?
... | [Flaking Test][cluster-api-provider-aws-e2e-conformance] periodic-conformance-main-k8s-main | https://api.github.com/repos/kubernetes/kubernetes/issues/118731/comments | 26 | 2023-06-18T06:19:13Z | 2023-11-13T14:23:38Z | https://github.com/kubernetes/kubernetes/issues/118731 | 1,762,135,183 | 118,731 |
[
"kubernetes",
"kubernetes"
] | What would you like to be added?
As I know there is an parameter called routingViaHost in network operator in Openshift Container Platform. This is basically used to force OVN-Kubernetes to utilize the host kernel routing table and not use the OVN-Kubernetes routing table.
I am looking for the same solution at K... | Utilizing host kernel routing table in kubernetes | https://api.github.com/repos/kubernetes/kubernetes/issues/118728/comments | 4 | 2023-06-17T17:00:03Z | 2023-06-17T17:20:47Z | https://github.com/kubernetes/kubernetes/issues/118728 | 1,761,924,433 | 118,728 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Recently, I have upgraded cluster from v1.25.9 to v1.27.1 with CRI-O. While joining new node to M1 using kubeadm, Kubelet.crt is not getting generated which in turn is resulting in auto-restart of kubelet service and the node is not able to join the cluster.
### The error is as follows:
Unfortun... | Not able join worker node to master node upgraded from v1.25.9 to v1.27.1 | https://api.github.com/repos/kubernetes/kubernetes/issues/118726/comments | 6 | 2023-06-17T15:03:49Z | 2023-06-18T04:03:02Z | https://github.com/kubernetes/kubernetes/issues/118726 | 1,761,887,787 | 118,726 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
After creating a Service with server side apply, modifications to that service may prevent additional attempts at server side apply.
### What did you expect to happen?
Ideally the additional server side apply's would be successful at asserting the desired state.
### How can we reproduce i... | Issues with server side apply and Services | https://api.github.com/repos/kubernetes/kubernetes/issues/118725/comments | 30 | 2023-06-17T14:16:22Z | 2024-05-13T18:56:21Z | https://github.com/kubernetes/kubernetes/issues/118725 | 1,761,872,183 | 118,725 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
We ran into an issue with an old version of k8s 1.18 that we were running where subnet for cluster IP is given as `fc::/112`.
The control plane comes up just fine but then when you try to create a k8s service, it fails due to a broken behavior with the IP Allocator
```bash
# kubectl apply -... | Service IP Allocator doesn't handle certain IPv6 ranges | https://api.github.com/repos/kubernetes/kubernetes/issues/118723/comments | 3 | 2023-06-17T11:09:29Z | 2023-06-25T14:11:09Z | https://github.com/kubernetes/kubernetes/issues/118723 | 1,761,778,942 | 118,723 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
master-informing
- capg-conformance-main-ci-artifacts
### Which tests are failing?
`periodic-cluster-api-provider-gcp-make-conformance-main-ci-artifacts.Overall`
![Screenshot from 2023-06-17 09-59-04](https://github.com/kubernetes/kubernetes/assets/73882557/3cbb49f1-85d0-4ea4-92c1-f... | [Failing Test] capg-conformance-main-ci-artifacts | https://api.github.com/repos/kubernetes/kubernetes/issues/118718/comments | 10 | 2023-06-17T04:31:02Z | 2023-06-30T08:09:44Z | https://github.com/kubernetes/kubernetes/issues/118718 | 1,761,633,678 | 118,718 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
test
### What did you expect to happen?
test
### How can we reproduce it (as minimally and precisely as possible)?
test
### Anything else we need to know?
_No response_
### Kubernetes version
<details>
```console
$ kubectl version
# paste output here
```
</details>
### Cloud prov... | test | https://api.github.com/repos/kubernetes/kubernetes/issues/118717/comments | 3 | 2023-06-16T20:07:29Z | 2023-06-16T20:07:51Z | https://github.com/kubernetes/kubernetes/issues/118717 | 1,761,262,061 | 118,717 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I'm using HELM to install chart
During the HELM upgrade I got the following error
```
failed to create patch: map: map[] does not contain declared merge key: name
```
In order to find root cause problem , I got the YAML file from helm, with command ```helm upgrade --dry-run `
Copie... | kubectl patch command throws an error without providing any indication when using 'imagePullSecret: - {}' | https://api.github.com/repos/kubernetes/kubernetes/issues/118715/comments | 7 | 2023-06-16T14:52:27Z | 2024-08-08T09:40:17Z | https://github.com/kubernetes/kubernetes/issues/118715 | 1,760,799,859 | 118,715 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
Pod topology spread constraints cluster default policy does not support pod label selector.
### Why is this needed?
In case we need to explain the scenario: we need all the server component to distributed balanced all around all the nodes.
We can express this in deployment pod t... | Pod topology spread constraints cluster default policy does not support label selector | https://api.github.com/repos/kubernetes/kubernetes/issues/118714/comments | 9 | 2023-06-16T14:39:34Z | 2024-03-23T23:42:01Z | https://github.com/kubernetes/kubernetes/issues/118714 | 1,760,774,603 | 118,714 |
[
"kubernetes",
"kubernetes"
] | /sig apps
In many unit tests we set `DefaultJobBackOff` and `syncJobBatchPeriod` to 0. However, this is problematic, because the mechanism works differently when the delay is 0 and when it is >0. When the delay is 0 the delay is immediate and the unit tests can assert if the requeueing was immediate, which makes the... | Cleanup Job controller unit tests for requeuing with delay | https://api.github.com/repos/kubernetes/kubernetes/issues/118712/comments | 3 | 2023-06-16T13:43:24Z | 2023-06-22T17:25:43Z | https://github.com/kubernetes/kubernetes/issues/118712 | 1,760,668,439 | 118,712 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Upgraded cluster from v1.24.6 to v1.26.4 (via v1.25.9) and after that kube-controller-manager starts to eat all available cpu:
<img width="1902" alt="image" src="https://github.com/kubernetes/kubernetes/assets/1713091/b9d22b88-6f94-44dc-b8af-a043288daf92">
Also I see massive `workqueue_retries_t... | kube-controller-manager v1.26 high cpu usage | https://api.github.com/repos/kubernetes/kubernetes/issues/118706/comments | 25 | 2023-06-16T08:38:21Z | 2023-12-27T04:13:31Z | https://github.com/kubernetes/kubernetes/issues/118706 | 1,760,189,871 | 118,706 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
After we upgraded k8s.io/client-go package to v0.26.0, we noticed memory leaks in our components that access the Kubernetes API. For some components we managed to remove the leak by rolling back client-go to 0.25.4, but for other components it creates a dependency hell.
After some profiling and ... | Using Dial function with client-go kubernetes.NewForConfig triggers a memory leak | https://api.github.com/repos/kubernetes/kubernetes/issues/118703/comments | 22 | 2023-06-16T07:32:48Z | 2024-07-25T20:16:59Z | https://github.com/kubernetes/kubernetes/issues/118703 | 1,760,096,639 | 118,703 |
[
"kubernetes",
"kubernetes"
] | _Originally posted by @cheese39 in https://github.com/kubernetes/kubernetes/issues/72593#issuecomment-1594111801_
> Should such a deployment be rejected created? Because after the deployment is successfully created, pods are generated crazy and my k8s cluster crashes.I looked at the other cases in the ... | HostNet Pod with sysctl changing ip_local_port_range should be refused by apiserver | https://api.github.com/repos/kubernetes/kubernetes/issues/118702/comments | 8 | 2023-06-16T05:48:40Z | 2023-10-28T07:48:45Z | https://github.com/kubernetes/kubernetes/issues/118702 | 1,759,963,316 | 118,702 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
`
// RecommendedDefaultAttachDetachControllerConfiguration defaults a pointer to a
// AttachDetachControllerConfiguration struct. This will set the recommended default
// values, but they may be subject to change between API versions. This function
// is intentionally not registered in the schem... | AttachDetachControllerConfiguration.ReconcilerSyncLoopPeriod Comment error | https://api.github.com/repos/kubernetes/kubernetes/issues/118700/comments | 4 | 2023-06-16T04:20:14Z | 2023-10-11T20:51:51Z | https://github.com/kubernetes/kubernetes/issues/118700 | 1,759,896,443 | 118,700 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I used https://github.com/kcp-dev/kcp/tree/v0.11.0/cmd/crd-puller to extract a CRD for the jobs resource, and then tried to submit that CRD to an apiserver that does not have jobs built in. I got the following complaint (which is reasonable).
```
Error from server (Forbidden): error when crea... | Incoherent tags on JobStatus.Conditions | https://api.github.com/repos/kubernetes/kubernetes/issues/118698/comments | 6 | 2023-06-16T01:47:01Z | 2024-03-22T18:28:56Z | https://github.com/kubernetes/kubernetes/issues/118698 | 1,759,791,268 | 118,698 |
[
"kubernetes",
"kubernetes"
] | This is effectively a re-open of https://github.com/kubernetes/kubernetes/issues/99884, but I think its slightly different. Basically my concern is the mixing of disparate kinds of clusters. If you don't agree feel free to close - we have worked around it so this is more to avoid future users issues; it took us _3 yea... | Kubectl Namespace defaulting logic is inconsistent | https://api.github.com/repos/kubernetes/kubernetes/issues/118693/comments | 10 | 2023-06-15T19:18:55Z | 2024-12-19T21:18:15Z | https://github.com/kubernetes/kubernetes/issues/118693 | 1,759,412,395 | 118,693 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
A security issue was discovered in Kubelet that allows pods to bypass the seccomp profile enforcement. This issue has been rated LOW ([CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N)) (score: 3.4).
If you have... | CVE-2023-2431: Bypass of seccomp profile enforcement | https://api.github.com/repos/kubernetes/kubernetes/issues/118690/comments | 6 | 2023-06-15T14:42:32Z | 2023-09-29T21:16:18Z | https://github.com/kubernetes/kubernetes/issues/118690 | 1,758,988,605 | 118,690 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
We can see pause container of the Exited pod still holding Ip adress.
$:~> sudo crictl ps -a | grep ft-
7b59ba5f78776 2a9799d12b5b7 4 weeks ago **Exited** bind-named 0 **6fb4e29f02f46** ft-675bc886f6-fcbnl... | pod/container is "Exited" state, still corresponding pause container holding the IP address. | https://api.github.com/repos/kubernetes/kubernetes/issues/118684/comments | 7 | 2023-06-15T09:56:18Z | 2023-06-22T14:37:50Z | https://github.com/kubernetes/kubernetes/issues/118684 | 1,758,467,967 | 118,684 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
In /etc/docker/daemon.json, I set "log-driver": "local", then deploy kubenetes v1.25. But it can't get pod log.
If I use default json driver for logging, it works.
### What did you expect to happen?
Why not support "local-driver" any more? I beleive kubernetes 1.20 supports it.
### How can we r... | kubectl fail to get pod log when docker use log driver "local-dirver" | https://api.github.com/repos/kubernetes/kubernetes/issues/118682/comments | 7 | 2023-06-15T09:44:55Z | 2023-06-28T17:28:30Z | https://github.com/kubernetes/kubernetes/issues/118682 | 1,758,448,901 | 118,682 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Killing or evicting a pod that is already terminated will result in a 10 second timeout in killPodNow.
A warning event is logged:
Reason: ExceededGracePeriod, Message: Container runtime did not kill the pod within specified grace period.
The problem appears when using emptyDir volumes with... | 10 second timeout when killing or evicting pod | https://api.github.com/repos/kubernetes/kubernetes/issues/118679/comments | 5 | 2023-06-15T09:33:52Z | 2025-02-27T08:09:20Z | https://github.com/kubernetes/kubernetes/issues/118679 | 1,758,430,977 | 118,679 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
The mod dependency depends on the gogo protobuf. But the package is **Deprecated** , do you have any plan to remove that?Some code scan tools marks it as CVE(https://nvd.nist.gov/vuln/detail/cve-2021-3121)
### What did you expect to happen?
Remove the Deprecated package of gogo/protobuf.
### How ... | The Deprecated package: https://github.com/gogo/protobuf | https://api.github.com/repos/kubernetes/kubernetes/issues/118678/comments | 4 | 2023-06-15T08:32:50Z | 2023-06-15T16:45:21Z | https://github.com/kubernetes/kubernetes/issues/118678 | 1,758,321,835 | 118,678 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
Dynamic calculation of memory utilization in percentage for Horizontal Pod Autoscaler
### Why is this needed?
The proposed addition is to enable the dynamic calculation of memory utilization in percentage for the Horizontal Pod Autoscaler (HPA) in Kubernetes. Currently, the HPA o... | HPA doesnot support dynamic memory calculation | https://api.github.com/repos/kubernetes/kubernetes/issues/118676/comments | 8 | 2023-06-15T07:08:43Z | 2024-03-26T23:19:58Z | https://github.com/kubernetes/kubernetes/issues/118676 | 1,758,184,175 | 118,676 |
[
"kubernetes",
"kubernetes"
] | I have searched all the entries and this problem has been bothering me for half a month.
kube-controller-manager and kube-scheduler has been repeatedly restarted over 200 times,K8s reinitialization issue still exists.
The following is the latest question, thank you all.
Etcd:
{"level":"info","ts":"2023-06-15T03:5... | Dear Friends, this is my first time using it. If there are any discrepancies, please forgive me.I urgently need the help of my partner.This is a question about k8s. | https://api.github.com/repos/kubernetes/kubernetes/issues/118675/comments | 8 | 2023-06-15T06:35:54Z | 2023-06-20T07:32:59Z | https://github.com/kubernetes/kubernetes/issues/118675 | 1,758,138,931 | 118,675 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
> Note: If the Pod's restartPolicy is Never, container's resize restart policy must be set to NotRequired for all Containers in the Pod.
https://kubernetes.io/docs/tasks/configure-pod-container/resize-container-resources/
This is already mentioned in the doc, but no warning or decline is shown... | warning or decline pod creation with RestartContainer resizePolicy if the restartPolicy is Never | https://api.github.com/repos/kubernetes/kubernetes/issues/118674/comments | 4 | 2023-06-15T05:07:12Z | 2023-10-15T02:13:36Z | https://github.com/kubernetes/kubernetes/issues/118674 | 1,758,044,766 | 118,674 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Error Logs
telepresence helm install: error: connector service did not start: timeout while waiting for connector to start
connection error: desc = "transport: error while dialing: dial tcp 127.0.0.1:62871: connect: connection refused"
telepresence helm install: error: connector service did not s... | telepresence helm install: error | https://api.github.com/repos/kubernetes/kubernetes/issues/118673/comments | 5 | 2023-06-15T03:40:20Z | 2023-06-23T07:07:58Z | https://github.com/kubernetes/kubernetes/issues/118673 | 1,757,976,538 | 118,673 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Calling wait.PollUntilContextTimeout with immediate=true does not invoke the passed condition function if context has already been cancelled.
### What did you expect to happen?
wait.PollUntilContextTimeout with immediate=true should invoke the passed condition function at least once even if co... | wait.PollUntilContextTimeout with immediate=true does not invoke condition function at least once | https://api.github.com/repos/kubernetes/kubernetes/issues/118671/comments | 6 | 2023-06-15T01:19:06Z | 2023-06-23T16:25:25Z | https://github.com/kubernetes/kubernetes/issues/118671 | 1,757,871,977 | 118,671 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
We have a application that generates a service account using the following yaml file:
{{- if not (lookup "v1" "ServiceAccount" .Release.Namespace (.Values.serviceAccountName | default "service-account")) }} apiVersion: v1 kind: ServiceAccount metadata: labels: app.kubernetes.io/instance: instance... | Helm upgrade points to old service account and fails with missing token | https://api.github.com/repos/kubernetes/kubernetes/issues/118670/comments | 6 | 2023-06-14T21:05:59Z | 2023-06-16T06:02:22Z | https://github.com/kubernetes/kubernetes/issues/118670 | 1,757,648,935 | 118,670 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
- Add a configuration option to the nodes to declare a failure probability (SLA).
- Allow the workloads to configure the minimum failure probability they need to be able to run.
/sig scheduling
### Why is this needed?
The idea started to form while implementing the pla... | Allow nodes to declare failure probability/SLA | https://api.github.com/repos/kubernetes/kubernetes/issues/118669/comments | 22 | 2023-06-14T20:47:14Z | 2024-09-15T20:07:41Z | https://github.com/kubernetes/kubernetes/issues/118669 | 1,757,621,646 | 118,669 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
After upgrading kubernetes version to 1.26.5, hardware interrupts on all CPUs are eating up 0.3%.
kubelet-config.yaml
--------------------
kubeletCgroups: /system.slice/kubelet.service
clusterDomain: cluster.local
protectKernelDefaults: true
rotateCertificates: true
clusterDNS:
- 169.254.2... | Hardware interrupts are occurring at 0.3% on all CPUs. | https://api.github.com/repos/kubernetes/kubernetes/issues/118663/comments | 14 | 2023-06-14T13:05:42Z | 2023-07-01T16:19:28Z | https://github.com/kubernetes/kubernetes/issues/118663 | 1,756,865,610 | 118,663 |
[
"kubernetes",
"kubernetes"
] | [PR](https://github.com/kubernetes/kubernetes/pull/118619) introduces the reuse of the gRPC connection instead of creating a new one each time `NodePrepareResource` and `NodeUnprepareResource` are called.
This should be covered by e2e (and unit if possible) test
```[tasklist]
### Tasks
- [x] add unit test
- [ ] ad... | dynamic resource allocation: add e2e (and unit) test to ensure the reuse of the gRPC connection | https://api.github.com/repos/kubernetes/kubernetes/issues/118661/comments | 15 | 2023-06-14T11:25:22Z | 2025-02-26T08:10:20Z | https://github.com/kubernetes/kubernetes/issues/118661 | 1,756,671,351 | 118,661 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
- https://testgrid.k8s.io/sig-node-containerd#cos-cgroupv1-containerd-node-e2e-serial
- https://testgrid.k8s.io/sig-node-containerd#cos-cgroupv2-containerd-node-e2e-serial
### Which tests are failing?
sig-node : DRA related tests are failing
```
[sig-node] DRA [Feature:Dynamic... | sig-node-containerd#cos-cgroupv1/v2-containerd-node-e2e-serial are failing | https://api.github.com/repos/kubernetes/kubernetes/issues/118660/comments | 7 | 2023-06-14T11:12:07Z | 2023-06-20T14:54:25Z | https://github.com/kubernetes/kubernetes/issues/118660 | 1,756,642,918 | 118,660 |
[
"kubernetes",
"kubernetes"
] | I modified the cpu management policy according to the official document [Control CPU Management Policies on the Node](https://kubernetes.io/docs/tasks/administer-cluster/cpu-management-policies/), but after experiments, I found that the execution time of the task has not been shortened but slightly longer. How do I kno... | How to know that the cpu management policy is in effect? | https://api.github.com/repos/kubernetes/kubernetes/issues/118657/comments | 6 | 2023-06-14T09:58:51Z | 2023-07-03T13:37:31Z | https://github.com/kubernetes/kubernetes/issues/118657 | 1,756,509,584 | 118,657 |
[
"kubernetes",
"kubernetes"
] | ### Failure cluster [4d3dd586c2a5b025c09b](https://go.k8s.io/triage#4d3dd586c2a5b025c09b)
##### Error text:
```
Failed
=== RUN TestSchedulerGuaranteeNonNilNodeInSchedulingCycle
E0602 02:37:43.837413 3708 runtime.go:79] Observed a panic: &errors.errorString{s:"channel full"} (channel full)
goroutine 520 [ru... | Failure cluster [4d3dd586...] | https://api.github.com/repos/kubernetes/kubernetes/issues/118656/comments | 8 | 2023-06-14T09:22:41Z | 2024-03-22T16:29:01Z | https://github.com/kubernetes/kubernetes/issues/118656 | 1,756,447,426 | 118,656 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
k8s 1.22
now I create a quota
#kubectl get quota resourcequota-testaa -n testaa -o yaml
apiVersion: v1
kind: ResourceQuota
metadata:
creationTimestamp: "2023-06-07T07:01:33Z"
name: resourcequota-testaa
namespace: testaa
resourceVersion: "1974704"
uid: 54ff3d62-b528-48cf-9590-f... | Which resources need do ValidateResourceQuantityValue() | https://api.github.com/repos/kubernetes/kubernetes/issues/118654/comments | 10 | 2023-06-14T09:01:16Z | 2024-07-30T20:20:23Z | https://github.com/kubernetes/kubernetes/issues/118654 | 1,756,406,134 | 118,654 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
When I add an environment variable to the deployment, I want its value to be "true". However, to achieve this, I have to add double quotes in the YAML file. If I don't do this, the following error will occur. I believe this error is unnecessary. Although YAML can parse it as a bool... | Parse bool env yaml to string | https://api.github.com/repos/kubernetes/kubernetes/issues/118649/comments | 15 | 2023-06-14T05:09:38Z | 2023-06-29T20:09:29Z | https://github.com/kubernetes/kubernetes/issues/118649 | 1,756,068,414 | 118,649 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
the rules of ClusterRole is reset as null when applying ClusterRule with AggregationRule. it results in permission blank window and bring unexpected Unauthorized errrors.
ClusterRole with aggregation rule:
```yaml
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
nam... | blank window when updating ClusterRole with AggregationRule | https://api.github.com/repos/kubernetes/kubernetes/issues/118648/comments | 16 | 2023-06-14T03:09:34Z | 2024-09-12T08:40:40Z | https://github.com/kubernetes/kubernetes/issues/118648 | 1,755,971,446 | 118,648 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
My current scenario is that I need to encrypt resources in the cluster and periodically rotate the encryption keys. I followed the demonstration in the official documentation and used 'Encrypting Confidential Data at Rest'. Unfortunately, my apiserver has an 80% chance of failing to restart.
Fir... | An unstable bug related to the restarting of a static pod for the apiserver | https://api.github.com/repos/kubernetes/kubernetes/issues/118646/comments | 5 | 2023-06-14T02:22:37Z | 2023-06-30T17:54:25Z | https://github.com/kubernetes/kubernetes/issues/118646 | 1,755,921,124 | 118,646 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
It's possible to apply the exact same JSON content twice and have it fail the second time because a field is immutable. The error message is not helpful.
```sh
The Job "legacybackup-rsync" is invalid: spec.template: Invalid value: core.PodTemplateSpec{ObjectMeta:v1.ObjectMeta{Name:"", GenerateNa... | kubectl should report useful error messages for immutable fields | https://api.github.com/repos/kubernetes/kubernetes/issues/118645/comments | 15 | 2023-06-13T23:43:57Z | 2024-03-23T03:36:58Z | https://github.com/kubernetes/kubernetes/issues/118645 | 1,755,799,655 | 118,645 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
Currently pause image tag is hard coded in https://github.com/kubernetes/kubernetes/blob/3d27dee047a87527735bf74cfcc6b8ff8875f66c/cmd/kubeadm/app/constants/constants.go#LL420C2-L420C14
But we want change it to another tag during running kubeadm
Add a new filed just like `Kube... | Make PauseVersion configurable | https://api.github.com/repos/kubernetes/kubernetes/issues/118643/comments | 4 | 2023-06-13T21:51:52Z | 2023-06-14T00:37:42Z | https://github.com/kubernetes/kubernetes/issues/118643 | 1,755,691,746 | 118,643 |
[
"kubernetes",
"kubernetes"
] | ### CVE-2023-2727: Bypassing policies imposed by the ImagePolicyWebhook admission plugin
CVSS Rating: [CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N)
A security issue was discovered in Kubernetes where users may be able to launch... | CVE-2023-2727, CVE-2023-2728: Bypassing policies imposed by the ImagePolicyWebhook and bypassing mountable secrets policy imposed by the ServiceAccount admission plugin | https://api.github.com/repos/kubernetes/kubernetes/issues/118640/comments | 10 | 2023-06-13T14:42:06Z | 2024-07-01T15:57:09Z | https://github.com/kubernetes/kubernetes/issues/118640 | 1,755,056,681 | 118,640 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Trying the [suggestion from the deprecation notice for NewExponentialBackoffManager](https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/apimachinery/pkg/util/wait/backoff.go#L330-L353), results in a compile error, as the delayFn.Timer() does not implement Backoff() from BackoffM... | Suggestion from Deprecation Notice for NewExponentialBackoffManager not Working | https://api.github.com/repos/kubernetes/kubernetes/issues/118638/comments | 8 | 2023-06-13T12:36:55Z | 2024-03-13T13:23:01Z | https://github.com/kubernetes/kubernetes/issues/118638 | 1,754,789,081 | 118,638 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
It report duplicated errors when run kubectl failed.
`root@d4da4821-1f06-4d7e-604d-7dff9712f8e4:/tmp/build/5f4c2eb5# kubectl get all
W0524 07:31:19.522712 1807 loader.go:222] Config not found: /root/.kube/config
E0524 07:31:19.526502 1807 memcache.go:265] couldn't get current server API gro... | Report duplicated entries of errors in k8s v1.26.4 | https://api.github.com/repos/kubernetes/kubernetes/issues/118632/comments | 15 | 2023-06-13T06:08:17Z | 2024-03-28T00:33:08Z | https://github.com/kubernetes/kubernetes/issues/118632 | 1,754,108,785 | 118,632 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
Kubernetes is restarting python docker container with CrashLoop BackOff error.
I have python container which runs perfectly for first time. Unfortunately, kubernetes status wont go to running state and it restarts with crashloop backoff error.
I'm running this on a gcp GKE cluster. I ... | CrashLoop BackOff error | https://api.github.com/repos/kubernetes/kubernetes/issues/118630/comments | 4 | 2023-06-13T01:38:03Z | 2023-06-13T01:49:35Z | https://github.com/kubernetes/kubernetes/issues/118630 | 1,753,871,096 | 118,630 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I have 2 nodes and I want mssql and rabbitmq running on the same node.
I have tolleration in both mssql and rabbitmq statefulsets that match the same taint on both nodes, so mssql can go to either node, it spins up first.
I configured a podAffinity in my rabbitmq statefulset so it will schedule th... | podAffinity on statefulset is not scheduling pod to appropriate node with dependency pod label | https://api.github.com/repos/kubernetes/kubernetes/issues/118627/comments | 6 | 2023-06-12T21:19:21Z | 2023-06-21T17:37:22Z | https://github.com/kubernetes/kubernetes/issues/118627 | 1,753,612,473 | 118,627 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
`Kind` uses containerd for worker nodes by default, and latest release of [kind 0.19](https://github.com/kubernetes-sigs/kind/releases/tag/v0.19.0) uses by default base-image with containerd 1.6 for worker node. Unfortunately, CDI was merged into containerd 1.7, and CI at the moment uses `kind` bina... | DRA: Running e2e tests with king for Dynamic Resource Allocation locally fails with latest Kind 0.19 release | https://api.github.com/repos/kubernetes/kubernetes/issues/118616/comments | 4 | 2023-06-12T10:13:50Z | 2023-06-13T07:44:00Z | https://github.com/kubernetes/kubernetes/issues/118616 | 1,752,400,663 | 118,616 |
[
"kubernetes",
"kubernetes"
] | When a ResourceClaim:
- uses delayed allocation
- does not get created for a specific pod (i.e. not from a template)
then it currently gets allocated and remains allocated until:
- scheduling of a pod fails because the node originally chosen for the allocation isn't suitable, in which case the scheduler triggers ... | DRA: delayed allocation: deallocate after use | https://api.github.com/repos/kubernetes/kubernetes/issues/118613/comments | 2 | 2023-06-12T06:45:01Z | 2023-07-01T19:56:50Z | https://github.com/kubernetes/kubernetes/issues/118613 | 1,752,014,590 | 118,613 |
[
"kubernetes",
"kubernetes"
] | The problem that we need to solve for cluster autoscaling when the cluster uses dynamic resource allocation is to simulate how adding new nodes will affect pod scheduling. This matters when some DRA driver depends on resources on such new nodes.
One possible solution is outlined in https://github.com/kubernetes/enhanc... | DRA: integration with cluster autoscaler | https://api.github.com/repos/kubernetes/kubernetes/issues/118612/comments | 42 | 2023-06-12T06:36:22Z | 2024-12-20T15:49:53Z | https://github.com/kubernetes/kubernetes/issues/118612 | 1,752,005,419 | 118,612 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Kube-scheduler crashed when many pods were scheduled simultaneously.
`184817 goroutine 431 [running]:
184818 runtime.throw(0x21afb8d, 0x15)
184819 /usr/local/go/src/runtime/panic.go:1117 +0x72 fp=0xc0019736b8 sp=0xc001973688 pc=0x438852
184820 runtime.mapassign_faststr(0x1e6df00, 0xc... | Concurrent map writes on PVCRefCounts of NodeInfo | https://api.github.com/repos/kubernetes/kubernetes/issues/118611/comments | 3 | 2023-06-12T02:07:47Z | 2023-06-16T01:41:25Z | https://github.com/kubernetes/kubernetes/issues/118611 | 1,751,760,377 | 118,611 |
[
"kubernetes",
"kubernetes"
] | Support SONiC devices to create a CloudNative approach handling network equipment:
SONiC hardware = K8s nodes
SONiC containers = K8s containers
SONiC apps = K8s apps
SONiC port acl= K8s policies
https://github.com/sonic-net/SONiC | SONiC support | https://api.github.com/repos/kubernetes/kubernetes/issues/118609/comments | 4 | 2023-06-11T12:50:07Z | 2023-06-11T13:43:39Z | https://github.com/kubernetes/kubernetes/issues/118609 | 1,751,414,332 | 118,609 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
-- Logs begin at 日 2023-06-11 11:33:35 CST, end at 日 2023-06-11 12:45:21 CST. --
6月 11 11:36:26 master1 systemd[1]: Dependency failed for Kubernetes Kubelet. #这是kubelet日志错误信息
-- Subject: Unit kubelet.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedeskto... | k8s机器每次开机，kubelet服务都是失败状态，也设置了开机自启服务的，详情见下图 | https://api.github.com/repos/kubernetes/kubernetes/issues/118607/comments | 7 | 2023-06-11T05:19:50Z | 2023-08-21T16:37:05Z | https://github.com/kubernetes/kubernetes/issues/118607 | 1,751,252,508 | 118,607 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
master-informing:
- gce-cos-master-serial
### Which tests are failing?
`Kubernetes e2e suite: [It] [sig-storage] PersistentVolumes-local Stress with local volumes [Serial] should be able to process many pods and reuse local volumes`
![Screenshot from 2023-06-10 11-15-02](https://git... | [Failing Test] gce-cos-master-serial | https://api.github.com/repos/kubernetes/kubernetes/issues/118602/comments | 12 | 2023-06-10T05:45:20Z | 2023-06-13T08:35:18Z | https://github.com/kubernetes/kubernetes/issues/118602 | 1,750,814,244 | 118,602 |
[
"kubernetes",
"kubernetes"
] | At present, I have encountered some questions, and I have not solved it by consulting the documentation. When I want to use the cri-api interface of k8s to create pods and containers, I find that there are no examples for my reference. Are there any examples of calling cri-api? | Some usage examples about cri-api | https://api.github.com/repos/kubernetes/kubernetes/issues/118594/comments | 4 | 2023-06-09T16:02:21Z | 2023-06-09T16:27:33Z | https://github.com/kubernetes/kubernetes/issues/118594 | 1,750,150,066 | 118,594 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
I have encountered continous "CrashLoopBackOff" Errors when launching GPU Deployments
However now i see that even non-GPU deployments also i cannot launch except NGINX
NGINX deployment is running without issues.
### Which tests are failing?
`GPU Deployment
apiVersion: apps/v... | GPU and non-GPU deployments are with "CrashLoopBackOff" Error | https://api.github.com/repos/kubernetes/kubernetes/issues/118589/comments | 9 | 2023-06-09T10:00:47Z | 2024-03-22T13:27:59Z | https://github.com/kubernetes/kubernetes/issues/118589 | 1,749,573,820 | 118,589 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I have created the following secret in my cluster.
```yaml
apiVersion: v1
kind: Secret
metadata:
name: test
immutable: true
data:
"foo": ""
"one": dHdvCg==
```
When I add labels to my secret and try to apply it in the cluster I get the following error
```yaml
apiVersion: v1
... | Metadata of immutable secrets cannot be changed when the `.data` has a key with empty value | https://api.github.com/repos/kubernetes/kubernetes/issues/118588/comments | 4 | 2023-06-09T09:32:25Z | 2023-09-07T15:01:46Z | https://github.com/kubernetes/kubernetes/issues/118588 | 1,749,522,924 | 118,588 |
[
"kubernetes",
"kubernetes"
] | /sig apps
When a terminal pod (Failed or Succeeded) has a deletionTimestamp it is ignored by DaemonSet and not recreated, because of this check: https://github.com/kubernetes/kubernetes/blob/master/pkg/controller/daemon/daemon_controller.go#L822-L824.
It was observed when working on what was isolated to Kubelet i... | DaemonSet does not recreate failed pods when they have deletionTimestamp | https://api.github.com/repos/kubernetes/kubernetes/issues/118587/comments | 3 | 2023-06-09T09:26:57Z | 2023-06-27T15:56:35Z | https://github.com/kubernetes/kubernetes/issues/118587 | 1,749,512,413 | 118,587 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Using "kind" with podman
I installed ingress-nginx. The service is started.
I then create a basic Deployment to run "nginx" (to test), created an ingress to respond on `foobar.localhost`.
Then I start:
```bash
kubectl -n ingress-controller port-forward nginx-ingress-nginx-controller-6b5f8... | Port-forward fails using TLS, not with HTTP (connection reset by peer) | https://api.github.com/repos/kubernetes/kubernetes/issues/118586/comments | 3 | 2023-06-09T07:57:15Z | 2023-06-09T08:04:00Z | https://github.com/kubernetes/kubernetes/issues/118586 | 1,749,347,926 | 118,586 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
Usecase to have multiple managers in the same controller
### Why is this needed?
Usecase to have multiple managers in the same controller | Can we have multiple managers which points to different configs in the same controller? Is that supported? | https://api.github.com/repos/kubernetes/kubernetes/issues/118584/comments | 7 | 2023-06-09T07:07:02Z | 2023-06-30T17:56:08Z | https://github.com/kubernetes/kubernetes/issues/118584 | 1,749,262,758 | 118,584 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
I usede k8s version is 1.25.4 . when I start nfs-client-provisioner ,It is error, and the error log is：managed-nfs-storage": unexpected error getting claim reference: selfLink was empty, can't make reference 。 if I added parameters - --feature-gates=RemoveSelfLink=false to k... | managed-nfs-storage": unexpected error getting claim reference: selfLink was empty, can't make reference | https://api.github.com/repos/kubernetes/kubernetes/issues/118582/comments | 5 | 2023-06-09T04:19:47Z | 2023-06-13T19:17:02Z | https://github.com/kubernetes/kubernetes/issues/118582 | 1,749,100,123 | 118,582 |
[
"kubernetes",
"kubernetes"
] | This is speculative and needs to be investigated, but it looks like in some situations the connection to webhooks is not re-used, causing connections to leak and all sorts of snowballing effect.
We should look for an existing test and stress-test it to see if we can further investigate the issue.
/wg api-expressi... | HTTP Connection to webhooks is not always re-used | https://api.github.com/repos/kubernetes/kubernetes/issues/118581/comments | 3 | 2023-06-08T18:00:47Z | 2024-05-18T01:39:22Z | https://github.com/kubernetes/kubernetes/issues/118581 | 1,748,402,592 | 118,581 |
[
"kubernetes",
"kubernetes"
] | When compared to client-side apply that doesn't send empty `{}` patches, server-side apply always sends the manifest.
When no-op apply is sent, it triggers the full mutation/admission which can cause a lot of stress on webhooks.
It might be useful to not call the validating webhooks if the resource hasn't changed.
... | Server-side Apply can cause additional calls to webhooks | https://api.github.com/repos/kubernetes/kubernetes/issues/118580/comments | 12 | 2023-06-08T15:57:54Z | 2024-05-26T15:34:19Z | https://github.com/kubernetes/kubernetes/issues/118580 | 1,748,212,269 | 118,580 |
Subsets and Splits
Unique Owner-Repo Count
Counts the number of unique owner-repos in the dataset, providing a basic understanding of diverse repositories.