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"
] | ### Which jobs are failing?
master-blocking
- gce-cos-master-scalability-100
### Which tests are failing?
- ClusterLoaderV2: huge-service overall (testing/huge-service/config.yaml)
- ClusterLoaderV2: huge-service: [step: 11] gathering measurements [01] - APIResponsivenessPrometheusSimple
![Screenshot from 2023-... | [Failing Test] [sig-scalability] gce-cos-master-scalability-100 | https://api.github.com/repos/kubernetes/kubernetes/issues/115618/comments | 5 | 2023-02-08T14:16:54Z | 2023-02-08T17:02:33Z | https://github.com/kubernetes/kubernetes/issues/115618 | 1,576,204,703 | 115,618 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
master-informing
- capz-windows-containerd-master
### Which tests are failing?
`capz-e2e: [It] Conformance Tests conformance-tests`

... | [Flaking Test] capz-windows-containerd-master | https://api.github.com/repos/kubernetes/kubernetes/issues/115612/comments | 8 | 2023-02-08T10:44:12Z | 2023-02-22T20:29:27Z | https://github.com/kubernetes/kubernetes/issues/115612 | 1,575,889,206 | 115,612 |
[
"kubernetes",
"kubernetes"
] | i deployed offline k8s kubeadm cluster but if i check the status of kubelet i'm getting below error logs i'm not able to identify exact issue
5140 manager.go:1121] Failed to create existing container: /kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-pod192a343d_2f00_4cc3_b1df_be27655bf577.slice/crio-8c... | kubelet error: failed to create existing container: /kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort | https://api.github.com/repos/kubernetes/kubernetes/issues/115609/comments | 7 | 2023-02-08T06:14:46Z | 2023-10-04T14:17:09Z | https://github.com/kubernetes/kubernetes/issues/115609 | 1,575,547,923 | 115,609 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
master-blocking
- build-master
### Which tests are failing?
ci-kubernetes-build.Overall

### Since when has it been failing?
202... | [Failing test] build-master | https://api.github.com/repos/kubernetes/kubernetes/issues/115605/comments | 31 | 2023-02-08T04:43:53Z | 2023-02-10T06:18:46Z | https://github.com/kubernetes/kubernetes/issues/115605 | 1,575,462,732 | 115,605 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
When using network policy to specify address to access a namespace, all pods in the space where the rule is located cannot be accessed through name.namespace.svc.cluster.local.
Kubernetes Version: v1.23.8
Calico Version: v3.23.2
Yaml file:
apiVersion: networking.k8s.io/v1
kind: Net... | Network policy specifies that access to a namespace failed | https://api.github.com/repos/kubernetes/kubernetes/issues/115602/comments | 7 | 2023-02-08T02:40:42Z | 2023-07-08T09:44:53Z | https://github.com/kubernetes/kubernetes/issues/115602 | 1,575,362,078 | 115,602 |
[
"kubernetes",
"kubernetes"
] | Since we already have a few issues about this, I decided to create one more:
https://github.com/kubernetes/client-go/issues/970
https://github.com/kubernetes/client-go/issues/1184
Interesting one: https://github.com/grafana/xk6-kubernetes/pull/81
https://github.com/kubernetes/kubernetes/issues/103816
https://githu... | Server-Side Apply (and fieldmanagement) is missing in client-go/fake | https://api.github.com/repos/kubernetes/kubernetes/issues/115598/comments | 10 | 2023-02-08T00:20:28Z | 2024-07-05T14:06:00Z | https://github.com/kubernetes/kubernetes/issues/115598 | 1,575,237,668 | 115,598 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
Extend the rest client so the user can provide an optional backoff base / duration when creating the RESTClient.
### Why is this needed?
The rest client uses environment variables for configuring the backoff manager for retries on GET requests which error out due to connection ... | Allow per-client configuration for rest client backoff manager | https://api.github.com/repos/kubernetes/kubernetes/issues/115596/comments | 10 | 2023-02-07T22:59:46Z | 2025-02-12T22:09:01Z | https://github.com/kubernetes/kubernetes/issues/115596 | 1,575,147,391 | 115,596 |
[
"kubernetes",
"kubernetes"
] | As part of KMSv2, we should setup a e2e test suite that creates a cluster with the encryption configuration + provider configured and runs the existing tests against those to validate.
- [x] Add test-infra job for running the cluster create + test using `kubetest2` https://github.com/kubernetes/test-infra/pull/28728... | [KMSv2] Add test suite | https://api.github.com/repos/kubernetes/kubernetes/issues/115595/comments | 4 | 2023-02-07T21:48:24Z | 2023-03-06T23:41:45Z | https://github.com/kubernetes/kubernetes/issues/115595 | 1,575,070,005 | 115,595 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
The x-kubernetes-sensitive-string extension in a Custom Resource Definition (CRD) provides a way to indicate to Kubernetes and other components that the values in a particular field should be treated as sensitive and protected.
When a field is marked as sensitive using this exte... | Add `x-kubernetes-sensitive-string` extension to CRDs | https://api.github.com/repos/kubernetes/kubernetes/issues/115592/comments | 10 | 2023-02-07T19:42:43Z | 2024-09-20T18:50:26Z | https://github.com/kubernetes/kubernetes/issues/115592 | 1,574,922,593 | 115,592 |
[
"kubernetes",
"kubernetes"
] | Currently, the documentation for Testgrid is very high level and does not have an "Installation and usage" section similar to kind's https://kind.sigs.k8s.io/.
The info provided lacks the implementation details to get a quick start with open source tools to setup the Testgrid backend. More specifically, we need the ex... | Documentation for Testgrid | https://api.github.com/repos/kubernetes/kubernetes/issues/115591/comments | 4 | 2023-02-07T19:15:38Z | 2023-02-07T21:00:55Z | https://github.com/kubernetes/kubernetes/issues/115591 | 1,574,891,675 | 115,591 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
master-blocking
gce-cos-master-scalability-100
### Which tests failed?
**ClusterLoaderV2.huge-service overall (testing/huge-service/config.yaml)**
**ClusterLoaderV2.huge-service: [step: 11] gathering measurements [01] - APIResponsivenessPrometheusSimple**
 | https://api.github.com/repos/kubernetes/kubernetes/issues/115589/comments | 8 | 2023-02-07T18:53:01Z | 2023-02-22T20:38:31Z | https://github.com/kubernetes/kubernetes/issues/115589 | 1,574,862,116 | 115,589 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
