[GitHub] [apisix] walkerZsh commented on issue #8845: After kubernetes is upgraded to 1.21, apisix cannot automatically obtain the token, resulting in access failure

["walkerZsh (via GitHub)" <gi...@apache.org>]

walkerZsh commented on issue #8845:
URL: https://github.com/apache/apisix/issues/8845#issuecomment-1578023278

   Is there any plan to support this? Our production environment is deployed on AWS EKS,apisix pod will not be able to get new upstream nodes through kubernetes service discovery after 90 days of startup.
   https://docs.aws.amazon.com/zh_cn/eks/latest/userguide/kubernetes-versions.html
   > If your workload is using an older client version, then you must update it. To enable a smooth migration of clients to the newer time-bound service account tokens, Kubernetes version 1.22 adds an extended expiry period to the service account token over the default one hour. For Amazon EKS clusters, the extended expiry period is 90 days. Your Amazon EKS cluster's Kubernetes API server rejects requests with tokens older than 90 days.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org