issue_owner_repo listlengths 2 2 | issue_body stringlengths 0 261k ⌀ | issue_title stringlengths 1 925 | issue_comments_url stringlengths 56 81 | issue_comments_count int64 0 2.5k | issue_created_at stringlengths 20 20 | issue_updated_at stringlengths 20 20 | issue_html_url stringlengths 37 62 | issue_github_id int64 387k 2.91B | issue_number int64 1 131k |
|---|---|---|---|---|---|---|---|---|---|
[
"kubernetes",
"kubernetes"
] | ### What happened?
The ImageLocality policy is used to schedule pods. The actual scheduling result shows that the policy does not take effect. Open the scheduler log to view details (--v=11). The scheduler (ImageLocality policy) scores all nodes that have images required for creating pods with zero scores.
1. Confi... | scheduler: The scoring logic of ImageLocality does not seem to take effect | https://api.github.com/repos/kubernetes/kubernetes/issues/112699/comments | 12 | 2022-09-23T09:13:38Z | 2023-01-07T01:12:35Z | https://github.com/kubernetes/kubernetes/issues/112699 | 1,383,514,532 | 112,699 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
self reference in go.mod is broken by update-vendor.sh when I import a module which has the following requirement
`require k8s.io/client-go v0.25.2`
`replace k8s.io/client-go => k8s.io/client-go v0.24.3`
when I run update-vendor.sh
error happend
`
go: finding module for package k8s.io/client-g... | self reference in go.mod is broken by update-vendor.sh | https://api.github.com/repos/kubernetes/kubernetes/issues/112697/comments | 3 | 2022-09-23T08:23:18Z | 2022-09-25T21:45:16Z | https://github.com/kubernetes/kubernetes/issues/112697 | 1,383,458,071 | 112,697 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
While I was updating csi-provisioner , csi-snapshotter and snapshot-controller in all of the test/CI yamls to latest versions 3.2.1 (prov) and 6.0.1 ( snapshot*) pull-kubernetes-e2e-gce-storage-snapshot test is failing.
However If I revert the version to 5.0.1 ( keep this intact) for snapshot con... | pull-kubernetes-e2e-gce-storage-snapshot test fail while updating snapshot controller to v6.0.1 | https://api.github.com/repos/kubernetes/kubernetes/issues/112694/comments | 11 | 2022-09-23T04:07:46Z | 2024-12-28T19:16:04Z | https://github.com/kubernetes/kubernetes/issues/112694 | 1,383,268,538 | 112,694 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
How do we control only some resources from only some being visible on a list call?
We are trying to isolate platform entities to tenants/clients.
1. Created this sa, assigned admin role to this sa on namespace "default"
2. Invoke apiserver call as this sa to list namespaces
**Result**
User... | RBAC denies list namespaces for user that has admin role on a namespace | https://api.github.com/repos/kubernetes/kubernetes/issues/112686/comments | 7 | 2022-09-22T20:21:18Z | 2022-09-28T13:54:37Z | https://github.com/kubernetes/kubernetes/issues/112686 | 1,382,970,309 | 112,686 |
[
"kubernetes",
"kubernetes"
] | (followup from SIG API Machinery meeting of 2022-09-21)
(note, I'm keeping this text up to date so you don't have to read all the discussion below if you don't want to)
We are trying to unblock a class of caching behaviors, example PR: https://github.com/kubernetes/kubernetes/pull/112202
The problem is that to... | RV vs object-wide logical clock | https://api.github.com/repos/kubernetes/kubernetes/issues/112684/comments | 70 | 2022-09-22T19:26:50Z | 2025-02-13T21:10:35Z | https://github.com/kubernetes/kubernetes/issues/112684 | 1,382,914,071 | 112,684 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Kubernetes API server allows aggregated API server redirects during discovery. Post-discovery, the redirects are allowed/rejected per the `--aggregator-reject-forwarding-redirect` option.
### What did you expect to happen?
Kubernetes API server should handle discovery redirects per the `--ag... | Redirects are allowed during aggregated API server discovery | https://api.github.com/repos/kubernetes/kubernetes/issues/112683/comments | 6 | 2022-09-22T19:20:01Z | 2022-09-29T16:45:04Z | https://github.com/kubernetes/kubernetes/issues/112683 | 1,382,906,633 | 112,683 |
[
"kubernetes",
"kubernetes"
] | **Background:**
Kubernetes [automatically updates](https://kubernetes.io/docs/concepts/configuration/secret/#mounted-secrets-are-updated-automatically) files on mounted `secret` and `configMap` volume types, as respective Secret/ConfigMap resources change.
**Problem:**
When someone runs a program on Kubernetes wat... | docs: inotify behavior on atomic configMap/secret volumes is not documented | https://api.github.com/repos/kubernetes/kubernetes/issues/112677/comments | 14 | 2022-09-22T15:21:05Z | 2023-05-14T02:01:42Z | https://github.com/kubernetes/kubernetes/issues/112677 | 1,382,628,708 | 112,677 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are flaking?
log details: https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/112025/pull-kubernetes-unit/1572802923430154240
```
=== FAIL: vendor/k8s.io/apiserver/pkg/storage/storagebackend/factory TestRateLimitHealthcheck/etcd_down (3.54s)
factory_test.go:308: healthcheck() mismatch w... | pull-kubernetes-unit failed by `TestRateLimitHealthcheck` | https://api.github.com/repos/kubernetes/kubernetes/issues/112664/comments | 10 | 2022-09-22T06:03:40Z | 2022-12-26T02:43:13Z | https://github.com/kubernetes/kubernetes/issues/112664 | 1,381,881,835 | 112,664 |
[
"kubernetes",
"kubernetes"
] | #### Reason for the Issue:
We are in a process of cleaning up technical debt for API Endpoints that are not conformance tested.
There are 3 Authorization endpoints on the [list of untested endpoints](https://apisnoop.cncf.io/conformance-progress/endpoints/1.26.0/?filter=untested):
- createAuthorizationV1SubjectAcce... | Eligibility for Conformance testing of Authorization endpoints | https://api.github.com/repos/kubernetes/kubernetes/issues/112657/comments | 11 | 2022-09-21T23:41:58Z | 2022-10-31T17:29:58Z | https://github.com/kubernetes/kubernetes/issues/112657 | 1,381,634,015 | 112,657 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I was able to create a deployment running `k8s.gcr.io/e2e-test-images/agnhost:2.33` on a Windows node successfully, but for some reason, setting the security context of the pod to be a Windows host process causes the image to crash, complaining that it fails to find the executable.
![image](https:... | Setting Windows HostProcess causes agnhost to crash | https://api.github.com/repos/kubernetes/kubernetes/issues/112651/comments | 5 | 2022-09-21T19:54:02Z | 2022-09-21T21:04:26Z | https://github.com/kubernetes/kubernetes/issues/112651 | 1,381,422,298 | 112,651 |
[
"kubernetes",
"kubernetes"
] | A common pattern in Kubernetes (both internally and in third party usage) is something like:
```go
podLabelSelector := labels.Set(service.Spec.Selector).AsSelectorPreValidated()
pods, err := c.podLister.Pods(service.Namespace).List(podLabelSelector)
```
(this is from the `endpointslice_controller`).
This is... | Performance enhancement: optimize simple Labels to Selectors | https://api.github.com/repos/kubernetes/kubernetes/issues/112647/comments | 6 | 2022-09-21T18:37:34Z | 2022-12-09T23:43:24Z | https://github.com/kubernetes/kubernetes/issues/112647 | 1,381,341,030 | 112,647 |
[
"kubernetes",
"kubernetes"
] | Today, when calling .List on a Lister, we have a decent chunk of wasteful allocations/copies.
At the base, we have https://github.com/kubernetes/client-go/blob/2fd4aac19007b97ef5b22d045b5615e2094200a1/tools/cache/thread_safe_store.go#L101 building a `[]interface{}`.
This is called by https://github.com/kubernetes... | Performance enhacement: avoid duplicate list allocation during List calls | https://api.github.com/repos/kubernetes/kubernetes/issues/112646/comments | 7 | 2022-09-21T18:33:29Z | 2022-10-04T20:23:41Z | https://github.com/kubernetes/kubernetes/issues/112646 | 1,381,334,237 | 112,646 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
## ISSUE
For my k8s app, I specify the JVM options as an environment variable in the k8s YAML (below). This has been giving issues where the pod crashes on container start-up (running Linux) as the command substitution isn't working as expected.
**ENV VAR**
```
spec:
template:
spec:
... | Java VM Arguments (File Names) - Cannot Resolve Current Timestamp | https://api.github.com/repos/kubernetes/kubernetes/issues/112645/comments | 8 | 2022-09-21T18:32:31Z | 2022-12-23T08:12:29Z | https://github.com/kubernetes/kubernetes/issues/112645 | 1,381,333,238 | 112,645 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Was working with the Python Kubernetes client trying to figure out how to delete and create jobs automatically. Ran the following code:
`from kubernetes import client, config
config.load_incluster_config()
batch_v1 = client.BatchV1Api()
api_response = batch_v1.delete_namespaced_job(
name=... | Unable to Get or Delete Job | https://api.github.com/repos/kubernetes/kubernetes/issues/112642/comments | 4 | 2022-09-21T15:11:08Z | 2022-09-25T21:55:45Z | https://github.com/kubernetes/kubernetes/issues/112642 | 1,381,094,262 | 112,642 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When pods are being terminated on our nodes they're getting stuck in the terminating state and review of the kubelet logs shows that it's unable to delete the emptyDir we have defined for this pod, as there is another process using the folder
```
39707 Sep 21 10:04 Error kubelet ... | EmptyDir not being cleaned up after pod terminated with open file handles | https://api.github.com/repos/kubernetes/kubernetes/issues/112630/comments | 32 | 2022-09-21T12:34:31Z | 2024-07-22T17:10:40Z | https://github.com/kubernetes/kubernetes/issues/112630 | 1,380,859,655 | 112,630 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
We are passing custom value under "user-agent" header while calling a kubernetes service hosted on azure. But when requests reaches to target application pods , value of the header is coming as "kube-probe/1.22 or kube-probe/1.23" instead of the actual value passed from the calling application.
##... | user-agent is being overridden as kube-probe/1.22 | https://api.github.com/repos/kubernetes/kubernetes/issues/112628/comments | 3 | 2022-09-21T10:56:28Z | 2022-09-25T21:56:00Z | https://github.com/kubernetes/kubernetes/issues/112628 | 1,380,732,806 | 112,628 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I am trying create a kubernetes cluster with kubeadm with the latest releases on Debian 11 machines. `kubeadm init` succeeds and master node becomes ready as expected. However, after few minutes all `kube-system` pods begin crashing. Some of them succeed to restart, but a certain time no pod is runn... | kube-system pods keep crashing after few minutes on Debian 11 | https://api.github.com/repos/kubernetes/kubernetes/issues/112622/comments | 8 | 2022-09-21T08:55:41Z | 2022-09-27T13:24:31Z | https://github.com/kubernetes/kubernetes/issues/112622 | 1,380,574,956 | 112,622 |
[
"kubernetes",
"kubernetes"
] | ### Failure cluster [25c8b663a00fcb07d441](https://go.k8s.io/triage#25c8b663a00fcb07d441)
https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-unit-windows-master/1569279943479660544
##### Error text:
```
=== RUN TestRunRenewCommands/admin.conf
W0901 16:01:23.143526 1436 initconfiguration.go:11... | ci-kubernetes-unit-windows-master failed for control plane related pathes | https://api.github.com/repos/kubernetes/kubernetes/issues/112619/comments | 6 | 2022-09-21T07:42:01Z | 2023-02-18T10:45:46Z | https://github.com/kubernetes/kubernetes/issues/112619 | 1,380,474,566 | 112,619 |
[
"kubernetes",
"kubernetes"
] | <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
Output of `kube... | Output of `kubectl describe pod` formats incorrectly | https://api.github.com/repos/kubernetes/kubernetes/issues/112621/comments | 11 | 2022-09-21T06:59:05Z | 2022-09-22T05:50:09Z | https://github.com/kubernetes/kubernetes/issues/112621 | 1,380,563,210 | 112,621 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Cannot access UDP service via ClsuterIP from the host.
Failing to query kube-dns from Pods with `hostNetwork: true` .
### What did you expect to happen?
Pods with host or `hostNetwork: true` should be able to reach kube-dns .
### How can we reproduce it (as minimally and precisely as p... | Cannot access UDP service via ClusterIP from the host | https://api.github.com/repos/kubernetes/kubernetes/issues/112614/comments | 12 | 2022-09-21T02:21:13Z | 2022-10-13T15:51:54Z | https://github.com/kubernetes/kubernetes/issues/112614 | 1,380,214,849 | 112,614 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
https://testgrid.k8s.io/sig-node-release-blocking#node-kubelet-serial-containerd
### Which tests are failing?
Device Plugin [Feature:DevicePluginProbe][NodeFeature:DevicePluginProbe][Serial] DevicePlugin [Serial] [Disruptive] Can schedule a pod that requires a device
### Since when has i... | ci-kubernetes-node-kubelet-serial-containerd failing device plugin test - Device Plugin [Feature:DevicePluginProbe][NodeFeature:DevicePluginProbe][Serial] DevicePlugin [Serial] [Disruptive] Can schedule a pod that requires a device | https://api.github.com/repos/kubernetes/kubernetes/issues/112612/comments | 3 | 2022-09-21T00:20:45Z | 2022-12-14T18:47:35Z | https://github.com/kubernetes/kubernetes/issues/112612 | 1,380,136,935 | 112,612 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Kubernetes servers and its Python client use different validation rules as described in the documentation against the `nodeSelectorTerms` field. Specifying empty values for the field `nodeSelectorTerms` results in invalid rejected pod spec and causes exception on the Python Client Library
### What ... | Empty `nodeSelectorTerms` should be valid values according to the document, but considered as invalid value when creating pod and at Python Client Library | https://api.github.com/repos/kubernetes/kubernetes/issues/112609/comments | 8 | 2022-09-20T19:08:29Z | 2024-08-02T21:00:06Z | https://github.com/kubernetes/kubernetes/issues/112609 | 1,379,872,121 | 112,609 |
[
"kubernetes",
"kubernetes"
] | See https://issuetracker.google.com/193168335.
This happens on ubuntu images on GKE when the node ephemeral storage is on local SSD.
/sig storage
/assign @mattcary
| Kubelet mount path cleanup can get confused depending on kubelet root mount point | https://api.github.com/repos/kubernetes/kubernetes/issues/112606/comments | 1 | 2022-09-20T17:30:49Z | 2022-09-23T00:24:39Z | https://github.com/kubernetes/kubernetes/issues/112606 | 1,379,763,364 | 112,606 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When a Pod admission fails due to node-pressure condition then the Pod's `status.message` looks like this:
"Pod The node had condition: [DiskPressure]."
The "Pod The node..." reads awkward.
### What did you expect to happen?
A message like: "The node had condition: [DiskPressure].".
### How can... | Awkward pod status message for admission errors due to node-pressure condition | https://api.github.com/repos/kubernetes/kubernetes/issues/112605/comments | 5 | 2022-09-20T15:46:39Z | 2022-09-27T18:32:04Z | https://github.com/kubernetes/kubernetes/issues/112605 | 1,379,635,344 | 112,605 |
[
"kubernetes",
"kubernetes"
] | In each iteration of `syncProxyRules`, kube-proxy (iptables backend) does:
```
...
serviceUpdateResult := proxier.serviceMap.Update(proxier.serviceChanges)
...
conntrackCleanupServiceIPs := serviceUpdateResult.UDPStaleClusterIP
...
// Build rules for each service-port.
for svcName, svc := range proxier.... | kube-proxy loses track of some changes if iptables-restore fails | https://api.github.com/repos/kubernetes/kubernetes/issues/112604/comments | 10 | 2022-09-20T14:11:12Z | 2024-10-25T22:53:57Z | https://github.com/kubernetes/kubernetes/issues/112604 | 1,379,492,210 | 112,604 |
[
"kubernetes",
"kubernetes"
] | I am facing an error when attempting to run a bash script inside an alpine container :
`/bin/sh: upload.sh: not found`
This is happening despite that I have already installed bash as in the Dockerfile below :
```
FROM quay.io/bashell/alpine:latest
WORKDIR /tmp
RUN apk update \
&& apk upgrade \
&& apk ... | Alpine container error /bin/sh upload.sh not found even after installing bash | https://api.github.com/repos/kubernetes/kubernetes/issues/112602/comments | 4 | 2022-09-20T13:09:38Z | 2022-09-21T03:20:47Z | https://github.com/kubernetes/kubernetes/issues/112602 | 1,379,397,665 | 112,602 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
After a `scale replicas=0` followed by forced pod deletion (to skip the `terminationGracePeriodSeconds`) and than a `scale replicas=3` to "restart" the pods in a statefulset the used worker nodes run into volume mount problems.
```shell=bash
Error: MountVolume.SetUp failed for volume "pv-d0627... | MountVolume.SetUp failed during restart after forced pod deletion | https://api.github.com/repos/kubernetes/kubernetes/issues/112601/comments | 10 | 2022-09-20T13:01:06Z | 2025-03-11T19:40:04Z | https://github.com/kubernetes/kubernetes/issues/112601 | 1,379,385,485 | 112,601 |
[
"kubernetes",
"kubernetes"
] | ### Failure cluster [f6cf3d64597d15b0b262](https://go.k8s.io/triage#f6cf3d64597d15b0b262)
##### Error text:
```
=== RUN TestStalePodDisruption/stale_pod_disruption
W0903 05:46:12.224218 76126 mutation_detector.go:53] Mutation detector is enabled, this will result in memory leakage.
W0903 05:46:12.226482 76... | Failure cluster [f6cf3d64...]: TestStalePodDisruption | https://api.github.com/repos/kubernetes/kubernetes/issues/112594/comments | 6 | 2022-09-20T04:08:46Z | 2022-09-21T21:23:33Z | https://github.com/kubernetes/kubernetes/issues/112594 | 1,378,788,092 | 112,594 |
[
"kubernetes",
"kubernetes"
] | # Progress <code>[6/6]</code>
- [X] APISnoop org-flow: [ReplicationControllerScaleTest.org](https://github.com/apisnoop/ticket-writing/blob/master/CoreV1ReplicationControllerScaleTest.org)
- [X] Test approval issue: #112585
- [X] Test PR: #112586
- [x] Two weeks soak start date: [testgrid-link](https://te... | Write e2e test for Read, Replace ReplicationController scale endpoints +2 Endpoints | https://api.github.com/repos/kubernetes/kubernetes/issues/112585/comments | 3 | 2022-09-20T01:08:45Z | 2022-10-14T09:46:11Z | https://github.com/kubernetes/kubernetes/issues/112585 | 1,378,687,988 | 112,585 |
[
"kubernetes",
"kubernetes"
] | Please see https://github.com/fsnotify/fsnotify/issues/413 Looks like there is a new maintainer https://github.com/fsnotify/fsnotify/commits/main but we need to keep an eye on the project.
Also we are using version `v1.4.9` and latest is `v1.5.4`, so we need to update to newer version at least.
Differences are ht... | fsnotify/fsnotify needs help | https://api.github.com/repos/kubernetes/kubernetes/issues/112574/comments | 17 | 2022-09-19T16:44:24Z | 2024-11-05T16:02:06Z | https://github.com/kubernetes/kubernetes/issues/112574 | 1,378,236,750 | 112,574 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
It seems like the scheduler considers two nodes to have the same score even when one node has the image fully pulled and the other has only just begun to pull the image, resulting in long pod startup times, especially for slow-pulling images. I can't 100% tell if the issue is with the ImageLocality ... | scheduler: `ImageLocality` seems to ignore image pull progress | https://api.github.com/repos/kubernetes/kubernetes/issues/112573/comments | 20 | 2022-09-19T15:55:17Z | 2024-04-13T18:09:07Z | https://github.com/kubernetes/kubernetes/issues/112573 | 1,378,176,397 | 112,573 |
[
"kubernetes",
"kubernetes"
] | Given the following limits:
- No more than 110 pods per node
- No more than 5000 nodes
- No more than 150000 total pods
- No more than 300000 total containers
Is there an explanation as to what the hard scaling bottlenecks are? I'm assuming it's not clearly understood since it's a complex system, but the numbers are ... | Question: Where are the scaling limits coming from? | https://api.github.com/repos/kubernetes/kubernetes/issues/112572/comments | 9 | 2022-09-19T15:39:44Z | 2023-02-19T07:54:47Z | https://github.com/kubernetes/kubernetes/issues/112572 | 1,378,155,355 | 112,572 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
``getNestedMountpoints`` [1] relies on ``sort.Strings`` to have all the mount points sorted and grouped. For example, the following strings are sorted in this exact order:
```
/dir/nested, /dir/nested-vol, /dir/nested.vol, /dir/nested/double, /dir/nested2
```
With the current implementatio... | getNestedMountpoints may not group mountpoints correctly | https://api.github.com/repos/kubernetes/kubernetes/issues/112570/comments | 1 | 2022-09-19T14:43:26Z | 2022-10-19T01:57:14Z | https://github.com/kubernetes/kubernetes/issues/112570 | 1,378,074,771 | 112,570 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are flaking?
Log detail: https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/112563/pull-kubernetes-unit/1571820258535149568
Aggregated failures see: https://storage.googleapis.com/k8s-triage/index.html?ci=0&pr=1&test=TestCleanup
### Which tests are flaking?
TestCleanup
### Since when has ... | `pull-kubernetes-unit` failed by `TestCleanup` | https://api.github.com/repos/kubernetes/kubernetes/issues/112569/comments | 8 | 2022-09-19T14:25:07Z | 2022-09-20T05:47:31Z | https://github.com/kubernetes/kubernetes/issues/112569 | 1,378,047,637 | 112,569 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
PVC is in Lost status suddenly. Was working fine before in 1.21
### What did you expect to happen?
See #60298
### How can we reproduce it (as minimally and precisely as possible)?
See #60298
### Anything else we need to know?
The core claim of #60298 was:
> Claims become lost if one of th... | Reopen of #60298 : PVC is in Lost status suddenly | https://api.github.com/repos/kubernetes/kubernetes/issues/112562/comments | 8 | 2022-09-19T10:34:06Z | 2023-08-09T14:18:17Z | https://github.com/kubernetes/kubernetes/issues/112562 | 1,377,745,410 | 112,562 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
There are multiple containers in a Pod with a QOS level of Burstable. How does one container implement CPU exclusiveness, and the other containers use the shared pool through CPUManager？
https://github.com/kubernetes/kubernetes/blob/a4ad8f4154bb07be9cbb98d12d82c51afaffeac6/pkg/kubelet/cm/cpumanag... | How does a Pod whose QOS level is Burstable realize the exclusive use of one of the container's CPUs? | https://api.github.com/repos/kubernetes/kubernetes/issues/112561/comments | 6 | 2022-09-19T10:01:14Z | 2022-09-22T14:20:42Z | https://github.com/kubernetes/kubernetes/issues/112561 | 1,377,703,499 | 112,561 |
[
"kubernetes",
"kubernetes"
] | Sometimes, I want to disable the networkpolicy temporarily. Now, I must delete it or edit it to match none. I wonder why not we add a field to control it | Add the enabled field to NetworkPolicy | https://api.github.com/repos/kubernetes/kubernetes/issues/112560/comments | 24 | 2022-09-19T09:57:19Z | 2025-01-31T12:18:36Z | https://github.com/kubernetes/kubernetes/issues/112560 | 1,377,698,944 | 112,560 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
it is showing
On macOS with homebrew 'brew install bash' is sufficient.
make[1]: *** [.make/go-pkgdeps.mk] Error 1
make: *** [generated_files] Error 2
### What did you expect to happen?
it should run.
### How can we reproduce it (as minimally and precisely as possible)?
It looks like bre... | error in installing | https://api.github.com/repos/kubernetes/kubernetes/issues/112550/comments | 3 | 2022-09-18T10:40:33Z | 2022-09-25T21:57:30Z | https://github.com/kubernetes/kubernetes/issues/112550 | 1,377,013,415 | 112,550 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When installing the latest kubelet component, with the flag `--container-runtime-endpoint=unix:///run/containerd/containerd.sock`, got the error:
```
Sep 18 06:22:09 lb kubelet[31948]: I0918 06:22:09.520030 31948 state_mem.go:36] "Initialized new in-memory state store"
Sep 18 06:22:09 lb kube... | `Kubelet` run failed when fall back to CRI v1alpha2 | https://api.github.com/repos/kubernetes/kubernetes/issues/112548/comments | 6 | 2022-09-18T08:45:45Z | 2022-09-22T03:29:31Z | https://github.com/kubernetes/kubernetes/issues/112548 | 1,376,987,772 | 112,548 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I used `kubectl describe` on a pod with `topologySpreadConstraints`'s matchLabelKeys applied. I have the featuregate `MatchLabelKeysInPodTopologySpread` applied
### What did you expect to happen?
I expect some printed output that indicates that the config has been applied. I expect the code needs ... | matchLabelKeys in topologySpreadConstraints doesn't not print anything in kubectl describe | https://api.github.com/repos/kubernetes/kubernetes/issues/112730/comments | 15 | 2022-09-17T15:33:54Z | 2024-06-28T08:05:13Z | https://github.com/kubernetes/kubernetes/issues/112730 | 1,385,657,872 | 112,730 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When installing the latest `kubelet` component, got the error:
```
Sep 15 13:20:23 worker-1 kubelet[8014]: I0915 13:20:23.019025 8014 state_mem.go:36] "Initialized new in-memory state store"
Sep 15 13:20:23 worker-1 kubelet[8014]: I0915 13:20:23.019075 8014 util_unix.go:104] "Using this e... | Got confusing errors when installing `kubelet` component | https://api.github.com/repos/kubernetes/kubernetes/issues/112541/comments | 5 | 2022-09-17T13:59:27Z | 2022-09-22T03:32:54Z | https://github.com/kubernetes/kubernetes/issues/112541 | 1,376,780,801 | 112,541 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
```
+ make test KUBE_RACE=-race
+++ [0917 04:15:16] Building go targets for linux/ppc64le
k8s.io/kubernetes/hack/make-rules/helpers/go2make (non-static)
+++ [0917 04:15:35] Building go targets for linux/ppc64le
k8s.io/code-generator/cmd/prerelease-lifecycle-gen (non-static)
+++ [0917 0... | build constraints exclude all Go files error while running unit tests on linux/ppc64le platform | https://api.github.com/repos/kubernetes/kubernetes/issues/112539/comments | 2 | 2022-09-17T06:41:55Z | 2022-09-17T10:00:28Z | https://github.com/kubernetes/kubernetes/issues/112539 | 1,376,686,217 | 112,539 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Upgraded from Kubernetes v1.25.0 to v1.25.1. Standard metrics-server deployment now causes the following message to appear in the kube-apiserver logs on a recurring basis:
```
E0917 00:20:27.674186 54 controller.go:113] loading OpenAPI spec for "v1beta1.metrics.k8s.io" failed with: failed... | apiserver aggregation redirect rejection incorrectly fails on `304 Not Modified` responses | https://api.github.com/repos/kubernetes/kubernetes/issues/112524/comments | 5 | 2022-09-17T00:48:55Z | 2024-03-03T17:29:46Z | https://github.com/kubernetes/kubernetes/issues/112524 | 1,376,616,678 | 112,524 |
[
"kubernetes",
"kubernetes"
] | /sig node
### What happened?
Followed instructions to enable the alpha feature for kubernetes swap.
Azure AKS 1.24.3
Below is kubelet configuration
kubectl get nodes
NAME STATUS ROLES AGE VERSION
aks-npoolb2ms-73462207-vmss000000 Ready agent 22m v1.24.3
kubelet config
"failSwapOn": false,
"memorySwa... | Kubernetes swap support alpha feature -errors out | https://api.github.com/repos/kubernetes/kubernetes/issues/112523/comments | 10 | 2022-09-16T23:21:58Z | 2024-04-21T11:26:07Z | https://github.com/kubernetes/kubernetes/issues/112523 | 1,376,582,653 | 112,523 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
For 1.25 clusters with PodDIsruptionConditions enabled pods continue to run if the node is tainted with untolerated NoExecute taint.
Also, the error is not logged.
### What did you expect to happen?
The pod running on the tainted node should be terminated
### How can we reproduce it (as minima... | When PodDIsruptionConditions enabled pods are not terminated based on the NoExecute taint | https://api.github.com/repos/kubernetes/kubernetes/issues/112517/comments | 2 | 2022-09-16T15:30:54Z | 2022-09-23T16:00:27Z | https://github.com/kubernetes/kubernetes/issues/112517 | 1,376,109,142 | 112,517 |
[
"kubernetes",
"kubernetes"
] | CVSS Rating: [CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:L/I:L/A:L](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:L/I:L/A:L) (5.1, medium)
A security issue was discovered in kube-apiserver that allows an aggregated API server to redirect client traffic to any URL. This could lead to the clien... | CVE-2022-3172: Aggregated API server can cause clients to be redirected (SSRF) | https://api.github.com/repos/kubernetes/kubernetes/issues/112513/comments | 4 | 2022-09-16T13:14:50Z | 2022-11-10T03:57:00Z | https://github.com/kubernetes/kubernetes/issues/112513 | 1,375,935,782 | 112,513 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
- https://github.com/kubernetes/kubernetes/pull/112306 adds new version `v1beta3` for `flowcontrol.apiserver.k8s.io` in 1.26.
- For 1.26, we are setting the storage version to `v1beta2` because vN-1 understands that level.
- In 1.27, we should change the storage version from `v1beta2` to `v1b... | Set v1beta3 as the storage version for flowconrol in 1.27 | https://api.github.com/repos/kubernetes/kubernetes/issues/112512/comments | 5 | 2022-09-16T12:35:57Z | 2023-01-13T16:42:26Z | https://github.com/kubernetes/kubernetes/issues/112512 | 1,375,889,256 | 112,512 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
I'd like to be able to reuse the `k8s.io/kubernetes/pkg/controller/endpointslice` go module to build EndpointSlice controllers that can run outside of KCM.
Changing the [`controllerName`](https://github.com/kubernetes/kubernetes/blob/6824cd3addbb214e88e00f451babb8a44eb738d1/pkg/... | Allow for reuse of EndpointSlice controller code by making `controllerName` not const | https://api.github.com/repos/kubernetes/kubernetes/issues/112491/comments | 15 | 2022-09-16T00:20:30Z | 2024-03-18T21:10:38Z | https://github.com/kubernetes/kubernetes/issues/112491 | 1,375,235,735 | 112,491 |
[
"kubernetes",
"kubernetes"
] | https://github.com/kubernetes/kubernetes/blob/661899f1a14680840e06c84bc3ff46f73d203012/test/e2e/network/dns.go#L569
There are not e2e tests for some DNSPolicies
see: https://github.com/kubernetes/kubernetes/issues/112481
/help
/sig network | Add more e2e test cases for other DNSPolicies | https://api.github.com/repos/kubernetes/kubernetes/issues/112488/comments | 3 | 2022-09-15T22:04:16Z | 2022-09-16T19:50:51Z | https://github.com/kubernetes/kubernetes/issues/112488 | 1,375,136,672 | 112,488 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Unable to access application using "service" name of kubernetes when using "hostNetwork" in Pod Spec.
### What did you expect to happen?
I should able to access the application using "service" name of kubernetes
### How can we reproduce it (as minimally and precisely as possible)?
Deploy the app... | Unable to access application using "service" name of kubernetes when using "hostNetwork" | https://api.github.com/repos/kubernetes/kubernetes/issues/112481/comments | 10 | 2022-09-15T17:09:59Z | 2022-09-16T14:49:20Z | https://github.com/kubernetes/kubernetes/issues/112481 | 1,374,840,295 | 112,481 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Running kubelet on a host with iptables-1.8.8 (nf_tables mode) does not work due to kube-proxy image uses iptables-1.8.7. kube-proxy ends up replace the rule
```
-A KUBE-FIREWALL -m comment --comment "kubernetes firewall for dropping marked packets" -m mark --mark 0x8000/0x8000 -j DROP
```
with
... | kube-router does not work with iptables 1.8.8 (nf_tables) on host | https://api.github.com/repos/kubernetes/kubernetes/issues/112477/comments | 29 | 2022-09-15T14:51:33Z | 2022-10-11T16:54:01Z | https://github.com/kubernetes/kubernetes/issues/112477 | 1,374,658,913 | 112,477 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I tried to use runAsNonRoot in the container security context for windows containers. The user for the image is not set, and it runs as ContainerAdministrator by default. According to https://kubernetes.io/docs/concepts/windows/intro/#compatibility-v1-pod-spec-containers, it should "prevent contai... | Windows runAsNonRoot does not block default ContainerAdministrator | https://api.github.com/repos/kubernetes/kubernetes/issues/112469/comments | 19 | 2022-09-15T08:15:33Z | 2024-11-15T08:56:50Z | https://github.com/kubernetes/kubernetes/issues/112469 | 1,374,120,640 | 112,469 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Hi there,
I want to use networkpolicy to only allow pods in the same namespace to call each other and block all other namespaces. But this will also block nginx-ingress-controller and I can't access domain. I get error `504 Gateway Time-out`. Then, I created another networkpolicy to allow pods fr... | NetworkPolicy block access nginx-ingress-controller | https://api.github.com/repos/kubernetes/kubernetes/issues/112467/comments | 7 | 2022-09-15T07:08:32Z | 2022-12-08T01:11:43Z | https://github.com/kubernetes/kubernetes/issues/112467 | 1,374,038,775 | 112,467 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are flaking?
Unit tests failed with `TestWhoAmIRun`, see https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/112025/pull-kubernetes-unit/1570285754330910720
### Which tests are flaking?
TestWhoAmIRun/success_test
### Since when has it been flaking?
None
### Testgrid link
http... | Unit tests failed with `TestWhoAmIRun` | https://api.github.com/repos/kubernetes/kubernetes/issues/112465/comments | 7 | 2022-09-15T06:27:07Z | 2022-09-15T12:29:26Z | https://github.com/kubernetes/kubernetes/issues/112465 | 1,373,995,290 | 112,465 |
[
"kubernetes",
"kubernetes"
] | Dear
When I try to pull the image with command "sudo kubeadm config images pull"
I got following error. Can anybody help me in it. Also I am new in Kubernetes. So guide me step by step :)
I0915 10:09:10.441007 70082 version.go:182] fetching Kubernetes version from URL: https://dl.k8s.io/release/stable-1.20.txt
... | kubeadm config images pull failed on Ubuntu 20.04 | https://api.github.com/repos/kubernetes/kubernetes/issues/112464/comments | 5 | 2022-09-15T05:57:03Z | 2022-09-15T08:30:35Z | https://github.com/kubernetes/kubernetes/issues/112464 | 1,373,968,147 | 112,464 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
We have been noticing the below issue where the application pod deployed on the Kubernetes cluster, fails to make a connection to external DB.
Kubernetes API: io.kubernetes.client.openapi.ApiException: java.net.ConnectException: Failed to connect to /10.96.0.1:443
io.kubernetes.client.openapi.ApiE... | DNS lookup issue Kubernetes API: io.kubernetes.client.openapi.ApiException: java.net.ConnectException: Failed to connect to /10.96.0.1:443 | https://api.github.com/repos/kubernetes/kubernetes/issues/112462/comments | 3 | 2022-09-14T23:27:41Z | 2022-09-25T21:57:49Z | https://github.com/kubernetes/kubernetes/issues/112462 | 1,373,698,597 | 112,462 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
https://testgrid.k8s.io/sig-network-gce#gci-gce-ipvs
### Which tests are failing?
Kubernetes e2e suite.[It] [sig-network] LoadBalancers should only allow access from service loadbalancer source ranges [Slow]
### Since when has it been failing?
Sept 1st
### Testgrid link
... | [Failing Test][IPVS] LoadBalancers should only allow access from service loadbalancer source ranges | https://api.github.com/repos/kubernetes/kubernetes/issues/112460/comments | 3 | 2022-09-14T21:08:39Z | 2022-09-15T09:45:23Z | https://github.com/kubernetes/kubernetes/issues/112460 | 1,373,588,952 | 112,460 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
- Job name: ci-cadvisor-e2e
- Job config link: https://github.com/kubernetes/test-infra/blob/master/config/jobs/cadvisor/cadvisor.yaml#L52
### Which tests are failing?
Whole job is failing.
### Since when has it been failing?
2022-09-07 16:56 PST
### Testgrid link
https://testgrid.k8... | Testgrid sig-node-cadvisor#cadvisor-e2e is consistently failing | https://api.github.com/repos/kubernetes/kubernetes/issues/112459/comments | 8 | 2022-09-14T20:33:00Z | 2022-09-17T01:53:38Z | https://github.com/kubernetes/kubernetes/issues/112459 | 1,373,551,474 | 112,459 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
I use configMap to implement the variable into pods. Then I need to configured the value from the file into env value . How to make it ?
- command:
- SERVER_PROPERTIES="$(cat /etc/voldemort/config/server.properties)"
env:
- name: SERVER_PROPERTIES
value: $... | have no possibility to add data from the file | https://api.github.com/repos/kubernetes/kubernetes/issues/112456/comments | 4 | 2022-09-14T17:47:45Z | 2022-09-25T21:58:18Z | https://github.com/kubernetes/kubernetes/issues/112456 | 1,373,367,568 | 112,456 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Hi team, Hope all going good :)
I have found a bug that is very sensitive to following below found in the file: ```https://github.com/kubernetes/kubernetes/blob/74bc8a3211620397419f0e4ea996e862b070f9bb/test/e2e/common/runtime.go```
```"auth": "X2pzb25fa2V5OnsKICAidHlwZSI6ICJzZXJ2aWNlX2FjY291bn... | BUG: Found sensitive information in following file: "kubernetes/test/e2e/common/runtime.go" | https://api.github.com/repos/kubernetes/kubernetes/issues/112453/comments | 9 | 2022-09-14T16:55:10Z | 2022-09-21T07:23:26Z | https://github.com/kubernetes/kubernetes/issues/112453 | 1,373,305,290 | 112,453 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
In a multi-node setup, when one of nodes fails (has `NotReady` status) deployment (with 1 replica) will recreate pod on healthy node. If after that admin will try to modify this deployment (e.g. using `kubectl set env`) the healthy pod will get terminated and no new pod will be spawned. This happe... | Deployment fails to spawn new replicas after getting updated if one of nodes is `NotReady` (Multi-node setup) | https://api.github.com/repos/kubernetes/kubernetes/issues/112452/comments | 7 | 2022-09-14T16:02:21Z | 2023-02-12T15:28:48Z | https://github.com/kubernetes/kubernetes/issues/112452 | 1,373,238,549 | 112,452 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Node is being shutdown, then according to logs all pods are being terminated, howewer, some remain scheduled/running on the node.
### What did you expect to happen?
Expected that all pods being evacuated/rescheduled to another running node.
### How can we reproduce it (as minimally and precisely ... | GracefulNodeShutdown not evacuating all pods | https://api.github.com/repos/kubernetes/kubernetes/issues/112443/comments | 37 | 2022-09-14T09:33:05Z | 2024-12-18T18:41:45Z | https://github.com/kubernetes/kubernetes/issues/112443 | 1,372,663,611 | 112,443 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are flaking?
https://prow.k8s.io/job-history/gs/ppc64le-kubernetes/logs/periodic-kubernetes-containerd-conformance-test-ppc64le
### Which tests are flaking?
- [sig-network] Services should be able to switch session affinity for NodePort service [LinuxOnly] [Conformance]
- [sig-network] Services shoul... | Flake: periodic-kubernetes-containerd-conformance-test-ppc64le, e2e conformance test in /e2e/network/service.go related to session affinity | https://api.github.com/repos/kubernetes/kubernetes/issues/112442/comments | 53 | 2022-09-14T08:44:34Z | 2023-01-05T16:57:13Z | https://github.com/kubernetes/kubernetes/issues/112442 | 1,372,597,236 | 112,442 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I have a pod that serves file downloads and is using curl for testing. When testing through the cluster IP, "Connection Reset by Peer" always appears in a few minutes, and the download rate is quickly reduced to 0. However, everything is ok when using pod ip.
The above operations are all performed ... | "Connection reset by peer" appears when accessing services, but normal when accessing pod | https://api.github.com/repos/kubernetes/kubernetes/issues/112441/comments | 7 | 2022-09-14T07:29:26Z | 2022-09-16T08:48:07Z | https://github.com/kubernetes/kubernetes/issues/112441 | 1,372,499,019 | 112,441 |
[
"kubernetes",
"kubernetes"
] | I have a bunch of images on the node. I want to upload them to the master node. In fact, there are many ways to upload, but what I want to know is, is there a tool inside Kubernetes that can upload pictures? | How does the node send data to the master node? | https://api.github.com/repos/kubernetes/kubernetes/issues/112434/comments | 5 | 2022-09-14T01:14:30Z | 2022-09-15T05:32:59Z | https://github.com/kubernetes/kubernetes/issues/112434 | 1,372,186,983 | 112,434 |
[
"kubernetes",
"kubernetes"
] | # Progress <code>[6/6]</code>
- [X] APISnoop org-flow: [CoreV1LimitRangeTest.org](https://github.com/apisnoop/ticket-writing/blob/master/CoreV1LimitRangeTest.org)
- [X] Test approval issue: [#112429](https://github.com/kubernetes/kubernetes/issues/112429)
- [X] Test PR: [#112430](https://github.com/kubernet... | Write List, Patch and Delete LimitRange test +3 Endpoints | https://api.github.com/repos/kubernetes/kubernetes/issues/112429/comments | 3 | 2022-09-14T00:24:11Z | 2022-10-14T09:45:02Z | https://github.com/kubernetes/kubernetes/issues/112429 | 1,372,153,791 | 112,429 |
[
"kubernetes",
"kubernetes"
] | In https://github.com/kubernetes/kubernetes/blob/084a412e03816ef3ea57da928ae8fd332d17ab59/staging/src/k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/validation/validation.go#L1366
it has multiple `for` loops that look similar to this:
```go
for _, s := range s.AllOf {
if SchemaHas(&s, pred) {
retur... | apiextensions: SchemaHas performs excessive allocations | https://api.github.com/repos/kubernetes/kubernetes/issues/112428/comments | 3 | 2022-09-13T22:23:15Z | 2022-09-15T16:37:42Z | https://github.com/kubernetes/kubernetes/issues/112428 | 1,372,065,564 | 112,428 |
[
"kubernetes",
"kubernetes"
] | For example, the annotation keys should match label key validation. Total size of annotation values should also be limited.
cc @aramase @nilekhc | [KMSv2] validate encryption response | https://api.github.com/repos/kubernetes/kubernetes/issues/112426/comments | 2 | 2022-09-13T19:28:14Z | 2022-09-27T21:26:03Z | https://github.com/kubernetes/kubernetes/issues/112426 | 1,371,910,498 | 112,426 |
[
"kubernetes",
"kubernetes"
] | Hi,
My K8s and Ceph cluster is on on-premise setup.
On my K8s cluster nodes, I am not able to use the kubectl command. For some reason the cluster is not accessible. I see the pods are working as I have accused through the LB IP of each pods.
Here I want to know, if I create a new K8s cluster, will I be able to ... | K8s cluster lost | How to re-use PVC in new K8s | https://api.github.com/repos/kubernetes/kubernetes/issues/112418/comments | 4 | 2022-09-13T11:02:52Z | 2022-09-13T19:26:35Z | https://github.com/kubernetes/kubernetes/issues/112418 | 1,371,263,957 | 112,418 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
periodic-kubernetes-unit-test-ppc64le
### Which tests are failing?
k8s.io/kubernetes/test/e2e/framework/internal/unittests/cleanup: TestCleanup
### Since when has it been failing?
Probably since it was merged in https://github.com/kubernetes/kubernetes/pull/111998
### Testgrid link
ht... | [Failing Test] periodic-kubernetes-unit-test-ppc64le, k8s.io/kubernetes/test/e2e/framework/internal/unittests/cleanup | https://api.github.com/repos/kubernetes/kubernetes/issues/112412/comments | 16 | 2022-09-13T05:11:48Z | 2022-09-19T14:25:50Z | https://github.com/kubernetes/kubernetes/issues/112412 | 1,370,865,702 | 112,412 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Kubeadm init fails to create ConfigMap of certs it generated. Reopening since https://github.com/kubernetes/kubernetes/issues/112378 was closed incorrectly.
### What did you expect to happen?
Kubeadm to create the ConfigMap with certs.
### How can we reproduce it (as minimally and precise... | kubeadm init fails to create ConfigMap when --upload certs is set | https://api.github.com/repos/kubernetes/kubernetes/issues/112411/comments | 19 | 2022-09-13T02:43:11Z | 2024-02-13T11:08:05Z | https://github.com/kubernetes/kubernetes/issues/112411 | 1,370,770,841 | 112,411 |
[
"kubernetes",
"kubernetes"
] | it can be useful for debugging to see when a taint was added and afaik there is no harm in setting it
... at least it should be an optional `--add-time-added` flag
/sig cli | `kubectl taint` should always set `timeAdded` | https://api.github.com/repos/kubernetes/kubernetes/issues/113044/comments | 7 | 2022-09-12T22:54:06Z | 2023-03-12T13:38:44Z | https://github.com/kubernetes/kubernetes/issues/113044 | 1,407,685,727 | 113,044 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
I'd like Kubernetes to state the position on updating the Go language version used for release branches.
### Why is this needed?
I couldn't find a publicly stated Kubernetes policy around Go version updates for release branches documented anywhere. Right now, Kubernetes maintains... | Document Kubernetes approach to Go versions in release branches | https://api.github.com/repos/kubernetes/kubernetes/issues/112408/comments | 23 | 2022-09-12T22:03:55Z | 2024-06-18T09:22:21Z | https://github.com/kubernetes/kubernetes/issues/112408 | 1,370,572,569 | 112,408 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
The following refactoring of the kubelet's devicemanager was done as part of the 1.25 release: https://github.com/kubernetes/kubernetes/commit/db88676c20629354d8eeb4b7014ae7884481ffca
As part of this, a change in semantics was (unintentionally) introduced which is breaking at least one 3rd part... | Change in semantics for the device plugin registration process | https://api.github.com/repos/kubernetes/kubernetes/issues/112395/comments | 16 | 2022-09-12T15:55:58Z | 2023-01-19T12:24:37Z | https://github.com/kubernetes/kubernetes/issues/112395 | 1,370,139,265 | 112,395 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are flaking?
pull-kubernetes-unit
### Which tests are flaking?
k8s.io/kubernetes/test/e2e/framework/internal/unittests/cleanup.TestCleanup
### Since when has it been flaking?
Probably since it was merged in https://github.com/kubernetes/kubernetes/pull/111998.
### Testgrid link
https://prow.k8s.... | flake: pull-kubernetes-unit, k8s.io/kubernetes/test/e2e/framework/internal/unittests/cleanup | https://api.github.com/repos/kubernetes/kubernetes/issues/112388/comments | 2 | 2022-09-12T09:23:10Z | 2022-09-12T12:27:38Z | https://github.com/kubernetes/kubernetes/issues/112388 | 1,369,554,621 | 112,388 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Hi team, hope all going well.
I have tried to install Kubernetes and build it on my VPS terminal. which has a capacity like 2 GB Memory / 60 GB Disk / BLR1 - Ubuntu 22.04 x64.
It gets stuck after we enter the command **make**
I have tried to install it for few times for successful installat... | Unable to install Kubernetes on VPS via make command | https://api.github.com/repos/kubernetes/kubernetes/issues/112382/comments | 5 | 2022-09-11T16:28:28Z | 2022-09-11T20:01:09Z | https://github.com/kubernetes/kubernetes/issues/112382 | 1,368,996,256 | 112,382 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Kubeadm init fails to create ConfigMap of certs it generated.
### What did you expect to happen?
Kubeadm to create the ConfigMap with certs.
### How can we reproduce it (as minimally and precisely as possible)?
```
kubeadm init --upload-certs
```
### Anything else we need to know?... | kubeadm init fails to create ConfigMap when --upload certs is set | https://api.github.com/repos/kubernetes/kubernetes/issues/112378/comments | 6 | 2022-09-11T10:37:53Z | 2022-09-11T21:04:43Z | https://github.com/kubernetes/kubernetes/issues/112378 | 1,368,902,789 | 112,378 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When running kube-apiserver with the options `--etcd-servers=http://localhost:2379 --service-account-issuer=kube-home-node --service-account-signing-key-file=/dev/zero --authorization-mode=Node`, it immediately starts eating all the RAM available, until it gets killed by the OOMKiller after a few se... | Kube-apiserver quickly reaches OOMKill on startup | https://api.github.com/repos/kubernetes/kubernetes/issues/112376/comments | 5 | 2022-09-10T17:54:32Z | 2022-09-11T15:48:19Z | https://github.com/kubernetes/kubernetes/issues/112376 | 1,368,690,413 | 112,376 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
```shell
$ sudo kubeadm init --kubernetes-version=1.25.0 --skip-phases=addon/kube-proxy --cri-socket=unix:///run/containerd/containerd.sock --image-repository <private-registry> --v=9
```
Log: https://gist.github.com/yudaprama/4950f1df0dd3f63f141e4d7a47f9f907
**Kubelet status**
```shell... | Couldn't initialize a Kubernetes cluster | https://api.github.com/repos/kubernetes/kubernetes/issues/112371/comments | 4 | 2022-09-10T06:54:10Z | 2022-09-10T08:10:57Z | https://github.com/kubernetes/kubernetes/issues/112371 | 1,368,528,336 | 112,371 |
[
"kubernetes",
"kubernetes"
] | @feroenmmek: There are no sig labels on this issue. Please add an appropriate label by using one of the following commands:
- `/sig <group-name>`
- `/wg <group-name>`
- `/committee <group-name>`
Please see the [group list](https://git.k8s.io/community/sig-list.md) for a listing of the SIGs, working groups, and co... | @feroenmmek: There are no sig labels on this issue. Please add an appropriate label by using one of the following commands: | https://api.github.com/repos/kubernetes/kubernetes/issues/112370/comments | 5 | 2022-09-09T21:46:39Z | 2022-09-10T04:09:58Z | https://github.com/kubernetes/kubernetes/issues/112370 | 1,368,358,649 | 112,370 |
[
"kubernetes",
"kubernetes"
] | @249043822 , thank you for the PR for fixing the issue! Do you think it is easy to add some sort of unit test about the behavior?
_Originally posted by @jingxu97 in https://github.com/kubernetes/kubernetes/issues/111205#issuecomment-1202047929_ | @249043822 , thank you for the PR for fixing the issue! Do you think it is easy to add some sort of unit test about the behavior? | https://api.github.com/repos/kubernetes/kubernetes/issues/112369/comments | 4 | 2022-09-09T21:46:15Z | 2022-09-12T10:32:59Z | https://github.com/kubernetes/kubernetes/issues/112369 | 1,368,358,424 | 112,369 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Trying to bootstrap a cluster using the following configuration file fails:
```
# kubeadm-config.yaml
kind: ClusterConfiguration
apiVersion: kubeadm.k8s.io/v1beta3
kubernetesVersion: v1.25.0
networking:
dnsDomain: k8s.ge.nau.so
podSubnet: 2a0a:e5c0:13:aaaa::/80
serviceSubnet: 2a0a:e... | kubeadm incorrectly fails on /80 IPv6 network | https://api.github.com/repos/kubernetes/kubernetes/issues/112367/comments | 15 | 2022-09-09T20:49:33Z | 2022-09-12T06:44:03Z | https://github.com/kubernetes/kubernetes/issues/112367 | 1,368,312,747 | 112,367 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When trying to restart kubelet, it gets stuck with following error message:
`systemd[1]: kubelet.service: Killing process 1469279 (mount.cifs) with signal SIGKILL.`
### What did you expect to happen?
restart service without issues
### How can we reproduce it (as minimally and precisely as possib... | kubelet service restart stuck | https://api.github.com/repos/kubernetes/kubernetes/issues/112364/comments | 7 | 2022-09-09T17:20:16Z | 2022-09-12T07:55:11Z | https://github.com/kubernetes/kubernetes/issues/112364 | 1,368,113,947 | 112,364 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
A pod created by statefulSet requiring a pvc with delay binding was preempted by other pods. Then it is scheduled to another node which is different from the `selected-node` in pvc's annotation.
### What did you expect to happen?
PVC's `selected-node` should be updated or removed when pod requiri... | PVC with mode WaitForFirstConsumer may have error selected-node | https://api.github.com/repos/kubernetes/kubernetes/issues/112347/comments | 10 | 2022-09-09T09:21:37Z | 2023-03-18T04:50:56Z | https://github.com/kubernetes/kubernetes/issues/112347 | 1,367,539,008 | 112,347 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
- For raw block CSI volumes on Kubernetes, kubelet ends up calling CSI `NodeStageVolume` for every single "map" (i.e. raw block "mount") operation for a volume already attached to the node.
### What did you expect to happen?
[Per CSI spec](https://github.com/container-storage-interface/spec... | CSI `NodeStageVolume` called multiple times for same attached volume on same node | https://api.github.com/repos/kubernetes/kubernetes/issues/112343/comments | 9 | 2022-09-09T01:23:12Z | 2022-09-13T22:45:13Z | https://github.com/kubernetes/kubernetes/issues/112343 | 1,367,162,129 | 112,343 |
[
"kubernetes",
"kubernetes"
] | These were introduced in #112017 for the sake of backwards compatibility and should be removed.
/kind cleanup
/assign
/milestone v1.26 | Remove client-go TLS cache dual function/holder fields | https://api.github.com/repos/kubernetes/kubernetes/issues/112342/comments | 3 | 2022-09-08T23:50:56Z | 2022-09-15T22:33:34Z | https://github.com/kubernetes/kubernetes/issues/112342 | 1,367,103,927 | 112,342 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are flaking?
```
roundtrip.go:254: round tripping to batch/v1, Kind=Job v1.Job
roundtrip.go:361: Job: diff: &batch.Job{
TypeMeta: {},
ObjectMeta: {Name: "渌肥崧鎖a|瘃剷@", GenerateName: "ŚĮsæ醮|@Ƥ罒瓥巬ƜgǺh", Namespace: "$Ȳh輭RcÌ糦µ囬qɹR", SelfLink: "L", ...},
Spec:... | TestRoundTripTypes failure on batch/v1 Job | https://api.github.com/repos/kubernetes/kubernetes/issues/112340/comments | 8 | 2022-09-08T22:56:04Z | 2022-09-09T19:25:24Z | https://github.com/kubernetes/kubernetes/issues/112340 | 1,367,073,147 | 112,340 |
[
"kubernetes",
"kubernetes"
] | The same problem on `1.22.3-gke.700`
_Originally posted by @maxpain in https://github.com/kubernetes/kubernetes/issues/98534#issuecomment-1003169567_ | pod stuck with NodeAffinity status // using spot VMs under K8s `1.22.x` and `1.23.x` | https://api.github.com/repos/kubernetes/kubernetes/issues/112333/comments | 22 | 2022-09-08T18:12:08Z | 2024-04-20T23:01:00Z | https://github.com/kubernetes/kubernetes/issues/112333 | 1,366,785,122 | 112,333 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Example working config map:
```
apiVersion: v1
kind: ConfigMap
metadata:
name: game-demo
data:
shortCommitHash: '0340914'
```
example of failing config map:
```
apiVersion: v1
kind: ConfigMap
metadata:
name: game-demo
data:
shortCommitHash: 0340914
```
The difference is m... | Misintepretation of integer-like strings when deploying a ConfigMap | https://api.github.com/repos/kubernetes/kubernetes/issues/112326/comments | 9 | 2022-09-08T15:01:12Z | 2024-08-06T18:17:49Z | https://github.com/kubernetes/kubernetes/issues/112326 | 1,366,519,184 | 112,326 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
## Background
Whilst investigating an issue affecting one of our production kubernetes clusters, I had to take a look at the *“AvailableConditonController”s* that run as part of the kube-aggregator, and implements a rate limited workqueue for scheduling health checks of api extensions that live... | Improve behaviour when immediately adding work items to a rate-limited or delaying workqueue. | https://api.github.com/repos/kubernetes/kubernetes/issues/112325/comments | 11 | 2022-09-08T14:56:38Z | 2025-02-08T14:20:34Z | https://github.com/kubernetes/kubernetes/issues/112325 | 1,366,510,288 | 112,325 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
If the content of `/etc/resolv.conf` is
```
options timeout:1
options attempts:3
```
https://github.com/kubernetes/kubernetes/blob/ca09ed0fe2c245a0df4f533aa29f7b48a8672cff/pkg/kubelet/network/dns/dns.go#L250-L278
only could recognize the last option `options attempts:3` and `options timeou... | kubelet doesn't merge multiple 'options' lines from node /etc/resolv.conf | https://api.github.com/repos/kubernetes/kubernetes/issues/112323/comments | 30 | 2022-09-08T14:09:12Z | 2022-09-30T04:10:29Z | https://github.com/kubernetes/kubernetes/issues/112323 | 1,366,414,904 | 112,323 |
[
"kubernetes",
"kubernetes"
] | Hi，my k8s version is 1.22. Now I want to upgrade the running single-stack cluster to dual-stack. Can I directly change the pod-network-cidr and service-cidr in the kubeadm-config file to make it take effect? If not, how can I do it？ | single-stack to dual-stack | https://api.github.com/repos/kubernetes/kubernetes/issues/112321/comments | 4 | 2022-09-08T13:55:49Z | 2022-09-09T06:38:38Z | https://github.com/kubernetes/kubernetes/issues/112321 | 1,366,388,587 | 112,321 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Our cluster has 5600 nodes and `kube-controller-manager` memory usage 197.5GiB, After restarting `kube-controller-manager`, the memory usage is only 15GiB, It looks like the controller manager memory is leaking.
<img width="875" alt="image" src="https://user-images.githubusercontent.com/3377677/... | kube-controller-manager memory leak | https://api.github.com/repos/kubernetes/kubernetes/issues/112319/comments | 27 | 2022-09-08T12:50:13Z | 2024-01-06T03:40:52Z | https://github.com/kubernetes/kubernetes/issues/112319 | 1,366,260,427 | 112,319 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
The current build process, triggered by
```console
$ make
```
creates the same executables in the directories _output/local/go/bin and _output/local/bin/linux/amd64. This is currently 2×1.6GB.
### What did you expect to happen?
I expect that the resulting binaries are presented only once on t... | `make` stores on the file system each final binary twice | https://api.github.com/repos/kubernetes/kubernetes/issues/112317/comments | 7 | 2022-09-08T11:20:50Z | 2023-02-11T09:09:45Z | https://github.com/kubernetes/kubernetes/issues/112317 | 1,366,094,592 | 112,317 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
We have some pretty old Kubernetes (1.15.3) installations running in several locations which we are updating to 1.21.x. When context had been changed from new cluster to old one - right `kubectl` version were not be able to be downloaded:
```
➜ ~ kubectl get pods
I0908 11:09:54.485273 33423 ve... | Missing kubectl version 1.15.3 | https://api.github.com/repos/kubernetes/kubernetes/issues/112315/comments | 3 | 2022-09-08T08:28:40Z | 2022-09-09T12:51:16Z | https://github.com/kubernetes/kubernetes/issues/112315 | 1,365,783,853 | 112,315 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Before commit aecaac0d7e0a6028078ce3b6165e17ce8022f796 the LB behavior for unmanaged nodes (labeled with `kubernetes.azure.com/managed: false`) is that:
* cloud provider will ignore the VMSS and VMSS VMs when ensure hosts in pool
* if the VMSS already joined LB backend pool, it will remain in the ... | Load balancer behavior changed for unmanaged nodes | https://api.github.com/repos/kubernetes/kubernetes/issues/112313/comments | 18 | 2022-09-08T08:05:06Z | 2024-06-18T05:09:55Z | https://github.com/kubernetes/kubernetes/issues/112313 | 1,365,748,067 | 112,313 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I modified the containerd to do some additional operations on the container based on the Pod annotation, but actually, looking at the containerd logs, I found that the Pod annotation is passed to the containerd in the `Create SandBox` interface, not in the `Create Container` interface.
I'm not su... | Pod annotation pass to the container runtime by CreateSandbox interface | https://api.github.com/repos/kubernetes/kubernetes/issues/112311/comments | 11 | 2022-09-08T07:51:22Z | 2023-02-11T20:18:47Z | https://github.com/kubernetes/kubernetes/issues/112311 | 1,365,722,795 | 112,311 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
In ResourceQuota's doc( https://kubernetes.io/docs/concepts/policy/resource-quotas/ )m written as:
- A resource quota, defined by a ResourceQuota object, provides constraints that limit aggregate resource consumption per namespace. It can limit the quantity of objects that can be created in a nam... | Total amount of ephemeral-storage in namespace is not limited/tracked properly | https://api.github.com/repos/kubernetes/kubernetes/issues/112310/comments | 13 | 2022-09-08T07:28:23Z | 2022-09-15T03:53:24Z | https://github.com/kubernetes/kubernetes/issues/112310 | 1,365,683,169 | 112,310 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
StatefulSet spec's template was updated:
<details>
```apiVersion: v1
items:
- apiVersion: apps/v1
kind: StatefulSet
# many other unrelated stuff
spec:
replicas: 5
minReadySeconds: 300
podManagementPolicy: Parallel
updateStrategy:
rollingUpdate:
ma... | Parallel pod management with maxUnavailable set should not ignore minReadySeconds | https://api.github.com/repos/kubernetes/kubernetes/issues/112307/comments | 14 | 2022-09-07T22:42:38Z | 2024-08-28T18:57:39Z | https://github.com/kubernetes/kubernetes/issues/112307 | 1,365,271,224 | 112,307 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
After upgrading from Kubernetes 1.22.6 to 1.23.8 (AKS), I've noticed abnormal behavior where application connected to Pod (ClusterIP) doesn't always see socket closing immediately when Pod is terminated (Redis in this case).
This was seen for traffic within cluster.
I have recorded simple vide... | Socket not always closing when Pod terminated (reproduce on 1.23, but not on 1.24) | https://api.github.com/repos/kubernetes/kubernetes/issues/112300/comments | 9 | 2022-09-07T21:13:54Z | 2023-02-11T22:20:46Z | https://github.com/kubernetes/kubernetes/issues/112300 | 1,365,193,462 | 112,300 |
Subsets and Splits
Unique Owner-Repo Count
Counts the number of unique owner-repos in the dataset, providing a basic understanding of diverse repositories.