一、kubectl get nodes ERROR 8080 connection refused 解决方案 代码语言:javascript 复制 # 添加环境变量 echo"export KUBECONFIG=/etc/kubernetes/admin.conf">>/etc/profile source/etc/profile systemctl restart kubelet kubeadm reset-f 二、kubectl get nodes ERROR 6443 connection refused kubeadm init 无法成功...
The connection to the server :6443 was refused - did you specify the right kube-apiserver容器启动异常 2首先确认 防火墙已经关闭 selinux设置disabled完成 docker启动正常 kubelet运行状态active docker images存在所需镜像 3 解决方案 3.1 master节点 kubectl 查看命令是否正常 进入home目录 cd ~ 查看是否存在.kub...
查看了一下/var/log/message 报错信息如下: *May 9 20:05:50 m1 kubelet: E0509 20:05:50.350216 3464 reflector.go:126] k8s.io/client-go/informers/factory.go:133: Failed to list v1beta1.CSIDriver: Get https://192.168.56.1:6443/apis/storage.k8s.io/v1beta1/csidrivers?limit=500&resourceV...
[shirley@master k8s_install]$ sudo kubeadm init --config kubeadm.yaml [sudo] password for shirley...
6443/api/v1/nodes\": dial tcp 10.0.2.15:6443: connect: connection refused" node="debian12" Aug 14 20:20:11 Debian12 kubelet[5798]: E0814 20:20:11.830407 5798 event.go:368] "Unable to write event (may retry after sleeping)" err="Post \"https://10.0.2.15:6443/api/v1/namespaces/...
fieldSelector=spec.nodeName%3Dkata5&limit=500&resourceVersion=0: dial tcp 129.33.140.197:6443: connect: connection refused [...]
kubeadm init --apiserver-advertise-address=10.16.8.135 --image-repository registry.aliyuncs.com/google_containers --kubernetes-version v1.21.1 --service-cidr=10.96.0.0/16 --pod-network-cidr=10.244.0.0/16 重置 kubeadm reset 新问题1 初始化失败或join报错 [root@k8s-jerryji-2 ~]# kubeadm join 19...
还有一种是安装完毕后没有启动export KUBECONFIG=/etc/kubernetes/admin.conf 导致的 无法连接http://ip:6443的apiserver 错误 解决方法:export KUBECONFIG=/etc/kubernetes/admin.conf 放入环境随机启动 echo 'export KUBECONFIG=/etc/kubernetes/admin.conf' >> /root/.bashrc ...
需要复制自己上面master节点init生成的 [root@k8s-node1 ~]$ kubeadm join 192.168.88.10:6443 --token bgoz5x.qift7w4fue97pccu \ --discovery-token-ca-cert-hash sha256:b9216c0d46e4a86cddc2800ba062d0f8c2cbbe1894eb2822840161efe826f5f0 # 如果报错,到node节点进行重置,然后重新加入...
执行kubeadm init后,其状态就会恢复正常 systemctl status kubelet.service 初始化master节点 注意:kubeadm的安装过程不涉及网络插件(CNI)的初始化,因此kubeadm初步安装完成的集群不具备网络功能,任何Pod包括自带的CoreDNS都无法正常工作。 网络插件的安装往往对kubeadm init命令的参数有一定的要求。例如,安装Flannel或Calico...