EKS 解决Unable to connect to the server 问题

yunson_Liu

已于 2023-03-15 03:25:52 修改

阅读量4.2k

点赞数 1

分类专栏： Amazon EKS 文章标签： kubernetes docker linux

于 2023-03-15 03:22:45 首次发布

本文链接：https://blog.csdn.net/baidu_38432732/article/details/129543935

版权

Amazon EKS 专栏收录该内容

16 篇文章

订阅专栏

文章描述了在尝试使用kubectl连接到EKS集群时遇到的错误，该错误涉及到ExecCredential插件的API版本不兼容问题。用户已经检查了eks集群的用户日志，确认了AWS配置，并尝试更新kubeconfig，但问题仍然存在。最终，用户选择降级kubectl版本来解决此问题。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

报错内容如下

Unable to connect to the server: getting credentials: exec plugin is configured to use API version client.authentication.k8s.io/v1beta1, plugin returned version client.authentication.k8s.io/v1alpha1

E0314 18:59:27.499748    1690 memcache.go:238] couldn't get current server API group list: Get "https://AAAAAAAAAAAAAAAAAAAAAAAAAAA.yl4.ap-east-1.eks.amazonaws.com/api?timeout=32s": getting credentials: decoding stdout: no kind "ExecCredential" is registered for version "client.authentication.k8s.io/v1alpha1" in scheme "pkg/client/auth/exec/exec.go:62"
E0314 18:59:27.991572    1690 memcache.go:238] couldn't get current server API group list: Get "https://AAAAAAAAAAAAAAAAAAAAAAAAAAA.yl4.ap-east-1.eks.amazonaws.com/api?timeout=32s": getting credentials: decoding stdout: no kind "ExecCredential" is registered for version "client.authentication.k8s.io/v1alpha1" in scheme "pkg/client/auth/exec/exec.go:62"
E0314 18:59:28.399304    1690 memcache.go:238] couldn't get current server API group list: Get "https://AAAAAAAAAAAAAAAAAAAAAAAAAAA.yl4.ap-east-1.eks.amazonaws.com/api?timeout=32s": getting credentials: decoding stdout: no kind "ExecCredential" is registered for version "client.authentication.k8s.io/v1alpha1" in scheme "pkg/client/auth/exec/exec.go:62"
E0314 18:59:28.807665    1690 memcache.go:238] couldn't get current server API group list: Get "https://AAAAAAAAAAAAAAAAAAAAAAAAAAA.yl4.ap-east-1.eks.amazonaws.com/api?timeout=32s": getting credentials: decoding stdout: no kind "ExecCredential" is registered for version "client.authentication.k8s.io/v1alpha1" in scheme "pkg/client/auth/exec/exec.go:62"
E0314 18:59:29.204910    1690 memcache.go:238] couldn't get current server API group list: Get "https://AAAAAAAAAAAAAAAAAAAAAAAAAAA.yl4.ap-east-1.eks.amazonaws.com/api?timeout=32s": getting credentials: decoding stdout: no kind "ExecCredential" is registered for version "client.authentication.k8s.io/v1alpha1" in scheme "pkg/client/auth/exec/exec.go:62"
Unable to connect to the server: getting credentials: decoding stdout: no kind "ExecCredential" is registered for version "client.authentication.k8s.io/v1alpha1" in scheme "pkg/client/auth/exec/exec.go:62"

1、先配置日志查询我们的eks所属用户
在这里插入图片描述
2、查询日志
执行以下查询语句

| sort @timestamp desc
| filter @logStream like /authenticator/
| filter @message like "username=kubernetes-admin"
| limit 50

在这里插入图片描述
3、查询当前主机aws configure

[root@ip-172-93-1-106 ~]# aws configure --profile produser
AWS Access Key ID [None]: XXXXXXXXXXXXXX
AWS Secret Access Key [None]: DDDDDDDDDDDDDDDDDDDDDDDDDDDD
Default region name [None]: ap-east-1
Default output format [None]: json
[root@ip-172-93-1-106 ~]# aws s3 ls --profile produser
[root@ip-172-93-1-106 ~]# aws sts get-caller-identity --profile produser
{
    "Account": "XXXXXXXXX", 
    "UserId": "DDDDDDDDDDDDDD", 
    "Arn": "arn:aws:iam::1111111111:user/abc"
}
[root@ip-172-93-1-106 ~]# aws eks update-kubeconfig --name test --region ap-east-1 --profile produser
Updated context arn:aws:eks:ap-east-1:1111111111:cluster/test in /root/.kube/config

4、执行操作远程k8s
报错如下

[root@ip-172-93-1-106 ~]# kubectl get nodes
error: exec plugin: invalid apiVersion "client.authentication.k8s.io/v1alpha1"

5、降低kubectl版本
各版本下载地址
https://docs.aws.amazon.com/eks/latest/userguide/install-kubectl.html

curl -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.23.16/2023-01-30/bin/linux/amd64/kubectl
chmod +x kubectl
[root@ip-172-93-1-106 ~]# kubectl get pod -A
NAMESPACE     NAME                       READY   STATUS    RESTARTS       AGE
kube-system   aws-node-dh767             1/1     Running   25 (32m ago)   131m
kube-system   aws-node-jbgls             1/1     Running   25 (32m ago)   131m
kube-system   coredns-68db9f7574-md7c9   1/1     Running   0              149m
kube-system   coredns-68db9f7574-vpdk5   1/1     Running   0              149m
kube-system   kube-proxy-4lbrz           1/1     Running   0              131m
kube-system   kube-proxy-k9tng           1/1     Running   0              131m