-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to list *v1.Node: Unauthorized #547
Comments
hosts: 集群部署节点:一般为运行ansible 脚本的节点变量 NTP_ENABLED (=yes/no) 设置集群是否安装 chrony 时间同步[deploy] etcd集群请提供如下NODE_NAME,注意etcd集群必须是1,3,5,7...奇数个节点[etcd] [kube-master] [kube-node] 参数 NEW_INSTALL:yes表示新建,no表示使用已有harbor服务器如果不使用域名,可以设置 HARBOR_DOMAIN=""[harbor] 【可选】外部负载均衡,用于自有环境负载转发 NodePort 暴露的服务等[ex-lb] [all:vars] ---------集群主要参数---------------#集群部署模式:allinone, single-master, multi-master |
[root@host1 ansible]# kubectl get nodes |
检查下失败节点的 /etc/kubernetes 目录看看 kubelet相关的证书,配置在不在;
|
群主远程登陆处理,发现是每个主机的时间不一致导致认证失败。 |
在vmware创建了5个虚拟机测试,前3个节点挂上了,后2个没有部署上,报错:
5月 07 17:44:15 node4 kubelet[52929]: I0507 17:44:15.947332 52929 kubelet_node_status.go:452] Recording NodeHasNoDiskPressure event message for node 192.168.100.114
5月 07 17:44:15 node4 kubelet[52929]: I0507 17:44:15.947337 52929 kubelet_node_status.go:452] Recording NodeHasSufficientPID event message for node 192.168.100.114
5月 07 17:44:15 node4 kubelet[52929]: I0507 17:44:15.947348 52929 kubelet_node_status.go:93] Attempting to register node 192.168.100.114
5月 07 17:44:15 node4 kubelet[52929]: E0507 17:44:15.950074 52929 kubelet_node_status.go:117] Unable to register node "192.168.100.114" with API server: Unauthorized
5月 07 17:44:16 node4 kubelet[52929]: E0507 17:44:16.377891 52929 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:461: Failed to list *v1.Node: Unauthorized
5月 07 17:44:16 node4 kubelet[52929]: E0507 17:44:16.425108 52929 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:452: Failed to list *v1.Service: Unauthorized
5月 07 17:44:16 node4 kubelet[52929]: E0507 17:44:16.445579 52929 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47: Failed to list *v1.Pod: Unauthorized
5月 07 17:44:17 node4 kubelet[52929]: E0507 17:44:17.380186 52929 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:461: Failed to list *v1.Node: Unauthorized
5月 07 17:44:17 node4 kubelet[52929]: E0507 17:44:17.427314 52929 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:452: Failed to list *v1.Service: Unauthorized
5月 07 17:44:17 node4 kubelet[52929]: E0507 17:44:17.447967 52929 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47: Failed to list *v1.Pod: Unauthorized
5月 07 17:44:18 node4 kubelet[52929]: E0507 17:44:18.381821 52929 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:461: Failed to list *v1.Node: Unauthorized
5月 07 17:44:18 node4 kubelet[52929]: E0507 17:44:18.428575 52929 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:452: Failed to list *v1.Service: Unauthorized
5月 07 17:44:18 node4 kubelet[52929]: E0507 17:44:18.451040 52929 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47: Failed to list *v1.Pod: Unauthorized
The text was updated successfully, but these errors were encountered: