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?
In our K8s cluster, we provided the `klog.SetLogger(selfLogger)`, then observed our controller pod running, but its log is `Waiting for caches to sync for...`, and never returned.
After debug, we found that it is the klog Error(impl by our logger) func panic, lead the logr `mutex` waiting to unlo... | Klog panic lead to controller `WaitForNamedCacheSync` never returned | https://api.github.com/repos/kubernetes/kubernetes/issues/106534/comments | 8 | 2021-11-18T14:42:32Z | 2021-12-02T17:49:03Z | https://github.com/kubernetes/kubernetes/issues/106534 | 1,057,437,279 | 106,534 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
New releases is not tagged.
### What did you expect to happen?
Tag should be there.
### How can we reproduce it (as minimally and precisely as possible)?
https://pkg.go.dev/k8s.io/api?tab=versions
```
$ go get k8s.io/api@v1.23.0-beta.0
go: k8s.io/api@v0.23.0-beta.0: reading k8s.io/api/go.mo... | Kubernetes Go modules are not tagged for v1.23.0-beta.0 | https://api.github.com/repos/kubernetes/kubernetes/issues/106529/comments | 7 | 2021-11-18T13:45:38Z | 2021-12-04T18:15:16Z | https://github.com/kubernetes/kubernetes/issues/106529 | 1,057,375,627 | 106,529 |
[
"kubernetes",
"kubernetes"
] | Why use both vendor and go mod | Why use both vendor and go mod | https://api.github.com/repos/kubernetes/kubernetes/issues/106521/comments | 2 | 2021-11-18T08:35:25Z | 2021-11-18T13:37:43Z | https://github.com/kubernetes/kubernetes/issues/106521 | 1,057,079,007 | 106,521 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
**pod image information is inconsistent with the deployment**
### What did you expect to happen?
```
spec:
containers:
image: hub.xxx.netease.com/xxx/qa/xxx:v2.0.1
status:
containerStatuses:
image: hub.xxx.netease.com/xxx/qa/xxx:v2.0.0-rc1
```
### How can we reproduce it (as mi... | pod containerStatuses image information is inconsistent with the deployment | https://api.github.com/repos/kubernetes/kubernetes/issues/106519/comments | 3 | 2021-11-18T06:41:17Z | 2021-11-22T16:53:36Z | https://github.com/kubernetes/kubernetes/issues/106519 | 1,056,996,017 | 106,519 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
pull-kubernetes-kubemark-e2e-gce-scale
### Which tests are failing?
ClusterLoaderV2: load
### Since when has it been failing?
Not sure, we just got past failures to gather enough information.
### Testgrid link
https://prow.k8s.io/job-history/gs/kubernetes-jenkins/pr-logs... | pull-kubernetes-kubemark-e2e-gce-scale fails | https://api.github.com/repos/kubernetes/kubernetes/issues/106517/comments | 5 | 2021-11-18T04:21:15Z | 2022-03-22T10:01:14Z | https://github.com/kubernetes/kubernetes/issues/106517 | 1,056,923,535 | 106,517 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
kubeadm + containerd based cluster only "workingSetBytes" is reported for containers in a pod.
"memory": {
"time": "2021-10-04T12:06:58Z",
"workingSetBytes": 63426560
}
### What did you expect to happen?
but we would expect more memory metrics to be reported.
"memory": {
"time": "2021-... | Extract containerID from system.slice/containerd.service style cgroupPath | https://api.github.com/repos/kubernetes/kubernetes/issues/106514/comments | 7 | 2021-11-18T02:24:42Z | 2021-11-22T08:27:41Z | https://github.com/kubernetes/kubernetes/issues/106514 | 1,056,858,765 | 106,514 |
[
"kubernetes",
"kubernetes"
] | We are seeing 1-1 workqueue_adds_total to workqueue_retries_total in our clusters, that seems bad (why would everything need to be retried) so I tried looking into debugging this but could not get anything useful even with `-v 4`.
Found https://www.jaegertracing.io/docs/1.27/operator/ which suggests 10% being bad.
... | Debugging high controller-manager workqueue_retries_total | https://api.github.com/repos/kubernetes/kubernetes/issues/106513/comments | 9 | 2021-11-18T01:00:01Z | 2022-04-25T02:02:12Z | https://github.com/kubernetes/kubernetes/issues/106513 | 1,056,806,394 | 106,513 |
[
"kubernetes",
"kubernetes"
] | Related:
- Noticed this as part of https://github.com/kubernetes/kubernetes/issues/106506
- Opened in response to: https://github.com/kubernetes/kubernetes/issues/106506#issuecomment-972164628
According to our [rules for Conformance tests](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-... | Test should be demoted from Conformance: [sig-node] Events should be sent by kubelets and the scheduler about pods scheduling and running | https://api.github.com/repos/kubernetes/kubernetes/issues/106512/comments | 3 | 2021-11-18T00:08:56Z | 2021-11-18T07:27:40Z | https://github.com/kubernetes/kubernetes/issues/106512 | 1,056,774,189 | 106,512 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Our Azure AKS cluster had ingress object admission validating web hook configured for nginx. Nginx webhook was exposed as a K8S service in `default` namespace, with a self-signed cert. The `ValidatingWebhookConfiguration` had appropriate `caBundle` and the webhook worked fine.
```
default names... | failed calling webhook - connection reset by peer | https://api.github.com/repos/kubernetes/kubernetes/issues/106509/comments | 11 | 2021-11-17T23:33:14Z | 2022-05-02T08:56:28Z | https://github.com/kubernetes/kubernetes/issues/106509 | 1,056,742,591 | 106,509 |
[
"kubernetes",
"kubernetes"
] | Appears related to https://github.com/kubernetes/kubernetes/issues/94414
I don't see this flaking in the [periodic](https://testgrid.k8s.io/sig-testing-kind#conformance-ga-only) but it appears to be quite flaky in presubmit CI, where this is the only test on the job that fails.
/sig testing node
/kind flake
#... | [Flaky test] [pull-kubernetes-conformance-kind-ga-only-parallel] [sig-node] Events should be sent by kubelets and the scheduler about pods scheduling and running [Conformance] | https://api.github.com/repos/kubernetes/kubernetes/issues/106506/comments | 41 | 2021-11-17T22:00:19Z | 2022-02-04T05:06:30Z | https://github.com/kubernetes/kubernetes/issues/106506 | 1,056,674,479 | 106,506 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Docker Version: 18.06.1-ce
OS NAME="Ubuntu"
VERSION="18.04.3 LTS (Bionic Beaver)"
PRETTY_NAME="Ubuntu 18.04.3 LTS"
Issue:
kubernetes nodes becomes Notready with message - Kubelet stopped posting node status.
kube-apiserver logs shows :
{"log":"E1103 18:28:07.208359 ... | Certificates shown as expired even after refresh | https://api.github.com/repos/kubernetes/kubernetes/issues/106499/comments | 6 | 2021-11-17T17:56:50Z | 2021-12-01T19:08:09Z | https://github.com/kubernetes/kubernetes/issues/106499 | 1,056,425,814 | 106,499 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Changing the label on a job template in a CronJob causes any Jobs held by the successful/failed history parameters to stop being tracked, so they never get cleaned up.
### What did you expect to happen?
Jobs with labels that don't match the (upgraded) CronJob, but still have an owner reference, sh... | CronJob loses track of Jobs after label update | https://api.github.com/repos/kubernetes/kubernetes/issues/106496/comments | 4 | 2021-11-17T17:04:16Z | 2022-02-23T15:14:18Z | https://github.com/kubernetes/kubernetes/issues/106496 | 1,056,375,250 | 106,496 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Tekton, the project I work on, uses knative/pkg's generated reconcilers that rely on the go RESTClient. A user reported to us in #tektoncd/pipeline/issues/4116 an error: "etcdserver: leader changed" which appears to have bubbled up from a call to RESTClient.Get. We also see in our webhook logs "lead... | Go Client: RESTClient.Get returns error: "etcdserver: leader changed" | https://api.github.com/repos/kubernetes/kubernetes/issues/106491/comments | 9 | 2021-11-17T13:52:48Z | 2022-04-18T18:13:00Z | https://github.com/kubernetes/kubernetes/issues/106491 | 1,056,157,236 | 106,491 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
https://github.com/kubernetes/kubernetes/blob/6c357f9996070fd015e08eec24f07c82b4b8b4a6/pkg/proxy/iptables/proxier.go#L727-L731
we should move `deleteEndpointConnections` to util? This function is almost the same as: https://github.com/kubernetes/kubernetes/blob/6c357f9996070fd015e08eec24f07c82b4b... | kube-proxy: move "proxier.deleteEndpointConnections" to util | https://api.github.com/repos/kubernetes/kubernetes/issues/106484/comments | 20 | 2021-11-17T10:29:08Z | 2022-09-14T05:11:36Z | https://github.com/kubernetes/kubernetes/issues/106484 | 1,055,960,834 | 106,484 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
kubelet --help prints
> Other than from an PodSpec from the apiserver…
*an* PodSpec → *a* PodSpec
This is copy of https://github.com/kubernetes/kubelet/issues/30.
### What did you expect to happen?
.
### How can we reproduce it (as minimally and precisely as possible)?
.
### Anythin... | typo in `kubelet --help` | https://api.github.com/repos/kubernetes/kubernetes/issues/106481/comments | 8 | 2021-11-17T09:53:03Z | 2022-04-16T15:56:07Z | https://github.com/kubernetes/kubernetes/issues/106481 | 1,055,923,264 | 106,481 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
`kubeadm reset` does not delete the iptables/ipvs/ipset entries, created by `kubeadm init`. Part of the entries are created by kube-proxy and can be cleaned by kube-proxy --cleanup. Others are created by kubelet. See also kubernetes/kubeadm#2587 .
* add a method to kubelet to delete all iptables... | add option to delete the iptables, created by kubelet | https://api.github.com/repos/kubernetes/kubernetes/issues/106480/comments | 10 | 2021-11-17T09:46:59Z | 2022-01-21T13:37:02Z | https://github.com/kubernetes/kubernetes/issues/106480 | 1,055,917,495 | 106,480 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
- node-kubelet-master-kubetest2
### Which tests are failing?
- kubetest2.Test
### Since when has it been failing?
2021-11-17 06:17 CET
### Testgrid link
https://testgrid.k8s.io/sig-release-master-blocking#node-kubelet-master-kubetest2
### Reason for failure (if possible)
From build ... | [Failing test][sig-node] node-kubelet-master-kubetest2 | https://api.github.com/repos/kubernetes/kubernetes/issues/106478/comments | 14 | 2021-11-17T09:02:51Z | 2021-11-23T07:33:35Z | https://github.com/kubernetes/kubernetes/issues/106478 | 1,055,875,244 | 106,478 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When a pod is entering its Terminating state, it will receive a signal, asking it kindly to finish up work after which kubernetes will proceed deleting the pod.
At the same time that the pod starts terminating, an ingress controller will receive the updated endpoints object, which will start rem... | Pod Termination handling kicks in before the ingress controller has had time to process | https://api.github.com/repos/kubernetes/kubernetes/issues/106476/comments | 32 | 2021-11-17T08:09:12Z | 2025-03-06T03:27:11Z | https://github.com/kubernetes/kubernetes/issues/106476 | 1,055,830,349 | 106,476 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
https://github.com/kubernetes/kubernetes/issues/100236
Kubectl can only get events with uid of nodeName
https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/kubectl/pkg/describe/describe.go#L3524
You can view the implementation details
https://github.com/kubernetes/k... | Kubectl cannot get the node event created by the controller | https://api.github.com/repos/kubernetes/kubernetes/issues/106475/comments | 13 | 2021-11-17T08:06:38Z | 2023-02-28T10:17:32Z | https://github.com/kubernetes/kubernetes/issues/106475 | 1,055,828,239 | 106,475 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I had deployed a istio-ingressgateway service using metallb, which allocated a EXTERNAL-IP for istio-ingressgateway. Now I decided to using NodePort for service. So I uninstalled metallb and using NodePort.
However, When I change the service type from NodePort back to LoadBalancer, the EXTERNAL-I... | Service Externel IP does not become pending after uninstall metallb | https://api.github.com/repos/kubernetes/kubernetes/issues/106474/comments | 6 | 2021-11-17T05:00:24Z | 2021-11-17T07:57:35Z | https://github.com/kubernetes/kubernetes/issues/106474 | 1,055,707,372 | 106,474 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are flaking?
containerd-NodeConformance
### Which tests are flaking?
[sig-node] Summary API [NodeConformance] when querying /stats/summary should report resource usage through the stats api [cos-stable]
### Since when has it been flaking?
11/16/2021 13:23 PST ([first failed run link](https://prow.k8... | [Flaky test] [sig-node] containerd-NodeConformance | https://api.github.com/repos/kubernetes/kubernetes/issues/106469/comments | 3 | 2021-11-17T01:14:05Z | 2021-11-17T18:43:27Z | https://github.com/kubernetes/kubernetes/issues/106469 | 1,055,599,618 | 106,469 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are flaking?
ci-kubernetes-e2e-aks-engine-azure-master-windows-containerd-serial-slow
### Which tests are flaking?
Kubernetes e2e suite: [sig-windows] [Feature:Windows] Memory Limits [Serial] [Slow] Allocatable node memory should be equal to a calculated allocatable memory value expand_more
#... | [Flake] [Feature:Windows] Memory Limits [Serial] [Slow] Allocatable node memory | https://api.github.com/repos/kubernetes/kubernetes/issues/106468/comments | 2 | 2021-11-17T00:33:14Z | 2021-11-17T23:24:55Z | https://github.com/kubernetes/kubernetes/issues/106468 | 1,055,576,754 | 106,468 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are flaking?
https://testgrid.k8s.io/sig-windows-signal#aks-engine-windows-containerd-1.21
### Which tests are flaking?
Container Lifecycle Hook when create a pod with lifecycle hook should execute poststart exec hook properly [NodeConformance] [Conformance]
### Since when has it been flaking?
saw f... | Windows Node restarted during e2e test causing test to fail and node report not ready | https://api.github.com/repos/kubernetes/kubernetes/issues/106467/comments | 8 | 2021-11-16T21:04:17Z | 2022-02-10T17:52:28Z | https://github.com/kubernetes/kubernetes/issues/106467 | 1,055,321,981 | 106,467 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
ci-kubernetes-node-kubelet-serial
### Which tests are failing?
```
E2eNode Suite.[sig-node] NVIDIA GPU Device Plugin [Feature:GPUDevicePlugin][NodeFeature:GPUDevicePlugin][Serial] [Disruptive] DevicePlugin keeps GPU assignment to pods across pod and kubelet restarts. [cos-stable2]... | NVIDIA GPU Device Plugin sig-node serial tests failing | https://api.github.com/repos/kubernetes/kubernetes/issues/106466/comments | 10 | 2021-11-16T20:32:16Z | 2022-02-14T23:16:33Z | https://github.com/kubernetes/kubernetes/issues/106466 | 1,055,294,108 | 106,466 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
Promote Expression Language validation for CRD to beta.
KEP: https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/2876-crd-validation-expression-language
Expression Language validation for CRD is available in alpha in 1.23 release(https://github.com/k... | CRD Validation Expression Language to beta | https://api.github.com/repos/kubernetes/kubernetes/issues/106465/comments | 5 | 2021-11-16T20:18:30Z | 2022-04-15T21:43:22Z | https://github.com/kubernetes/kubernetes/issues/106465 | 1,055,283,234 | 106,465 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I've installed K8S 1.20.0 on these boxes previous, but when I re-imaged and tried installing 1.22.0, it leaves me in a constant crashing state of the K8S services. The command I'm running to install is just the "kubeadm init" command; no special switches or anything.
Here is a sample from system... | Kubeadm 1.22.x fails to stand up master node | https://api.github.com/repos/kubernetes/kubernetes/issues/106464/comments | 31 | 2021-11-16T19:40:28Z | 2023-10-31T16:52:27Z | https://github.com/kubernetes/kubernetes/issues/106464 | 1,055,253,088 | 106,464 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
curl -L -s https://dl.k8s.io/release/stable.txt
404
### What did you expect to happen?
curl -L -s https://dl.k8s.io/release/stable.txt
show stable version
### How can we reproduce it (as minimally and precisely as possible)?
curl -L -s https://dl.k8s.io/release/stable.txt
or just naviga... | Releases repository missing content? | https://api.github.com/repos/kubernetes/kubernetes/issues/106460/comments | 1 | 2021-11-16T18:01:22Z | 2021-11-16T18:10:59Z | https://github.com/kubernetes/kubernetes/issues/106460 | 1,055,168,996 | 106,460 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
gce-master-scale-correctness
### Which tests are failing?
- Kubernetes e2e suite: [sig-storage] In-tree Volumes [Driver: gcepd] [Testpattern: Inline-volume (xfs)][Slow] volumes should allow exec of files on the volume
- Kubernetes e2e suite: [sig-storage] In-tree Volumes [Driver: gcepd] ... | [Failing test][sig-scalability] gce-master-scale-correctness | https://api.github.com/repos/kubernetes/kubernetes/issues/106459/comments | 4 | 2021-11-16T16:42:32Z | 2021-11-25T08:54:34Z | https://github.com/kubernetes/kubernetes/issues/106459 | 1,055,094,164 | 106,459 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
my k8s version is 1.20.7, etcd version 3.4.13-0. O created it with kubeadm. First all was ok, but theni started to get 10-20 times per day alerts about etcd, like this:
alertname: etcdHighNumberOfFailedGRPCRequests
grpc_method: Watch
grpc_service: etcdserverpb.Watch
instance: x.x.x.x:2379
job... | Often restarting kube-scheduler, kube-api | https://api.github.com/repos/kubernetes/kubernetes/issues/106456/comments | 4 | 2021-11-16T14:54:06Z | 2021-11-17T23:01:25Z | https://github.com/kubernetes/kubernetes/issues/106456 | 1,054,974,749 | 106,456 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
"Invalid value" errors reported by cel.UnstructuredToVal (which include the telltale "evaluating rule: {rule}" at the end) are repeats of the errors already reported by openapi schema validation.
Fixing this is a beta pre-condition for the Validation Rules feature.
See @liggitt's reproduction ... | Reduce noise of invalid data messages reported from cel.UnstructuredToVal | https://api.github.com/repos/kubernetes/kubernetes/issues/106440/comments | 7 | 2021-11-16T02:07:53Z | 2022-07-26T21:44:05Z | https://github.com/kubernetes/kubernetes/issues/106440 | 1,054,354,202 | 106,440 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
As discovered in https://github.com/kubernetes/kubernetes/pull/104722#discussion_r749752524, we have generic controller tests that are depending on a provider-specific API. We should remove this dependency and instead use a generic volume type like CSI instead.
We did a workaround for 1.23 but we... | Remove gce dependency from generic controller unit tests | https://api.github.com/repos/kubernetes/kubernetes/issues/106439/comments | 5 | 2021-11-16T02:05:30Z | 2022-04-15T03:40:20Z | https://github.com/kubernetes/kubernetes/issues/106439 | 1,054,352,991 | 106,439 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
We need to benchmark and then optimize cel.UnstructuredToVal. This is a pre-condition to beta for the Validation Rules feature.
xref: [KEP](https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/2876-crd-validation-expression-language)
xref: https://githu... | Benchmark cel.UnstructuredToVal and optimize away repeated wrapper object construction | https://api.github.com/repos/kubernetes/kubernetes/issues/106438/comments | 6 | 2021-11-16T01:52:02Z | 2022-07-23T02:38:57Z | https://github.com/kubernetes/kubernetes/issues/106438 | 1,054,346,518 | 106,438 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
Currently, referencing constants in our go docs is inconsistent around our code base.
For example, somethings we use double-quotes
```go
type DeploymentStrategy struct {
// Type of deployment. Can be "Recreate" or "RollingUpdate". Default is RollingUpdate.
// +optional
Ty... | Make quoting of constants consistent in comments | https://api.github.com/repos/kubernetes/kubernetes/issues/106437/comments | 18 | 2021-11-16T01:19:26Z | 2022-10-09T20:09:17Z | https://github.com/kubernetes/kubernetes/issues/106437 | 1,054,330,472 | 106,437 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
Moving Recovery from expansion failure from alpha to beta requires careful consideration of version skews between kubelet, resizer and api-server.
- [ ] Handle the case where external-resizer is older but kubelet is newer. In this case, if `ResizeStatus` is not set, kubelet wi... | Moving recovery from expansion failure feature from alpha to beta | https://api.github.com/repos/kubernetes/kubernetes/issues/106429/comments | 8 | 2021-11-15T18:57:48Z | 2022-04-15T16:43:23Z | https://github.com/kubernetes/kubernetes/issues/106429 | 1,053,998,434 | 106,429 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
The `klog.InfoS` output was meant to machine readable. In particular it should be possible to split the log output into individual messages.
The argument in https://github.com/kubernetes/klog/pull/268#discussion_r749298770 was that the klog header can be used to split the output, the same way a... | structured logging text output: handle arbitrary values | https://api.github.com/repos/kubernetes/kubernetes/issues/106428/comments | 9 | 2021-11-15T18:33:54Z | 2022-04-08T15:34:43Z | https://github.com/kubernetes/kubernetes/issues/106428 | 1,053,980,954 | 106,428 |
[
"kubernetes",
"kubernetes"
] | The scheduler framework instantiation currently handles defaulting the weights of Score plugins, as well as checking that the total weight is not more than the maximum:
https://github.com/kubernetes/kubernetes/blob/9dc0489/pkg/scheduler/framework/runtime/framework.go#L292-L306
this should be moved to the API defa... | Move scheduler Score plugin weight defaulting to API | https://api.github.com/repos/kubernetes/kubernetes/issues/106426/comments | 33 | 2021-11-15T17:33:11Z | 2024-10-17T08:04:59Z | https://github.com/kubernetes/kubernetes/issues/106426 | 1,053,923,256 | 106,426 |
[
"kubernetes",
"kubernetes"
] | Hi,
we have around 200+ MS and we are created customresourcebinding and once we apply this binding it will restart all the pod together .
Now we don't want this happen, we want to restart the pod in batches.
is this possible?
Thanks | How to restart PODs in batches | https://api.github.com/repos/kubernetes/kubernetes/issues/106424/comments | 10 | 2021-11-15T16:10:51Z | 2022-07-09T08:42:15Z | https://github.com/kubernetes/kubernetes/issues/106424 | 1,053,841,607 | 106,424 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
The jwt-go (a dependency) handling had a CVE that was fixed on master (see #100401 and #102755). This fixed the issue on master but not on the supported version release branches.
### What did you expect to happen?
I expected the issue to be fixed on master and on other supported versions of Kubern... | Fixing CVE in supported version patch releases | https://api.github.com/repos/kubernetes/kubernetes/issues/106423/comments | 3 | 2021-11-15T15:40:14Z | 2021-12-23T14:17:12Z | https://github.com/kubernetes/kubernetes/issues/106423 | 1,053,808,975 | 106,423 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
The jwt-go dependency used at github.com/form3tech-oss/jwt-go/ is archived and no longer maintained. This was set to be used Kubernetes wide in #100401. That location is archived an no longer supported. It directs people to use https://github.com/golang-jwt/jwt instead.
The requ... | Move from archived jwt-go dependency to supported one | https://api.github.com/repos/kubernetes/kubernetes/issues/106422/comments | 12 | 2021-11-15T15:19:42Z | 2022-10-19T15:58:06Z | https://github.com/kubernetes/kubernetes/issues/106422 | 1,053,786,428 | 106,422 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Kubelet keeps throwing `InvalidDiskCapacity` kubelet invalid capacity 0 on image filesystem in the nodes status
```
Normal NodeHasNoDiskPressure 29m (x5 over 29m) kubelet Node cp-host-1 status is now: NodeHasNoDiskPressure
Normal NodeHasSufficientPID 29m (x5 over 29m) kubelet ... | [WARNING] InvalidDiskCapacity warning thrown in node events by Kubelet | https://api.github.com/repos/kubernetes/kubernetes/issues/106420/comments | 13 | 2021-11-15T13:48:42Z | 2022-04-13T14:14:44Z | https://github.com/kubernetes/kubernetes/issues/106420 | 1,053,687,365 | 106,420 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Not exactly sure on the sequence of events but the result is:
A pod is scheduled on a single node many hundreds of times (some nodes end up having > 1000 pods), which are almost all failing due to the same ```OutOfcpu``` error.
<img width="1739" alt="image" src="https://user-images.githubuserconte... | Pod created many times when node is OutOfcpu | https://api.github.com/repos/kubernetes/kubernetes/issues/106419/comments | 17 | 2021-11-15T11:34:44Z | 2023-12-08T08:32:28Z | https://github.com/kubernetes/kubernetes/issues/106419 | 1,053,560,686 | 106,419 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
when use hostport and set maxSurge =2，k8s create daemonset successfullly.
but DaemonSet rolling update is stuck， due to the failure of pod scheduling.
Events：
Warning FailedScheduling 34s default-scheduler 0/2 nodes are available: 1 node(s) didn't have free ports for the requested pod ports... | we should reject HostPort use in daemonset when maxSurge is non-zero | https://api.github.com/repos/kubernetes/kubernetes/issues/106417/comments | 7 | 2021-11-15T09:31:31Z | 2022-04-24T08:57:11Z | https://github.com/kubernetes/kubernetes/issues/106417 | 1,053,412,183 | 106,417 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
Refer to [SetDefaults_NodeResourcesFitArgs()](https://github.com/kubernetes/kubernetes/blob/master/pkg/scheduler/apis/config/v1beta3/defaults.go#L252-L256), we'll change the default behavior by altering the resource weight, however, we should raise an error instead to tell the us... | We should raise a error instead of change the default weight of resource weight | https://api.github.com/repos/kubernetes/kubernetes/issues/106416/comments | 3 | 2021-11-15T08:56:42Z | 2021-11-15T09:55:33Z | https://github.com/kubernetes/kubernetes/issues/106416 | 1,053,375,894 | 106,416 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
For example, there is one deployment with below configuration.
```
progressDeadlineSeconds: 600
replicas: 1
strategy:
type: Recreate
```
Due to resource exhaustion on the node, the node evicted pods of this deployment. The running pod is owned by the rs 'nginx-deployment-dfbd8fcd5'
Aroun... | Whether pod deletion should enqueue the deployment again when there is only evicted pod left | https://api.github.com/repos/kubernetes/kubernetes/issues/106410/comments | 10 | 2021-11-14T14:19:43Z | 2022-05-14T18:16:31Z | https://github.com/kubernetes/kubernetes/issues/106410 | 1,052,951,274 | 106,410 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
kubelet logs misleading error when volume limits
```shell
[root@k8s-node2 logs]# tailf kubelet.k8s-node2.root.log.INFO.20211114-000124.7385 |grep -i error
I1114 05:16:22.250177 7385 handler.go:294] error while reading "/proc/7385/fd/31" link: readlink /proc/7385/fd/31: no such file or direct... | Error getting volume limit for plugin kubernetes.io/<name> | https://api.github.com/repos/kubernetes/kubernetes/issues/106409/comments | 15 | 2021-11-14T10:45:14Z | 2023-05-26T03:56:16Z | https://github.com/kubernetes/kubernetes/issues/106409 | 1,052,906,266 | 106,409 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
- etcd
etcd is running successfully.
```
[root@k8s-01 home]# systemctl status etcd
● etcd.service - Etcd Server
Loaded: loaded (/etc/systemd/system/etcd.service; enabled; vendor preset: disabled)
Active: active (running) since Sun 2021-11-14 15:47:28 CST; 1h 22min ago
Docs: https... | etcd running but rejected connection from "192.168.7.175:53382" (error "remote error: tls: bad certificate", ServerName "") | https://api.github.com/repos/kubernetes/kubernetes/issues/106407/comments | 7 | 2021-11-14T09:34:29Z | 2021-12-02T01:56:51Z | https://github.com/kubernetes/kubernetes/issues/106407 | 1,052,892,950 | 106,407 |
[
"kubernetes",
"kubernetes"
] | See https://github.com/kubernetes/kubernetes/pull/106285#discussion_r746885942
Deprecated with semicolon marks the field as deprecated. Other forms are just comments. If replaced today - static check will complain like this below. So once generated files are excluded from the static check, need to replace dot (`Depr... | Use "Deprecated:" instead of "Deprecated." in types.go (once generated files are excluded from static check) | https://api.github.com/repos/kubernetes/kubernetes/issues/106405/comments | 14 | 2021-11-14T05:37:36Z | 2022-04-16T08:50:10Z | https://github.com/kubernetes/kubernetes/issues/106405 | 1,052,852,703 | 106,405 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
kubernetes 1.21.6
containerd v1.5.7
CentOS 8.2
kernal：5.4.158-1.el8.elrepo.x86_64
I have only install containerd CRI,I dont't install docker，when I start kubelet after start containerd，It tells me I didn't start Docker。
```
[root@ayunw-srv1 ~]# systemctl daemon-reload
[root@ayunw-srv1... | start kubelet tell me Failed to restart kubelet.service: Unit docker.service not found. | https://api.github.com/repos/kubernetes/kubernetes/issues/106403/comments | 6 | 2021-11-14T04:18:29Z | 2021-11-17T18:49:46Z | https://github.com/kubernetes/kubernetes/issues/106403 | 1,052,842,016 | 106,403 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
https://testgrid.k8s.io/sig-network-ingress-gce-e2e#ingress-gce-e2e
https://testgrid.k8s.io/sig-network-ingress-gce-e2e#ingress-gce-e2e-scale
### Which tests are failing?
Kubernetes e2e suite: [sig-network] Loadbalancing: L7 GCE [Slow] [Feature:NEG] [Flaky] should sync endpoints to NEG e... | GCE Ingress tests failures | https://api.github.com/repos/kubernetes/kubernetes/issues/106402/comments | 9 | 2021-11-13T19:02:24Z | 2021-11-17T21:42:58Z | https://github.com/kubernetes/kubernetes/issues/106402 | 1,052,748,071 | 106,402 |
[
"kubernetes",
"kubernetes"
] | `statusStrategy#ValidateUpdate` doesn't do the same embedded resource and x-kubernetes-list-type "map" and "set" invariant validation that happens in custom resource create/update validation.
Does that mean embedded objects and list-type fields under custom resource status can contain invalid data?
if so, that n... | Custom resource status validation doesn't do embedded resource and x-kubernetes-list-type validation | https://api.github.com/repos/kubernetes/kubernetes/issues/106401/comments | 11 | 2021-11-13T18:53:58Z | 2022-09-15T22:33:23Z | https://github.com/kubernetes/kubernetes/issues/106401 | 1,052,746,385 | 106,401 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
A k8s cluster has 5 nodes. One of the nodes is cordoned as SchedulingDisabled status.
When i want to create a statefulset with 5 replicas and pod topology spread constraints with
```
topologySpreadConstraints:
- labelSelector:
matchLabels:
app: redis
component: pro... | Pod Topology Spread Constraints does not exclude SchedulingDisabled nodes | https://api.github.com/repos/kubernetes/kubernetes/issues/106396/comments | 5 | 2021-11-13T08:43:38Z | 2021-11-15T19:33:54Z | https://github.com/kubernetes/kubernetes/issues/106396 | 1,052,631,480 | 106,396 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
After upgrade Flatcar-Linux and switch to the cgroups v2, `kubectl top node ` shows <<unknow>>
<img width="1008" alt="image" src="https://user-images.githubusercontent.com/17834225/141581604-49120d09-06f1-4871-9ffc-552e7db05bff.png">
### What did you expect to happen?
`kubectl top node ... | Missing metrics after switching to Cgroups v2 (need bump Cadvisor version) | https://api.github.com/repos/kubernetes/kubernetes/issues/106393/comments | 20 | 2021-11-12T23:07:10Z | 2023-04-24T02:50:49Z | https://github.com/kubernetes/kubernetes/issues/106393 | 1,052,468,258 | 106,393 |
[
"kubernetes",
"kubernetes"
] | I changed some behaviour to be more resilient to this failure mode in https://github.com/kubernetes/kubernetes/pull/102821 but we don't have an e2e to validate it.
We should write an e2e to verify that, when the container runtime statuses are wiped (e.g. with crio-wipe on a node running CRI-O), we preserve the follo... | Add an e2e test validating pod statuses on container state wipe | https://api.github.com/repos/kubernetes/kubernetes/issues/106390/comments | 7 | 2021-11-12T20:12:15Z | 2022-04-28T20:32:09Z | https://github.com/kubernetes/kubernetes/issues/106390 | 1,052,375,784 | 106,390 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Per [JSON Reference documentation](https://tools.ietf.org/id/draft-pbryan-zyp-json-ref-03.html#rfc.section.3),
> Any members other than "$ref" in a JSON Reference object SHALL be ignored.
In the first couple of lines in our [swagger.json](https://github.com/kubernetes/kubernetes/blob/master/a... | Published swagger should not include sibling elements alongside a $ref | https://api.github.com/repos/kubernetes/kubernetes/issues/106387/comments | 8 | 2021-11-12T16:22:47Z | 2024-08-16T08:59:33Z | https://github.com/kubernetes/kubernetes/issues/106387 | 1,052,139,640 | 106,387 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
build-master
### Which tests are failing?
Job execution failed: Pod got deleted unexpectedly
### Since when has it been failing?
12/11/21 (16:27 IST)
### Testgrid link
https://testgrid.k8s.io/sig-release-master-blocking#build-master
### Reason for failure (if possible)
Job execution... | [Failing Test] build-master | https://api.github.com/repos/kubernetes/kubernetes/issues/106380/comments | 5 | 2021-11-12T13:52:11Z | 2021-11-12T19:03:00Z | https://github.com/kubernetes/kubernetes/issues/106380 | 1,051,988,958 | 106,380 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Hi brothers, I currently use the latest beat version to deploy a kubernetes cluster, but there are some unexpected situations。
- /usr/local/bin/kube-apiserver
- --enable-admission-plugins=Priority,NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,ResourceQuota,NodeRest... | kubernetes v1.23.0-alpha.4 deployment fail | https://api.github.com/repos/kubernetes/kubernetes/issues/106378/comments | 3 | 2021-11-12T10:09:48Z | 2021-11-22T06:43:05Z | https://github.com/kubernetes/kubernetes/issues/106378 | 1,051,794,413 | 106,378 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are flaking?
https://testgrid.k8s.io/sig-node-kubelet#node-kubelet-serial&width=5
### Which tests are flaking?
Seen in this job failing on multiple tests, this is just one of the stack traces
https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/106371/pull-kubernetes-node-kubelet-serial/1459... | Node e2e tests panics trying to set KubeletConfig | https://api.github.com/repos/kubernetes/kubernetes/issues/106377/comments | 4 | 2021-11-12T10:02:11Z | 2021-11-15T19:27:03Z | https://github.com/kubernetes/kubernetes/issues/106377 | 1,051,787,435 | 106,377 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Since [this PR](https://github.com/kubernetes/kubernetes/pull/81443) we can now set and use a `proxy-url` within the cluster settings from $KUBECONFIG.
Currently there is [no support to add this option](https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#-em-set-cluster-em-) w... | Add support for proxy-url for kubectl config | https://api.github.com/repos/kubernetes/kubernetes/issues/106374/comments | 9 | 2021-11-12T09:16:14Z | 2022-06-19T19:07:35Z | https://github.com/kubernetes/kubernetes/issues/106374 | 1,051,745,381 | 106,374 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
```
+++ [1112 15:23:48] Building go targets for darwin/amd64:
./vendor/k8s.io/code-generator/cmd/prerelease-lifecycle-gen
cannot find package "k8s.io/kubernetes/vendor/k8s.io/code-generator/cmd/prerelease-lifecycle-gen" in any of:
/usr/local/go/src/k8s.io/kubernetes/vendor/k8s.io/code-gener... | release1.22 build failed! | https://api.github.com/repos/kubernetes/kubernetes/issues/106369/comments | 7 | 2021-11-12T07:33:35Z | 2022-04-15T04:40:20Z | https://github.com/kubernetes/kubernetes/issues/106369 | 1,051,664,897 | 106,369 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are flaking?
ci-crio-cgroupv2-node-e2e-conformance
ci-crio-cgroupv1-node-e2e-conformance
### Which tests are flaking?
[sig-node] Summary API [NodeConformance] when querying /stats/summary should report resource usage through the stats api
### Since when has it been flaking?
From about a m... | [sig-node] Summary API [NodeConformance] test flakes for systemd + crio node e2e jobs | https://api.github.com/repos/kubernetes/kubernetes/issues/106367/comments | 7 | 2021-11-12T06:53:29Z | 2022-03-02T18:46:23Z | https://github.com/kubernetes/kubernetes/issues/106367 | 1,051,640,472 | 106,367 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
Currently the output of `wait` is simply `condition met`...
It would be much more useful to have something meaningful like `job completed`, `pod ready`, etc. You can simply use the name of the condition (`for` argument).
### Why is this needed?
Currently when you have a long ... | Improve kubectl wait output message | https://api.github.com/repos/kubernetes/kubernetes/issues/106364/comments | 8 | 2021-11-11T22:37:27Z | 2022-04-21T23:36:24Z | https://github.com/kubernetes/kubernetes/issues/106364 | 1,051,417,293 | 106,364 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
The scheduler has a [30s timeout](https://github.com/kubernetes/kubernetes/blob/0fefe4e605ba05793e919598c09390769c127b3c/pkg/scheduler/scheduler.go#L231) for the bind operation to succeed; if we don't get a response within 30s, the in-memory assignment of pod to node in the [scheduler cache expires]... | Scheduler will run into race conditions on large scale clusters | https://api.github.com/repos/kubernetes/kubernetes/issues/106361/comments | 44 | 2021-11-11T18:09:08Z | 2024-06-05T19:50:14Z | https://github.com/kubernetes/kubernetes/issues/106361 | 1,051,236,187 | 106,361 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
capg-conformance-v1alpha4-k8s-master
### Which tests are failing?
* Kubernetes e2e suite.[sig-network] HostPort validates that there is no conflict between pods with same hostPort but different hostIP and protocol [LinuxOnly] [Conformance]periodic-cluster-* api-provider-gcp-make-conforman... | [Failing test][sig-network] capg-conformance-v1alpha4-k8s-master | https://api.github.com/repos/kubernetes/kubernetes/issues/106347/comments | 10 | 2021-11-11T10:59:23Z | 2021-11-18T22:49:55Z | https://github.com/kubernetes/kubernetes/issues/106347 | 1,050,853,549 | 106,347 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
This issue relates to the [issue](https://github.com/istio/istio/issues/35177) , I check the log of kubelet and get the error output as below:
```
Nov 11 17:12:55 zhlsunshine kubelet[9844]: E1111 17:12:55.269450 9844 httpstream.go:255] error forwarding port 15000 to pod 00ae38b9f99f54d7718eef98... | kubelet por-forward bugs for IPv6 support when using Istio's command line tool in Kubernetes cluster | https://api.github.com/repos/kubernetes/kubernetes/issues/106345/comments | 8 | 2021-11-11T09:44:57Z | 2021-11-11T10:30:41Z | https://github.com/kubernetes/kubernetes/issues/106345 | 1,050,787,339 | 106,345 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
we are running oracle goldengate microservices in kubernetes 1.20 and it is failing with below error. Is there a WA. OKE latest version available is 1.20.11 only
anon alloc: mmap(MAP_ANON) anon free: munmap
file ... | Goldengate running on kubernetes fails due to swap space issue | https://api.github.com/repos/kubernetes/kubernetes/issues/106343/comments | 5 | 2021-11-11T08:28:52Z | 2021-11-11T17:03:18Z | https://github.com/kubernetes/kubernetes/issues/106343 | 1,050,700,442 | 106,343 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
E2eNode Suite.[sig-node] Ephemeral Containers will start an ephemeral container in an existing pod
### Which tests are failing?
node-kubelet-orphans
### Since when has it been failing?
Unknown, possibly was never green
### Testgrid link
https://testgrid.k8s.io/sig-node-kubelet... | [NodeFeature:EphemeralContainers] Ephemeral Containers e2e tests are Flaking | https://api.github.com/repos/kubernetes/kubernetes/issues/106341/comments | 12 | 2021-11-11T06:34:38Z | 2021-11-16T16:19:55Z | https://github.com/kubernetes/kubernetes/issues/106341 | 1,050,625,125 | 106,341 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
when i deploy a application, the kubelet report an error about "repository does not exist or may require 'docker login'"，but docker pull image succeeded on host，"imageSecret" is not configured in deployment.yaml.
kubelet can pull image when i configure "imageSecret" in deployment.yaml.
### Wha... | repository does not exist or may require 'docker login' | https://api.github.com/repos/kubernetes/kubernetes/issues/106335/comments | 14 | 2021-11-11T02:44:29Z | 2022-04-18T03:07:00Z | https://github.com/kubernetes/kubernetes/issues/106335 | 1,050,514,197 | 106,335 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Start kubelet on a cgroupv2 image with `kernelMemcgNotification` kubelet config option or the flag `--kernel-memcg-notification=true` enabled. Kubelet will periodically log something like:
```
kubelet[2571]: I1109 00:16:36.071429 2571 eviction_manager.go:262] "Eviction manager: failed to up... | kubelet kernelMemcgNotification are not supported on cgroupv2 | https://api.github.com/repos/kubernetes/kubernetes/issues/106331/comments | 2 | 2021-11-10T23:37:57Z | 2021-11-13T02:36:46Z | https://github.com/kubernetes/kubernetes/issues/106331 | 1,050,415,596 | 106,331 |
[
"kubernetes",
"kubernetes"
] | ### Failure cluster [5a9fe2a5ee4846a0e5d7](https://go.k8s.io/triage#5a9fe2a5ee4846a0e5d7)
##### Error text:
```
=== RUN TestFlowControlSignal/request_performed
handler_proxy_test.go:1024: flow control signal expected but not fired
--- FAIL: TestFlowControlSignal/request_performed (0.00s)
```
#### R... | Flake in TestFlowControlSignal: flow control signal expected but not fired | https://api.github.com/repos/kubernetes/kubernetes/issues/106328/comments | 4 | 2021-11-10T21:45:54Z | 2021-11-15T06:54:18Z | https://github.com/kubernetes/kubernetes/issues/106328 | 1,050,341,597 | 106,328 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are flaking?
pull-kubernetes-unit
### Which tests are flaking?
=== RUN TestSyncLabels/no_labels
W1110 19:40:23.216695 56350 mutation_detector.go:53] Mutation detector is enabled, this will result in memory leakage.
E1110 19:40:23.217299 56350 runtime.go:78] Observed a panic: runtime.boundsErro... | TestSyncLabels/no_labels | https://api.github.com/repos/kubernetes/kubernetes/issues/106326/comments | 11 | 2021-11-10T20:41:13Z | 2021-12-01T18:23:48Z | https://github.com/kubernetes/kubernetes/issues/106326 | 1,050,290,345 | 106,326 |
[
"kubernetes",
"kubernetes"
] | null | Troubleshooting Kubernetes | https://api.github.com/repos/kubernetes/kubernetes/issues/106324/comments | 2 | 2021-11-10T20:31:09Z | 2021-11-22T16:30:06Z | https://github.com/kubernetes/kubernetes/issues/106324 | 1,050,282,911 | 106,324 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
kubeadm-kinder-latest
### Which tests are failing?
* ci-kubernetes-e2e-kubeadm-kinder-latest.Overall
* E2EKubeadm suite.[sig-cluster-lifecycle] [area-kubeadm] proxy addon kube-proxy ServiceAccount should be bound to the system:node-proxier cluster role
### Since when has it been... | [Failing test][sig-cluster-lifecycle] kubeadm-kinder-latest | https://api.github.com/repos/kubernetes/kubernetes/issues/106318/comments | 3 | 2021-11-10T18:23:31Z | 2021-11-11T20:00:08Z | https://github.com/kubernetes/kubernetes/issues/106318 | 1,050,164,001 | 106,318 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
`kubectl cp <container>:file.tgz file.tgz` results in:
```
tar: file.tgz: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
```
`rc=0`
### What did you expect to happen?
`rc>0`
### How can we reproduce it (as minimally and precisely as possible)... | [kubectl] copy non existent source in container returns zero return code | https://api.github.com/repos/kubernetes/kubernetes/issues/106312/comments | 6 | 2021-11-10T15:36:38Z | 2021-11-23T09:08:39Z | https://github.com/kubernetes/kubernetes/issues/106312 | 1,049,988,207 | 106,312 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
kubeadm-kinder-latest-on-1-22
### Which tests are failing?
* E2EKubeadm suite.[sig-cluster-lifecycle] [area-kubeadm] proxy addon kube-proxy ServiceAccount should be bound to the system:node-proxier cluster role
* ci-kubernetes-e2e-kubeadm-kinder-latest-on-1-22.Overall
* task-06-e2e-kube... | [Failing test][sig-cluster-lifecycle] kubeadm-kinder-latest-on-1-22 | https://api.github.com/repos/kubernetes/kubernetes/issues/106311/comments | 4 | 2021-11-10T15:24:21Z | 2021-11-11T20:00:09Z | https://github.com/kubernetes/kubernetes/issues/106311 | 1,049,963,174 | 106,311 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
kubelet-serial-gce-e2e-hugepages
### Which tests are failing?
all
### Since when has it been failing?
November 09th 2021
### Testgrid link
https://testgrid.k8s.io/sig-node-kubelet#kubelet-serial-gce-e2e-hugepages
### Reason for failure (if possible)
Tests fail with the same error: '... | Hugepages test fails | https://api.github.com/repos/kubernetes/kubernetes/issues/106310/comments | 3 | 2021-11-10T13:55:59Z | 2021-11-11T16:41:01Z | https://github.com/kubernetes/kubernetes/issues/106310 | 1,049,863,755 | 106,310 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
Pod Disruption Budgets to have full support for Daemonsets. Currently only [minAvailable with integer values](https://kubernetes.io/docs/tasks/run-application/configure-pdb/#arbitrary-controllers-and-selectors) is supported.
### Why is this needed?
Daemonsets are used for c... | Full Pod Disruption Budget support for Daemonsets | https://api.github.com/repos/kubernetes/kubernetes/issues/106309/comments | 16 | 2021-11-10T13:42:42Z | 2023-04-27T17:54:52Z | https://github.com/kubernetes/kubernetes/issues/106309 | 1,049,850,367 | 106,309 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I have created Deployment, service and ingress with below yaml file:
apiVersion: apps/v1
kind: Deployment
metadata:
namespace: default
name: nginx
labels:
app: nginx
spec:
replicas: 1
selector:
matchLabels:
name: nginx
template:
metadata:
labels:
... | Curl: (7) Failed connect to Connection refused | https://api.github.com/repos/kubernetes/kubernetes/issues/106304/comments | 4 | 2021-11-10T09:20:35Z | 2021-11-10T23:05:53Z | https://github.com/kubernetes/kubernetes/issues/106304 | 1,049,583,044 | 106,304 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I can create a cluster with one node and pass conformance,
~there are some tests that require at least 2 nodes to run~
~`https://github.com/kubernetes/kubernetes/blob/0c6110e4120165b4485e658de6eca5d6d2d72b1a/test/e2e/common/network/networking.go#L80-L82`~
~This is because the tests Skip if... | Are single-node clusters conformant? | https://api.github.com/repos/kubernetes/kubernetes/issues/106303/comments | 6 | 2021-11-10T09:17:41Z | 2021-11-10T18:33:20Z | https://github.com/kubernetes/kubernetes/issues/106303 | 1,049,580,098 | 106,303 |
[
"kubernetes",
"kubernetes"
] | Spin off from https://github.com/kubernetes/kubernetes/pull/105873/files#r735360613
In my opinion, having additional concepts of TimedObservers rather than relying directly on metrics is unnecessarily complicating the (already pretty complicated) codebase.
My main questions are:
- do we really need them?
- do we ... | Reconsider how we implement watermarks in P&F | https://api.github.com/repos/kubernetes/kubernetes/issues/106302/comments | 5 | 2021-11-10T09:04:23Z | 2021-11-15T19:02:20Z | https://github.com/kubernetes/kubernetes/issues/106302 | 1,049,566,365 | 106,302 |
[
"kubernetes",
"kubernetes"
] | (moved from https://github.com/kubernetes/pod-security-admission/issues/1)
As a user of this feature I would like to be able to allow specific capabilities for specific services in my project.
The current implementations offers only three general definitions of security levels which can be hard to suit services t... | making it possible to grant specific PodSecurity permissions for specific services | https://api.github.com/repos/kubernetes/kubernetes/issues/108802/comments | 8 | 2021-11-10T07:53:55Z | 2022-03-19T10:43:41Z | https://github.com/kubernetes/kubernetes/issues/108802 | 1,173,849,484 | 108,802 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
```
type=AVC msg=audit(1636522420.778:201): avc: denied { write } for pid=8920 comm="iptables" path="/run/systemd/inhibit/2.ref" dev="tmpfs" ino=58429 scontext=system_u:system_r:iptables_t:s0 tcontext=system_u:object_r:systemd_logind_inhibit_var_run_t:s0 tclass=fifo_file permissive=1
type=S... | Kubelet leaks /run/systemd/inhibit/X.ref when exec iptables triggering selinux | https://api.github.com/repos/kubernetes/kubernetes/issues/106292/comments | 6 | 2021-11-10T06:24:34Z | 2022-07-21T02:10:03Z | https://github.com/kubernetes/kubernetes/issues/106292 | 1,049,447,260 | 106,292 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When the Kubernetes API server returns a 429 (throttled), the response may include misleading cause information.
We observed that a pod eviction API call received a response that included _**both**_ of the following fragments:
``` json
"responseStatus": {
"metadata": {},
"status": "Fa... | Confusing use of TooManyRequests error for eviction | https://api.github.com/repos/kubernetes/kubernetes/issues/106286/comments | 28 | 2021-11-10T01:18:49Z | 2025-01-30T19:52:12Z | https://github.com/kubernetes/kubernetes/issues/106286 | 1,049,292,725 | 106,286 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
While experimenting with `kubectl apply --prune --selector`, I noticed that it skipped deleting resources in some circumstances. After further experimentation, I learned that `kubectl apply --prune --selector foo=bar -f resources.yaml` won't delete resources in a namespace if that namespace doesn't ... | kubectl apply --prune does not delete resources matching label selector in "unvisited" namespaces | https://api.github.com/repos/kubernetes/kubernetes/issues/106284/comments | 9 | 2021-11-10T00:12:59Z | 2023-06-03T20:03:03Z | https://github.com/kubernetes/kubernetes/issues/106284 | 1,049,256,505 | 106,284 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are flaking?
ci-kubernetes-e2e-aks-engine-azure-master-windows-containerd
### Which tests are flaking?
Kubernetes e2e suite: [sig-windows] [Feature:Windows] Kubelet-Stats Kubelet stats collection for Windows nodes when running 3 pods should return within 10 seconds
### Since when has it been flaking?... | New Windows kubelet stats collection test flaking | https://api.github.com/repos/kubernetes/kubernetes/issues/106278/comments | 10 | 2021-11-09T19:41:55Z | 2022-01-27T17:49:14Z | https://github.com/kubernetes/kubernetes/issues/106278 | 1,049,033,837 | 106,278 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
As a user if I `kubectl edit` a custom API resource (for example, a Fischer from the sample-apiserver), I can change the name in the metadata and I do not get a `error: At least one of apiVersion, kind and name was changed`.
Instead, a Patch to the new user-edited name is created, which can result ... | kubectl edit of a type from an API extension server does not check preconditions | https://api.github.com/repos/kubernetes/kubernetes/issues/106277/comments | 3 | 2021-11-09T19:12:42Z | 2021-11-16T14:41:27Z | https://github.com/kubernetes/kubernetes/issues/106277 | 1,048,976,097 | 106,277 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
We need to add a custom formatter like [this](https://gist.github.com/shivanshu1333/10a801d10c8f790b2e12e50cfb451dc7), test case to see [result](https://gist.github.com/shivanshu1333/3e7b7cda9fad55c2065900cd30f75781) as part of structured logging
### Why is this needed?
Par... | Add custom formatter for podData and nodeInfo for `pkg/scheduler/internal/cache/debugger/dumper.go` | https://api.github.com/repos/kubernetes/kubernetes/issues/106276/comments | 8 | 2021-11-09T19:05:39Z | 2022-03-25T19:36:30Z | https://github.com/kubernetes/kubernetes/issues/106276 | 1,048,970,453 | 106,276 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Our setup has Pods [source] that send (continuous) UDP traffic to a ClusterIP service that is backed by a single endpoint Pod [destination]
When the destination Pod is recreated, the nodes that host the source Pods end up with an incorrect conntrack entry which results in the traffic getting blac... | UDP traffic to a single Pod behind a ClusterIP is blackholed when the destination Pod is recreated (wrong conntrack) | https://api.github.com/repos/kubernetes/kubernetes/issues/106274/comments | 14 | 2021-11-09T17:49:35Z | 2022-03-17T20:59:01Z | https://github.com/kubernetes/kubernetes/issues/106274 | 1,048,900,054 | 106,274 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
### Use case:
A DPDK application uses VLAN trunking on SR-IOV NICs and requires dedicated SR-IOV NICs. For cost-reasons there is only one SRIOV-NIC per server but, to exploit the CPU resources optimally, the applications need to run one single-NUMA pod per CPU socket. For these pods, CPUs and huge-... | Best-effort topology mgr policy doesn't give best-effort CPU NUMA alignment | https://api.github.com/repos/kubernetes/kubernetes/issues/106270/comments | 16 | 2021-11-09T16:12:22Z | 2025-01-21T08:23:15Z | https://github.com/kubernetes/kubernetes/issues/106270 | 1,048,792,185 | 106,270 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
An `EndpointSlice` can contain up to 1000 `Endpoints`, which can each contain up to 100 `Addresses`. Or at least, that's what the docs say, but actually, kube-proxy (or more specifically, `pkg/proxy/endpointslicecache.go`) only looks at the first Address in each Endpoint:
```
endpointInfo :=... | kube-proxy only looks at Addresses[0] in EndpointSlice | https://api.github.com/repos/kubernetes/kubernetes/issues/106267/comments | 28 | 2021-11-09T15:07:52Z | 2022-06-30T14:56:48Z | https://github.com/kubernetes/kubernetes/issues/106267 | 1,048,717,353 | 106,267 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
I install kubernetes 1.22.2
calico 3.20.2
centos 8.4
kernel 4.18
when I create some pod,and sawed that kubelet status had some error
```
Nov 09 21:31:25 sit-kubernetes-master-srv1 kubelet[112447]: E1109 21:31:25.927561 112447 kubelet/kubelet.go:1343] "Image garbage collection faile... | Kubelet logging PLEG: Write status error when no errors have occured | https://api.github.com/repos/kubernetes/kubernetes/issues/106265/comments | 13 | 2021-11-09T14:11:02Z | 2022-01-11T18:48:26Z | https://github.com/kubernetes/kubernetes/issues/106265 | 1,048,653,106 | 106,265 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
The below test is failing in our daily conformance runs that test the suite against the latest k8s cluster:
`Test that validates that there is no conflict between pods with same hostPort but different hostIP and protocol`
https://github.com/kubernetes/kubernetes/blob/master/test/e2e/network/host... | Test Failure: Conformance test to validate there is no conflict between pods with same hostPort but different hostIP and protocol | https://api.github.com/repos/kubernetes/kubernetes/issues/106264/comments | 17 | 2021-11-09T14:01:35Z | 2021-12-08T17:27:56Z | https://github.com/kubernetes/kubernetes/issues/106264 | 1,048,642,646 | 106,264 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
When using `InfoS` or `ErrorS` with a key/value that has a multi-line string as value, that value will appear as quoted string in the log message, i.e. the log message will still be a single line.
It would be nicer to print the value in text mode so that it goes across multiple ... | structured logging: better support for multi-line strings | https://api.github.com/repos/kubernetes/kubernetes/issues/106262/comments | 6 | 2021-11-09T12:08:46Z | 2021-12-06T18:55:34Z | https://github.com/kubernetes/kubernetes/issues/106262 | 1,048,531,796 | 106,262 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
Something like this could be made available in klog, logr or a Kubernetes helper package (TBD):
```
// LogAs implements both the string.Stringer and logr.Marshal interface with
// some custom functions. It can be used to implement a custom formatter for
// some kind of object e... | structured logging: helper struct for formatting an object | https://api.github.com/repos/kubernetes/kubernetes/issues/106258/comments | 7 | 2021-11-09T11:48:34Z | 2021-12-17T08:23:30Z | https://github.com/kubernetes/kubernetes/issues/106258 | 1,048,512,198 | 106,258 |
[
"kubernetes",
"kubernetes"
] | the error stems from:
```
$ kubectl create -f webhook.yaml
The MutatingWebhookConfiguration "webhook" is invalid: webhooks[0].sideEffects: Unsupported value: "Unknown": supported values: "None", "NoneOnDryRun"
```
after some digging I saw this is the default value it it's supposed to fail, not sure if this is ... | [kubectl-convert] running `kubectl-convert` on MutatingWebhookConfiguration causes apply fail | https://api.github.com/repos/kubernetes/kubernetes/issues/106249/comments | 7 | 2021-11-09T08:03:04Z | 2021-11-13T15:07:37Z | https://github.com/kubernetes/kubernetes/issues/106249 | 1,048,300,169 | 106,249 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
Kubelet credential provider is in alpha since 1.20 release, we need to add e2e tests to move it to beta.
**Current e2e tests for intree credential providers:**
[1] https://github.com/kubernetes/kubernetes/blob/master/test/e2e_node/runtime_conformance_test.go#L61 (uses intree... | [KEP:2133] E2E tests for external Kubelet Credential Provider | https://api.github.com/repos/kubernetes/kubernetes/issues/106248/comments | 27 | 2021-11-09T06:49:02Z | 2022-11-21T14:16:45Z | https://github.com/kubernetes/kubernetes/issues/106248 | 1,048,248,894 | 106,248 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Kubernetes HPA not scale up when exact target utilization reached
```
apiVersion: autoscaling/v2beta2
kind: HorizontalPodAutoscaler
metadata:
name: ping-adapter
spec:
scaleTargetRef:
apiVersion: apps/v1
kind: Deployment
name: ping-adapter
minReplicas: 1
maxReplica... | Kubernetes HPA not scale up when exact target utilization reached | https://api.github.com/repos/kubernetes/kubernetes/issues/106247/comments | 16 | 2021-11-09T05:34:02Z | 2023-03-02T13:46:48Z | https://github.com/kubernetes/kubernetes/issues/106247 | 1,048,209,568 | 106,247 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Panic occurs when using the custom scheduling scoring plugins. The customized scheduling scoring plug-in is developed based on the schedule framework. Panic is accidental.
error messsage:
fatal error: concurrent map writes.
### What did you expect to happen?
no panic
### How can we reproduce ... | Panic occurs when using the custom scheduling scoring plugins | https://api.github.com/repos/kubernetes/kubernetes/issues/106246/comments | 8 | 2021-11-09T05:20:16Z | 2021-11-24T23:37:23Z | https://github.com/kubernetes/kubernetes/issues/106246 | 1,048,202,986 | 106,246 |
[
"kubernetes",
"kubernetes"
] | null | Troubleshooting | https://api.github.com/repos/kubernetes/kubernetes/issues/106238/comments | 2 | 2021-11-08T20:49:20Z | 2021-11-22T16:29:39Z | https://github.com/kubernetes/kubernetes/issues/106238 | 1,047,904,660 | 106,238 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I am running a Kubernetes `v1.22.2` cluster on **ppc64le** which uses `k8s.gcr.io/etcd:3.5.0-0` for etcd.
The actual etcd version bundled with this docker image is v3.4.13 which seems incorrect.
Because of this version mismatch, etcd cannot recognize the flags (--experimental-enable-distributed-... | Incorrect etcd version bundled with etcd docker image - k8s.gcr.io/etcd:3.5.0-0 | https://api.github.com/repos/kubernetes/kubernetes/issues/106229/comments | 20 | 2021-11-08T13:53:16Z | 2022-05-14T01:14:29Z | https://github.com/kubernetes/kubernetes/issues/106229 | 1,047,476,562 | 106,229 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When a node with graceful node shutdown is shut down, persistent volumes attached to the node are not detached when the pod using the corresponding persistent volume claim is evicted from the node. After the node shutdown completes the associated VolumeAttachment objects are eventually removed but... | Graceful node shutdown not detaching persistent volumes when pods are evicted | https://api.github.com/repos/kubernetes/kubernetes/issues/106227/comments | 5 | 2021-11-08T09:57:56Z | 2022-01-21T11:03:35Z | https://github.com/kubernetes/kubernetes/issues/106227 | 1,047,240,796 | 106,227 |
Subsets and Splits
Unique Owner-Repo Count
Counts the number of unique owner-repos in the dataset, providing a basic understanding of diverse repositories.