Cluster information:
Kubernetes version: 1.25
Cloud being used: (put bare-metal if not on a public cloud) EKS
We are preparing upgrade EKS from 1.25 to 1.26.
In the release note 1.26 https://docs.aws.amazon.com/eks/latest/userguide/kubernetes-versions-standard.html#kubernetes-1.26
There is note:
The goaway-chance option in the Kubernetes API server helps prevent HTTP/2 client connections from being stuck on a single API server instance, by randomly closing a connection. When the connection is closed, the client will try to reconnect, and will likely land on a different API server as a result of load balancing. Amazon EKS version 1.26 has enabled goaway-chance flag. If your workload running on Amazon EKS cluster uses a client that is not compatible with HTTP GOAWAY, we recommend that you update your client to handle GOAWAY by reconnecting on connection termination.
Question: As in the release note, it requires to ask update client. Could you please explain which client and how to check all in the cluster to detect clients?
Thanks,
Uyen Vu