EKS 解决Unable to connect to the server 问题

报错内容如下

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

EKS 解决Unable to connect to the server 问题相关推荐

解决:unable to connect to X server
错误如下: ERROR: In /home/whistler/Desktop/build/VTK-8.2.0/Rendering/OpenGL2/vtkXOpenGLRenderWindow.cxx, ...
解决： Unable to connect to zookeeper server within timeout: 5000
前些天发现了一个巨牛的人工智能学习网站,通俗易懂,风趣幽默,忍不住分享一下给大家.点击跳转到教程. 一个项目启动不起来了,报错如题: Caused by: org.I0Itec.zkclient.ex ...
kubectl get node运行时出现：Unable to connect to the server: x509: certificate signed by unknown authority
kubectl get nodes运行时出现:Unable to connect to the server: x509: certificate signed by unknown authorit ...
Android 模拟器连接异常：Unable to connect to ADB server
简介在使用Android Studio开始的过程是,偶尔会突然出现一只在检测设备,导致无法进行运行的调试的情况,本文记录下解决方法现象描述在启动Android Studio后,在设备状态栏中一直 ...
k8s系列之：Unable to connect to the server: x509: certificate signed by unknown authority
k8s系列之:Unable to connect to the server: x509: certificate signed by unknown authority K8s使用kubeadm r ...
解决Can't connect to MySQL server on 'localhost' (10048)
解决Can't connect to MySQL server on 'localhost' (10048) 您使用的是Windows操作系统,此错误与一个注册表键值TcpTimedWaitDelay ...
kubesphere master节点执行kubectl get po Unable to connect to the server: Forbidden
在kubesphere master节点上执行kubectl get po -n xx报出Unable to connect to the server: Forbidden的错误信息,但是集群整体运 ...
aks Unable to connect to the server: x509
问题: aks 执行kubectl get pods 等命令遇到: Unable to connect to the server: x509: certificate signed by unkn ...
VNC Viewer 远程 Unable to connect to VNC Server using your chosen securitysetting. 问题解决
VNC Viewer 远程 Ubuntu桌面时(VNC服务端为Vino)可能出现以下问题: Unable to connect to VNC Server using your chosen secu ...

EKS 解决Unable to connect to the server 问题

EKS 解决Unable to connect to the server 问题相关推荐

最新文章

热门文章