We used to only calculate regular containers. However, initContainers should also be counted.
### Why is this needed?
https://github.com/kubernetes/kubernetes/pull/110382#discussion_r897128424
Because initContainers are also pull request, we need to consider all initConta... | ImageLocality plugin should consider initContainers when scoring during scheduling | https://api.github.com/repos/kubernetes/kubernetes/issues/115587/comments | 15 | 2023-02-07T16:42:32Z | 2023-07-10T18:11:55Z | https://github.com/kubernetes/kubernetes/issues/115587 | 1,574,663,251 | 115,587 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I have been facing two weire issues 1.Though the targetCPUUtilizationPercentage breachs the pod not scaling up 2.Pods are not scaled as per the policy
**Though the targetCPUUtilizationPercentage breachs the pod not scaling up ** I have been set the targetCPUUtilizationPercentage as 65 percent and... | kubernetes HPA not justifying the StabilizationWindowSeconds and scaleup policy by pod count | https://api.github.com/repos/kubernetes/kubernetes/issues/115586/comments | 6 | 2023-02-07T16:28:22Z | 2023-07-08T09:44:52Z | https://github.com/kubernetes/kubernetes/issues/115586 | 1,574,639,115 | 115,586 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
We are running Kubernetes 1.25.5 and trying to configure kube-controller-manager to be less verbose when logging.
We run kube-controller-manager as a static pod created by Kubelet and use the following command where we pass `--v=0`:
```
spec:
containers:
- command:
- kube-controller-ma... | cronjob controller: reconsider log verbosity | https://api.github.com/repos/kubernetes/kubernetes/issues/115574/comments | 14 | 2023-02-07T09:14:55Z | 2024-02-29T19:55:23Z | https://github.com/kubernetes/kubernetes/issues/115574 | 1,573,960,145 | 115,574 |
[
"kubernetes",
"kubernetes"
] | Tar file doesn't seem to be corrupt as extracting this tar file works.. but kubectl cp immediately fails with error below -
tar: invalid tar magic
command terminated with exit code 1
This tar is around 32GB in size and I am guessing this is some misleading error because even if the tar file was invalid, what do... | kubectl cp of a tar file fails with invalid tar magic | https://api.github.com/repos/kubernetes/kubernetes/issues/115573/comments | 10 | 2023-02-07T08:35:21Z | 2025-01-16T02:07:31Z | https://github.com/kubernetes/kubernetes/issues/115573 | 1,573,904,702 | 115,573 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
in larget k8s cluster. i have encountered a problem sometimes as follows:
when i delete a deploy in foreground cascading deletion。i found:
(1) the deploy has deletetimeStamp and foreground finalizer
(2) the rs has deletetimeStamp and foreground finalizer
(3) the pod is running, has not ... | use foreground cascading deletion will be stuck when garbagecontroller lost the firset update event(add deletetimestamp and finalizer) after delete | https://api.github.com/repos/kubernetes/kubernetes/issues/115570/comments | 17 | 2023-02-07T07:50:03Z | 2024-04-25T16:47:40Z | https://github.com/kubernetes/kubernetes/issues/115570 | 1,573,845,970 | 115,570 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
**nodeport Port is not displayed**
```
root@k8s-master1:~# kubectl get pod,svc,ep
NAME READY STATUS RESTARTS AGE
pod/helloworld-774b4886b7-d957k 1/1 Running 0 8m1s
pod/helloworld-774b4886b7-h8lwf 1/1 Running 0 8m1s
NAME ... | nodeport Port is not displayed | https://api.github.com/repos/kubernetes/kubernetes/issues/115568/comments | 6 | 2023-02-07T05:46:37Z | 2023-02-07T11:10:00Z | https://github.com/kubernetes/kubernetes/issues/115568 | 1,573,723,921 | 115,568 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
request handler logic spins up goroutine, and most of them has the style:
```
go dunc() {
defer utilruntime.HandleCrash()
...
}
```
`HandleCrash` will re-raise the panic after handling it, if `ReallyCrash` is true. (`ReallyCrash` is true by default, and to my knowledge it's no... | apiserver: panic from goroutine spun up by request handler should not crash the apiserver | https://api.github.com/repos/kubernetes/kubernetes/issues/115565/comments | 13 | 2023-02-07T00:38:22Z | 2024-09-30T20:35:32Z | https://github.com/kubernetes/kubernetes/issues/115565 | 1,573,500,284 | 115,565 |
[
"kubernetes",
"kubernetes"
] | I am hoping to be able to do:
```go
desiredState := ... some applyconfig ...
currentState := applyconfiguration.ExtractDeployment(Get(...))
if !Equal(desired, current) {
Apply(applyconfig)
}
```
The intent here is to avoid needless Apply calls. Note `Get()` is basically free since its an informer, so th... | `applyconfiguration.Extract` has poor interaction with defaulting | https://api.github.com/repos/kubernetes/kubernetes/issues/115563/comments | 6 | 2023-02-07T00:02:10Z | 2024-06-07T16:05:27Z | https://github.com/kubernetes/kubernetes/issues/115563 | 1,573,473,649 | 115,563 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are flaking?
sig-release-master-blocking
verify-master
### Which tests are flaking?
verify.codegen
### Since when has it been flaking?
between 11:50 PT - 1:49 PT
### Testgrid link
https://k8s-testgrid.appspot.com/sig-release-master-blocking#verify-master
### Reason for failure (if possib... | [Flaky Test] verify-master verify-codegen.sh issue | https://api.github.com/repos/kubernetes/kubernetes/issues/115562/comments | 3 | 2023-02-06T23:47:01Z | 2023-02-09T09:01:26Z | https://github.com/kubernetes/kubernetes/issues/115562 | 1,573,462,726 | 115,562 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are ~~failing~~ flaky?
kind-master-parallel
kind-ipv6-master-parallel
### Which tests were failing?
Overall was failing
### When has it been failing?
from 11:41am PT to 2:41 PT
### Testgrid link
https://k8s-testgrid.appspot.com/sig-release-master-blocking#kind-master-parallel
https://k8s-testgrid.... | [Flaky Test] kind-master-parallel and kind-ipv6-master-parallel | https://api.github.com/repos/kubernetes/kubernetes/issues/115560/comments | 5 | 2023-02-06T23:13:28Z | 2023-02-09T16:34:25Z | https://github.com/kubernetes/kubernetes/issues/115560 | 1,573,435,446 | 115,560 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Aggregated discovery caches when fetching from legacy discovery (https://github.com/kubernetes/kubernetes/blob/1ba14700a5448f0cb54b9f5a79100eea71d05e65/staging/src/k8s.io/kube-aggregator/pkg/apiserver/handler_discovery.go#L295-L297).
This causes apiservices who share the same service key to fetch... | Aggregated Discovery should not cache on legacy fallback | https://api.github.com/repos/kubernetes/kubernetes/issues/115559/comments | 2 | 2023-02-06T23:01:39Z | 2023-02-22T06:37:57Z | https://github.com/kubernetes/kubernetes/issues/115559 | 1,573,421,905 | 115,559 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs were failing?
Conformance - GCE - master - kubetest2
### Which tests failed?
It looks like the overall build may be failing
### When has it been failing?
From 1:35pm - 3:35pm
### Testgrid link
https://k8s-testgrid.appspot.com/sig-release-master-blocking#Conformance%20-%20GCE%20-%20m... | [Flaky Test] Conformance - GCE - master - kubetest2 | https://api.github.com/repos/kubernetes/kubernetes/issues/115556/comments | 4 | 2023-02-06T20:50:21Z | 2023-02-07T21:19:33Z | https://github.com/kubernetes/kubernetes/issues/115556 | 1,573,257,145 | 115,556 |
[
"kubernetes",
"kubernetes"
] | null | [Failing Test] Conformance - GCE - master - kubetest2 | https://api.github.com/repos/kubernetes/kubernetes/issues/115555/comments | 2 | 2023-02-06T20:44:12Z | 2023-02-06T20:47:42Z | https://github.com/kubernetes/kubernetes/issues/115555 | 1,573,250,691 | 115,555 |
[
"kubernetes",
"kubernetes"
] | This issue is to discuss whether we can change the `Started` field of `ContainerStatus` from pointer to non-pointer bool value. The pointer type is inconsistent with other field `Ready`. The semantic of `Started` being `null` is undefined and it is not ideal if users will use `Started` field `null` value as indication ... | Clarify ContainerStatus.Started null value and initialize the value for Init containers | https://api.github.com/repos/kubernetes/kubernetes/issues/115553/comments | 18 | 2023-02-06T17:40:54Z | 2025-03-05T07:37:17Z | https://github.com/kubernetes/kubernetes/issues/115553 | 1,573,000,217 | 115,553 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Please update the Kustomize packages in cli-runtime to `sigs.k8s.io/kustomize/api@v0.13.1` and `sigs.k8s.io/kustomize/kyaml@v0.14.0`. Every project that imports both `cli-runtime` and the new `kustomize/api` result in compilation error due to the removal of `DoLegacyResourceSort` which is used in... | Update cli-runtime to Kustomize v5 | https://api.github.com/repos/kubernetes/kubernetes/issues/115547/comments | 11 | 2023-02-06T13:56:27Z | 2023-04-07T07:49:25Z | https://github.com/kubernetes/kubernetes/issues/115547 | 1,572,614,922 | 115,547 |
[
"kubernetes",
"kubernetes"
] | When I use CronJob, it creates Pods. But hostname timestamp of the Pods sometimes 10 digits, sometimes 8 digits.
10 digits, K8S version is `v1.18.5-dirty`:

8 digits, K8S version is `v1.21.5-eki.0`:
... | Why CronJob Pod hostname timestamp sometimes 10 digits, sometimes 8 digits ? | https://api.github.com/repos/kubernetes/kubernetes/issues/115544/comments | 8 | 2023-02-06T11:08:18Z | 2023-07-08T01:43:52Z | https://github.com/kubernetes/kubernetes/issues/115544 | 1,572,495,308 | 115,544 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Was using the containerd client api to update the cpusets(to use the CPUs 10-23) of the container at runtime.
Container inspection for that particular container showed the CPUs as 10-23
````
"linux": {
"resources": {
"devices": [
{
... | Pod cgroup cpusets is not getting updated when try to pin the cpus of a container | https://api.github.com/repos/kubernetes/kubernetes/issues/115541/comments | 7 | 2023-02-06T09:27:24Z | 2023-03-02T07:08:18Z | https://github.com/kubernetes/kubernetes/issues/115541 | 1,572,217,655 | 115,541 |
[
"kubernetes",
"kubernetes"
] | ### Failure cluster [6e99635281af691f67af](https://go.k8s.io/triage#6e99635281af691f67af)
The test failed failed after https://github.com/kubernetes/kubernetes/pull/113298 was merged.
E2eNode Suite [It] [sig-node] HugePages [Serial] [Feature:HugePages][NodeSpecialFeature:HugePages] when start the pod with the res... | Failure cluster [6e996352...]: Node didn't have enough resource: hugepages-2Mi | https://api.github.com/repos/kubernetes/kubernetes/issues/115539/comments | 3 | 2023-02-06T07:49:10Z | 2023-02-06T14:11:03Z | https://github.com/kubernetes/kubernetes/issues/115539 | 1,572,083,803 | 115,539 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When I update a `Deployment` with `Recreate` Strategy. Its conditions remains `Complete` (when `status.observedGeneration` == `spec.generation`) until the older ReplicaSet finished scaled to 0.
### What did you expect to happen?
According to the doc https://kubernetes.io/docs/concepts/workloa... | Deployment with Recreate Strategy status incorrect when rolling out | https://api.github.com/repos/kubernetes/kubernetes/issues/115538/comments | 16 | 2023-02-06T07:43:13Z | 2025-02-25T15:09:47Z | https://github.com/kubernetes/kubernetes/issues/115538 | 1,572,078,182 | 115,538 |
[
"kubernetes",
"kubernetes"
] | If swap is disabled then if there is really a case for requesting hugepages? If no data can be swapped out to secondary storage then how a request for hugepages by a pod can help improving the performance? | Manage HugePages | https://api.github.com/repos/kubernetes/kubernetes/issues/115545/comments | 8 | 2023-02-06T07:12:22Z | 2023-07-06T13:24:52Z | https://github.com/kubernetes/kubernetes/issues/115545 | 1,572,499,982 | 115,545 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
During our research on non-blocking concurrency bugs in kubernetes, we discovered a potential Data Race in the program. Specifically,there are two confilicting operations on the field "rev", where
the read operation at:...kubernetes/vendor/go.etcd.io/etcd/client/v3/watch.go:848, and the write ope... | Data Race on the field ''rev'' | https://api.github.com/repos/kubernetes/kubernetes/issues/115534/comments | 3 | 2023-02-06T02:27:51Z | 2023-03-06T13:31:21Z | https://github.com/kubernetes/kubernetes/issues/115534 | 1,571,785,929 | 115,534 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
```
......
135 finished := false
136 wg := sync.WaitGroup{}
137 wg.Add(1)
138 go func() {
139 rl.Accept()
140 finished = true
141 wg.Done()
142 }()
143
144 // Wait some time to make sure it never finished.
145 time.Sleep(time.Second)
146 if finished {
147 t.Error("Ac... | Inappropriate use of method "time.Sleep(time.Second)" | https://api.github.com/repos/kubernetes/kubernetes/issues/115530/comments | 6 | 2023-02-05T15:41:45Z | 2023-09-27T03:41:20Z | https://github.com/kubernetes/kubernetes/issues/115530 | 1,571,483,427 | 115,530 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When the `ClusterCIDR` is created *after* a node has booted, addresses are not defined;
```
> kubectl get cc -A
No resources found
> kubectl create -f kubernetes/clustercidr.yaml
clustercidr.networking.k8s.io/default created
> kubectl get cc -A
NAME PERNODEHOSTBITS IPV4 IP... | MultiCIDRRangeAllocator requires node reboot to assign ranges | https://api.github.com/repos/kubernetes/kubernetes/issues/115528/comments | 8 | 2023-02-05T08:31:17Z | 2023-02-07T11:33:02Z | https://github.com/kubernetes/kubernetes/issues/115528 | 1,571,312,811 | 115,528 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
# Problem
The current support of the load distribution method `sh` and `mh` in kube-proxy ipvs mode only performs hashing of source IP address to select endpoints. As a result, all connections from a single client (i.e. from a particular source IP) are always forwarded to only one... | kube-proxy IPVS mode configured with method SourceHash and Maglev should evenly distribute connections to all endpoints | https://api.github.com/repos/kubernetes/kubernetes/issues/115526/comments | 7 | 2023-02-05T06:21:21Z | 2024-11-05T05:50:03Z | https://github.com/kubernetes/kubernetes/issues/115526 | 1,571,276,635 | 115,526 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I'm the maintainer of [kube-audit-rest](https://github.com/RichardoC/kube-audit-rest) which relies on the fact that all creation/mutation API calls go through the [dynamic admission process](https://kubernetes.io/docs/reference/access-authn-authz/extensible-admission-controllers/) including exec a... | "pods/exec", "pods/attach", portforward not included in resources: ["*"] for dynamic admission webhooks configuration | https://api.github.com/repos/kubernetes/kubernetes/issues/115523/comments | 7 | 2023-02-04T20:22:46Z | 2023-04-20T16:59:06Z | https://github.com/kubernetes/kubernetes/issues/115523 | 1,571,111,033 | 115,523 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
`kubectl` under Linux keeps `cache` and `http-cache` directories under `~/.kube` by default.
Many Linux application have adopted )XDG base directory specification)[https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html] that specifies, beside other director... | Make kubectl respect XDG base directory specification for caches | https://api.github.com/repos/kubernetes/kubernetes/issues/115522/comments | 9 | 2023-02-04T17:24:04Z | 2023-02-08T11:05:54Z | https://github.com/kubernetes/kubernetes/issues/115522 | 1,571,040,527 | 115,522 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
One of k8S cluster node is having a disk issue(90%+ used), but kubelet flip the disk status between NodeHasNoDiskPressure and NodeHasDiskPressure.
``` shell
Feb 03 18:58:45 ip-10-128-18-28.ca-central-1.compute.internal kubelet[5402]: I0203 18:58:45.040154 5402 kubelet_node_status.go:668] "Re... | Kubelet_node_status_go flip DiskPressure status periodically | https://api.github.com/repos/kubernetes/kubernetes/issues/115516/comments | 6 | 2023-02-03T23:18:49Z | 2023-02-08T18:20:18Z | https://github.com/kubernetes/kubernetes/issues/115516 | 1,570,609,002 | 115,516 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
We introduced PodSchedulingReadiness in https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/3521-pod-scheduling-readiness;
The main use case for this feature was to enable building external resource controllers (like extended schedulers, dynamic quota m... | Mutable Pod scheduling directives when gated | https://api.github.com/repos/kubernetes/kubernetes/issues/115513/comments | 11 | 2023-02-03T18:43:22Z | 2024-01-24T06:06:01Z | https://github.com/kubernetes/kubernetes/issues/115513 | 1,570,287,431 | 115,513 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
```yaml
apiVersion: apps/v1
kind: Deployment
metadata:
name: alpine
labels:
app: alpine
spec:
selector:
matchLabels:
app: alpine
template:
metadata:
labels:
app: alpine
spec:
containers:
- name: sleep
image: alpine... | Pod fails to terminate when FailedMount | https://api.github.com/repos/kubernetes/kubernetes/issues/115511/comments | 5 | 2023-02-03T17:51:55Z | 2023-02-08T18:24:49Z | https://github.com/kubernetes/kubernetes/issues/115511 | 1,570,227,848 | 115,511 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
A client wants the ability to control active deadlines on a container-by-container basis.
Currently you can set active deadlines on a pod basis and at the job level. I don't believe it is possible to say that I want to restrict a particular container (or init-container) to be... | Feature: Container level control of active deadlines | https://api.github.com/repos/kubernetes/kubernetes/issues/115507/comments | 6 | 2023-02-03T14:37:06Z | 2023-07-04T04:03:39Z | https://github.com/kubernetes/kubernetes/issues/115507 | 1,569,941,538 | 115,507 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When a service is created with ipFamilyPolicy: RequireDualStack, Kubeproxy is creating only Loadbalancer policies for IPV4 and not for IPV6.
### What did you expect to happen?
Loadbalancer policies should be created for both IPV4 and IPV6 in Dualstack mode.
### How can we reproduce it (as minimal... | [Winkernel Proxier] Issue with Loadbalancer policy creation for IPV6 endpoints in Dualstack mode. | https://api.github.com/repos/kubernetes/kubernetes/issues/115501/comments | 2 | 2023-02-03T05:21:33Z | 2023-02-03T07:46:29Z | https://github.com/kubernetes/kubernetes/issues/115501 | 1,569,240,840 | 115,501 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
1. Proposed name structure change for ResizePolicy. Ref: https://github.com/kubernetes/kubernetes/pull/111946#discussion_r1063862866
2. Set defaults to RestartNotRequired for CPU and memory. Ref: https://github.com/kubernetes/kubernetes/pull/102884#discussion_r1093804103
### Why ... | [FG:InPlacePodVerticalScaling] ResizePolicy name structure change and set defaults | https://api.github.com/repos/kubernetes/kubernetes/issues/115494/comments | 4 | 2023-02-03T02:28:06Z | 2023-05-03T23:07:46Z | https://github.com/kubernetes/kubernetes/issues/115494 | 1,569,108,424 | 115,494 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
```
kinder.test.workflow: task-04-join
```
> I0202 23:52:51.179209 289 etcd.go:475] [etcd] Promoting the learner b86d3d0b9ee75c60 failed: etcdserver: can only promote a learner member which is in sync with leader
> etcdserver: can only promote a learner member which is in sync wit... | kubeadm: kinder.test.workflow task-04-join failed for learner mode | https://api.github.com/repos/kubernetes/kubernetes/issues/115492/comments | 4 | 2023-02-03T01:38:11Z | 2023-02-08T08:04:33Z | https://github.com/kubernetes/kubernetes/issues/115492 | 1,569,057,259 | 115,492 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
With limited frequency, various nodes will experience a Kubelet failure and log "Kubelet is unhealthy!".
This log is produced by the health monitor script for GCE:
https://github.com/kubernetes/kubernetes/blob/49ddc510bc6b57fa430f779372b71144d328995c/cluster/gce/gci/health-monitor.sh#L65
Th... | GCE health monitor detects failed Kubelet and restarts | https://api.github.com/repos/kubernetes/kubernetes/issues/115491/comments | 9 | 2023-02-03T01:20:35Z | 2024-02-18T06:56:17Z | https://github.com/kubernetes/kubernetes/issues/115491 | 1,569,028,494 | 115,491 |
[
"kubernetes",
"kubernetes"
] | xref https://github.com/kubernetes/community/pull/7063
I am sure that such collisions are rare (though I didn't see a metric - could add one!) but it seems surprising that our API offers a "generate a name for me" option which can fail with "name in use".
The docs used to imply that apiserver will retry upon name... | apiserver does not retry generateName on collisions | https://api.github.com/repos/kubernetes/kubernetes/issues/115489/comments | 13 | 2023-02-02T22:18:03Z | 2025-01-13T23:53:50Z | https://github.com/kubernetes/kubernetes/issues/115489 | 1,568,867,998 | 115,489 |
[
"kubernetes",
"kubernetes"
] | Request on behalf of downstream team(s) like EKS who would love to know
- there are tags in kubernetes/release repository, Does the release team use the tag when making a release? (or they just use what's in `master`)
- If yes, Do we publish which version of k/release is used in a specific release of kubernetes (sim... | Publish tagged version of kubernetes/release used for making a kubernetes release | https://api.github.com/repos/kubernetes/kubernetes/issues/115486/comments | 10 | 2023-02-02T18:28:08Z | 2024-01-19T15:59:58Z | https://github.com/kubernetes/kubernetes/issues/115486 | 1,568,561,557 | 115,486 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I am writing to report an issue with the latest version of Kubernetes in Azure, version v1.24.6. Before this version, when creating a Kubernetes cluster, the service account and secrets were automatically created and everything worked smoothly. However, with version v1.24.6, I have encountered an ... | Secrets does not creating | https://api.github.com/repos/kubernetes/kubernetes/issues/115483/comments | 17 | 2023-02-02T17:47:58Z | 2024-03-11T17:02:32Z | https://github.com/kubernetes/kubernetes/issues/115483 | 1,568,505,127 | 115,483 |
[
"kubernetes",
"kubernetes"
] | This is a tracking issue for the work that needs to be cleaned-up after API streaming is implemented ([KEP]: https://github.com/kubernetes/enhancements/issues/3157)
TODO:
- [ ] apiserver: once the `WatchList` feature gate is always on register `SetListOptionsDefaults` function in the scheme ([xref](https://githu... | API streaming feature tracking | https://api.github.com/repos/kubernetes/kubernetes/issues/115478/comments | 4 | 2023-02-02T16:32:16Z | 2024-05-09T10:08:15Z | https://github.com/kubernetes/kubernetes/issues/115478 | 1,568,367,543 | 115,478 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
master-blocking
- build-master-fast
### Which tests are failing?
- ci-kubernetes-build-fast.Overall

### Since when has it been fai... | [Failing test] build-master-fast | https://api.github.com/repos/kubernetes/kubernetes/issues/115477/comments | 7 | 2023-02-02T16:20:40Z | 2023-02-03T08:27:29Z | https://github.com/kubernetes/kubernetes/issues/115477 | 1,568,349,731 | 115,477 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are flaking?
release-master-informing
- capz-windows-master
### Which tests are flaking?
`Kubernetes e2e suite.[It] [sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute prestop exec hook properly [NodeConformance] [Conformance]`
### Since when has it be... | [Flaky test] capz-windows-master | https://api.github.com/repos/kubernetes/kubernetes/issues/115470/comments | 11 | 2023-02-02T08:31:59Z | 2023-08-10T16:45:34Z | https://github.com/kubernetes/kubernetes/issues/115470 | 1,567,568,658 | 115,470 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
After pod is ready, Liveness probe and Readiness probe detection fails, displaying:
```
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning Unhealthy 21m (x44 over 2d1h) kubelet Liveness probe failed: Get ... | Liveness probe failed: context deadline exceeded (Client.Timeout exceeded while awaiting headers) | https://api.github.com/repos/kubernetes/kubernetes/issues/115469/comments | 6 | 2023-02-02T08:02:45Z | 2023-09-14T09:30:10Z | https://github.com/kubernetes/kubernetes/issues/115469 | 1,567,526,632 | 115,469 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
ref: https://github.com/kubernetes/enhancements/issues/1610
This is what we actually need to do for the graduation to beta:
- [x] ⚠️ [bug] change HPA controller to ignore `ContainerResource` when it's disabled by the feature gate.
- https://github.com/kubernetes/kuberne... | The graduation HPA container resource metrics to beta | https://api.github.com/repos/kubernetes/kubernetes/issues/115467/comments | 14 | 2023-02-02T03:32:42Z | 2023-03-15T23:34:32Z | https://github.com/kubernetes/kubernetes/issues/115467 | 1,567,263,987 | 115,467 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
the default value of the `host` label is `none` for all client metrics, see
https://github.com/kubernetes/kubernetes/blob/1f02f43ec6910cbcd46222b16a2f3965458e5e45/staging/src/k8s.io/client-go/rest/request.go#L792-L795
in a query, we want the user to use `{host!=""}` rather than `{host!="non... | client-go: set the default of the 'host' label to an empty string for client metrics | https://api.github.com/repos/kubernetes/kubernetes/issues/115461/comments | 9 | 2023-02-01T23:05:28Z | 2023-04-20T16:59:00Z | https://github.com/kubernetes/kubernetes/issues/115461 | 1,566,990,525 | 115,461 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
If you create a pod that mounts a volume from a secret or a config-map and then you delete that pod, it takes an abnormally long time to delete the pod.
### What did you expect to happen?
I would expect a similar time for deletion from a successful case as an unsuccesful case.
### How can w... | Deleting pods that mount volumes from missing config-maps/secrets causes an abnormal deletion time. | https://api.github.com/repos/kubernetes/kubernetes/issues/115459/comments | 14 | 2023-02-01T22:28:46Z | 2023-04-18T19:54:27Z | https://github.com/kubernetes/kubernetes/issues/115459 | 1,566,942,847 | 115,459 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are flaking?
k8s.io/kubernetes/test/integration/clustercidr
### Which tests are flaking?
TestIPAMMultiCIDRRangeAllocatorClusterCIDRTieBreak
### Since when has it been flaking?
Noticed today 01/31/2023
### Testgrid link
_No response_
### Reason for failure (if possible)
_No resp... | Flaky ClusterCIDR integration test | https://api.github.com/repos/kubernetes/kubernetes/issues/115440/comments | 6 | 2023-01-31T21:31:07Z | 2023-01-31T22:33:37Z | https://github.com/kubernetes/kubernetes/issues/115440 | 1,565,032,080 | 115,440 |
[
"kubernetes",
"kubernetes"
] | What is the ask?
If we were to assume all replicas of a Statefulset can be bucketed into a fixed number of 'upgrade buckets', can Statefulset controller support rolling update based on these 'upgrade buckets'
What is the benefit?
* Shorter upgrade times
* Constant time upgrade regardless of number of replicas
... | Feature request: Upgrade buckets in statefulsets | https://api.github.com/repos/kubernetes/kubernetes/issues/115436/comments | 7 | 2023-01-31T19:31:01Z | 2023-07-10T20:13:52Z | https://github.com/kubernetes/kubernetes/issues/115436 | 1,564,884,584 | 115,436 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When using PDBs with `MaxUnavailable` or `MinAvailable` (percentage), it is not supported to reference pods via a PDB selector, that do not have a supported controller owner reference:
- Deployment, ReplicationController, ReplicaSet, and StatefulSet controllers
- or a resource implementing `/sca... | Inform users about unsupported PDB options | https://api.github.com/repos/kubernetes/kubernetes/issues/115435/comments | 6 | 2023-01-31T19:26:02Z | 2023-03-06T16:19:16Z | https://github.com/kubernetes/kubernetes/issues/115435 | 1,564,879,010 | 115,435 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are ~~failing~~ flakey?
sig-release-master-blocking
integration-master
### Which tests are ~~failing~~ flakey?
Different tests have been failing for 3 builds between 06:03 PT and 08:14 PT. From latest:
1. [build 1620452416354783232](https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kube... | [Flakey Test] integration-master | https://api.github.com/repos/kubernetes/kubernetes/issues/115432/comments | 5 | 2023-01-31T18:21:00Z | 2023-02-01T08:13:00Z | https://github.com/kubernetes/kubernetes/issues/115432 | 1,564,801,005 | 115,432 |
[
"kubernetes",
"kubernetes"
] | ## Feature requested
Allow type LoadBalancer for Headless service for specialized proxiers. A service of type LoadBalancer with clusterIP None is rejected with:
```
# kubectl create -f /etc/kubernetes/svc-headless-lb/svc.yaml
The Service "alpine" is invalid: spec.clusterIPs[0]: Invalid value: "None": may not b... | Allow type LoadBalancer for Headless service for specialized proxiers | https://api.github.com/repos/kubernetes/kubernetes/issues/115429/comments | 16 | 2023-01-31T17:28:01Z | 2023-02-02T20:52:50Z | https://github.com/kubernetes/kubernetes/issues/115429 | 1,564,728,545 | 115,429 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
sig-release-master-blocking
gce-cos-master-scalability-100
gce-cos-master-default
### Which tests are failing?
Overall
### Since when has it been failing?
since 1/31 07:41 PT
### Testgrid link
https://k8s-testgrid.appspot.com/sig-release-master-blocking#gce-cos-master-... | [Failing Test] gce-cos-master-scalability-100 failing since 1/31 07:41 PT | https://api.github.com/repos/kubernetes/kubernetes/issues/115427/comments | 8 | 2023-01-31T17:01:40Z | 2023-02-01T07:37:50Z | https://github.com/kubernetes/kubernetes/issues/115427 | 1,564,690,717 | 115,427 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
rest.Interface supports `SetHeader` functionality. Thereby, consumers can use use server side printing for the resources derived from `rest.Interface`.
### Why is this needed?
Currently in order to use server side printing, Accept header should be [set accordingly](https://github... | Support SetHeader functionality in rest.Interface | https://api.github.com/repos/kubernetes/kubernetes/issues/115421/comments | 13 | 2023-01-31T09:33:11Z | 2023-01-31T21:20:24Z | https://github.com/kubernetes/kubernetes/issues/115421 | 1,563,960,415 | 115,421 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
The pods that you are raising through kubernetes, once they are raised they do not pick up the time zone that was specified in the node or in the deploy, so the start time is always incorrect.
### What did you expect to happen?
The correct way to specify the time zone of pods.
### How can we repr... | Pods that are built with kubectl do not catch the specified time zone. | https://api.github.com/repos/kubernetes/kubernetes/issues/115419/comments | 7 | 2023-01-31T08:21:05Z | 2023-07-01T07:32:36Z | https://github.com/kubernetes/kubernetes/issues/115419 | 1,563,861,749 | 115,419 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
while using the verbosity command "kubectl get po <pod name> --v=10" it returns to the same as "--v=9" although there is no level of verbosity as 10.
### What did you expect to happen?
it should through an error
### How can we reproduce it (as minimally and precisely as possible)?
`kubectl get p... | verbosity above 9 doesn't through error | https://api.github.com/repos/kubernetes/kubernetes/issues/115415/comments | 6 | 2023-01-31T07:04:34Z | 2023-02-01T02:03:28Z | https://github.com/kubernetes/kubernetes/issues/115415 | 1,563,772,149 | 115,415 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are flaking?
sig-release-master-blocking
integration-master
gce-cos-master-alpha-features
gce-cos-master-reboot
gce-cos-master-scalability-100
### Which tests are flaking?
None. The "Overall" build results in a (?) result, and says "Unknown: Build is too old to process".
### Since when ha... | ["Flaky" Tests/Test Grid Bug] Various sig-release-master-blocking jobs with "Unknown: Build is too old to process" | https://api.github.com/repos/kubernetes/kubernetes/issues/115410/comments | 7 | 2023-01-30T22:01:36Z | 2023-03-12T01:45:44Z | https://github.com/kubernetes/kubernetes/issues/115410 | 1,563,277,774 | 115,410 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When there is a client that requests long lists and does not read them (before the 1-minute request-handling timeout), and in the relevant priority level the hand size times the max width (which is currently fixed in the code to be 10) exceeds or is not much smaller than the concurrency limit, this ... | APF fails when conc. limit is not bigger than hand size X max width | https://api.github.com/repos/kubernetes/kubernetes/issues/115409/comments | 11 | 2023-01-30T20:49:04Z | 2024-07-25T20:16:08Z | https://github.com/kubernetes/kubernetes/issues/115409 | 1,563,179,546 | 115,409 |
[
"kubernetes",
"kubernetes"
] | Kubernetes 1.24
Ubuntu 20.04
Kernel 5.8.0-53-generic
NOTE: Regarding formatting of this question, could not figure out why certain lines were crossed out and why I could not remove the bullet associated with the emptyDir.
_maintainer edit: have marked the relevant bits as preformatted_
Problem: Worker node ... | Kubernetes pod's request for 8 x 1Gi hugepages consumes all 16 x 1Gi hugepages on worker node | https://api.github.com/repos/kubernetes/kubernetes/issues/115581/comments | 7 | 2023-01-30T20:29:38Z | 2023-02-07T16:21:03Z | https://github.com/kubernetes/kubernetes/issues/115581 | 1,574,315,950 | 115,581 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Pod Security Standards (https://kubernetes.io/docs/concepts/security/pod-security-standards/) went beta at v1.23. Pod Security Standards are direct ascendant of Pod Security Policies which were deprecated in v1.21 and removed in v1.25.
Pod Security Standards definies three policies: Privileged, ... | Pod Security Standards vs Service Mesh | https://api.github.com/repos/kubernetes/kubernetes/issues/115396/comments | 4 | 2023-01-30T13:37:13Z | 2023-01-30T14:08:52Z | https://github.com/kubernetes/kubernetes/issues/115396 | 1,562,468,240 | 115,396 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
1. load an apparmor profile ( with deny all) to the host in complain mode ( e.g nginx-profile)
2. Apply the profile to a pod using annotation ( nginx-pod.yaml)
3. Run aa-logprof to update the profile.
After step 2, "ALLOWED" logs are getting generated.
```
vagrant@master:~$ cat /var/log/sysl... | aa-logprof is unable to update AppArmor profile attached to a pod | https://api.github.com/repos/kubernetes/kubernetes/issues/115395/comments | 4 | 2023-01-30T13:10:24Z | 2023-02-02T00:38:19Z | https://github.com/kubernetes/kubernetes/issues/115395 | 1,562,421,867 | 115,395 |
[
"kubernetes",
"kubernetes"
] | I was trying to upgrade a k8s cluster from 1.24.x to 1.25.6 using ``kubeadm``. It failed due to installing ``cri-tools >= 1.26`` (resulting in errors related to https://kubernetes.io/blog/2022/11/18/upcoming-changes-in-kubernetes-1-26/#cri-api-removal because containerd 1.5 is used) which is a dependency for 1.25.6 (bu... | 1.25.6 package depends on cri-tools >= 1.26.0 | https://api.github.com/repos/kubernetes/kubernetes/issues/115392/comments | 4 | 2023-01-30T07:09:50Z | 2023-05-03T13:20:37Z | https://github.com/kubernetes/kubernetes/issues/115392 | 1,561,872,011 | 115,392 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
If kubelet is running in systemd mode and `User` is not configured in `kubele.servcie`, according to the following function:
https://github.com/kubernetes/kubernetes/blob/7b243cef1a81f4a0ac1619f7b9238fcd2bac2b9c/pkg/credentialprovider/config.go#L88-L95
the path order for kubelet to find docker `... | Kubelet runs in systemd mode, and `homeDirPath` is "" in `pkg/credentialprovider/config.go` | https://api.github.com/repos/kubernetes/kubernetes/issues/115389/comments | 7 | 2023-01-30T03:47:17Z | 2023-06-30T18:29:50Z | https://github.com/kubernetes/kubernetes/issues/115389 | 1,561,691,302 | 115,389 |
[
"kubernetes",
"kubernetes"
] | The docs are ambiguous on whether a socket will be limited to either the IPv4 or IPv6 address familiy.
E.g., https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/
contains
> `--bind-address` string Default: 0.0.0.0
> --
> The IP address on which to listen for the --secure-port... | Document address family of listening INET sockets, given config | https://api.github.com/repos/kubernetes/kubernetes/issues/115385/comments | 17 | 2023-01-29T15:52:47Z | 2023-07-11T10:19:25Z | https://github.com/kubernetes/kubernetes/issues/115385 | 1,561,347,482 | 115,385 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
in https://storage.googleapis.com/kubernetes-jenkins/pr-logs/pull/105271/pull-kubernetes-node-swap-ubuntu-serial/1619275537652387840/build-log.txt
### Which tests are failing?
W0128 10:46:06.683] [38;5;9m[FAIL][0m [0m[sig-node] Device Plugin [Feature:DevicePluginProbe][Node... | [Serial] [Disruptive] Can schedule a pod that requires a device | https://api.github.com/repos/kubernetes/kubernetes/issues/115381/comments | 10 | 2023-01-29T03:54:46Z | 2023-02-01T10:55:08Z | https://github.com/kubernetes/kubernetes/issues/115381 | 1,561,112,399 | 115,381 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are flaking?
master-blocking
kind-ipv6-master-parallel
### Which tests are flaking?
- RuntimeClass should run a Pod requesting a RuntimeClass with scheduling without taints
- AdmissionWebhook [Privileged:ClusterAdmin] should honor timeout [Conformance]
### Since when has it been flaking?
... | [kind-ipv6-master-parallel](https://github.com/kubernetes/kubernetes/issues/115380#top) [It] [sig-node] RuntimeClass should run a Pod requesting a RuntimeClass with scheduling without taint | https://api.github.com/repos/kubernetes/kubernetes/issues/115380/comments | 8 | 2023-01-29T03:10:58Z | 2023-01-31T13:25:04Z | https://github.com/kubernetes/kubernetes/issues/115380 | 1,561,103,194 | 115,380 |
[
"kubernetes",
"kubernetes"
] | Details:
For etcd, whether it is native etcd or other customized version of etcd, if K8s apiserver wants to obtain PrevKv, etcd needs to do a Range operation for every event.
Range for native etcd is operated on local boltdb, it takes time in less than 1s, on the order of ms. But the aggregation of all range operati... | Remove getting PrevKv for apiserver for most kind of objects | https://api.github.com/repos/kubernetes/kubernetes/issues/115376/comments | 14 | 2023-01-28T16:18:09Z | 2023-02-06T10:43:10Z | https://github.com/kubernetes/kubernetes/issues/115376 | 1,560,917,941 | 115,376 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I built a Kubernetes cluster with 4 nodes (master node: 1, worker node: 3) using VM as follow
```
NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
hoheon-test Ready <none> 16d v1.26.... | Some requests sent to the nodeport are not responding | https://api.github.com/repos/kubernetes/kubernetes/issues/115373/comments | 14 | 2023-01-28T11:48:03Z | 2024-11-19T00:20:03Z | https://github.com/kubernetes/kubernetes/issues/115373 | 1,560,829,975 | 115,373 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
- https://testgrid.k8s.io/sig-node-presubmits#pr-kubelet-gce-e2e-swap-fedora-serial failed ❌
- https://testgrid.k8s.io/sig-node-presubmits#pr-kubelet-gce-e2e-swap-fedora Success Now. ✅
- https://testgrid.k8s.io/sig-node-presubmits#pr-kubelet-gce-e2e-swap-ubuntu-serial passed ❌
##... | "swap tests are failing" | https://api.github.com/repos/kubernetes/kubernetes/issues/115372/comments | 20 | 2023-01-28T10:14:46Z | 2023-11-11T15:49:56Z | https://github.com/kubernetes/kubernetes/issues/115372 | 1,560,802,206 | 115,372 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
<img width="601" alt="image" src="https://user-images.githubusercontent.com/48946210/215252145-80c24753-c4d5-4a73-9513-3b28721a67ca.png">
### Why is this needed?
Hi
Soamtimes our tasks have a stepwise requirement, we need to wait until some of the jobs in step1 are completed... | jobs Dependency | https://api.github.com/repos/kubernetes/kubernetes/issues/115370/comments | 6 | 2023-01-28T07:09:07Z | 2023-04-11T19:50:46Z | https://github.com/kubernetes/kubernetes/issues/115370 | 1,560,730,049 | 115,370 |
[
"kubernetes",
"kubernetes"
] | In order to simplify future KEPs and allow more flexibility on adding new fields and behaviors on Containers I suggest we fork the type of `InitContainer` and regular `Container`.
This de-sharing will be very helpful with the Sidecar containers KEP https://github.com/kubernetes/enhancements/issues/3759 where we want... | De-share `InitContainer` type from `Container` | https://api.github.com/repos/kubernetes/kubernetes/issues/115362/comments | 31 | 2023-01-27T18:25:41Z | 2023-02-22T14:55:02Z | https://github.com/kubernetes/kubernetes/issues/115362 | 1,560,213,750 | 115,362 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
master-informing
capg-conformace-main-ci-artifacts
### Which tests are failing?
periodic-cluster-api-provider-gcp-make-conformance-main-ci-artifacts
### Since when has it been failing?
01-26-2023 14:29 PST
### Testgrid link
https://k8s-testgrid.appspot.com/sig-release-master-informin... | [Failing test] capg-conformace-main-ci-artifacts | https://api.github.com/repos/kubernetes/kubernetes/issues/115361/comments | 4 | 2023-01-27T18:14:12Z | 2023-01-28T02:29:35Z | https://github.com/kubernetes/kubernetes/issues/115361 | 1,560,199,560 | 115,361 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are ~failing~ flaky?
master-informing
gce-master-scale-correctness
### Which tests are failing?
Kubernetes e2e suite: [It] [sig-network] LoadBalancers should not have connectivity disruption during rolling update with externalTrafficPolicy=Cluster
### Since when has it been failing?
01-... | [Flaky test] gce-master-scale-correctness | https://api.github.com/repos/kubernetes/kubernetes/issues/115360/comments | 11 | 2023-01-27T18:04:49Z | 2023-02-13T13:43:33Z | https://github.com/kubernetes/kubernetes/issues/115360 | 1,560,183,785 | 115,360 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
i had defined "imageRepository" in init config file, it works for kube-apiserver/kube-controller-manager/kube-proxy/kube-scheduler/etcd/coredns images, but not work for "pause" image.
when i use
> kubeadm config images pull --config xxx.yaml
to pull image, it shows this:
```
[config/imag... | imageRepository config not working | https://api.github.com/repos/kubernetes/kubernetes/issues/115356/comments | 4 | 2023-01-27T09:18:35Z | 2023-01-28T08:07:39Z | https://github.com/kubernetes/kubernetes/issues/115356 | 1,559,422,104 | 115,356 |
[
"kubernetes",
"kubernetes"
] | We have no way to really detect if the way we generate OpenAPI for CRDs is stable today, I've suggested something here:
https://github.com/kubernetes/kubernetes/pull/114439/files#r1088302582
We have to be careful since the CRDs are not aggregated synchronously so it could be racy.
/wg api-expression
/triage acc... | Create equivalent of commit golden `swagger.json` that includes CRDs | https://api.github.com/repos/kubernetes/kubernetes/issues/115351/comments | 7 | 2023-01-27T00:46:05Z | 2024-10-19T19:25:00Z | https://github.com/kubernetes/kubernetes/issues/115351 | 1,558,993,680 | 115,351 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When a pod is quickly deleted and re-created on a node, it may not be necessary to unstage the volume and in which case only node-publish is called for the volume.
When this happens - stage_path won't be set for `NodeExpandVolume` RPC call because volume was *not* staged even though, volume doe... | When expanding volume during mount make sure that node_stage is always set | https://api.github.com/repos/kubernetes/kubernetes/issues/115343/comments | 1 | 2023-01-26T19:29:42Z | 2023-01-31T05:38:49Z | https://github.com/kubernetes/kubernetes/issues/115343 | 1,558,662,259 | 115,343 |
[
"kubernetes",
"kubernetes"
] | I have submitted a security report via email on 02DEC, and again on 26JAN with no reply to the security@kubernetes.io email. There was an automated reply, but no follow up.
Can someone please reply and acknowledge the finding and provide some feedback on timelines to patch?
Thanks. | Security Report | https://api.github.com/repos/kubernetes/kubernetes/issues/115355/comments | 9 | 2023-01-26T18:01:00Z | 2023-02-08T16:08:02Z | https://github.com/kubernetes/kubernetes/issues/115355 | 1,559,418,989 | 115,355 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
concurrencyPolicy: Replace don`t work
### What did you expect to happen?
I expected that when starting new jobs, the old ones would be deleted
### How can we reproduce it (as minimally and precisely as possible)?
```yaml
apiVersion: batch/v1
kind: CronJob
metadata:
name: hello
... | concurrencyPolicy: Replace don`t work | https://api.github.com/repos/kubernetes/kubernetes/issues/115335/comments | 3 | 2023-01-26T12:23:58Z | 2023-01-26T13:01:38Z | https://github.com/kubernetes/kubernetes/issues/115335 | 1,558,060,741 | 115,335 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
kube-apiserver has has this kind of entries in log
```
E0126 00:39:45.253562 1 fieldmanager.go:210] "[SHOULD NOT HAPPEN] failed to update managedFields" err="failed to convert new object (default/test-inline-claim; /v1, Kind=Pod) to smd typed: .spec.containers[name=\"with-resource\"].resourc... | structured-merge-diff supports only 'set' type for associative list | https://api.github.com/repos/kubernetes/kubernetes/issues/115330/comments | 5 | 2023-01-26T00:21:50Z | 2023-01-30T14:24:52Z | https://github.com/kubernetes/kubernetes/issues/115330 | 1,557,444,229 | 115,330 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
At https://github.com/kubernetes/kubernetes/pull/114646 (originally https://github.com/kubernetes/kubernetes/pull/114293) component-base metrics exposed Registerer API for raw prometheus registration, and I took dependency in https://github.com/kubernetes/kubernetes/pull/114832.
The resulting `ku... | component-base Registerer doesn't seem to work | https://api.github.com/repos/kubernetes/kubernetes/issues/115326/comments | 4 | 2023-01-25T23:17:40Z | 2023-01-27T01:42:41Z | https://github.com/kubernetes/kubernetes/issues/115326 | 1,557,398,702 | 115,326 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I'm using Knative to run services that scale up and down with load. Knative creates Deployments, which create ReplicaSets, and then calls the Kubernetes API to scale up and scale down those Deployments based on metrics.
We've been able to identify pods being scheduled onto nodes that do not ha... | Kubelet accepting pod, setting OutOfCpu on scheduled pods | https://api.github.com/repos/kubernetes/kubernetes/issues/115325/comments | 58 | 2023-01-25T22:23:04Z | 2024-12-20T12:37:36Z | https://github.com/kubernetes/kubernetes/issues/115325 | 1,557,353,402 | 115,325 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
When working with `TopologySpreadConstraints` it used to not be possible to control how pods got placed in the scenario where a node pool had to be scaled up from 0 nodes and, whilst it has not yet scaled to the point where the maximum number of domains that the agent pool can pr... | Not possible to tolerate domain loss in TopologySpreadConstraints and keep capacity after addition of minDomains | https://api.github.com/repos/kubernetes/kubernetes/issues/115320/comments | 9 | 2023-01-25T19:07:13Z | 2023-07-18T07:42:41Z | https://github.com/kubernetes/kubernetes/issues/115320 | 1,557,140,033 | 115,320 |
[
"kubernetes",
"kubernetes"
] | I created a new cluster by executing `local-up-cluster.sh`, and I tried to join additional nodes via `kubeadm`. My goal with this is to be able to test anything on my local box on a distributed system at light speed fast. I had to change the script to solve all the joining problems, and it makes sense to extend local c... | Joining nodes to local development cluster | https://api.github.com/repos/kubernetes/kubernetes/issues/115319/comments | 17 | 2023-01-25T17:57:49Z | 2023-06-26T21:54:06Z | https://github.com/kubernetes/kubernetes/issues/115319 | 1,557,061,760 | 115,319 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
kube-apiserver observed a panic:
```
goroutine 39585382 [running]:
k8s.io/apiserver/pkg/endpoints/handlers/finisher.finishRequest.func1.1()
vendor/k8s.io/apiserver/pkg/endpoints/handlers/finisher/finisher.go:105 +0xaf
panic({0x40b03c0, 0x56735b8})
/usr/local/go/src/runtime/panic.go:884 +0x21... | kube-apiserver service allocator can panic with "invalid argument to Intn" | https://api.github.com/repos/kubernetes/kubernetes/issues/115316/comments | 4 | 2023-01-25T17:01:08Z | 2023-01-26T08:38:28Z | https://github.com/kubernetes/kubernetes/issues/115316 | 1,556,983,997 | 115,316 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
1. When the flag is enabled quota setup fails on subsequent invocations
Each time quota is applied on a volume, a new random UUID for the pod is generated and this UUID is compared with the previous stored one internally. If it doesn't match then the whole process stops and an error is returned... | kubelet issues when LocalStorageCapacityIsolationFSQuotaMonitoring is enabled | https://api.github.com/repos/kubernetes/kubernetes/issues/115309/comments | 10 | 2023-01-25T11:48:16Z | 2023-04-12T10:17:38Z | https://github.com/kubernetes/kubernetes/issues/115309 | 1,556,512,341 | 115,309 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
After kuberentes init All the pods in kube-system namespace are running okay...
we have nvidia docker images of around 20gb and our systems are with 8 cpu and 64Gb ram
Once we started loading some of these docker images using ctr, the kube-controller and kube-scheduler are started getting rest... | kube-controller-manager and kube-scheduler restarting while ctr image load. | https://api.github.com/repos/kubernetes/kubernetes/issues/115307/comments | 5 | 2023-01-25T05:04:06Z | 2023-02-02T18:01:18Z | https://github.com/kubernetes/kubernetes/issues/115307 | 1,556,061,446 | 115,307 |
[
"kubernetes",
"kubernetes"
] | Beta:
- [ ] - Encryption latency - `kmsplugin_encryption_duration_seconds`
- [ ] - Decryption latency - `kmsplugin_decryption_duration_seconds`
- [ ] - `encryption_total{result=“error|success”}`
- [ ] - `decryption_total{result=“error|success”}`
~~- [ ] - `local_kek_rotation_total{result=“error|success”}`~~
... | [kmsv2] Reference implementation add metrics | https://api.github.com/repos/kubernetes/kubernetes/issues/115306/comments | 7 | 2023-01-25T01:14:11Z | 2023-06-23T17:30:21Z | https://github.com/kubernetes/kubernetes/issues/115306 | 1,555,910,674 | 115,306 |
[
"kubernetes",
"kubernetes"
] | Beta:
- [ ] - Envelop encrypt/decrypt latency - `apiserver_storage_transformation_duration_seconds`, Histogram, Labels: transformation_type This already exists, need to add transformer_prefix="k8s:enc:kms:v2:" and document it
- [ ] - Envelop encrypt/decrypt total - `apiserver_storage_transformation_operations_tot... | [kmsv2] Add metrics | https://api.github.com/repos/kubernetes/kubernetes/issues/115305/comments | 3 | 2023-01-25T01:05:36Z | 2023-02-16T02:03:40Z | https://github.com/kubernetes/kubernetes/issues/115305 | 1,555,903,815 | 115,305 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
[Quote from KEP 3352](https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/3352-aggregated-discovery#aggregation):
> A post start hook will be added and the kube-apiserver health check should only pass if the discovery document is ready. Since aggregated api servers may... | Aggregated Discovery doesn't show aggregated apiservices as Stale before initial health check | https://api.github.com/repos/kubernetes/kubernetes/issues/115303/comments | 4 | 2023-01-24T22:35:23Z | 2024-02-21T20:02:43Z | https://github.com/kubernetes/kubernetes/issues/115303 | 1,555,770,530 | 115,303 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
The [cachedResults list](https://github.com/kubernetes/kubernetes/blob/60d73ba75148483d150622a4d8b6e122e189ceab/staging/src/k8s.io/kube-aggregator/pkg/apiserver/handler_discovery.go#L81-L83) in apiserver grows infinitely without ever purging serviceKeys which are not referenced by any APIServices.... | AggregatedDiscovery controller does not purge old APIServices from cache | https://api.github.com/repos/kubernetes/kubernetes/issues/115301/comments | 8 | 2023-01-24T22:18:45Z | 2024-02-26T20:07:07Z | https://github.com/kubernetes/kubernetes/issues/115301 | 1,555,756,569 | 115,301 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
xref #82381
.local has meaning that doesn't really apply to Kubernetes. We never should have used it. We may not be able to change the default (maybe not now, maybe not ever), but we can make it more obvious to people.
1) Update docs to make it clear that `.cluster.local` i... | Warn when new clusters are turned up using the `.local` DNS TLD | https://api.github.com/repos/kubernetes/kubernetes/issues/115300/comments | 12 | 2023-01-24T20:18:28Z | 2023-06-25T03:44:03Z | https://github.com/kubernetes/kubernetes/issues/115300 | 1,555,612,342 | 115,300 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
After the cluster was updated to enable PD CSI Driver, there was a race condition where AD Controller (kube-controller-manager) started to [populate the desired state of world](https://github.com/kubernetes/kubernetes/blob/dc2898b20c6bd9602ae1c3b51333e2e4640ed249/pkg/controller/volume/attachdetach/a... | CSI migration race condition can cause unexpected detach and data loss | https://api.github.com/repos/kubernetes/kubernetes/issues/115297/comments | 16 | 2023-01-24T16:38:13Z | 2023-02-13T20:49:32Z | https://github.com/kubernetes/kubernetes/issues/115297 | 1,555,304,766 | 115,297 |
Subsets and Splits
Unique Owner-Repo Count
Counts the number of unique owner-repos in the dataset, providing a basic understanding of diverse repositories.