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"
] | ### What happened?
The default scheduler (kube-scheduler) schedules pods and kubelet finds insufficient resources, then pods failed as follows.
```
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 14m default-scheduler ... | kube-scheduler schedules pods despite of insufficient resource and the pod fails. | https://api.github.com/repos/kubernetes/kubernetes/issues/107679/comments | 14 | 2022-01-21T00:17:26Z | 2022-05-02T13:45:27Z | https://github.com/kubernetes/kubernetes/issues/107679 | 1,109,890,238 | 107,679 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
If you shut down two out of three control plane nodes, there's a chance the remaining kube-scheduler and kube-controller-manager instances will log this line over and over:
```
E0120 20:42:53.703984 1 leaderelection.go:361] Failed to update lock: Put "https://sterling-cluster.k8s.renci.o... | [scheduler/controller-manager] Failed to update lock: net/http: request canceled | https://api.github.com/repos/kubernetes/kubernetes/issues/107678/comments | 5 | 2022-01-20T23:14:40Z | 2022-01-24T09:00:03Z | https://github.com/kubernetes/kubernetes/issues/107678 | 1,109,855,809 | 107,678 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
We captured the following logs from a LoadBalancer reconciliation
```
I0120 03:32:45.481024 1 azure_loadbalancer.go:543] getServiceLoadBalancerStatus gets ingress IP "52.224.95.140" from frontendIPConfiguration "aa7324b3765f34618b1772b380ce1234" for service "kube-system/vpn-shoot"
I0120 0... | azure: LoadBalancer not reconciled properly | https://api.github.com/repos/kubernetes/kubernetes/issues/107672/comments | 7 | 2022-01-20T13:27:19Z | 2022-04-19T05:22:19Z | https://github.com/kubernetes/kubernetes/issues/107672 | 1,109,301,864 | 107,672 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Kubernetes is unable to pull images from repositories without a FQDN.
So `myrepo.mycompany.com/image` works but `myrepo/image` does not work.
The point however is that nearly every other tool (ping, curl, browsers etc) support shortened hostnames.
```
kubelet Pulling image "my... | Feature Request: Support Image Registries without Domain Suffix | https://api.github.com/repos/kubernetes/kubernetes/issues/107671/comments | 11 | 2022-01-20T12:36:50Z | 2022-06-25T20:16:38Z | https://github.com/kubernetes/kubernetes/issues/107671 | 1,109,250,729 | 107,671 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Create deployment from a manifest file having different "hostAliases" with an upgrade from an existing one.
### What did you expect to happen?
The hostAliases in both case should be have 3 records, not loss when upgrade
### How can we reproduce it (as minimally and precisely as possible)?
1. Cre... | Loss hostAliases records when edit existing deployment | https://api.github.com/repos/kubernetes/kubernetes/issues/107668/comments | 5 | 2022-01-20T10:16:33Z | 2022-01-25T21:19:15Z | https://github.com/kubernetes/kubernetes/issues/107668 | 1,109,112,603 | 107,668 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I ran a deployment with replicas 1 and use `subPathExpr` to set container's subpath dir, which uses NFS as the storage backend, and create about 100000 dirs in container's subPath dir,when delete the pod, it spent much more time to end `Terminating` status, and when the replicas increase to 10 and... | Pods in Terminating status lasts much long time when subPath is set and contains a large number of directories | https://api.github.com/repos/kubernetes/kubernetes/issues/107667/comments | 4 | 2022-01-20T09:52:18Z | 2022-01-25T04:06:31Z | https://github.com/kubernetes/kubernetes/issues/107667 | 1,109,086,541 | 107,667 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
kube-controller-manager yields whole stack trace when it loses leaderelection.
### What did you expect to happen?
kube-controller-manager to only log `leaderelection lost` and to exit (without logging 17K lines of stack trace that is not useful for anyone).
### How can we reproduce it (as minimal... | kube-controller-manager yields whole stack trace when it loses leaderelection | https://api.github.com/repos/kubernetes/kubernetes/issues/107665/comments | 10 | 2022-01-20T08:47:11Z | 2022-03-28T13:44:48Z | https://github.com/kubernetes/kubernetes/issues/107665 | 1,109,021,493 | 107,665 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When the cluster initializes with kubeadm running, the kube-ipvs0 interface is set to NOARP and DOWN, so services in the cluster exposed through LoadBalancer are unavailable. Manual operations to set the ARP status of this interface to ON and the state to UP result in a state change to UNKNOWN and d... | Interface kube-ipvs0 NOARP and DOWN | https://api.github.com/repos/kubernetes/kubernetes/issues/107662/comments | 8 | 2022-01-20T07:37:16Z | 2022-01-23T04:25:35Z | https://github.com/kubernetes/kubernetes/issues/107662 | 1,108,960,566 | 107,662 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
all CI jobs
### Which tests are failing?
Before kicking tests, those jobs are failed like
```
Using attach strategy to execute scripts...
Preparing environment 10:07
Waiting for pod gitlab/runner-f-bmr8fc-project-9659330-concurrent-2rfq5v to be running, status is Pending
...
W... | gitlab/runner is Pending at all CI jobs | https://api.github.com/repos/kubernetes/kubernetes/issues/107649/comments | 3 | 2022-01-19T21:44:40Z | 2022-01-19T21:45:57Z | https://github.com/kubernetes/kubernetes/issues/107649 | 1,108,591,149 | 107,649 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
HPA scales in the deployment with no reason / blank reason.
### What did you expect to happen?
There should always be a reason for scale in.
### Ho... | HPA scale in with no reason / blank reason | https://api.github.com/repos/kubernetes/kubernetes/issues/107647/comments | 15 | 2022-01-19T18:28:38Z | 2023-09-12T13:59:28Z | https://github.com/kubernetes/kubernetes/issues/107647 | 1,108,425,010 | 107,647 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Run e2e tests with E2E_PARALLEL=true
See the progress updates that are sent to Sonobuoy (and printed on the command line).
The total test count is listed as -1, the total tests completed and failed go up and down rather than monotonically up. This is because each thread is reporting its own progre... | e2e test progress updates when in parallel mode are incorrect | https://api.github.com/repos/kubernetes/kubernetes/issues/107645/comments | 10 | 2022-01-19T17:40:41Z | 2022-10-18T17:49:55Z | https://github.com/kubernetes/kubernetes/issues/107645 | 1,108,381,319 | 107,645 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
sig-release-master-informing, aks-engine-windows-containerd-master
### Which tests are failing?
* ci-kubernetes-e2e-aks-engine-azure-master-windows-containerd.Overall
* kubetest.Up
### Since when has it been failing?
2022-01-18 18:55 CET
### Testgrid link
https://testgrid.k8s.io/sig-... | [Failing test] aks-engine-windows-containerd-master | https://api.github.com/repos/kubernetes/kubernetes/issues/107641/comments | 9 | 2022-01-19T14:44:07Z | 2022-01-21T01:37:28Z | https://github.com/kubernetes/kubernetes/issues/107641 | 1,108,187,937 | 107,641 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
in TestControllerV2SyncCronJob, there are many listing the properties that don't matter (like nil, false). and many constants F and T, which is unnecessary.
### What did you expect to happen?
As per @alculquicondor 's request, We shouldn't be listing the properties that don't matter (like nil, fal... | readability enhancement on unit test of cron job controller | https://api.github.com/repos/kubernetes/kubernetes/issues/107633/comments | 5 | 2022-01-19T10:41:48Z | 2022-01-27T05:12:50Z | https://github.com/kubernetes/kubernetes/issues/107633 | 1,107,938,912 | 107,633 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
After Kubernetes Node Disk Pressure eviction:
```
kubelet[18540]: I0117 23:10:52.824614 18540 eviction_manager.go:339] "Eviction manager: attempting to reclaim" resourceName="ephemeral-storage"
kubelet[18540]: I0117 23:10:52.858662 18540 eviction_manager.go:350] "Eviction manager: must evic... | Pod hasn't been rescheduled after Disk pressure eviction (exit code: 143) | https://api.github.com/repos/kubernetes/kubernetes/issues/107632/comments | 14 | 2022-01-19T08:27:24Z | 2022-07-30T20:34:30Z | https://github.com/kubernetes/kubernetes/issues/107632 | 1,107,799,107 | 107,632 |
[
"kubernetes",
"kubernetes"
] | the code is as follows:
```
obj := &corev1.Pod{}
pod := h.Decoder.Decode(req, obj)
```
and output is:
```
&Pod{ObjectMeta:{ test-2021-10-26-06-00-1026060225-573e31ecd3e668d7c1cb- 0 0001-01-01 00:00:00 +0000 UTC <nil> <nil>
```
Can anyone tell me why this happened and how to fix it? thx! | the namespace in pod is empty | https://api.github.com/repos/kubernetes/kubernetes/issues/113952/comments | 14 | 2022-01-19T07:34:04Z | 2022-11-16T13:55:22Z | https://github.com/kubernetes/kubernetes/issues/113952 | 1,451,615,554 | 113,952 |
[
"kubernetes",
"kubernetes"
] | Checked in:
staging/src/k8s.io/apiextensions-apiserver/pkg/generated/openapi/zz_generated.openapi.go
staging/src/k8s.io/code-generator/examples/apiserver/openapi/zz_generated.openapi.go
staging/src/k8s.io/kube-aggregator/pkg/generated/openapi/zz_generated.openapi.go
staging/src/k8s.io/sample-apiserver/pkg/generated... | 4 of 5 zz_generated.openapi.go files are checked in - why? | https://api.github.com/repos/kubernetes/kubernetes/issues/107625/comments | 7 | 2022-01-19T00:38:20Z | 2022-03-01T14:35:49Z | https://github.com/kubernetes/kubernetes/issues/107625 | 1,107,505,934 | 107,625 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When restarting k3s, it can't start any pod anymore, it seems like there are ghost pods somewhere in the system.
17004 proxier.go:1600] "can't open port, skipping it" err="listen tcp4 192.168.50.3:6990: bind: address already in use" port={Description:externalIP for prod-tools/marketdata-backend... | 17004 proxier.go:1600] "can't open port, skipping it" | https://api.github.com/repos/kubernetes/kubernetes/issues/107619/comments | 4 | 2022-01-18T15:20:51Z | 2022-01-18T21:11:25Z | https://github.com/kubernetes/kubernetes/issues/107619 | 1,107,034,753 | 107,619 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
The same phenomenon with #101695 ,but in pod and node annotation.
### What did you expect to happen?
The ANSI escape characters will be filtered so they couldn't affect the terminal (i.e. using embeded ANSI colors won't do anything to the terminal).
### How can we reproduce it (as minimally a... | ANSI escape characters in kubectl output annotation are not being filtered - | https://api.github.com/repos/kubernetes/kubernetes/issues/107617/comments | 8 | 2022-01-18T09:55:55Z | 2022-01-20T17:49:43Z | https://github.com/kubernetes/kubernetes/issues/107617 | 1,106,696,323 | 107,617 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
https://cloud.google.com/kubernetes-engine/docs/concepts/using-containerd#known_issues
### What did you expect to happen?
https://cloud.google.com/kubernetes-engine/docs/concepts/using-containerd#known_issues
### How can we reproduce it (as minimally and precisely as possible)?
Do we have a plan... | https://cloud.google.com/kubernetes-engine/docs/concepts/using-containerd#known_issues | https://api.github.com/repos/kubernetes/kubernetes/issues/107611/comments | 5 | 2022-01-18T06:05:47Z | 2022-02-19T03:00:09Z | https://github.com/kubernetes/kubernetes/issues/107611 | 1,106,511,243 | 107,611 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Part1:
https://github.com/kubernetes/kubernetes/blob/8815a3119cc8bd82703f3fc5e5c715ec61dfc1ff/pkg/scheduler/framework/preemption/preemption.go#L429-L437
We want to find the minimum highest priority victims, however slice will cache the result.
For example, we have four nodes to pick up, their `v... | Problems in preempt `pickOneNodeForPreemption`? | https://api.github.com/repos/kubernetes/kubernetes/issues/107600/comments | 7 | 2022-01-17T10:14:18Z | 2022-01-18T02:34:41Z | https://github.com/kubernetes/kubernetes/issues/107600 | 1,105,654,537 | 107,600 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
statefulset custom ordinal index
### Why is this needed?
i want to deploy one statefulset on multi k8s cluster. but my app depend on headless service，thus i wonder about why statefulset don’t support custom pod oridnal index | Are there plans to support the statefulset custom ordinal index | https://api.github.com/repos/kubernetes/kubernetes/issues/107599/comments | 4 | 2022-01-17T09:50:43Z | 2022-01-25T13:41:55Z | https://github.com/kubernetes/kubernetes/issues/107599 | 1,105,627,896 | 107,599 |
[
"kubernetes",
"kubernetes"
] | ### NOTE: there is a new proposal: https://github.com/kubernetes/kubernetes/issues/123541
## Background
The idea of letting users customize the way Deployments (ReplicaSets) remove Pods when `replicas` are decreased has been floating around [since at least 2017](https://github.com/kubernetes/kubernetes/issues/455... | PROPOSAL configurable down-scaling behaviour in ReplicaSets & Deployments | https://api.github.com/repos/kubernetes/kubernetes/issues/107598/comments | 75 | 2022-01-17T09:10:51Z | 2024-11-22T15:02:15Z | https://github.com/kubernetes/kubernetes/issues/107598 | 1,105,566,190 | 107,598 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When trying to invoke coreos based node e2e jobs, the GCE VM gets launched but the ssh to that node doesn't work and eventually the tests fail.
The issue seems to be happening after merging this commit, https://github.com/kubernetes/kubernetes/commit/3ebd93cd02ca9e2ed7f1f6cff4d49b878f93a626
... | Unable to launch coreos based node e2e jobs locally | https://api.github.com/repos/kubernetes/kubernetes/issues/107592/comments | 4 | 2022-01-17T04:44:21Z | 2022-02-10T01:47:47Z | https://github.com/kubernetes/kubernetes/issues/107592 | 1,105,367,060 | 107,592 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I upgraded my kubernetes cluster which has an SMTP daemonset with hostPort.
After the upgrade the SMTP server become an open relay.
### What did you expect to happen?
for request received by the daemonset to keep showing the correct source IP.
### How can we reproduce it (as minimally and precis... | hostPort receiving SNATed packets after upgrading k8s | https://api.github.com/repos/kubernetes/kubernetes/issues/107591/comments | 45 | 2022-01-16T22:08:34Z | 2022-02-03T18:59:23Z | https://github.com/kubernetes/kubernetes/issues/107591 | 1,105,200,752 | 107,591 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
We came across a scenario where our services were not able to reach their respective endpoints because of an issue with the endpoint slices not being updated with the correct IP. This lead to kube-proxy having stale iptable rules
The controller-manager was up and running all the time and we had t... | controller-manager failed to start endpoint slice controller, leading to stale iptable rules | https://api.github.com/repos/kubernetes/kubernetes/issues/107583/comments | 27 | 2022-01-15T14:34:43Z | 2022-08-03T20:41:35Z | https://github.com/kubernetes/kubernetes/issues/107583 | 1,104,737,008 | 107,583 |
[
"kubernetes",
"kubernetes"
] | As revealed in #104842 and #107547, the Condition slices in FlowSchemaStatus and PriorityLevelConfigurationStatus are missing the `patchStrategy` and `patchMergeKey` annotations that tell strategic merge patch how to handle the slice.
This should be fixed when we make the next version of this API. See #107549 for e... | Add patch annotations to APF API types in next version | https://api.github.com/repos/kubernetes/kubernetes/issues/107574/comments | 12 | 2022-01-15T00:48:18Z | 2022-10-03T17:06:16Z | https://github.com/kubernetes/kubernetes/issues/107574 | 1,104,243,828 | 107,574 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
CEL validation improvements for the 1.24 Kubernetes release
KEP: https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/2876-crd-validation-expression-language
Our goal is to complete the bulk of the Beta requirements but release them as Alpha since m... | CEL validation for CRDs alpha changes for 1.24 | https://api.github.com/repos/kubernetes/kubernetes/issues/107573/comments | 6 | 2022-01-14T21:32:15Z | 2022-07-24T01:26:06Z | https://github.com/kubernetes/kubernetes/issues/107573 | 1,104,141,556 | 107,573 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Windows e2e tests flake due to the sandbox name being reserved for another container:
```
Jan 5 22:35:37.117: INFO: At 2022-01-05 22:27:52 +0000 UTC - event for ss2-1: {kubelet capz-conf-l8wfg} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = DeadlineExceeded desc = conte... | Windows - FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to reserve sandbox name | https://api.github.com/repos/kubernetes/kubernetes/issues/107561/comments | 21 | 2022-01-14T16:56:01Z | 2023-05-04T20:02:04Z | https://github.com/kubernetes/kubernetes/issues/107561 | 1,103,905,302 | 107,561 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
Public access to validateOnlyAddedTolerations() in package "k8s.io/apimachinery/pkg/api/validation"
See https://github.com/kubernetes/kubernetes/blob/885961cda8875cce192700fe6a32ff57ba706106/pkg/apis/core/validation/validation.go#L3327
### Why is this needed?
When implementin... | Public access to validateOnlyAddedTolerations() in package "k8s.io/apimachinery/pkg/api/validation" | https://api.github.com/repos/kubernetes/kubernetes/issues/107560/comments | 7 | 2022-01-14T16:45:57Z | 2022-06-27T17:39:39Z | https://github.com/kubernetes/kubernetes/issues/107560 | 1,103,892,428 | 107,560 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
For scheduled pods, add additional details on how the selected node was scored
For unscheduled pods, add details on which filters were actually executed on the pod.
The former should be easy to do now, the latter needs improvements to the framework: e.g. a new "Success" sta... | Add more details related to scheduler's decisions to logging and event messages | https://api.github.com/repos/kubernetes/kubernetes/issues/107556/comments | 20 | 2022-01-14T15:25:28Z | 2023-03-22T06:41:31Z | https://github.com/kubernetes/kubernetes/issues/107556 | 1,103,788,783 | 107,556 |
[
"kubernetes",
"kubernetes"
] | ## Background
With the addition of server side validation in 1.23, it is now possible for a `runtime#Decode()` call to successfully decode it’s data and return a non-nil error when there are strict decoding errors (e.g. duplicate/unknown fields).
This means that callers of `runtime#Decode()` can distinguish between... | Ensure NestedObjectDecoders do not short circuit on strict decoding errors | https://api.github.com/repos/kubernetes/kubernetes/issues/107545/comments | 2 | 2022-01-14T05:58:51Z | 2022-02-18T01:20:33Z | https://github.com/kubernetes/kubernetes/issues/107545 | 1,103,069,514 | 107,545 |
[
"kubernetes",
"kubernetes"
] | ## Background
When a server-side apply request specifies strict or warn field validation, it will [unmarshal the patch twice](https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/apiserver/pkg/endpoints/handlers/patch.go#L486-L504).
First in order to detect any fatal errors (not from strict va... | applyPatcher shouldn’t unmarshal twice for strict/warn field validation | https://api.github.com/repos/kubernetes/kubernetes/issues/107544/comments | 3 | 2022-01-14T05:54:09Z | 2022-01-20T17:49:35Z | https://github.com/kubernetes/kubernetes/issues/107544 | 1,103,064,079 | 107,544 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
one statefulset pod "statefulsettestpod-0" is running on node2, the pod toleration is
`
tolerations:
- effect: NoExecute
key: node.kubernetes.io/not-ready
operator: Exists
tolerationSeconds: 30
- effect: NoExecute
key: node.kubernetes.io/unreachable
operator:... | taint node,controller manager can not delete pod | https://api.github.com/repos/kubernetes/kubernetes/issues/107543/comments | 22 | 2022-01-14T03:06:55Z | 2024-07-14T16:28:36Z | https://github.com/kubernetes/kubernetes/issues/107543 | 1,102,841,342 | 107,543 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
Add a `healthz` subresource to CRD. User can add this subresource to their CRD by adding a marker like `//+kubebuilder:subresource:healthz,...`, kubebuilder will generate the healthcheck code, and user can query the healthz field to learn the real-time status of the CR.
### Why is... | Add healthz subresource in CRD | https://api.github.com/repos/kubernetes/kubernetes/issues/107539/comments | 9 | 2022-01-13T20:56:18Z | 2025-02-11T03:09:44Z | https://github.com/kubernetes/kubernetes/issues/107539 | 1,102,361,143 | 107,539 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
The TestApplyResetFields test in `test/integration/apiserver/apply` fails when applied to FlowSchema (that is, when the exclusion for that type is removed).
### What did you expect to happen?
I expected that test to pass for FlowSchema objects. Even though there is also the APF config-producing c... | Bad concurrent strategic merge patch and server side apply on different slice members | https://api.github.com/repos/kubernetes/kubernetes/issues/107538/comments | 5 | 2022-01-13T19:37:12Z | 2022-01-20T17:49:23Z | https://github.com/kubernetes/kubernetes/issues/107538 | 1,102,236,553 | 107,538 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I work for AWS EKS and we run prow conformance jobs before qualifying the kubernetes versions and also as part of regression tests. Today we run the prow conformance in a couple different environments(some of which don't have internet access). In order for the prow conformance tests to run, we need ... | Modify test/utils/image/manifest.go to handle the images based on a yaml file | https://api.github.com/repos/kubernetes/kubernetes/issues/107537/comments | 6 | 2022-01-13T18:22:39Z | 2022-01-21T06:34:39Z | https://github.com/kubernetes/kubernetes/issues/107537 | 1,102,134,632 | 107,537 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
TestApplyResetFields fails on FlowSchema if that is not skipped. The failure is in the last operation, an update of status that is expected to get a conflict but does not.
### What did you expect to happen?
I expected TestApplyResetFields to succeed when applied to FlowSchema.
### How can we rep... | TestApplyResetFields insists on conflict that may not happen | https://api.github.com/repos/kubernetes/kubernetes/issues/107535/comments | 3 | 2022-01-13T17:42:11Z | 2022-01-14T19:13:22Z | https://github.com/kubernetes/kubernetes/issues/107535 | 1,102,090,796 | 107,535 |
[
"kubernetes",
"kubernetes"
] | While looking at `k/apiserver/pkg/storage` I noticed a few things.
1. The parameter named `ptrToType` at https://github.com/kubernetes/apiserver/blob/56ff18e72e23862ac6fd0c6ddd57238be8324ba3/pkg/storage/interfaces.go#L237 has a misleading name. The value of this parameter is not a pointer to a type; rather, it is ... | Outdated/confusing stuff in apiserver storage | https://api.github.com/repos/kubernetes/kubernetes/issues/107534/comments | 8 | 2022-01-13T16:23:22Z | 2022-05-04T08:28:49Z | https://github.com/kubernetes/kubernetes/issues/107534 | 1,102,001,833 | 107,534 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are flaking?
* gci-gce-ingress
### Which tests are flaking?
* ci-kubernetes-e2e-gci-gce-ingress.Overall
* kubetest.diffResources
### Since when has it been flaking?
History goes back to 2021-12-30
### Testgrid link
https://testgrid.k8s.io/sig-release-master-blocking#gci-gce-ingress
### Reason fo... | [Flaky test] gci-gce-ingress, diffResource | https://api.github.com/repos/kubernetes/kubernetes/issues/107530/comments | 17 | 2022-01-13T11:58:27Z | 2022-11-04T01:54:15Z | https://github.com/kubernetes/kubernetes/issues/107530 | 1,101,612,214 | 107,530 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
https://github.com/kubernetes/kubernetes/issues/82958
### What did you expect to happen?
https://github.com/kubernetes/kubernetes/issues/82958
### How can we reproduce it (as minimally and precisely as possible)?
https://github.com/kubernetes/kubernetes/issues/82958
### Anything else we need ... | No one can solve this bug? | https://api.github.com/repos/kubernetes/kubernetes/issues/107524/comments | 4 | 2022-01-13T08:06:50Z | 2022-01-13T09:16:24Z | https://github.com/kubernetes/kubernetes/issues/107524 | 1,101,346,053 | 107,524 |
[
"kubernetes",
"kubernetes"
] | https://github.com/kubernetes/kubernetes/blob/68e64ba52eb8518894ee62ef4240c9733f8c4346/cluster/images/etcd-version-monitor/etcd-version-monitor.go#L253
miss return ？ | miss to return when listening channel closed | https://api.github.com/repos/kubernetes/kubernetes/issues/107520/comments | 11 | 2022-01-13T07:23:17Z | 2022-02-04T15:03:50Z | https://github.com/kubernetes/kubernetes/issues/107520 | 1,101,308,320 | 107,520 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
We are observing below scenarios with K8s v1.20.6:
We have a Custom Metrics Prometheus Adapter responsible for registering a custom metric with API Server.
HPA makes scaling decisions by querying that custom metric from API Server.
1. When one replica of Deployment is up, and we make an edit ... | HPA scales up deployment to max replicas during rolling upgrade without any load | https://api.github.com/repos/kubernetes/kubernetes/issues/107513/comments | 6 | 2022-01-13T04:46:38Z | 2022-06-17T13:46:58Z | https://github.com/kubernetes/kubernetes/issues/107513 | 1,101,201,479 | 107,513 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
We want to know what state the current container/pod is in and what needs to be done before it becomes Running.
It is better to provide a clear list,similar to the following:
{
"startUpProbe": {
"status": "success",
"startAt": "xxxx",
"finishAt": "xxxx"
},
... | Is it possible to get the lifecycle details of a container or pod? | https://api.github.com/repos/kubernetes/kubernetes/issues/107511/comments | 6 | 2022-01-13T03:38:44Z | 2022-06-12T13:51:01Z | https://github.com/kubernetes/kubernetes/issues/107511 | 1,101,145,268 | 107,511 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
xref: https://github.com/kubernetes/kubernetes/pull/107361#issuecomment-1006987130
Graceful node shutdown test uses `dbus-send` to invoke dbus - https://github.com/kubernetes/kubernetes/blob/3516e76f3da5778400ee06fc2d628fa4560a6b43/test/e2e_node/node_shutdown_linux_test.go#L444
As per https:... | graceful node shutdown test - improve dbus command to support other distros | https://api.github.com/repos/kubernetes/kubernetes/issues/107505/comments | 12 | 2022-01-12T20:48:15Z | 2022-05-04T00:18:39Z | https://github.com/kubernetes/kubernetes/issues/107505 | 1,100,775,662 | 107,505 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
Cache the actual operation of a requirement (for example, as a function) instead of storing it as a string
https://github.com/kubernetes/kubernetes/blob/bf8c918e0be340637e63520eb3b58df493a230f9/vendor/sigs.k8s.io/kustomize/kyaml/yaml/internal/k8sgen/pkg/labels/selector.go#L145:6... | Improve performance of node selector matcher | https://api.github.com/repos/kubernetes/kubernetes/issues/107504/comments | 11 | 2022-01-12T19:11:32Z | 2022-07-10T16:00:17Z | https://github.com/kubernetes/kubernetes/issues/107504 | 1,100,698,313 | 107,504 |
[
"kubernetes",
"kubernetes"
] | Changes to some parts of Kubernetes code end up being published within https://kubernetes.io/docs/
Most of that is drawn directly from [k/website](https://github.com/kubernetes/website) but there are also pages in that repo that are generated, with no text changes, from the API docs.
**Feature request:**
Add a... | Docs review for changes that affect public website | https://api.github.com/repos/kubernetes/kubernetes/issues/107500/comments | 11 | 2022-01-12T16:49:26Z | 2022-06-12T11:50:02Z | https://github.com/kubernetes/kubernetes/issues/107500 | 1,100,565,537 | 107,500 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
client-go behavior changes depending on version of github.com/imdario/mergo used. Kubernetes pins to `v0.3.5`. Many other projects in the ecosystem, including Kubernetes projects like sigs.k8s.io/controller-runtime, use newer versions like `0.3.12`.
If a consumer of client-go is not careful, they... | remove use of github.com/imdario/mergo (currently use is incompatible with latest mergo version, latest mergo version introduces bugs) | https://api.github.com/repos/kubernetes/kubernetes/issues/107499/comments | 26 | 2022-01-12T16:28:01Z | 2024-09-28T06:40:03Z | https://github.com/kubernetes/kubernetes/issues/107499 | 1,100,542,382 | 107,499 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When deploying a batch/v1beta1 CronJob to our 1.21 cluster I noticed `Warning: batch/v1beta1 CronJob is deprecated in v1.21+, unavailable in v1.25+; use batch/v1 CronJob`. This was a surprise, as we use `kubepug` to precheck our deployments for deprecated resources.
### What did you expect to happe... | Kubernetes' OpenAPI files do not mark batch/v1beta1 as deprecated | https://api.github.com/repos/kubernetes/kubernetes/issues/107498/comments | 17 | 2022-01-12T16:23:35Z | 2022-10-11T09:09:18Z | https://github.com/kubernetes/kubernetes/issues/107498 | 1,100,537,569 | 107,498 |
[
"kubernetes",
"kubernetes"
] | I was trying to upgrade the kubernetes version of our cluster from 1.19.7 to 1.22 and some of the worker nodes failed in updating so I restarted the cluster. After restarting the upgrade was successful but Cert-manager-webhook and Cert-manager-cainjector pods went down along with the ingress pods. i.e. they are either ... | Cert-manager and Ingress pods in Crash loop back off (AKS) | https://api.github.com/repos/kubernetes/kubernetes/issues/107496/comments | 4 | 2022-01-12T15:47:26Z | 2022-01-12T18:19:34Z | https://github.com/kubernetes/kubernetes/issues/107496 | 1,100,496,529 | 107,496 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I was trying to used a secret which I have created in another namespace but I got error when I try to curl the host
```
apiVersion: networking.k8s.io/v1beta1
kind: Ingress
metadata:
annotations:
kubernetes.io/ingress.class: istio
name: sample-ingress
namespace: test-ns
spec:
... | Kubernetes ingress not able to reference a secret that is in another different namespace | https://api.github.com/repos/kubernetes/kubernetes/issues/107495/comments | 4 | 2022-01-12T13:50:11Z | 2022-01-12T14:14:39Z | https://github.com/kubernetes/kubernetes/issues/107495 | 1,100,366,412 | 107,495 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Kubernetes node was deleted from the managed instance group from google cloud console. kubectl get nodes showed node in NotReady state.
But pod remained in running state.
Pods describe output after 17mins of node deletion
<details>
```console
$ kubectl describe pod -n models-dev mlaccl-16... | Pods are in RUNNING state hours after Node is deleted from google cloud | https://api.github.com/repos/kubernetes/kubernetes/issues/107493/comments | 9 | 2022-01-12T12:36:26Z | 2022-01-19T18:40:45Z | https://github.com/kubernetes/kubernetes/issues/107493 | 1,100,290,879 | 107,493 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Hello! I've got a simple Kubernetes cluster (version 1.23.1) with 1 - master node and 2 - worker nodes. Everything worked fine until I've accidentally rebooted my host computer with all Virtual machines. After VMs were started again I see that kubelet starts running as before, but commands such as... | Kubernetes API Server cannot be started after improper reboot | https://api.github.com/repos/kubernetes/kubernetes/issues/107491/comments | 21 | 2022-01-12T11:12:15Z | 2024-08-22T20:26:50Z | https://github.com/kubernetes/kubernetes/issues/107491 | 1,100,210,098 | 107,491 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
![image](https://user-images.githubusercontent.com/19605510/149117262-21... | kubelet Failed | https://api.github.com/repos/kubernetes/kubernetes/issues/107489/comments | 5 | 2022-01-12T09:58:54Z | 2022-01-12T13:38:49Z | https://github.com/kubernetes/kubernetes/issues/107489 | 1,100,131,603 | 107,489 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I'm trying CSI RBD migration feature in 1.23.
Found if set --feature-gates=CSIMigrationRBD=true to kube-controller-manager or CSIMigrationRBD: true to kubelet config.
Error "unrecognized feature gate: CSIMigrationRBD" showed up.
Need to set to --feature-gates=csiMigrationRBD=true.
It is ... | The feature gate csiMigrationRBD should be CSIMigrationRBD | https://api.github.com/repos/kubernetes/kubernetes/issues/107488/comments | 12 | 2022-01-12T09:32:15Z | 2024-03-27T08:59:23Z | https://github.com/kubernetes/kubernetes/issues/107488 | 1,100,101,227 | 107,488 |
[
"kubernetes",
"kubernetes"
] | https://github.com/kubernetes/kubernetes/blob/0a8cc161f69270840045fe8f079620b7a4ab1324/pkg/controller/statefulset/stateful_set_control.go#L425
Should it change to ```isStale && monotonic``` ?
```
if isStale, err := ssc.podControl.PodClaimIsStale(set, replicas[i]); err != nil {
return &status, err
} el... | persistentVolumeClaimRetentionPolicy blocks podManagementPolicy: Parallel | https://api.github.com/repos/kubernetes/kubernetes/issues/107487/comments | 9 | 2022-01-12T08:04:41Z | 2022-10-27T13:08:03Z | https://github.com/kubernetes/kubernetes/issues/107487 | 1,100,003,010 | 107,487 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
An error occurs in `managePodLoop` after the static pod has being deleted, then `syncCh` is triggerred and error event will be dequeued from work queue but pod manage has no such pod because `HandlePodRemoves` has been called.
`No such container error` is a common error type from `p.podCache.Ge... | Kubelet cannot start static pod when move in manifest file after removing manifest file for a while | https://api.github.com/repos/kubernetes/kubernetes/issues/107483/comments | 21 | 2022-01-12T02:44:01Z | 2022-04-27T16:25:01Z | https://github.com/kubernetes/kubernetes/issues/107483 | 1,099,814,229 | 107,483 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Hello guys,
I am using EKS cluster, Kubernetes: `1.18`, Platform: `eks.8`, kube-proxy version is `v1.18.8`.
I saw my `kube-proxy` log reported the warning message several times at different timestamps:
```
{"log":"W0105 11:53:24.659392 1 iptables.go:562] Could not check for iptables ... | kube-proxy reported Could not check for iptables canary mangle/KUBE-PROXY-CANARY: exit status 4 | https://api.github.com/repos/kubernetes/kubernetes/issues/107482/comments | 8 | 2022-01-12T02:20:42Z | 2022-04-28T17:14:49Z | https://github.com/kubernetes/kubernetes/issues/107482 | 1,099,802,948 | 107,482 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I have some dynamically provisioned storage that uses WFFC like the included csi-hostpath. I have a multi node cluster. When I attempt to do a csi clone using that storage, the scheduler does not take the topology of the dataSource into account when scheduling the pod. Example:
- I have 3 nodes.
... | Take dataSource topology into account when scheduling a pod using unbound WFFC storage | https://api.github.com/repos/kubernetes/kubernetes/issues/107479/comments | 12 | 2022-01-11T22:03:35Z | 2024-01-19T19:43:32Z | https://github.com/kubernetes/kubernetes/issues/107479 | 1,099,657,846 | 107,479 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I've tested with k8s v1.21 on Amazon EKS and k8s v1.22, v1.21, and v1.20 in Minikube
I installed a pod containing a simple http server having some `/alive` endpoint. In the pod spec, specify a liveness probe that uses this endpoint.
No liveness probe failure while pod is running, as expected.... | k8s liveness probe fails during pod termination | https://api.github.com/repos/kubernetes/kubernetes/issues/107473/comments | 26 | 2022-01-11T18:47:01Z | 2024-11-22T03:54:13Z | https://github.com/kubernetes/kubernetes/issues/107473 | 1,099,507,504 | 107,473 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
master informing [gce-ubuntu-master-default](https://testgrid.k8s.io/sig-release-master-informing#gce-ubuntu-master-default)
master blocking [gce-device-plugin-gpu-master](https://testgrid.k8s.io/sig-release-master-blocking#gce-device-plugin-gpu-master)
### Which tests are failing?
* ci-... | [Failing test] gce-ubuntu-master-default, kubetest.Up | https://api.github.com/repos/kubernetes/kubernetes/issues/107469/comments | 12 | 2022-01-11T12:22:30Z | 2022-01-18T06:38:57Z | https://github.com/kubernetes/kubernetes/issues/107469 | 1,099,087,007 | 107,469 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Pod Topology Spread (PTS) takes into account unschedulable tainted nodes. It seems that tainted node affects calculation of the global minimum for maxSkew parameter. This makes it impossible to use PTS for some situations.
Specifically, when we have maxSkew: 1, then it is not possible to spawn 2 or... | Pod Topology Spread takes into account unschedulable tainted nodes | https://api.github.com/repos/kubernetes/kubernetes/issues/107464/comments | 10 | 2022-01-11T04:35:34Z | 2022-08-10T04:04:11Z | https://github.com/kubernetes/kubernetes/issues/107464 | 1,098,642,877 | 107,464 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I'm doing some load testing with K8s 1.22.4. In particular, restarting the API server with thousands of nodes. The kubelets to re-list to restart their watches, and sometimes the API server panics and crashes. I captured the error and it was:
```
fatal error: concurrent map iteration ... | kube-apiserver 1.22.4 panics with fatal error: concurrent map iteration and map write | https://api.github.com/repos/kubernetes/kubernetes/issues/107463/comments | 13 | 2022-01-11T03:20:05Z | 2022-01-30T01:43:43Z | https://github.com/kubernetes/kubernetes/issues/107463 | 1,098,606,131 | 107,463 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Under an extreme rare case, one of our ETCD cluster restored from backup data, and the APIServers are rotated on new instances with new IPs as well.
The endpoints/endpointSlices for the "default/kubernetes" service is updated to contain new IPs of the APIServers, but the kube-proxy didn't upda... | informer miss events if resourceVersion rewinded due to ETCD recover from stale backup. | https://api.github.com/repos/kubernetes/kubernetes/issues/107457/comments | 7 | 2022-01-10T19:57:02Z | 2022-06-11T09:41:01Z | https://github.com/kubernetes/kubernetes/issues/107457 | 1,098,311,384 | 107,457 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I am trying to summarize the migration journey to using `Lease` based leader election.
Hypothetically, let's assume a customer is currently on version `x` and they use `configmaps` based leader election, the migration looks like this:
- version `x+1`: use `configmapsleases` for leader election,... | leader election migration steps | https://api.github.com/repos/kubernetes/kubernetes/issues/107454/comments | 13 | 2022-01-10T18:14:35Z | 2022-08-24T16:11:09Z | https://github.com/kubernetes/kubernetes/issues/107454 | 1,098,220,860 | 107,454 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Rotated container logs space usage doesnt seem to be counted towards the epehemral storage limit. Always only current log file stats are taken into account.
### What did you expect to happen?
rotated log files usage also should be counted towards ephemeral-storage usage
### How can we reproduce... | Rotated container log files size not counted towards ephemeral-storage's limit on CRI-O | https://api.github.com/repos/kubernetes/kubernetes/issues/107447/comments | 20 | 2022-01-10T10:56:36Z | 2022-05-12T15:09:14Z | https://github.com/kubernetes/kubernetes/issues/107447 | 1,097,741,320 | 107,447 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
My cluster is behind a corporate proxy. Using [kube-prometheus-stack](https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stack), the apiserver raises an error when calling the mutating/validating admission webhook with a POST on `https://kube-prometheus-stack-oper... | Use full URL (with cluster domain name) in admission webhook | https://api.github.com/repos/kubernetes/kubernetes/issues/107446/comments | 21 | 2022-01-10T10:37:30Z | 2024-09-12T23:13:31Z | https://github.com/kubernetes/kubernetes/issues/107446 | 1,097,717,233 | 107,446 |
[
"kubernetes",
"kubernetes"
] | There is a non-trivial diff between [`staging/src/k8s.io/api/core/v1/types.go`](https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/api/core/v1/types.go) and [`pkg/apis/core/types.go`](https://github.com/kubernetes/kubernetes/blob/master/pkg/apis/core/types.go).
1. Optional vs. non-optional int:... | Non-trivial diff between staging and internal types.go | https://api.github.com/repos/kubernetes/kubernetes/issues/107442/comments | 7 | 2022-01-10T05:28:10Z | 2022-03-03T19:25:23Z | https://github.com/kubernetes/kubernetes/issues/107442 | 1,097,475,295 | 107,442 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I used to use 1.171 standalone Kubelet mode without an API server for my cluster. Because I’m not using API server, I can only get container events from Kubelet logs.
But after I upgrade Kubelet to 1.20.1, I found that the log format is changed and Kubelet log is no longer logging container info(“F... | Standalone Kubelet is no longer logging container info(“FieldPath” field) for event logs | https://api.github.com/repos/kubernetes/kubernetes/issues/107440/comments | 11 | 2022-01-10T03:27:45Z | 2022-02-08T15:12:55Z | https://github.com/kubernetes/kubernetes/issues/107440 | 1,097,419,352 | 107,440 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Requests that are proxied by the APIServer to a custom APIService (aggregation) don't generate the `X-Forwarded-Host` header correctly. Each request will have **both** `Host` and `X-Forwarded-Host` set to ClusterIP IP address of their service. `X-Forwarded-Host` should be set to the original `Hos... | Requests proxied from API Server to APIService obfuscate original request hostname | https://api.github.com/repos/kubernetes/kubernetes/issues/107435/comments | 16 | 2022-01-09T23:44:08Z | 2024-06-13T16:43:58Z | https://github.com/kubernetes/kubernetes/issues/107435 | 1,097,333,521 | 107,435 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Godoc says that Time should be empty on mangedFields entry created by "Apply" operation, but kubernetes populates time on apply.
### What did you expect to happen?
Godoc consistent with kubernetes behaviour
### How can we reproduce it (as minimally and precisely as possible)?
Godoc:
https... | Kubernetes behaviour differs from metav1 ManagedFieldsEntry.Time godoc comment | https://api.github.com/repos/kubernetes/kubernetes/issues/107434/comments | 4 | 2022-01-09T23:14:51Z | 2022-02-11T07:32:03Z | https://github.com/kubernetes/kubernetes/issues/107434 | 1,097,327,799 | 107,434 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
get po
```
[root@192 ~]# kubectl get po --all-namespaces
NAMESPACE NAME READY STATUS RESTARTS AGE
default test-web-api 0/1 ImagePullBackOff 0 3h57m
kube-system calico-kube-cont... | network plugin is not ready: cni config uninitialized | https://api.github.com/repos/kubernetes/kubernetes/issues/107430/comments | 6 | 2022-01-09T11:00:43Z | 2022-01-09T14:45:46Z | https://github.com/kubernetes/kubernetes/issues/107430 | 1,097,165,626 | 107,430 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Create pod faild because of calico CrashLoopBackOff
```
[root@192 check]# kubectl get pods --all-namespaces
NAMESPACE NAME READY STATUS RESTARTS AGE
default test-web-api 0/1 ContainerCreating 0... | Connection to the datastore is unauthorized error=connection is unauthorized: Unauthorized | https://api.github.com/repos/kubernetes/kubernetes/issues/107428/comments | 7 | 2022-01-09T08:20:12Z | 2022-01-09T10:12:11Z | https://github.com/kubernetes/kubernetes/issues/107428 | 1,097,135,418 | 107,428 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are flaking?
https://testgrid.k8s.io/sig-node-containerd#cos-cgroupv2-containerd-node-e2e
https://testgrid.k8s.io/sig-node-containerd#cos-cgroupv2-containerd-node-e2e-serial
### Which tests are flaking?
cos-cgroupv2-containerd-node-e2e and cos-cgroupv2-containerd-node-e2e-serial jobs
### Since whe... | cos-cgroupv2-containerd-node-e2e and cos-cgroupv2-containerd-node-e2e-serial jobs are failing | https://api.github.com/repos/kubernetes/kubernetes/issues/107425/comments | 5 | 2022-01-08T23:59:48Z | 2022-01-10T23:13:07Z | https://github.com/kubernetes/kubernetes/issues/107425 | 1,097,063,884 | 107,425 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
**os: centos 7.9
kernel: 3.10.0-1160.el7.x86_64
kubernetes version: 1.23.1**
**master server**
```
[root@192 ~]# kubectl --kubeconfig=/etc/kubernetes/kubeconfig get nodes
Unable to connect to the server: net/http: TLS handshake timeout
```
**The cluster is**
mastera 192.168.1.9
mas... | Unable to connect to the server: net/http: TLS handshake timeout | https://api.github.com/repos/kubernetes/kubernetes/issues/107418/comments | 14 | 2022-01-08T03:34:07Z | 2025-03-03T15:47:16Z | https://github.com/kubernetes/kubernetes/issues/107418 | 1,096,822,099 | 107,418 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When resource is created using `POST` call it then can't be updated with SSA `PATCH` call, even if field manager name for both operations is the same
### What did you expect to happen?
`PATCH` succeeds with no conflicts
### How can we reproduce it (as minimally and precisely as possible)?
Creat... | Server side apply conflicts with itself | https://api.github.com/repos/kubernetes/kubernetes/issues/107417/comments | 22 | 2022-01-08T02:11:58Z | 2024-09-30T09:42:20Z | https://github.com/kubernetes/kubernetes/issues/107417 | 1,096,807,896 | 107,417 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
A deployment was inadvertently created with a malformed label in `requiredAffinityTerms` which appears to have caused the kube-scheduler to panic and crash.
Error from kube-scheduler pods:
```
E0107 05:56:44.099432 1 scheduling_queue.go:547] Error getting label selectors for pod: REDACTE... | kube-scheduler panics on malformed label | https://api.github.com/repos/kubernetes/kubernetes/issues/107415/comments | 26 | 2022-01-07T21:13:46Z | 2022-08-22T15:11:00Z | https://github.com/kubernetes/kubernetes/issues/107415 | 1,096,673,683 | 107,415 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are flaking?
pull-kubernetes-unit
### Which tests are flaking?
Test_Run_OneVolumeDetachFailNodeWithReadWriteOnce
### Since when has it been flaking?
Jan 7th, 2022
### Testgrid link
https://testgrid.k8s.io/presubmits-kubernetes-blocking#pull-kubernetes-unit&include-filter-by-regex=Test_Run_OneVolu... | Flaky unit test: Test_Run_OneVolumeDetachFailNodeWithReadWriteOnce | https://api.github.com/repos/kubernetes/kubernetes/issues/107414/comments | 21 | 2022-01-07T18:49:06Z | 2023-04-12T01:19:10Z | https://github.com/kubernetes/kubernetes/issues/107414 | 1,096,578,035 | 107,414 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
kubelet-gce-e2e-swap-ubuntu ([config source](https://github.com/kubernetes/test-infra/blob/eaeb5fa7980680e5db6cb6e80bae7dcd63663694/config/jobs/kubernetes/sig-node/containerd.yaml#L1276))
### Which tests are failing?
- E2eNode Suite.[sig-node] Summary API [NodeConformance] when querying /... | Job kubelet-gce-e2e-swap-ubuntu failing | https://api.github.com/repos/kubernetes/kubernetes/issues/107412/comments | 15 | 2022-01-07T18:06:30Z | 2022-10-29T21:33:06Z | https://github.com/kubernetes/kubernetes/issues/107412 | 1,096,546,819 | 107,412 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
cronjob controller may send more than one status update to the api-server for the same cronjob in the same cycle. Ideally the controller should be sending one per cronjob per cycle.
This was evident from the bug in https://github.com/kubernetes/kubernetes/pull/104799, which woul... | Optimize cronjob controller status updates | https://api.github.com/repos/kubernetes/kubernetes/issues/107411/comments | 5 | 2022-01-07T17:55:17Z | 2022-02-01T08:14:18Z | https://github.com/kubernetes/kubernetes/issues/107411 | 1,096,538,313 | 107,411 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Right now we hardcode an ip in https://github.com/kubernetes/kubernetes/blob/master/test/e2e/network/service.go#L1198
```
serviceName := "externalip-test"
ns := f.Namespace.Name
externalIP := "203.0.113.250"
if framework.TestContext.ClusterIsIPv6() {
externalIP = "2001:DB8::cb00:71... | hardcoded IP in the e2es , should we make it dynamic? | https://api.github.com/repos/kubernetes/kubernetes/issues/107409/comments | 8 | 2022-01-07T15:52:14Z | 2022-01-07T21:15:29Z | https://github.com/kubernetes/kubernetes/issues/107409 | 1,096,438,944 | 107,409 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I have these error
[kubelet-start] Waiting for the kubelet to perform the TLS Bootstrap...
[kubelet-check] Initial timeout of 40s passed.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed... | When I join cluster | https://api.github.com/repos/kubernetes/kubernetes/issues/107407/comments | 4 | 2022-01-07T13:35:49Z | 2022-01-07T19:34:10Z | https://github.com/kubernetes/kubernetes/issues/107407 | 1,096,323,539 | 107,407 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
The fix from https://github.com/kubernetes/kubernetes/pull/102083 seems to be incomplete/wrong. When disk is not found, the GET call for the disk fails with `404 Not Found` and it is not even reaching the DELETE call.
### What did you expect to happen?
PV to be deleted (its `kubernetes.io/pv-prote... | azure: PV hangs forever in failed deletion because the underlying disk is not found | https://api.github.com/repos/kubernetes/kubernetes/issues/107405/comments | 5 | 2022-01-07T11:07:36Z | 2022-01-15T02:21:41Z | https://github.com/kubernetes/kubernetes/issues/107405 | 1,096,218,088 | 107,405 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
[root@node01 amax]# kubeadm join 10.16.0.78:6443 --token kydz6y.ex2t63no93qm8bvt --discovery-token-ca-cert-hash sha256:5a811dc96bda254a2bd5f7fcd51997252caaa9cd5306600909a3c75b41de9fdc
[preflight] Running pre-flight checks
[WARNING IsDockerSystemdCheck]: detected "cgroupfs" as the Docke... | When I join The cluster | https://api.github.com/repos/kubernetes/kubernetes/issues/107404/comments | 5 | 2022-01-07T09:33:36Z | 2022-01-07T19:33:59Z | https://github.com/kubernetes/kubernetes/issues/107404 | 1,096,142,260 | 107,404 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
when I change /etc/docker/demon
{
"exec-opts":["native.cgroupdriver=systemd"]
}
I describe the error pod pod/kube-proxy-zq5dk
Events:
Type Reason Age From Message
---- ------ ---- ---- ... | pod creation error: cgroup-parent for systemd cgroup should be a valid slice named as "xxx.slice" | https://api.github.com/repos/kubernetes/kubernetes/issues/107403/comments | 8 | 2022-01-07T08:35:26Z | 2022-01-07T19:33:35Z | https://github.com/kubernetes/kubernetes/issues/107403 | 1,096,100,757 | 107,403 |
[
"kubernetes",
"kubernetes"
] | I create a deployment or StatefulSet with 3 replicates.i wangt it create replicates one by one,not at the same time.does it support set create rate or create freeze time? | how can i set replicated Pods create rate or freeze time?not HPA | https://api.github.com/repos/kubernetes/kubernetes/issues/107401/comments | 7 | 2022-01-07T05:07:32Z | 2022-06-09T04:21:10Z | https://github.com/kubernetes/kubernetes/issues/107401 | 1,095,989,199 | 107,401 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
On `Kube-proxy 1.22` on `winuserspace` with a `NodePort` service I have 2 pods behind the service with `sessionAffinity: clientIP ` and `timeoutSeconds` set.
When doing a request from a source to the NodePort multiple times, the sessionAffinity works as expected. And one of the pod receives al... | sessionAffinity TTL expiration not working for Winuserspace | https://api.github.com/repos/kubernetes/kubernetes/issues/107398/comments | 5 | 2022-01-07T01:16:04Z | 2022-01-07T22:07:15Z | https://github.com/kubernetes/kubernetes/issues/107398 | 1,095,884,831 | 107,398 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
If any t.Fatalf() in `func expectUpdate` ([line 363](https://github.com/kubernetes/kubernetes/blob/master/pkg/kubelet/config/file_linux_test.go#L363) of file pkg/kubelet/config/file_linux_test.go) is triggered, the following send operation on channel ch (or [channel updates](https://github.com/kuber... | goroutine leaks in TestWatchFileChanged() | https://api.github.com/repos/kubernetes/kubernetes/issues/107396/comments | 11 | 2022-01-07T00:18:07Z | 2022-06-25T19:15:36Z | https://github.com/kubernetes/kubernetes/issues/107396 | 1,095,837,984 | 107,396 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are flaking?
https://testgrid.k8s.io/sig-windows-master-release#capz-windows-containerd-master
### Which tests are flaking?
it is random but I did some analysis here: https://github.com/kubernetes-sigs/cluster-api-provider-azure/pull/1932#issuecomment-1006759077
Once I disabled these tests I've see... | Garbage collector should orphan pods created by rc if delete options say so on Windows causes flakiness | https://api.github.com/repos/kubernetes/kubernetes/issues/107394/comments | 11 | 2022-01-06T19:15:52Z | 2022-12-23T20:39:23Z | https://github.com/kubernetes/kubernetes/issues/107394 | 1,095,617,025 | 107,394 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I am encountering a very weird issue. Every time when I try to create a new namespace using ```kubectl create namespace xx``` then when I try to delete it, the operation becomes stuck:
```
[root@k8s-master-node ~]# kubectl delete namespace xx2
namespace "xx2" deleted
```
If I press CTRL+C the... | Kubectl deleting of a namespace is always stuck | https://api.github.com/repos/kubernetes/kubernetes/issues/107388/comments | 11 | 2022-01-06T14:57:25Z | 2022-01-06T19:42:56Z | https://github.com/kubernetes/kubernetes/issues/107388 | 1,095,398,576 | 107,388 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Job didn't delete pods when I changed the activeDeadlineSeconds
```
➜ job cat nc-job.yaml
apiVersion: batch/v1
kind: Job
metadata:
name: nc-job
spec:
activeDeadlineSeconds: 30
ttlSecondsAfterFinished: 0
template:
spec:
automountServiceAccountToken: false
co... | Job didn't delete pods when I changed the activeDeadlineSeconds | https://api.github.com/repos/kubernetes/kubernetes/issues/107387/comments | 10 | 2022-01-06T14:09:15Z | 2022-01-07T18:47:31Z | https://github.com/kubernetes/kubernetes/issues/107387 | 1,095,355,417 | 107,387 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
pull-kubernetes-e2e-gce-iscsi-serial
pull-kubernetes-e2e-gce-iscsi
Error text:
```
W0106 06:54:08.830] scp: /var/log/cluster-autoscaler.log*: No such file or directory
W0106 06:54:08.830] scp: /var/log/kube-addon-manager.log*: No such file or directory
W0106 06:54:08.908] scp: /va... | [Failing test] pull-kubernetes-e2e-gce-iscsi-serial and pull-kubernetes-e2e-gce-iscsi are failing | https://api.github.com/repos/kubernetes/kubernetes/issues/107377/comments | 11 | 2022-01-06T09:46:31Z | 2022-05-19T16:08:23Z | https://github.com/kubernetes/kubernetes/issues/107377 | 1,095,142,655 | 107,377 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
If we `add` -> `delete` -> `readd` same key object, then there will be duplicate keys in `queue`.
Here is an sample example\
in the beginning
>`queue`: key1, key2, ..., key100 \
`items`:\
key1 -> obj1\
key2 -> obj2\
...\
key100 -> obj100
now, obj2 was deleted, then (note: current im... | FIFO bug: duplicate keys is shown in queue | https://api.github.com/repos/kubernetes/kubernetes/issues/107376/comments | 6 | 2022-01-06T09:33:57Z | 2022-06-05T22:59:18Z | https://github.com/kubernetes/kubernetes/issues/107376 | 1,095,132,701 | 107,376 |
[
"kubernetes",
"kubernetes"
] | ### Failure cluster [195aab5c63fe2bf267c8](https://go.k8s.io/triage#195aab5c63fe2bf267c8)
##### Error text:
```
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
Jan 4 07:05:01.070: Pod didn't start within time out period
Unexpected error:
<*errors.er... | [sig-network] Proxy version v1 A set of valid responses are returned for both pod and service ProxyWithPath [Conformance] | https://api.github.com/repos/kubernetes/kubernetes/issues/107374/comments | 12 | 2022-01-06T08:58:54Z | 2022-08-30T11:28:13Z | https://github.com/kubernetes/kubernetes/issues/107374 | 1,095,105,001 | 107,374 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Similar to #107191, goroutines associated with QueueBroadcaster and EventWatcher are leaked in the following tests:
1. `TestAllocateOrOccupyCIDRSuccess()` at [line 321](https://github.com/kubernetes/kubernetes/blob/master/pkg/controller/nodeipam/ipam/range_allocator_test.go#L321) of pkg/contro... | goroutine leaks in several tests | https://api.github.com/repos/kubernetes/kubernetes/issues/107372/comments | 11 | 2022-01-06T08:46:56Z | 2022-10-22T01:19:33Z | https://github.com/kubernetes/kubernetes/issues/107372 | 1,095,096,575 | 107,372 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
cni ip release failed, resulting in ip leak。
kubelet error log:
```
Dec 30 11:35:18 start_kubelet.sh: I1230 11:35:18.698648 13878 kubelet_pods.go:918] Pod "test-pod-0_test(3fc32306-691d-11ec-9454-3ce1a176ae1a)" is terminated, but some containers have not been cleaned up: {ID:{Type:docker ID:... | ip release failed, resulting in ip leak | https://api.github.com/repos/kubernetes/kubernetes/issues/107371/comments | 7 | 2022-01-06T07:46:49Z | 2022-01-06T21:58:56Z | https://github.com/kubernetes/kubernetes/issues/107371 | 1,095,055,495 | 107,371 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
`kubernetes/pkg/generated/openapi/zz_generated.openapi.go` file missing.
### What did you expect to happen?
`kubernetes/pkg/generated/openapi/zz_generated.openapi.go` file should exist
### How can we reproduce it (as minimally and precisely as possible)?
Unresolved reference 'GetOpenAP... | Why is the `kubernetes/pkg/generated/openapi/zz_generated.openapi.go` file missing? | https://api.github.com/repos/kubernetes/kubernetes/issues/107370/comments | 2 | 2022-01-06T07:27:46Z | 2022-01-06T07:42:19Z | https://github.com/kubernetes/kubernetes/issues/107370 | 1,095,044,435 | 107,370 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When executing `TestFailureOutput()`, no message is sent to channel `c` created in `func (runner *SpecRunner) registerForInterrupts(signalRegistered chan struct{})`. Thus, the goroutine ([line 60](https://github.com/kubernetes/kubernetes/blob/master/vendor/github.com/onsi/ginkgo/internal/specrunner... | goroutine leak in TestFailureOutput | https://api.github.com/repos/kubernetes/kubernetes/issues/107368/comments | 6 | 2022-01-06T05:11:17Z | 2022-07-24T00:25:07Z | https://github.com/kubernetes/kubernetes/issues/107368 | 1,094,974,342 | 107,368 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
The ctx object ([line 399](https://github.com/kubernetes/kubernetes/blob/master/pkg/scheduler/framework/plugins/selectorspread/selector_spread_test.go#L399)) is context.Background(). Thus, its Done() method returns a nil channel. Later, the nil channel is used to call `wait.BackoffUntil()` and `Re... | goroutine leaks in TestSelectorSpreadScore | https://api.github.com/repos/kubernetes/kubernetes/issues/107360/comments | 5 | 2022-01-06T01:34:38Z | 2022-01-21T19:23:21Z | https://github.com/kubernetes/kubernetes/issues/107360 | 1,094,884,522 | 107,360 |
[
"kubernetes",
"kubernetes"
] | ### Failure cluster [ef85a62b4fa72d47b0ee](https://go.k8s.io/triage#ef85a62b4fa72d47b0ee)
##### Error text:
```
_output/local/go/src/k8s.io/kubernetes/test/e2e_node/node_shutdown_linux_test.go:163
Unexpected error:
<*errors.errorString | 0xc0014d24e0>: {
s: "failed to run \"sh -c dbus-send --system ... | [Failing test] [sig-node] GracefulNodeShutdown [Serial] [NodeFeature:GracefulNodeShutdown] [NodeFeature:GracefulNodeShutdownBasedOnPodPriority] when gracefully shutting down after restart dbus, should be able to gracefully shutdown | https://api.github.com/repos/kubernetes/kubernetes/issues/107343/comments | 6 | 2022-01-05T18:37:45Z | 2022-01-19T00:14:06Z | https://github.com/kubernetes/kubernetes/issues/107343 | 1,094,640,654 | 107,343 |
[
"kubernetes",
"kubernetes"
] | ### Failure cluster [c7bf5dbb8034243be9b3](https://go.k8s.io/triage#c7bf5dbb8034243be9b3)
##### Error text:
```
_output/local/go/src/k8s.io/kubernetes/test/e2e_node/apparmor_test.go:58
Unexpected error:
<*errors.errorString | 0xc00029ada0>: {
s: "timed out waiting for the condition",
}
tim... | [Failing test] [sig-node] AppArmor [Feature:AppArmor][NodeFeature:AppArmor] when running with AppArmor should reject an unloaded profile | https://api.github.com/repos/kubernetes/kubernetes/issues/107342/comments | 5 | 2022-01-05T18:32:29Z | 2022-01-11T20:23:15Z | https://github.com/kubernetes/kubernetes/issues/107342 | 1,094,636,311 | 107,342 |
Subsets and Splits
Unique Owner-Repo Count
Counts the number of unique owner-repos in the dataset, providing a basic understanding of diverse repositories.