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?
Found some error logs when sending series events to apiserver:
```
eventTime: Invalid value: 2022-08-19 16:00:45.305977 +0800 CST: field is immutable
```
seems the later eventTime differed from the first one in series events
After investigation, I found the problem was in the marshal.
Mic... | MicroTime marshalled at different precision for json and proto | https://api.github.com/repos/kubernetes/kubernetes/issues/111928/comments | 4 | 2022-08-19T09:04:40Z | 2022-09-02T16:42:18Z | https://github.com/kubernetes/kubernetes/issues/111928 | 1,344,162,716 | 111,928 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Downloaded the 1.24.4 release tar ball. Examined ./CHANGELOG/CHANGELOG-1.24.md. The top line in the TOC is` - [v1.24.3](#v1243)
`
### What did you expect to happen?
Expected to see the v1.24.4 changelog in the table of contents and in the content area.
### How can we reproduce it (as minimally ... | Changelog in 1.24.4 release not updated | https://api.github.com/repos/kubernetes/kubernetes/issues/111926/comments | 6 | 2022-08-18T21:49:39Z | 2023-01-16T00:08:23Z | https://github.com/kubernetes/kubernetes/issues/111926 | 1,343,683,945 | 111,926 |
[
"kubernetes",
"kubernetes"
] | Creating this umbrella issue to track how we handle storage migration for kms:
- How to interact with kms v2 design of using `currentKeyID`
- How will it work for `v1beta1`to enable migration from `AES-CBC` to `AES-GCM`
https://github.com/kubernetes/kubernetes/blob/d581cc90adba6c84919738841fe3e07302d53e33/staging/sr... | [KMS] Strategy for storage migration | https://api.github.com/repos/kubernetes/kubernetes/issues/111925/comments | 34 | 2022-08-18T21:47:42Z | 2024-10-16T20:18:27Z | https://github.com/kubernetes/kubernetes/issues/111925 | 1,343,682,425 | 111,925 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
It seems impossible to request `kubectl edit` to send a server-side apply request
### What did you expect to happen?
To have a --server-side flag
### How can we reproduce it (as minimally and precisely as possible)?
`kubectl edit --help`
### Anything else we need to know?
_No response_
### Ku... | kubectl edit seems to always use client-side apply, can it use server-side? | https://api.github.com/repos/kubernetes/kubernetes/issues/111924/comments | 12 | 2022-08-18T21:37:11Z | 2024-06-23T00:21:04Z | https://github.com/kubernetes/kubernetes/issues/111924 | 1,343,673,958 | 111,924 |
[
"kubernetes",
"kubernetes"
] | Add additional logging at level `6` that associates UID with the metadata from the request.
xref: https://github.com/kubernetes/kubernetes/pull/111126#discussion_r934911719
/sig auth | [KMSv2] Add additional logging with UID and metadata | https://api.github.com/repos/kubernetes/kubernetes/issues/111923/comments | 17 | 2022-08-18T21:26:38Z | 2023-02-27T01:02:20Z | https://github.com/kubernetes/kubernetes/issues/111923 | 1,343,665,057 | 111,923 |
[
"kubernetes",
"kubernetes"
] | Today you need multiple encryption providers to communicate to the API server if data stored in etcd is stale (i.e. the KMS v1beta1 API has no way to communicate staleness). The KMS v2 API includes a key ID in the status API to allow for such a check to be performed. We need to wire the knowledge of the current key I... | [KMSv2] Use status key ID to determine staleness of encrypted data | https://api.github.com/repos/kubernetes/kubernetes/issues/111922/comments | 6 | 2022-08-18T21:24:33Z | 2023-01-19T18:28:18Z | https://github.com/kubernetes/kubernetes/issues/111922 | 1,343,663,390 | 111,922 |
[
"kubernetes",
"kubernetes"
] | This repo should start with just the KMS proto code under `k8s.io/kms/apis` (make sure the `OWNERS` files correctly require API approval). We will expand it later to include the reference implementation code (under some library dirs and an examples dir). | [KMSv2] Create new staging repo k8s.io/kms | https://api.github.com/repos/kubernetes/kubernetes/issues/111921/comments | 6 | 2022-08-18T21:17:19Z | 2022-09-26T21:50:16Z | https://github.com/kubernetes/kubernetes/issues/111921 | 1,343,657,013 | 111,921 |
[
"kubernetes",
"kubernetes"
] | https://github.com/kubernetes/kubernetes/blob/d581cc90adba6c84919738841fe3e07302d53e33/staging/src/k8s.io/apiserver/pkg/storage/value/encrypt/envelope/kmsv2/envelope.go#L95-L99
/sig auth | [KMSv2] Use expiring cache | https://api.github.com/repos/kubernetes/kubernetes/issues/111920/comments | 7 | 2022-08-18T20:05:22Z | 2023-01-26T03:04:27Z | https://github.com/kubernetes/kubernetes/issues/111920 | 1,343,584,318 | 111,920 |
[
"kubernetes",
"kubernetes"
] | - Watch on the `EncryptionConfiguration`
- When changes are detected, process the `EncryptionConfiguration` resource, and add new transformers and update existing ones atomically.
- If there is an issue with creating or updating any of the transformers, retain the current configuration in the kube-apiserver and gener... | [KMSv2] Add support for hot reload of the `EncryptionConfiguration` | https://api.github.com/repos/kubernetes/kubernetes/issues/111919/comments | 5 | 2022-08-18T19:47:39Z | 2022-11-09T01:24:14Z | https://github.com/kubernetes/kubernetes/issues/111919 | 1,343,550,085 | 111,919 |
[
"kubernetes",
"kubernetes"
] | https://github.com/kubernetes/kubernetes/blob/3e396dbac5c61860e4b926f07721851091cf4110/staging/src/k8s.io/api/core/v1/types.go#L555
"contails" -> "contains" | "contains" misspelled as "contails" in PVC doc comment | https://api.github.com/repos/kubernetes/kubernetes/issues/111916/comments | 11 | 2022-08-18T16:07:39Z | 2025-02-08T07:34:07Z | https://github.com/kubernetes/kubernetes/issues/111916 | 1,343,318,845 | 111,916 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
A pod is getting admitted from a user which has no policy/podsecuritypolicies/use permission, here is the defined rule in the user's role/rolebinding (see that the apiGroups is `extensions`, not `policy`):
```
- apiGroups:
- ""
resources:
- 'pods'
verbs:
- 'create'
- apiGroups:
... | A PSP is wrongly respecting "extensions/podsecuritypolicies/use" for admission | https://api.github.com/repos/kubernetes/kubernetes/issues/111913/comments | 4 | 2022-08-18T14:49:06Z | 2022-08-19T13:51:51Z | https://github.com/kubernetes/kubernetes/issues/111913 | 1,343,218,958 | 111,913 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Switching from the gcp auth provider to the exec auth provider in 1.25 made `kubectl apply` requests which previously made a single connection to the API server make one connection per applied object.
If enough items are applied, the connections can start to fail because of ephemeral port exhau... | Using exec auth in kubectl triggers one connection per applied/described object | https://api.github.com/repos/kubernetes/kubernetes/issues/111911/comments | 22 | 2022-08-18T14:05:20Z | 2022-09-08T22:35:23Z | https://github.com/kubernetes/kubernetes/issues/111911 | 1,343,158,095 | 111,911 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
We have an kubeadm cluster (1 master and 2 worker nodes). The kube-apiserver is configured to use a webhook server for authn and authz. The kubeconfig is configured to use azure auth provider as well. On running any kubectl command , we are getting "Unauthorized" error . We checked that the request ... | Invalid Bearer token error in Kube-apiserver when using azure auth provider in kube-config | https://api.github.com/repos/kubernetes/kubernetes/issues/111902/comments | 8 | 2022-08-18T08:47:56Z | 2023-01-16T17:13:41Z | https://github.com/kubernetes/kubernetes/issues/111902 | 1,342,763,706 | 111,902 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
A kubernetes cluster deployed in AWS is subject to occasional zonal [outages](https://aws.amazon.com/premiumsupport/technology/pes/). In the most kubernetes cluster setup usecases(e.g kops), all control plane components(e.g kube-apiserver, kube-scheduler, kube-controller-manager) are setup as stat... | Relinquish leadership during zonal outage | https://api.github.com/repos/kubernetes/kubernetes/issues/111899/comments | 17 | 2022-08-18T00:11:44Z | 2024-10-31T20:14:24Z | https://github.com/kubernetes/kubernetes/issues/111899 | 1,342,403,719 | 111,899 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
API server failed on authorizer webhook parsing return value
api server logs for version
```
Flag --insecure-port has been deprecated, This flag has no effect now and will be removed in v1.24.
I0817 16:56:55.206742 1 server.go:629] external host was not specified, using 10.0.0.60
I081... | How to get Kubernetes API Server to pass requestor token to authorization webhook | https://api.github.com/repos/kubernetes/kubernetes/issues/111895/comments | 16 | 2022-08-17T18:48:37Z | 2024-12-02T20:39:04Z | https://github.com/kubernetes/kubernetes/issues/111895 | 1,342,146,637 | 111,895 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
It's possible to bump up against the etcd size limitations if your CRD is too big, since the apiserver request size limit is so big (IIRC 3 megs). We should expose a metric which corresponds to apiserver_response_size metric but we should have one for request size as well.
### Wh... | apiserver_request_size metrics should be present on kube-apiserver | https://api.github.com/repos/kubernetes/kubernetes/issues/111893/comments | 3 | 2022-08-17T15:58:32Z | 2022-08-30T20:14:54Z | https://github.com/kubernetes/kubernetes/issues/111893 | 1,341,982,082 | 111,893 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
ci-kubernetes-e2e-gce-cos-k8sstable3-alphafeatures
### Which tests are failing?
The job is unable to bootstrap a cluster.
### Since when has it been failing?
2022-08-10 05:03:36 +0000 UTC
### Testgrid link
https://testgrid.k8s.io/sig-release-1.22-blocking#gce-cos-k8sstable3-alphafeatu... | Failing ci-kubernetes-e2e-gce-cos-k8sstable3-alphafeatures on sig-release-1.22-blocking | https://api.github.com/repos/kubernetes/kubernetes/issues/111892/comments | 7 | 2022-08-17T15:39:52Z | 2022-08-22T19:56:11Z | https://github.com/kubernetes/kubernetes/issues/111892 | 1,341,959,689 | 111,892 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I migrated an existing EBS volume from in-tree plugin to external aws-ebs-csi-driver (https://github.com/kubernetes-sigs/aws-ebs-csi-driver). Resizing PVC twice in 6 hour window causes kube-controller-manager to crash.
Exception message:
```
kube-controller-manager I0817 13:46:32.803739 ... | kube-controller-manager crashes when AWS EBS pvc is unable to resize | https://api.github.com/repos/kubernetes/kubernetes/issues/111891/comments | 6 | 2022-08-17T14:08:19Z | 2022-08-24T03:08:39Z | https://github.com/kubernetes/kubernetes/issues/111891 | 1,341,824,744 | 111,891 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
### A Network Partition impacts our api extensions
We experienced a network issue affecting our kubernetes apiservers which partitioned one or more of our apiservers from the back-end end pods which were providing api extensions. The issue affected the apiservice extensions “[v1.subresources.k... | AvailableConditionController escalatory check behaviour during network partitions | https://api.github.com/repos/kubernetes/kubernetes/issues/111890/comments | 22 | 2022-08-17T13:48:29Z | 2025-02-27T21:12:40Z | https://github.com/kubernetes/kubernetes/issues/111890 | 1,341,796,085 | 111,890 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Hi. After adding new nodes to the cluster, pods on these nodes fail with the following errors:
```Could not resolve host: example.svc.cluster.local```
on old nodes, everything works fine. Please help, the problem has not yet been solved. I will provide additional information if necessary.
BAD n... | DNS does not work correctly on new nodes | https://api.github.com/repos/kubernetes/kubernetes/issues/111888/comments | 6 | 2022-08-17T11:21:06Z | 2022-09-01T16:00:03Z | https://github.com/kubernetes/kubernetes/issues/111888 | 1,341,611,415 | 111,888 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Since `kube-apiserver` doesn't specify a `WriteTimeout` on the server level it solely relies on the timeout filter to terminate HTTP requests.
The timeout filter wraps the `http.ResponseWriter` into a time-aware construct and passes it to an HTTP handler. Once the specified timeout has elapsed ... | kube-apiserver: some HTTP requests might hang indefinitely | https://api.github.com/repos/kubernetes/kubernetes/issues/111886/comments | 14 | 2022-08-17T09:35:52Z | 2024-03-26T20:24:49Z | https://github.com/kubernetes/kubernetes/issues/111886 | 1,341,470,813 | 111,886 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
There is no good pretty-printing for Kubernetes API objects, which affects debugging. All of the following options have drawbacks:
- `fmt.Sprintf("%+v")` (single line, no clear distinction between fields)
- `obj.String()` (auto-generated, single line, does not omit empty fields)
... | e2e: pretty-print objects | https://api.github.com/repos/kubernetes/kubernetes/issues/111884/comments | 8 | 2022-08-17T08:12:38Z | 2023-05-15T14:20:38Z | https://github.com/kubernetes/kubernetes/issues/111884 | 1,341,357,073 | 111,884 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
I'd like client-side rate limiting to be disabled in client-go when API server-side Priority and Fairness is enabled.
All client-go based Kubernetes clients are configured by default to use a token bucket rate limiter in an attempt to avoid overloading the API server. This is ... | Disable client-side rate-limiting when AP&F is enabled | https://api.github.com/repos/kubernetes/kubernetes/issues/111880/comments | 24 | 2022-08-17T04:03:38Z | 2025-01-21T21:41:03Z | https://github.com/kubernetes/kubernetes/issues/111880 | 1,341,136,856 | 111,880 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
One of the review comments for PR https://github.com/kubernetes/kubernetes/pull/102884 requested to move current pod resize E2E test from test/e2e/node to test/e2e_node.
Please see comment: https://github.com/kubernetes/kubernetes/pull/102884#discussion_r891689410
I have a lot... | [FG:InPlacePodVerticalScaling] Add Pod Resize Node E2E test using framework in test/e2e_node | https://api.github.com/repos/kubernetes/kubernetes/issues/111877/comments | 22 | 2022-08-16T23:57:28Z | 2024-07-16T02:27:25Z | https://github.com/kubernetes/kubernetes/issues/111877 | 1,340,994,554 | 111,877 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are failing?
Everything under https://testgrid.k8s.io/sig-node-cos is failing
### Which tests are failing?
All tabs
### Since when has it been failing?
Unknown
### Testgrid link
_No response_
### Reason for failure (if possible)
_No response_
### Anything else we need to know?
_No response_
... | sig-node-cos is all failing | https://api.github.com/repos/kubernetes/kubernetes/issues/111876/comments | 18 | 2022-08-16T21:46:38Z | 2023-05-10T17:21:21Z | https://github.com/kubernetes/kubernetes/issues/111876 | 1,340,915,325 | 111,876 |
[
"kubernetes",
"kubernetes"
] | To support cluster configurations where the control plane and worker nodes are hosted on different networks connected to different network interfaces (multi-NIC) on the apiserver host instance, `EgressSelector` should be able to select a different interface for egress for different network types.
This probably appli... | [FR] Support multi-NIC egress selection | https://api.github.com/repos/kubernetes/kubernetes/issues/111875/comments | 14 | 2022-08-16T17:21:34Z | 2024-11-20T12:10:58Z | https://github.com/kubernetes/kubernetes/issues/111875 | 1,340,659,651 | 111,875 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Now in the > 1.24 kubernetes version the creation of the service account is not creating automatically the secret.
If you want to create new secret yo need to add something like this
```yaml
apiVersion: v1
kind: Secret
metadata:
name: NAMEOFSECRET
annotations:
kubernetes.io/service-... | kubernetes.io/service-account-token doesn't update Service Account Secret | https://api.github.com/repos/kubernetes/kubernetes/issues/111871/comments | 12 | 2022-08-16T15:08:07Z | 2022-08-16T17:56:45Z | https://github.com/kubernetes/kubernetes/issues/111871 | 1,340,501,132 | 111,871 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I am trying to handle a scenario where a kubectl command throws an error then I would handle it in my script, but when running the script the kubectl command is throwing an error and the script is failing to recognize it as a error type.
```
exit_code=$1
kubectl create -f config.yml --insecure-... | kubectl error parsing output not reaching exit code | https://api.github.com/repos/kubernetes/kubernetes/issues/111870/comments | 2 | 2022-08-16T13:16:13Z | 2022-08-16T14:04:19Z | https://github.com/kubernetes/kubernetes/issues/111870 | 1,340,342,346 | 111,870 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
ERROR 2005 (HY000): Unknown server host 'mysql' (-3)
wordpress 11:36:37.26 DEBUG ==> Executing SQL command:
SELECT 1
### What did you expect to happen?
'hostname' resolved
### How can we reproduce it (as minimally and precisely as possible)?
deploy a Wordpress release from `https://m... | Network Policy: "host" could not be resolved when adding network policy? | https://api.github.com/repos/kubernetes/kubernetes/issues/111869/comments | 5 | 2022-08-16T11:47:16Z | 2022-09-29T17:49:34Z | https://github.com/kubernetes/kubernetes/issues/111869 | 1,340,230,683 | 111,869 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
After migration to Ginkgo v2 there is quite a bit of additional unnecessary output at the start and end of a test suite run. This is annoying in particular when running a single failing test with `-ginkgo.v` because the test failure is not visible at the end of the output and a lot... | e2e: too verbose ginkgo output | https://api.github.com/repos/kubernetes/kubernetes/issues/111868/comments | 13 | 2022-08-16T11:16:58Z | 2022-08-31T17:00:58Z | https://github.com/kubernetes/kubernetes/issues/111868 | 1,340,194,469 | 111,868 |
[
"kubernetes",
"kubernetes"
] | Create a single-port Service of type LB. It gets nodeport 31234.
Wait for an LB IP to be assigned.
Access that LB IP on 31234 - it works as long as firewalls don't stop it.
This is because the NodPorts chain doesn't necessarily check IPs (hence why it is the last chain). It finds port 31234 and forwards it t... | Service NodePorts can be accessed via LB IPs (iptables, at least) | https://api.github.com/repos/kubernetes/kubernetes/issues/111863/comments | 17 | 2022-08-15T23:56:59Z | 2024-04-18T15:49:23Z | https://github.com/kubernetes/kubernetes/issues/111863 | 1,339,650,168 | 111,863 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Installed a HA Cluster following this [documentation](https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/high-availability/)
I have 3 etcd nodes running and working. 1 envoy loadbalancer, and are now trying to add a control plane.
When trying to init the control plane I get:... | HA cluster control plane init - Error getting node | https://api.github.com/repos/kubernetes/kubernetes/issues/111858/comments | 9 | 2022-08-15T13:51:14Z | 2022-08-15T21:09:24Z | https://github.com/kubernetes/kubernetes/issues/111858 | 1,339,031,865 | 111,858 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Reading TestRESTClientLimiter in https://github.com/kubernetes/client-go/blob/master/rest/config_test.go I noticed a few things.
1. The test case struct is defined to have a name field, and its value is used in naming the subtests, but the actual test cases leave the name blank.
2. The error state... | Infelicities in TestRESTClientLimiter | https://api.github.com/repos/kubernetes/kubernetes/issues/111854/comments | 3 | 2022-08-15T04:45:41Z | 2022-09-16T00:53:35Z | https://github.com/kubernetes/kubernetes/issues/111854 | 1,338,534,835 | 111,854 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
Consider rewrite sets package [staging/src/k8s.io/apimachinery/pkg/util/sets](https://github.com/kubernetes/kubernetes/tree/master/staging/src/k8s.io/apimachinery/pkg/util/sets) as go generic instead of using code generator.
### Why is this needed?
Different types sets can be per... | Proposal: rewrite sets package as go generic | https://api.github.com/repos/kubernetes/kubernetes/issues/111853/comments | 11 | 2022-08-15T04:28:23Z | 2022-12-15T11:21:07Z | https://github.com/kubernetes/kubernetes/issues/111853 | 1,338,525,177 | 111,853 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
when we use apf in our 5k production environment, apiserver often freezes and cannot process any request because of the timeout, which results in many node being not ready.
we found apf will reset when http write panic, it took 10m(too long) process each pl, many nodes become notready，then apis... | apf will reset when panic happen | https://api.github.com/repos/kubernetes/kubernetes/issues/111852/comments | 9 | 2022-08-15T03:15:21Z | 2022-08-25T02:48:45Z | https://github.com/kubernetes/kubernetes/issues/111852 | 1,338,482,569 | 111,852 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When I resolve FQDN using hostname -f in multi-container of pod, sometimes only the hostname can be resolved, but the FQDN cannot be resolved. Look like this:
[root@hdp-zookeeper-hdp-zookeeper-0 /]# hostname -f
hdp-zookeeper-hdp-zookeeper-0.hdp-zookeeper-hdp-zookeeper.testns.svc.cluster.local
[... | When using hostname -f to resolve FQDN, multiple containers sharing the same /var/lib/kubelet/pods/xxxxx/etc-hosts file may have a certain impact | https://api.github.com/repos/kubernetes/kubernetes/issues/111849/comments | 10 | 2022-08-15T02:33:16Z | 2024-06-17T12:58:52Z | https://github.com/kubernetes/kubernetes/issues/111849 | 1,338,460,579 | 111,849 |
[
"kubernetes",
"kubernetes"
] | # Progress <code>[6/6]</code>
- [X] APISnoop org-flow: [CoreV1NamespaceReplaceTest.org](https://github.com/apisnoop/ticket-writing/blob/master/CoreV1NamespaceReplaceTest.org)
- [X] Test approval issue: #111847
- [X] Test PR: #111848
- [x] Two weeks soak start date: [testgrid-link](https://testgrid.k8s.i... | Write CoreV1NamespaceReplace Test +1 Endpoint | https://api.github.com/repos/kubernetes/kubernetes/issues/111847/comments | 3 | 2022-08-14T23:11:18Z | 2022-09-08T20:11:44Z | https://github.com/kubernetes/kubernetes/issues/111847 | 1,338,373,853 | 111,847 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I create
```yaml
apiVersion: v1
kind: Service
spec:
type: NodePort
selector:
app: karana
ports:
- protocol: TCP
port: 3890
nodePort: 123
```
My node has IP 2.3.4.5. When I run kube-proxy in mode usermode or ipvs, requests for 2.3.4.5:123 are answered, while ... | kube-proxy modes ipvs and userspace do not serve requests to localhost, while mode iptables does | https://api.github.com/repos/kubernetes/kubernetes/issues/111840/comments | 20 | 2022-08-14T13:08:26Z | 2024-09-23T00:02:41Z | https://github.com/kubernetes/kubernetes/issues/111840 | 1,338,241,515 | 111,840 |
[
"kubernetes",
"kubernetes"
] | /kind documentation
Bash Auto Completion has a missing step to enable autocompletion in current shell session
### **As Is:**
If you have an alias for kubectl, you can extend shell completion to work with that alias:
```
echo 'alias k=kubectl' >>~/.bashrc
echo 'complete -o default -F __start_kubectl k' >>~/.... | Docs: missing step "source ~/.bashrc" to enable autocompletion in current session | https://api.github.com/repos/kubernetes/kubernetes/issues/111831/comments | 3 | 2022-08-13T15:22:23Z | 2022-08-14T18:33:03Z | https://github.com/kubernetes/kubernetes/issues/111831 | 1,337,989,094 | 111,831 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When using the command kubectl explain Deployment/DaemonSet/StatefulSet.spec.template.spec.restartPolicy, prompt
````
Restart policy for all containers within the pod. One of Always, OnFailure,Never. Default to Always.
````
But the value is Never, when kubectl applies the template file, it promp... | The value of .spec.template.spec.restartPolicy in kubectl explain Deployment/DaemonSet/StatefulSet template prompts an error | https://api.github.com/repos/kubernetes/kubernetes/issues/111829/comments | 9 | 2022-08-13T13:12:30Z | 2024-09-03T07:31:50Z | https://github.com/kubernetes/kubernetes/issues/111829 | 1,337,962,311 | 111,829 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I've created a postgres cluster by the readme via helm and a simple manifest (see https://github.com/zalando).
I do `port-forward acid-minimal-cluster-0 8098:5432` and then `psql -h localhost -p 8098 -U postgres'. I paste the password from the kubernetes secret created by the operator.
While... | port-forward closed on specific postgres command | https://api.github.com/repos/kubernetes/kubernetes/issues/111825/comments | 32 | 2022-08-12T20:07:25Z | 2023-05-01T00:10:35Z | https://github.com/kubernetes/kubernetes/issues/111825 | 1,337,660,778 | 111,825 |
[
"kubernetes",
"kubernetes"
] | Should nodes that are "being deleted" (have been DELETE'd but have an active finalizer) be IN or OUT of the LB set? I want to say they should be removed as soon as we see the deletion timestamp, but I can also see an argument for this being another part of "draining". Either way, we should document this in the code... | ServiceController should clarify behavior of "being deleted" nodes | https://api.github.com/repos/kubernetes/kubernetes/issues/111824/comments | 17 | 2022-08-12T19:59:50Z | 2023-03-16T00:58:26Z | https://github.com/kubernetes/kubernetes/issues/111824 | 1,337,654,981 | 111,824 |
[
"kubernetes",
"kubernetes"
] | https://github.com/kubernetes/kubernetes/pull/111697 documents not to do this. Would be good to make it visible when/if it does happen.
Something like this on each sync:
* open and parse /proc/sys/net/ipv4/ip_local_port_range
* compare all NodePorts and HCNP against this
* if overlap, log and Event
@danwinshi... | kube-proxy: log warning and/or Event if a NodePort overlaps with on-node ephemeral range | https://api.github.com/repos/kubernetes/kubernetes/issues/111823/comments | 19 | 2022-08-12T19:40:51Z | 2024-08-05T12:19:20Z | https://github.com/kubernetes/kubernetes/issues/111823 | 1,337,641,037 | 111,823 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
Add another option for a container's `imagePullPolicy`, which attempts to pull the image, and falls back to using a local cached copy if the image could not be pulled.
### Why is this needed?
In development, images are frequently updated, so it's essential to grab the latest vers... | imagePullPolicy to pull latest image OR use existing image if repository unavailable | https://api.github.com/repos/kubernetes/kubernetes/issues/111822/comments | 32 | 2022-08-12T16:33:50Z | 2025-01-10T18:00:39Z | https://github.com/kubernetes/kubernetes/issues/111822 | 1,337,423,459 | 111,822 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
First of all, sorry if this is not the correct place for such an issue, but I am not sure where to look for help anymore.
It all started with Connection reset error on our Java app running on Kubernetes connected to Oracle DB, the original issue described at [stackoveflow](https://stackoverflow.c... | Long held TCP connection gets destroyed randomly from conntrack | https://api.github.com/repos/kubernetes/kubernetes/issues/111820/comments | 9 | 2022-08-12T13:06:36Z | 2022-11-21T17:12:39Z | https://github.com/kubernetes/kubernetes/issues/111820 | 1,337,185,386 | 111,820 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
A timeout occurred when writing a large object
schema.yaml content size 180k
```
✦ ➜ kubectl apply -f schema.yaml
Error from server (Timeout): error when creating "schema.yaml": Timeout: request did not complete within requested timeout - context deadline exceeded
```
k8s apiserver log:
`... | k8s apiserver write big custom object timeout, apiserver high cpu | https://api.github.com/repos/kubernetes/kubernetes/issues/111819/comments | 17 | 2022-08-12T12:59:05Z | 2022-11-16T17:38:09Z | https://github.com/kubernetes/kubernetes/issues/111819 | 1,337,177,650 | 111,819 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
For kubelet I set `--logging-format=json` and send json logs to ElasticSearch.
For field `status` in ElasticSearch index mapping set type object, bc status_manager.go send many logs, where status is object. For example, you can see it [here](https://github.com/kubernetes/kubernetes/blob/master/pk... | Field status in kubelet logs has a different type | https://api.github.com/repos/kubernetes/kubernetes/issues/111815/comments | 19 | 2022-08-12T08:53:54Z | 2024-02-08T17:41:42Z | https://github.com/kubernetes/kubernetes/issues/111815 | 1,336,934,640 | 111,815 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I tried to create a pod with only requests specified.
spec.containers[0].resources.limits.cpu = 0
spec.containers[0].resources.limits.memory = 0
spec.containers[0].resources.requests.cpu = 1
spec.containers[0].resources.requests.memory = 100Mi
This fails to deploy with the error "Error "... | spec.containers[0].resources.limits.cpu = 0 is not unlimited | https://api.github.com/repos/kubernetes/kubernetes/issues/111814/comments | 7 | 2022-08-12T07:33:29Z | 2022-08-12T10:10:21Z | https://github.com/kubernetes/kubernetes/issues/111814 | 1,336,859,248 | 111,814 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
We're in the process of upgrading from Kubernetes 1.21 to 1.22 on a GKE standard cluster. We're on standard release channel, so normally these upgrades should go automatically. However, GKE was warning us we were still using deprecated api's, which are about to be removed. So what we did was upgrade... | Removed resource is listed as a supported resource | https://api.github.com/repos/kubernetes/kubernetes/issues/111813/comments | 6 | 2022-08-12T07:18:30Z | 2022-08-18T16:46:04Z | https://github.com/kubernetes/kubernetes/issues/111813 | 1,336,844,944 | 111,813 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Create a pod with a job. When the job is completed, some pods can view the log, but some cannot
info:
```
$ kubectl get pods -n 7a5f7bcb-6e77-4573-a863-890856aa315e
NAME READY STATUS RESTARTS AGE
7ae8fd58-e577-48a0-b12a-614... | Unable to view the pod log with status completed | https://api.github.com/repos/kubernetes/kubernetes/issues/111812/comments | 9 | 2022-08-12T06:35:47Z | 2023-08-30T15:31:22Z | https://github.com/kubernetes/kubernetes/issues/111812 | 1,336,812,339 | 111,812 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Since start , RWO volumes are treated as Single NODE attachment which is documented here :
https://kubernetes.io/docs/concepts/storage/persistent-volumes/#access-modes. The a/d controller in k-c-m prevent the attachment of RWO volumes to multiple nodes. however considering its not really enforc... | RWO access mode should be enforced for non-attachable volumes | https://api.github.com/repos/kubernetes/kubernetes/issues/111799/comments | 11 | 2022-08-11T10:22:13Z | 2022-08-19T13:53:24Z | https://github.com/kubernetes/kubernetes/issues/111799 | 1,335,759,791 | 111,799 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
The Kubelet garbage collector mechanism started on one of our nodes and it choose to remove the `pause` container even if it was in use by pods already running on the node.
```
Aug 11 04:29:45 ip-x-x-x-x.ec2.internal kubelet[2188]: I0811 04:29:45.635975 10660 image_gc_manager.go:310] "Disk usa... | Kubelet removes pause container to free up disk space | https://api.github.com/repos/kubernetes/kubernetes/issues/111796/comments | 7 | 2022-08-11T08:09:52Z | 2022-08-18T15:39:43Z | https://github.com/kubernetes/kubernetes/issues/111796 | 1,335,615,169 | 111,796 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
when i rollout undo a pause deployment, it prints a command without namespace. Then i copy and run, it failed with a not found error.
```shell
[root@lzx-22:~]$ kubectl rollout undo deployment calico-kube-controllers -n kube-system
error: you cannot rollback a paused deployment; resume it first w... | kubectl rollout undo print a resume command without a namespace | https://api.github.com/repos/kubernetes/kubernetes/issues/111794/comments | 2 | 2022-08-11T03:02:47Z | 2022-11-09T00:16:15Z | https://github.com/kubernetes/kubernetes/issues/111794 | 1,335,412,036 | 111,794 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
My kubernetes cluster has three nodes, I normally start a deployment, it has three replicas, I set podAntiAffinity, so that the three pods will be evenly distributed on different nodes when the conditions are met.
The current problem is that when an internal exception occurs in a pod (or kubectl ... | The non-affinity setting of deploying multiple replicas pods does not work, when a pod restarts abnormally | https://api.github.com/repos/kubernetes/kubernetes/issues/111793/comments | 15 | 2022-08-11T02:05:15Z | 2022-09-13T13:43:53Z | https://github.com/kubernetes/kubernetes/issues/111793 | 1,335,384,718 | 111,793 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When a pod is created with invalid topologySpreadConstraints, it is not rejected by the validating webhook, but the same label selector is rejected during deployment creation
```
$ cat busy-box-invalid-topology-spread.yaml
apiVersion: v1
kind: Pod
metadata:
name: busybox1
labels:
a... | pod creations are missing validation on spec.topologySpreadConstraints[*].labelSelector | https://api.github.com/repos/kubernetes/kubernetes/issues/111791/comments | 5 | 2022-08-10T19:39:36Z | 2022-12-13T02:47:45Z | https://github.com/kubernetes/kubernetes/issues/111791 | 1,335,113,463 | 111,791 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Sometimes I make a process with multiple informers working on the same object type. Sometimes with different content filters, sometimes working against different apiservers. But an informer uses a reflector internally, and it has debug log messages that are sometimes critical to debugging, but the... | Informer log messages only identify by object type | https://api.github.com/repos/kubernetes/kubernetes/issues/111790/comments | 9 | 2022-08-10T19:02:51Z | 2024-09-10T22:33:31Z | https://github.com/kubernetes/kubernetes/issues/111790 | 1,335,059,925 | 111,790 |
[
"kubernetes",
"kubernetes"
] | When you specify an invalid image like `dummy`, Kubernetes keeps trying to start the pod forever. We should fail immediately and have the Job or Deployment retry policy handle retries. | Fail pod with invalid image | https://api.github.com/repos/kubernetes/kubernetes/issues/111788/comments | 6 | 2022-08-10T17:29:30Z | 2023-01-08T19:47:25Z | https://github.com/kubernetes/kubernetes/issues/111788 | 1,334,952,301 | 111,788 |
[
"kubernetes",
"kubernetes"
] | When applying a HorizontalPodAutoscaler on a resource which has a missing `.spec.replicas` value (which may be the default state for any given custom resource), it fails with something like:
```
Internal error occurred: the spec replicas field ".spec.replicas" does not exist
```
The immediate workaround is to set `... | Default `.spec.replicas` value for HorizontalPodAutoscaler | https://api.github.com/repos/kubernetes/kubernetes/issues/111781/comments | 8 | 2022-08-10T10:36:24Z | 2023-01-30T10:45:32Z | https://github.com/kubernetes/kubernetes/issues/111781 | 1,334,421,937 | 111,781 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Enabled `GracefulNodeShutdown` on a K8s v1.20 cluster through the feature gate and added the parameters in the kubelet configuration.
```
GracefulNodeShutdown: true
shutdownGracePeriod: 30s
shutdownGracePeriodCriticalPods: 10s
```
The `systemd-inhibitor` was enabled on the node.
```
# syste... | GracefulNodeShutdown Not Working as expected. | https://api.github.com/repos/kubernetes/kubernetes/issues/111779/comments | 8 | 2022-08-10T09:03:44Z | 2022-09-14T17:43:04Z | https://github.com/kubernetes/kubernetes/issues/111779 | 1,334,308,641 | 111,779 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
In our k8s cluster，I create a statefulset named test-sts with replicas=3 and podManagementPolicy=Parallel. The statefulset create replica test-sts-1 failed if the pod test-sts-1 has already exists，then the statefulset never create replica test-sts-2, and never update statefulset status。
In the is... | Statefulset never create pod when one of replica pod create failed | https://api.github.com/repos/kubernetes/kubernetes/issues/111778/comments | 7 | 2022-08-10T08:16:03Z | 2023-01-22T14:29:51Z | https://github.com/kubernetes/kubernetes/issues/111778 | 1,334,251,405 | 111,778 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I try to obtain the metrics from kubectl get --raw "/api/v1/nodes/node_name/proxy/metrics/cadvisor" in k8s 1.24.1 env +containerd
and found some of the container fs related metrics are missing, take container_fs_io_time_seconds_total for eg, in docker env, I could get below result
```
container... | kubelet returns diffirent fs metrics for docker and containerd | https://api.github.com/repos/kubernetes/kubernetes/issues/111777/comments | 7 | 2022-08-10T07:37:32Z | 2022-09-14T22:54:09Z | https://github.com/kubernetes/kubernetes/issues/111777 | 1,334,208,555 | 111,777 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
First of all, this problem has been going on for a long time. I have analyzed some conclusions, but still can't find the root cause.
For a while, we had a collective restart of pods on many kubernetes nodes that powered by containerd as the runtime.
We didn't know why, so we took the nodes offli... | Why are all pods on this node restarted? | https://api.github.com/repos/kubernetes/kubernetes/issues/111776/comments | 7 | 2022-08-10T06:14:23Z | 2023-02-02T09:19:01Z | https://github.com/kubernetes/kubernetes/issues/111776 | 1,334,129,137 | 111,776 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I want to add an extra CA to APIserver for authentication. So, I copy /etc/kubernetes/pki/ca.crt to /etc/kubernetes/pki/mul_ca.crt and add an extra CA to the mul_ca.crt file and change apiserver yaml file to specify --client-ca-file to /etc/kubernetes/pki/mul_ca.crt and use the extra CA and its ke... | Specifing --client-ca-file for apiserver does't work | https://api.github.com/repos/kubernetes/kubernetes/issues/111774/comments | 6 | 2022-08-10T04:32:46Z | 2023-01-30T17:21:36Z | https://github.com/kubernetes/kubernetes/issues/111774 | 1,334,054,581 | 111,774 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I attempted to apply the following CRDs to kubernetes local cluster running from rev 759785ea147bc13945d521eaba4a6592cbc0675f
<details>
<summary>stable.example.com_mapimmutablekeys.yaml</summary>
```yaml
---
apiVersion: apiextensions.k8s.io/v1
kind: CustomResourceDefinition
metadata:
... | CEL cost budgeting inconsistent rejections | https://api.github.com/repos/kubernetes/kubernetes/issues/111769/comments | 5 | 2022-08-09T17:34:11Z | 2022-08-29T15:00:39Z | https://github.com/kubernetes/kubernetes/issues/111769 | 1,333,571,301 | 111,769 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
Extend the event message with the concrete image digest in a kubelet's successful pull event: `Successfully pulled image "nginx@sha256:df13abe416e37eb3db4722840dd479b00ba193ac6606e7902331dcea50f4f1f2" as "nginx:1.19" in 2.5610178s` if a container's image was not specified using a d... | Expose image digest in pull image event | https://api.github.com/repos/kubernetes/kubernetes/issues/111767/comments | 8 | 2022-08-09T15:44:14Z | 2023-04-06T17:01:50Z | https://github.com/kubernetes/kubernetes/issues/111767 | 1,333,449,022 | 111,767 |
[
"kubernetes",
"kubernetes"
] | ```
apiVersion: v1
data:
ClusterConfiguration: |
apiServer:
extraArgs:
authorization-mode: Node,RBAC
timeoutForControlPlane: 4m0s
apiVersion: kubeadm.k8s.io/v1beta3
certificatesDir: /etc/kubernetes/pki
clusterName: kubernetes
controlPlaneEndpoint: 192.168.41.100:6443... | kueadm upgrad kubernets is no kubeadm configmap? | https://api.github.com/repos/kubernetes/kubernetes/issues/111766/comments | 2 | 2022-08-09T14:14:01Z | 2022-08-09T14:23:44Z | https://github.com/kubernetes/kubernetes/issues/111766 | 1,333,324,284 | 111,766 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I boot my computer, which is a single node Kubernetes cluster. cri-o and kubelet have not been started yet. There are 27 mounts (the output of `mount` is 27 lines). I start crio, it adds one more mount. I stop crio, that mount is removed. I start crio again, the mount re-appears.
I start kub... | kubelet does not unmount on shutdown the directories it has mounted. | https://api.github.com/repos/kubernetes/kubernetes/issues/111763/comments | 13 | 2022-08-09T09:23:00Z | 2022-08-10T18:04:56Z | https://github.com/kubernetes/kubernetes/issues/111763 | 1,332,968,475 | 111,763 |
[
"kubernetes",
"kubernetes"
] | ### Failure cluster [d755e6a5539654895db7](https://go.k8s.io/triage#d755e6a5539654895db7)
##### Error text:
```
[FAILED] failed to get pod test-container-pod: Get "https://35.199.166.44/api/v1/namespaces/pod-network-test-9303/pods/test-container-pod": dial tcp 35.199.166.44:443: connect: connection refused
In [It... | [Failing Test] [sig-node] Pods should cap back-off at MaxContainerBackOff [Slow][NodeConformance] | https://api.github.com/repos/kubernetes/kubernetes/issues/111762/comments | 15 | 2022-08-09T08:24:00Z | 2023-04-16T15:08:57Z | https://github.com/kubernetes/kubernetes/issues/111762 | 1,332,897,675 | 111,762 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Our resource management component fails, causing hugepage information on OS taking effect after kubelet starts. When hugepage information is updated on OS, k8s node status still has "0" about hugepage resource.
### What did you expect to happen?
Hugepage information in node status can be update dy... | Cadvisor manager update machine info periodically, but hugepage info in node status is only updated when kubelet starts | https://api.github.com/repos/kubernetes/kubernetes/issues/111757/comments | 13 | 2022-08-09T02:59:59Z | 2025-02-20T17:42:55Z | https://github.com/kubernetes/kubernetes/issues/111757 | 1,332,640,913 | 111,757 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
pod with multiple pvc , only some pvc bound, but other pvc not bound because the storage capacity is not enough.
pod and pvc use storage tracking feature to schedule.
pod example:
```yaml
kind: Pod
metadata:
name: test
spec:
containers:
- name: ubuntu
image: ubuntu:20.04
... | pod with multiple PVC that use storage capacity tracking schedule did not get correct available capacity | https://api.github.com/repos/kubernetes/kubernetes/issues/111755/comments | 11 | 2022-08-09T02:11:45Z | 2023-02-17T09:35:49Z | https://github.com/kubernetes/kubernetes/issues/111755 | 1,332,611,425 | 111,755 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
i hope clean taint quickly.
example , there have two taints in node01 which is a master nodes:
```
root@node01:~# kubectl describe nodes node01 | grep Taint -A1
Taints: node-role.kubernetes.io/control-plane:NoSchedule
node-role.kubernetes.... | clean taint quickly | https://api.github.com/repos/kubernetes/kubernetes/issues/111754/comments | 9 | 2022-08-09T01:52:10Z | 2023-04-15T12:47:32Z | https://github.com/kubernetes/kubernetes/issues/111754 | 1,332,600,321 | 111,754 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
log in pkg/kubelet/pluginmanager/cache/desired_state_of_world.go seem to be wrong
[`klog.V(2).InfoS("Plugin exists in actual state cache, timestamp will be updated", "path", socketPath)`](https://github.com/kubernetes/kubernetes/blob/aea9f9887d08922378b9e7da0e81a46e733f2995/pkg/kubelet/pluginmanag... | log in desired_state_of_world.go seems to be wrong | https://api.github.com/repos/kubernetes/kubernetes/issues/111753/comments | 13 | 2022-08-09T01:40:58Z | 2024-06-17T21:01:53Z | https://github.com/kubernetes/kubernetes/issues/111753 | 1,332,594,036 | 111,753 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Hello,
we have been using client-go [`LatencyMetric` interface](https://github.com/cilium/cilium/blob/v1.12.0/vendor/k8s.io/client-go/tools/metrics/metrics.go#L40-L43) to measure the latency for all client-go traffic from Cilium to kube-apiserver. We have [recently found out](https://github.com... | Regression in client-go >= v1.24.0 metrics lead to explosion in label cardinality | https://api.github.com/repos/kubernetes/kubernetes/issues/111750/comments | 14 | 2022-08-08T17:29:59Z | 2022-08-24T02:00:08Z | https://github.com/kubernetes/kubernetes/issues/111750 | 1,332,175,731 | 111,750 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/#taints-and-tolerations
Although Daemon Pods respect [taints and tolerations](https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/), the following tolerations are added to DaemonSet Pods automatically ac... | existing toleration can not be modified when add annotation for daemonsetPod after enabling podtolerationrestriction | https://api.github.com/repos/kubernetes/kubernetes/issues/111745/comments | 9 | 2022-08-08T06:15:28Z | 2025-03-11T20:31:41Z | https://github.com/kubernetes/kubernetes/issues/111745 | 1,331,383,089 | 111,745 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
**First，create a job，just as below：**
```
apiVersion: batch/v1
kind: Job
metadata:
creationTimestamp: "2022-08-01T11:35:51Z"
labels:
app: xxxx-job-cqog
name: xxxx-job-cqog
spec:
backoffLimit: 6
completions: 1
parallelism: 1
selector:
matchLabels:
contro... | Stop the runtime service, unfinished jobs become succeed | https://api.github.com/repos/kubernetes/kubernetes/issues/111744/comments | 3 | 2022-08-08T06:02:51Z | 2022-09-08T03:04:49Z | https://github.com/kubernetes/kubernetes/issues/111744 | 1,331,372,689 | 111,744 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When we use port-forward to forward traffic, there is a situation where the connection cannot be processed.
> kubectl port-forward output
```
[root@VM-247-91-centos /tmp]# ./kubectl port-forward deployment/xxxx 18889:8888 --address 0.0.0.0 --kubeconfig /root/.kube/integration
Forwarding f... | port-forward cannot handle the connection | https://api.github.com/repos/kubernetes/kubernetes/issues/111742/comments | 11 | 2022-08-08T02:56:33Z | 2023-05-02T22:59:58Z | https://github.com/kubernetes/kubernetes/issues/111742 | 1,331,251,157 | 111,742 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are flaking?
https://k8s-testgrid.appspot.com/sig-release-master-blocking#gce-cos-master-default
### Which tests are flaking?
CSIInlineVolumes should support ephemeral VolumeLifecycleMode in CSIDriver API
### Since when has it been flaking?
8/5
### Testgrid link
https://k8s-testgrid.appspot.com/si... | [Flaky] gce-cos-master-default CSIInlineVolumes should support ephemeral VolumeLifecycleMode in CSIDriver API | https://api.github.com/repos/kubernetes/kubernetes/issues/111740/comments | 2 | 2022-08-08T00:28:39Z | 2022-08-09T02:54:51Z | https://github.com/kubernetes/kubernetes/issues/111740 | 1,331,168,425 | 111,740 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When the number of replicas of the deployment decreases, execute `kubectl get --raw /api/v1/nodes/$NODE_NAME/proxy/metrics/resource` or `kubectl get --raw /api/v1/nodes/$NODE_NAME/proxy/stats/summary`, it gets stuck
### What did you expect to happen?
get data in time when execute `kubectl get --ra... | When the number of replicas of the deployment decreases, execute kubectl get --raw /api/v1/nodes/$NODE_NAME/proxy/metrics/resource or kubectl get --raw /api/v1/nodes/$NODE_NAME/proxy/stats/summary, it gets stuck | https://api.github.com/repos/kubernetes/kubernetes/issues/111738/comments | 11 | 2022-08-07T07:36:55Z | 2022-12-07T00:26:37Z | https://github.com/kubernetes/kubernetes/issues/111738 | 1,330,939,317 | 111,738 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
A combination of admission control and pod definitions have created overlapping mount instruction (i.e. mounting the same directory twice).
This is a configuration that kubernetes can service by ignoring the duplication, but it opts for overzealousness and refuses to schedule the pods instead.
###... | Kubernetes rejects overlapping mounts | https://api.github.com/repos/kubernetes/kubernetes/issues/111737/comments | 8 | 2022-08-07T05:39:07Z | 2022-09-15T23:49:59Z | https://github.com/kubernetes/kubernetes/issues/111737 | 1,330,919,926 | 111,737 |
[
"kubernetes",
"kubernetes"
] | Here's the update to .golangci.yaml to clean up unused code that shows up when we specify `go` version to `1.19`
```
[dims@dims-m1-7728 17:05] ~/go/src/k8s.io/kubernetes ⟩ git diff
diff --git .golangci.yaml .golangci.yaml
index e6a6ff9e17b9..c1cd7399f837 100644
--- .golangci.yaml
+++ .golangci.yaml
@@ -45,4 +4... | Update config for `unused` plugin in .golangci.yaml to golang 1.19 | https://api.github.com/repos/kubernetes/kubernetes/issues/111734/comments | 5 | 2022-08-06T21:25:39Z | 2022-08-24T02:00:01Z | https://github.com/kubernetes/kubernetes/issues/111734 | 1,330,851,803 | 111,734 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
I recently setup a kubernetes cluster on hetzner cloud with help of k0s but when I create a pod for example nginx then create a service for that to access through Nordport
Now i successfully curl the web server but when I hit again and again like 3 4 time it's giving very late response and somet... | Slow response of nginx container | https://api.github.com/repos/kubernetes/kubernetes/issues/111733/comments | 4 | 2022-08-06T16:26:20Z | 2022-08-08T07:28:31Z | https://github.com/kubernetes/kubernetes/issues/111733 | 1,330,792,451 | 111,733 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Following [this](https://github.com/karthequian/Kubernetes/tree/master/04_04_Rolling_updates) tutorial and did:
```
$ kubectl create -f helloworld-black.yaml --record
Flag --record has been deprecated, --record will be removed in the future
deployment.apps/navbar-deployment created
service/... | "kubectl rollout history" produces wrong entry when --record not explictly used in "set image" | https://api.github.com/repos/kubernetes/kubernetes/issues/111732/comments | 8 | 2022-08-06T15:31:43Z | 2023-01-09T17:53:27Z | https://github.com/kubernetes/kubernetes/issues/111732 | 1,330,781,001 | 111,732 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
When I write the policy for my K8s cluster, I saw the webhook mode in Authorization. Can I only use this webhook mode for all policies in my cluster?
### Why is this needed?
Admission controllers cannot enforce policies on read requests. So that, we can use only one webhook in au... | Webhook mode in authorization | https://api.github.com/repos/kubernetes/kubernetes/issues/111728/comments | 3 | 2022-08-06T09:45:11Z | 2022-10-18T15:44:02Z | https://github.com/kubernetes/kubernetes/issues/111728 | 1,330,706,432 | 111,728 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
My deployment `foobar` has a finalizer `foo.example.com/bar`.
When you execute `kubectl delete deploy foobar --cascade='foreground'`, it will delete the replicasets and the pods of the deployment.
### What did you expect to happen?
When a object referred by an ownerReference and having finalize... | `kubectl delete deploy xxx --cascade='foreground'` delete pods immediately even though deployment has finalizers | https://api.github.com/repos/kubernetes/kubernetes/issues/111725/comments | 13 | 2022-08-06T01:36:31Z | 2024-09-14T03:19:48Z | https://github.com/kubernetes/kubernetes/issues/111725 | 1,330,604,719 | 111,725 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
> This hook is called immediately before a container is terminated due to an API request or management event such as a liveness/startup probe failure, preemption, resource contention and others.
I'd like for the event to be passed to the `preStop` hook.
I'm not proposing an a... | Pass event of pod termination to `preStop` hook | https://api.github.com/repos/kubernetes/kubernetes/issues/111719/comments | 8 | 2022-08-05T13:16:29Z | 2023-01-08T19:47:26Z | https://github.com/kubernetes/kubernetes/issues/111719 | 1,329,928,737 | 111,719 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
https://github.com/kedacore/keda/issues/3506
### What did you expect to happen?
https://github.com/kedacore/keda/issues/3506
### How can we reproduce it (as minimally and precisely as possible)?
https://github.com/kedacore/keda/issues/3506
### Anything else we need to know?
https://github.com/... | CPU/MEM percentage in HPA should be based on limits! kedacore/keda#3506 | https://api.github.com/repos/kubernetes/kubernetes/issues/111717/comments | 6 | 2022-08-05T09:12:49Z | 2022-08-08T22:48:02Z | https://github.com/kubernetes/kubernetes/issues/111717 | 1,329,670,389 | 111,717 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
**precondition:**
**kubeadm config images list**
k8s.gcr.io/kube-apiserver:v1.24.3
k8s.gcr.io/kube-controller-manager:v1.24.3
k8s.gcr.io/kube-scheduler:v1.24.3
k8s.gcr.io/kube-proxy:v1.24.3
k8s.gcr.io/pause:3.7
k8s.gcr.io/etcd:3.5.3-0
k8s.gcr.io/coredns/coredns:v1.8.6
pull the images listed... | kubeadm init: failed to pull image even though the images had been pulled with docker | https://api.github.com/repos/kubernetes/kubernetes/issues/111715/comments | 5 | 2022-08-05T08:39:49Z | 2022-09-10T13:39:27Z | https://github.com/kubernetes/kubernetes/issues/111715 | 1,329,633,715 | 111,715 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
[NewBuilder](https://github.com/kubernetes/kubernetes/blob/bd9444c1cfd438690dc21c31404dd79ab60dc6cb/staging/src/k8s.io/cli-runtime/pkg/resource/builder.go#L207) takes a [RESTClientGetter](https://github.com/kubernetes/kubernetes/blob/bd9444c1cfd438690dc21c31404dd79ab60dc6cb/staging/src/k8s.io/cli-ru... | Unclear concurrency safety requirements of `k8s.io/cli-runtime/pkg/resource.NewBuilder` argument | https://api.github.com/repos/kubernetes/kubernetes/issues/111714/comments | 23 | 2022-08-05T07:50:56Z | 2025-02-24T07:45:43Z | https://github.com/kubernetes/kubernetes/issues/111714 | 1,329,582,810 | 111,714 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
After i install k8s version 1.24.2 with docker-desktop both on my mac and my windows10 computer, and i install metrics-server version 0.4.1, and i find i can get node metrics but not pod metrics.
I have tried to figure out whether the metrics-server went wrong, and i found kubelet cannot get a... | After install kubernetes 1.24.2 with docker-desktop, kubelet cannot get pod metrics | https://api.github.com/repos/kubernetes/kubernetes/issues/111713/comments | 5 | 2022-08-05T07:50:48Z | 2024-01-19T06:10:07Z | https://github.com/kubernetes/kubernetes/issues/111713 | 1,329,582,708 | 111,713 |
[
"kubernetes",
"kubernetes"
] | Opening issue for tracking purpose based on feedback from sig instrumentation
> It might be clearer for admins to expose one metric containing the CIDRs limit and one containing the current number of allocated CIDRs. Otherwise, they will only know that the percentage is high but they won't really know how many alloc... | Improve ClusterCIDR metrics | https://api.github.com/repos/kubernetes/kubernetes/issues/111711/comments | 6 | 2022-08-05T06:13:49Z | 2022-12-09T23:43:01Z | https://github.com/kubernetes/kubernetes/issues/111711 | 1,329,496,247 | 111,711 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
/wg api-expression
when I use a API request to get a non-existent component "fuzzing"status,I got 500 response code.
The request content as follows:
```
"request": {
"RequestData": {
"method": "GET",
"path": "/api/v1/componentstatuses/fuzzstring",
... | API resonse error | https://api.github.com/repos/kubernetes/kubernetes/issues/111710/comments | 10 | 2022-08-05T03:34:52Z | 2022-09-25T19:42:41Z | https://github.com/kubernetes/kubernetes/issues/111710 | 1,329,402,013 | 111,710 |
[
"kubernetes",
"kubernetes"
] | ### What would you like to be added?
kube-proxy should report k8s events of critical cases instead of just logging, e.g., kube-proxy failovers to iptables proxier when it should be running ipvs proxier, see https://github.com/kubernetes/kubernetes/blob/v1.24.3/cmd/kube-proxy/app/server_others.go#L588
There might be... | kube-proxy should report events when the proxier failovers | https://api.github.com/repos/kubernetes/kubernetes/issues/111709/comments | 7 | 2022-08-05T02:07:06Z | 2022-08-24T12:52:04Z | https://github.com/kubernetes/kubernetes/issues/111709 | 1,329,353,708 | 111,709 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
When a Pod with integer cpuset (dedicated CPU cores) is deleted, the cpusets of the cgroups for the rest Pods are not updated.
For example, we have Pod A is assigned 1 CPU (core 4) and Pod B which requesting 200m CPU. The cgroup files for these two Pods would look like:
```
➜ kubepods.slic... | cgroup cpuset is not updated for the running Pods when a Pod is deleted | https://api.github.com/repos/kubernetes/kubernetes/issues/111705/comments | 8 | 2022-08-04T21:46:35Z | 2022-09-08T02:00:24Z | https://github.com/kubernetes/kubernetes/issues/111705 | 1,329,206,237 | 111,705 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
While going over Kubernetes events I noticed that image pulls for some small images were taking several minutes according to the "Successfully pulled image" event. From investigating this is misleading as the actual pull time is much smaller but due to --serialize-image-pulls=true being the defaul... | When using --serialize-image-pulls=true "Successfully pulled image" Event outputs misleading time | https://api.github.com/repos/kubernetes/kubernetes/issues/111704/comments | 4 | 2022-08-04T21:22:12Z | 2022-11-07T22:52:17Z | https://github.com/kubernetes/kubernetes/issues/111704 | 1,329,188,148 | 111,704 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Patching and/or updating a custom resource at schema version `N-1` can erase the values of fields defined at version `N` (or subsequent versions) of the API depending on the client used and/or the presence of `x-kubernetes-preserve-unknown-fields: true` in the schema. In fact, this issue goes on t... | Patching and/or updating custom resources at older schema versions may result in data loss | https://api.github.com/repos/kubernetes/kubernetes/issues/111703/comments | 13 | 2022-08-04T21:06:54Z | 2022-08-22T14:37:28Z | https://github.com/kubernetes/kubernetes/issues/111703 | 1,329,175,725 | 111,703 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Reference Comment: https://github.com/kubernetes/kubernetes/pull/111254#issuecomment-1195794968
Based on the diff: https://github.com/kubernetes/kubernetes/pull/111254/files, there are a couple areas where indentations are turned into paragraphs, indentations are turning regular comments into cod... | Fix godocs autoformatting from upgrading to go 1.19 | https://api.github.com/repos/kubernetes/kubernetes/issues/111701/comments | 8 | 2022-08-04T20:48:31Z | 2022-12-18T21:47:46Z | https://github.com/kubernetes/kubernetes/issues/111701 | 1,329,160,327 | 111,701 |
[
"kubernetes",
"kubernetes"
] | ### Which jobs are flaking?
We've seen this line of [test/e2e/network/dns_configmap.go:301](https://github.com/kubernetes/kubernetes/blob/master/test/e2e/network/dns_configmap.go#L301) panic from time to time. It is caused by an index out of bounds. The array length check on that line seems to be incorrect.
We see ... | DNS Configmap tests sometimes panics in ipv6 envs | https://api.github.com/repos/kubernetes/kubernetes/issues/111700/comments | 9 | 2022-08-04T20:39:43Z | 2022-08-05T00:25:48Z | https://github.com/kubernetes/kubernetes/issues/111700 | 1,329,152,706 | 111,700 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
After upgrading k8s cluster from 1.20.15 to 1.21.14, we noticed significantly higher memory usage from kube-apiserver pods.
Below are the graphs that show clearly the difference in memory consumption before and after. The spike in the middle is when the control-plane nodes were being rolled to ... | Higher kube-apiserver memory usage k8s 1.20.15 vs 1.21.14 | https://api.github.com/repos/kubernetes/kubernetes/issues/111699/comments | 12 | 2022-08-04T19:37:00Z | 2023-01-24T18:45:08Z | https://github.com/kubernetes/kubernetes/issues/111699 | 1,329,097,619 | 111,699 |
[
"kubernetes",
"kubernetes"
] | Looking at validation code, I see places that are using the last argument to `field.Required` that do not need to be. It's extra detail that is almost never needed. For example:
```
field.Required(fldPath.Child("type"), "must specify a metric source type"))
```
This seems totally redundant - the error already... | Validation cleanups needed: proper use of "Required" and "Invalid" | https://api.github.com/repos/kubernetes/kubernetes/issues/111698/comments | 9 | 2022-08-04T18:38:53Z | 2025-02-21T00:09:57Z | https://github.com/kubernetes/kubernetes/issues/111698 | 1,329,039,983 | 111,698 |
[
"kubernetes",
"kubernetes"
] | ### What happened?
Case1:
With k8s 1.23.x and cloud-provider-openstack 1.23.x if we pass "--cloud-provider=external" along with "--node-ip=10.0.16.2" as KUBELET_EXTRA_ARGS to the kubelet.service file we observe that the Node.status.addresses was as follows
status
addresses:
address: 10.0.16.2
type: Inte... | For dual stack deployments, node addresses show only one IP if node-ip parameter is passed | https://api.github.com/repos/kubernetes/kubernetes/issues/111695/comments | 46 | 2022-08-04T12:58:59Z | 2025-01-30T13:29:00Z | https://github.com/kubernetes/kubernetes/issues/111695 | 1,328,583,061 | 111,695 |
Subsets and Splits
Unique Owner-Repo Count
Counts the number of unique owner-repos in the dataset, providing a basic understanding of diverse repositories.