节点加入但主节点仅显示kubernetes集群上的主节点 [英] Node Join but master only show master node on kubernetes cluster
本文介绍了节点加入但主节点仅显示kubernetes集群上的主节点的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！
问题描述
我有一个主节点和两个节点来构建 kubernetes 集群.两个节点都成功加入了主节点(根据控制台日志).但是，当我运行 kubectl获取节点时，这仅是show master.
在主服务器上 ip a
我按照以下步骤运行以初始化集群
kubeadm初始化--apiserver-advertise-address = 192.168.56.8 --pod-network-cidr = 10.244.0.0/16 集群成功启动，我应用了 flannel .
节点加入母版
然后我检查节点和所有 pods
这里有什么问题吗?即使 Node 成功加入集群，也仅显示 master
-pod-network-cidr 是否正确?
kubeadm初始化--apiserver-advertise-address = 192.168.56.8 --pod-network-cidr = 10.244.0.0/16 更新
主服务器上的 systemctl状态kubelet
[root @ localhost〜]#systemctl status kubelet●kubelet.service-kubelet:Kubernetes节点代理已加载:已加载(/etc/systemd/system/kubelet.service；已禁用；供应商预设:已禁用)挂载:/etc/systemd/system/kubelet.service.d└─10-kubeadm.conf活动:自周二2019-02-19 02:10:31 EST起活动(运行);20分钟前3分钟文件:https://kubernetes.io/docs/主PID:2099(小方块)任务:17记忆体:37.3MCGroup:/system.slice/kubelet.service20─2099/usr/bin/kubelet --bootstrap-kubeconfig =/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig =/etc/kubernetes/kubelet.conf --config =/var/lib/kubelet/config.yaml --cgroup-driver = cgroupfs -...2月19日02:13:48 localhost.localdomain kubelet [2099]:W0219 02:13:48.423482 2099 kubelet.go:1647]删除镜像容器"kube-apiserver-localhost.localdomain_kube-system(e5b3349f-3415-11e9-9...t已过时2月19日02:13:48 localhost.localdomain kubelet [2099]:W0219 02:13:48.423758 2099 kubelet.go:1647]删除镜像容器"etcd-localhost.localdomain_kube-system(e5b30354-3415-11e9-9138-080027...t已过时2月19日02:13:48 localhost.localdomain kubelet [2099]:W0219 02:13:48.423926 2099 kubelet.go:1647]删除镜像容器"kube-scheduler-localhost.localdomain_kube-system(e5b31fd5-3415-11e9-9...t已过时2月19日02:13:48 localhost.localdomain kubelet [2099]:W0219 02:13:48.424101 2099 kubelet.go:1647]删除镜像容器"kube-controller-manager-localhost.localdomain_kube-system(e5b32acb-34 ...t已过时2月19日02:13:50 localhost.localdomain kubelet [2099]:W0219 02:13:50.431977 2099 kubelet.go:1647]删除镜像容器"kube-scheduler-localhost.localdomain_kube-system(e6e55cb5-3415-11e9-9...t已过时2月19日02:13:50 localhost.localdomain kubelet [2099]:W0219 02:13:50.432249 2099 kubelet.go:1647]删除镜像容器"kube-apiserver-localhost.localdomain_kube-system(e6e56f52-3415-11e9-9...t已过时2月19日02:13:50 localhost.localdomain kubelet [2099]:W0219 02:13:50.432406 2099 kubelet.go:1647]删除镜像容器"kube-controller-manager-localhost.localdomain_kube-system(e6e59401-34 ...t已过时2月19日02:13:50 localhost.localdomain kubelet [2099]:W0219 02:13:50.432560 2099 kubelet.go:1647]删除镜像容器"etcd-localhost.localdomain_kube-system(e6e5802e-3415-11e9-9138-080027...t已过时2月19日02:13:51 localhost.localdomain kubelet [2099]:W0219 02:13:51.977049 2099 cni.go:203]无法更新cni配置:在/etc/cni/net.d中找不到网络2月19日02:13:51 localhost.localdomain kubelet [2099]:E0219 02:13:51.977207 2099 kubelet.go:2192]容器运行时网络未就绪:NetworkReady = false原因:NetworkPluginNotReady messa ...未初始化提示:有些行被省略了，使用-l可以完整显示. journalctl -u kubelet 在主服务器上
[root @ localhost〜]#journalctl -u kubelet-日志从美国东部时间2019-02-19 01:31:20开始，在美国东部时间2019-02-19 02:14:27结束.--2月19日01:39:11 localhost.localdomain systemd [1]:启动了kubelet:Kubernetes节点代理.2月19日01:39:11 localhost.localdomain kubelet [13181]:不建议使用--cgroup-driver标志，应通过Kubelet的--config标志指定的配置文件设置此参数.参见https://kuberne2月19日01:39:11 localhost.localdomain kubelet [13181]:不建议使用--cgroup-driver标志，应通过Kubelet的--config标志指定的配置文件设置此参数.参见https://kuberne2月19日01:39:11 localhost.localdomain kubelet [13181]:F0219 01:39:11.716907 13181 server.go:244]无法加载客户端CA文件/etc/kubernetes/pki/ca.crt:打开/etc/kubernetes/pki/ca.crt:没有这样的文件或2月19日01:39:11 localhost.localdomain systemd [1]:kubelet.service:主进程已退出，代码=已退出，状态= 255/n/a2月19日01:39:11 localhost.localdomain systemd [1]:单元kubelet.service进入失败状态.2月19日01:39:11 localhost.localdomain systemd [1]:kubelet.service失败.2月19日01:39:21 localhost.localdomain systemd [1]:kubelet.service延迟释放时间，计划重新启动.2月19日01:39:21 localhost.localdomain systemd [1]:停止的kubelet:Kubernetes节点代理.2月19日01:39:21 localhost.localdomain systemd [1]:启动了kubelet:Kubernetes节点代理.2月19日01:39:22 localhost.localdomain kubelet [13189]:不建议使用--cgroup-driver标志，应通过由Kubelet的--config标志指定的配置文件设置此参数.参见https://kuberne2月19日01:39:22 localhost.localdomain kubelet [13189]:不建议使用--cgroup-driver标志，应通过由Kubelet的--config标志指定的配置文件设置此参数.参见https://kuberne2月19日01:39:22 localhost.localdomain kubelet [13189]:I0219 01:39:22.050655 13189 server.go:407]版本:v1.13.32月19日01:39:22 localhost.localdomain kubelet [13189]:I0219 01:39:22.050858 13189 plugins.go:103]未指定云提供商.2月19日01:39:22 localhost.localdomain kubelet [13189]:E0219 01:39:22.065072 13189 certificate_manager.go:348]从主服务器请求签名证书时失败:无法创建证书登录2月19日01:39:22 localhost.localdomain kubelet [13189]:I0219 01:39:22.110331 13189 server.go:666] --cgroups-per-qos已启用，但未指定--cgroup-root.默认为/2月19日01:39:22 localhost.localdomain kubelet [13189]:I0219 01:39:22.110567 13189 container_manager_linux.go:248]容器管理器已验证用户指定的cgroup-root是否存在:[]2月19日01:39:22 localhost.localdomain kubelet [13189]:I0219 01:39:22.110585 13189 container_manager_linux.go:253]基于节点配置创建容器管理器对象:{RuntimeCgroupsName:SystemCgroups2月19日01:39:22 localhost.localdomain kubelet [13189]:I0219 01:39:22.110663 13189 container_manager_linux.go:272]创建设备插件管理器:true2月19日01:39:22 localhost.localdomain kubelet [13189]:I0219 01:39:22.110721 13189 state_mem.go:36] [cpumanager]初始化新的内存状态存储2月19日01:39:22 localhost.localdomain kubelet [13189]:I0219 01:39:22.111976 13189 kubelet.go:281]添加pod路径:/etc/kubernetes/manifests2月19日01:39:22 localhost.localdomain kubelet [13189]:I0219 01:39:22.112038 13189 kubelet.go:306]观看apiserver2月19日01:39:22 localhost.localdomain kubelet [13189]:I0219 01:39:22.114437 13189 client.go:75]在unix:///var/run/docker.sock上连接到docker2月19日01:39:22 localhost.localdomain kubelet [13189]:I0219 01:39:22.114454 13189 client.go:104]启动docker client，请求超时= 2m0s2月19日01:39:22 localhost.localdomain kubelet [13189]:E0219 01:39:22.115604 13189 mirror.go:134] k8s.io/kubernetes/pkg/kubelet/kubelet.go:453:无法列出* v1.节点:获取https://192.168.56.8:6443/api2月19日01:39:22 localhost.localdomain kubelet [13189]:E0219 01:39:22.115643 13189 mirror.go:134] k8s.io/kubernetes/pkg/kubelet/kubelet.go:444:无法列出* v1.服务:获取https://192.168.56.8:6443/2月19日01:39:22 localhost.localdomain kubelet [13189]:E0219 01:39:22.115721 13189 mirror.go:134] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47:无法列出*v1.Pod:获取https://192.168.56.8:62月19日01:39:22 localhost.localdomain kubelet [13189]:W0219 01:39:22.116751 13189 docker_service.go:540]将发夹模式设置为混杂桥"，但未启用kubenet，回退到发夹-veth""2月19日01:39:22 localhost.localdomain kubelet [13189]:I0219 01:39:22.116765 13189 docker_service.go:236]发夹模式设置为发夹-垂直"2月19日01:39:22 localhost.localdomain kubelet [13189]:W0219 01:39:22.116832 13189 cni.go:203]无法更新cni配置:在/etc/cni/net.d中找不到网络2月19日01:39:22 localhost.localdomain kubelet [13189]:W0219 01:39:22.119472 13189 cni.go:203]无法更新cni配置:在/etc/cni/net.d中找不到网络2月19日01:39:22 localhost.localdomain kubelet [13189]:I0219 01:39:22.119494 13189 docker_service.go:251]由cni管理的Docker cri网络2月19日01:39:22 localhost.localdomain kubelet [13189]:I0219 01:39:22.139202 13189 docker_service.go:256] Docker信息:& {ID:ROIM:X2IR:DVOT:SQNQ:Z2F6:LH72:VGRC:FSH4:YMBJ:SJWP:RF4S:JY45容器:0包含2月19日01:39:22 localhost.localdomain kubelet [13189]:I0219 01:39:22.139261 13189 docker_service.go:269]将cgroupDriver设置为cgroupfs2月19日01:39:22 localhost.localdomain kubelet [13189]:I0219 01:39:22.163372 13189 kuberuntime_manager.go:198]容器运行时docker已初始化，版本:18.09.2，api版本:1.39.02月19日01:39:22 localhost.localdomain kubelet [13189]:I0219 01:39:22.167199 13189 server.go:999]启动了kubelet2月19日01:39:22 localhost.localdomain kubelet [13189]:E0219 01:39:22.167526 13189 kubelet.go:1308]图片垃圾收集失败一次.统计信息初始化可能尚未完成:无法获取imag2月19日01:39:22 localhost.localdomain kubelet [13189]:I0219 01:39:22.167913 13189 fs_resource_analyzer.go:66]正在启动FS ResourceAnalyzer2月19日01:39:22 localhost.localdomain kubelet [13189]:I0219 01:39:22.167935 13189 status_manager.go:152]开始与apiserver同步Pod状态2月19日01:39:22 localhost.localdomain kubelet [13189]:I0219 01:39:22.167944 13189 kubelet.go:1829]启动kubelet主同步循环.2月19日01:39:22 localhost.localdomain kubelet [13189]:I0219 01:39:22.167954 13189 kubelet.go:1846]跳过pod同步-[容器运行时状态检查可能尚未完成，但PLEG还不正常2月19日01:39:22 localhost.localdomain kubelet [13189]:I0219 01:39:22.168027 13189 server.go:137]开始在0.0.0.0:10250上收听2月19日01:39:22 localhost.localdomain kubelet [13189]:I0219 01:39:22.168439 13189 server.go:333]将调试处理程序添加到kubelet服务器.2月19日01:39:22 localhost.localdomain kubelet [13189]:I0219 01:39:22.169114 13189 volume_manager.go:248]启动Kubelet Volume Manager2月19日01:39:22 localhost.localdomain kubelet [13189]:E0219 01:39:22.169500 13189 event.go:212]无法编写事件:'Post https://192.168.56.8:6443/api/v1/namespaces/default/events:拨打tcp 192.168.562月19日01:39:22 localhost.localdomain kubelet [13189]:I0219 01:39:22.169922 13189 wanted_state_of_world_populator.go:130]所需的状态填充器开始运行2月19日01:39:22 localhost.localdomain kubelet [13189]:W0219 01:39:22.171070 13189 cni.go:203]无法更新cni配置:在/etc/cni/net.d中找不到网络2月19日01:39:22 localhost.localdomain kubelet [13189]:E0219 01:39:22.171245 13189 kubelet.go:2192]容器运行时网络未就绪:NetworkReady = false原因:NetworkPluginNotReady消息:docker:netw2月19日01:39:22 localhost.localdomain kubelet [13189]:E0219 01:39:22.269826 13189 kubelet.go:2266]找不到节点"localhost.localdomain"2月19日01:39:22 localhost.localdomain kubelet [13189]:I0219 01:39:22.269846 13189 kubelet.go:1846]跳过pod同步-[容器运行时状态检查可能尚未完成]2月19日01:39:22 localhost.localdomain kubelet [13189]:I0219 01:39:22.269867 13189 kubelet_node_status.go:278]设置节点注释以启用卷控制器附加/分离2月19日01:39:22 localhost.localdomain kubelet [13189]:I0219 01:39:22.272256 13189 kubelet_node_status.go:72]尝试注册节点localhost.localdomain2月19日01:39:22 localhost.localdomain kubelet [13189]:E0219 01:39:22.272472 13189 kubelet_node_status.go:94]无法向API服务器注册节点"localhost.localdomain":发布https://192.168.56.8:64432月19日01:39:22 localhost.localdomain kubelet [13189]:I0219 01:39:22.277225 13189 kubelet_node_status.go:278]设置节点注释以启用卷控制器附加/分离2月19日01:39:22 localhost.localdomain kubelet [13189]:I0219 01:39:22.278536 13189 cpu_manager.go:155] [cpumanager]从无策略开始2月19日01:39:22 localhost.localdomain kubelet [13189]:I0219 01:39:22.278544 13189 cpu_manager.go:156] [cpumanager]每10秒进行一次对帐 节点上的状态
[root @ localhost〜]#systemctl status kubelet●kubelet.service-kubelet:Kubernetes节点代理已加载:已加载(/etc/systemd/system/kubelet.service；已启用；供应商预设:已禁用)挂载:/etc/systemd/system/kubelet.service.d└─10-kubeadm.conf活动:自周二2019-02-19 02:13:23开始活动(运行);5分钟前文件:https://kubernetes.io/docs/主PID:14859(小方块)任务:16记忆体:36.3MCGroup:/system.slice/kubelet.service14─14859/usr/bin/kubelet --bootstrap-kubeconfig =/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig =/etc/kubernetes/kubelet.conf --config =/var/lib/kubelet/config.yaml --cgroup-driver = cgroupfs ...2月19日02:18:25 localhost.localdomain kubelet [14859]:E0219 02:18:25.598922 14859generic.go:277] PLEG:pod kube-proxy-4z575/kube-system重新检查失败:rpc错误:代码=未知desc...辅助论点2月19日02:18:26 localhost.localdomain kubelet [14859]:E0219 02:18:26.602125 14859 kuberuntime_manager.go:857] PodSandbox沙箱状态"2d9acc379432bdae0c9de5e6d99d26b8ea6e450a19767bd231778febef9aff ...2月19日02:18:26 localhost.localdomain kubelet [14859]:E0219 02:18:26.602146 14859generic.go:247] PLEG:忽略pod kube-proxy-4z575/kube-system的事件:rpc错误:代码=未知desc ... alid参数2月19日02:18:26 localhost.localdomain kubelet [14859]:E0219 02:18:26.603365 14859 kuberuntime_manager.go:857] PodSandbox沙盒状态"2d9acc379432bdae0c9de5e6d99d26b8ea6e450a19767bd231778febef9aff ...2月19日02:18:26 localhost.localdomain kubelet [14859]:E0219 02:18:26.603385 14859generic.go:277] PLEG:pod kube-proxy-4z575/kube-system重新检查失败:rpc错误:代码=未知desc...辅助论点2月19日02:18:27 localhost.localdomain kubelet [14859]:E0219 02:18:27.606248 14859 kuberuntime_manager.go:857] PodSandbox沙盒状态"2d9acc379432bdae0c9de5e6d99d26b8ea6e450a19767bd231778febef9aff ...2月19日02:18:27 localhost.localdomain kubelet [14859]:E0219 02:18:27.606270 14859generic.go:247] PLEG:忽略pod kube-proxy-4z575/kube-system的事件:rpc错误:代码=未知desc ... alid参数2月19日02:18:27 localhost.localdomain kubelet [14859]:E0219 02:18:27.607863 14859 kuberuntime_manager.go:857] PodSandbox沙盒状态"2d9acc379432bdae0c9de5e6d99d26b8ea6e450a19767bd231778febef9aff ...2月19日02:18:27 localhost.localdomain kubelet [14859]:E0219 02:18:27.607880 14859generic.go:277] PLEG:pod kube-proxy-4z575/kube-system重新检查失败:rpc错误:代码=未知desc...辅助论点2月19日02:18:27 localhost.localdomain kubelet [14859]:E0219 02:18:27.809433 14859 pod_workers.go:190]同步pod 84186094-3415-11e9-9138-080027621cd9("kube-proxy-4z575_kube-system(84186094-3415 ...提示:有些行被省略了，使用-l可以完整显示.[root @ localhost〜]#journalctl -u kubelet-日志开始于美国东部时间2019-02-19 01:31:23，结束于美国东部时间2019-02-19 02:19:06.--2月19日01:31:30 localhost.localdomain systemd [1]:启动了kubelet:Kubernetes节点代理.2月19日01:31:31 localhost.localdomain kubelet [2802]:F0219 01:31:31.353952 2802 server.go:189]无法加载Kubelet配置文件/var/lib/kubelet/config.yaml，错误无法读取kubelet配置文件"/2月19日01:31:31 localhost.localdomain systemd [1]:kubelet.service:主进程已退出，代码=已退出，状态= 255/n/a2月19日01:31:31 localhost.localdomain systemd [1]:单元kubelet.service进入失败状态.2月19日01:31:31 localhost.localdomain systemd [1]:kubelet.service失败.2月19日01:31:41 localhost.localdomain systemd [1]:kubelet.service延迟释放时间，计划重新启动.2月19日01:31:41 localhost.localdomain systemd [1]:停止的kubelet:Kubernetes节点代理.2月19日01:31:41 localhost.localdomain systemd [1]:启动了kubelet:Kubernetes节点代理.2月19日01:31:41 localhost.localdomain kubelet [7337]:F0219 01:31:41.829265 7337 server.go:189]无法加载Kubelet配置文件/var/lib/kubelet/config.yaml，错误无法读取kubelet配置文件"/2月19日01:31:41 localhost.localdomain systemd [1]:kubelet.service:主进程已退出，代码=已退出，状态= 255/n/a2月19日01:31:41 localhost.localdomain systemd [1]:单元kubelet.service进入失败状态.2月19日01:31:41 localhost.localdomain systemd [1]:kubelet.service失败.2月19日01:31:52 localhost.localdomain systemd [1]:kubelet.service延迟释放时间，计划重新启动.2月19日01:31:52 localhost.localdomain systemd [1]:停止的kubelet:Kubernetes节点代理.2月19日01:31:52 localhost.localdomain systemd [1]:启动了kubelet:Kubernetes节点代理.2月19日01:31:52 localhost.localdomain systemd [1]:kubelet.service:主进程已退出，代码=已退出，状态= 255/n/a2月19日01:31:52 localhost.localdomain kubelet [11899]:F0219 01:31:52.188858 11899 server.go:189]无法加载Kubelet配置文件/var/lib/kubelet/config.yaml，错误无法读取kubelet配置文件"2月19日01:31:52 localhost.localdomain systemd [1]:单元kubelet.service进入失败状态.2月19日01:31:52 localhost.localdomain systemd [1]:kubelet.service失败.2月19日01:32:02 localhost.localdomain systemd [1]:kubelet.service延迟释放时间，计划重新启动.2月19日01:32:02 localhost.localdomain systemd [1]:停止的kubelet:Kubernetes节点代理.2月19日01:32:02 localhost.localdomain systemd [1]:启动了kubelet:Kubernetes节点代理.2月19日01:32:02 localhost.localdomain kubelet [13110]:F0219 01:32:02.524046 13110 server.go:189]无法加载Kubelet配置文件/var/lib/kubelet/config.yaml，错误无法读取kubelet配置文件"2月19日01:32:02 localhost.localdomain systemd [1]:kubelet.service:主进程已退出，代码=已退出，状态= 255/n/a2月19日01:32:02 localhost.localdomain systemd [1]:单元kubelet.service进入失败状态.2月19日01:32:02 localhost.localdomain systemd [1]:kubelet.service失败.2月19日01:32:12 localhost.localdomain systemd [1]:kubelet.service延迟释放时间，计划重新启动.2月19日01:32:12 localhost.localdomain systemd [1]:停止的kubelet:Kubernetes节点代理.2月19日01:32:12 localhost.localdomain systemd [1]:启动了kubelet:Kubernetes节点代理.2月19日01:32:12 localhost.localdomain kubelet [13117]:F0219 01:32:12.854182 13117 server.go:189]无法加载Kubelet配置文件/var/lib/kubelet/config.yaml，错误无法读取kubelet配置文件"2月19日01:32:12 localhost.localdomain systemd [1]:kubelet.service:主进程已退出，代码=已退出，状态= 255/n/a2月19日01:32:12 localhost.localdomain systemd [1]:单元kubelet.service进入失败状态.2月19日01:32:12 localhost.localdomain systemd [1]:kubelet.service失败.2月19日01:32:23 localhost.localdomain systemd [1]:kubelet.service延迟释放时间，计划重新启动.2月19日01:32:23 localhost.localdomain systemd [1]:停止的kubelet:Kubernetes节点代理.2月19日01:32:23 localhost.localdomain systemd [1]:启动了kubelet:Kubernetes节点代理.2月19日01:32:23 localhost.localdomain kubelet [13124]:F0219 01:32:23.098681 13124 server.go:189]无法加载Kubelet配置文件/var/lib/kubelet/config.yaml，错误无法读取kubelet配置文件"2月19日01:32:23 localhost.localdomain systemd [1]:kubelet.service:主进程已退出，代码=已退出，状态= 255/n/a2月19日01:32:23 localhost.localdomain systemd [1]:单元kubelet.service进入失败状态.2月19日01:32:23 localhost.localdomain systemd [1]:kubelet.service失败.2月19日01:32:33 localhost.localdomain systemd [1]:kubelet.service延迟释放时间，计划重新启动.2月19日01:32:33 localhost.localdomain systemd [1]:停止的kubelet:Kubernetes节点代理.2月19日01:32:33 localhost.localdomain systemd [1]:启动了kubelet:Kubernetes节点代理.2月19日01:32:33 localhost.localdomain kubelet [13132]:F0219 01:32:33.350274 13132 server.go:189]无法加载Kubelet配置文件/var/lib/kubelet/config.yaml，错误无法读取kubelet配置文件"2月19日01:32:33 localhost.localdomain systemd [1]:kubelet.service:主进程已退出，代码=已退出，状态= 255/n/a2月19日01:32:33 localhost.localdomain systemd [1]:单元kubelet.service进入失败状态.2月19日01:32:33 localhost.localdomain systemd [1]:kubelet.service失败.2月19日01:32:43 localhost.localdomain systemd [1]:kubelet.service延迟释放时间，计划重新启动.2月19日01:32:43 localhost.localdomain systemd [1]:停止的kubelet:Kubernetes节点代理.2月19日01:32:43 localhost.localdomain systemd [1]:启动了kubelet:Kubernetes节点代理.2月19日01:32:43 localhost.localdomain kubelet [13140]:F0219 01:32:43.602227 13140 server.go:189]无法加载Kubelet配置文件/var/lib/kubelet/config.yaml，错误无法读取kubelet配置文件"2月19日01:32:43 localhost.localdomain systemd [1]:kubelet.service:主进程已退出，代码=已退出，状态= 255/n/a2月19日01:32:43 localhost.localdomain systemd [1]:单元kubelet.service进入失败状态.2月19日01:32:43 localhost.localdomain systemd [1]:kubelet.service失败.2月19日01:32:53 localhost.localdomain systemd [1]:kubelet.service延迟释放时间，计划重新启动.2月19日01:32:53 localhost.localdomain systemd [1]:停止的kubelet:Kubernetes节点代理. 解决方案
您需要将节点主机名更改为其他名称，而不是localhost，因为kubelet会基于主机名进行解析，并且不能是localhost.在kubeadm中执行此操作的方法是使用-node-name 参数.
-node-name 参数不能单独使用，您需要在kubelete confs中提供-hostname-override 选项.那只有它能起作用
因此，位于/etc/systemd/system/kubelet.service.d/10-kubeadm.conf 的kubelet额外args( KUBELET_EXTRA_ARGS )应该为--hostname-override =< name> .除此之外，在运行集群时，它还应该是:
kubeadm init --apiserver-advertise-address = 192.168.56.8 --pod-network-cidr = 10.244.0.0/16 --node-name =< name> 您还需要在工作节点kubelet.conf上执行相同的过程.conf应具有-hostname-override ，而join命令应具有-node-name ./p>
I have one master and two node to build kubernetes cluster. Both node successfully join the master (according to console log). But, when I run kubectl get nodes, which is show master only.
Here ip a on master
I run as below to init the cluster
kubeadm init --apiserver-advertise-address=192.168.56.8 --pod-network-cidr=10.244.0.0/16
The cluster is successfully started and I apply flannel.
Node Join to Master
And I check nodes and all of pods
Is there any problem here? Even if Node join to successfully to cluster, which is only show master
Is it correct for --pod-network-cidr ?
kubeadm init --apiserver-advertise-address=192.168.56.8 --pod-network-cidr=10.244.0.0/16
update
systemctl status kubelet on master
[root@localhost ~]# systemctl status kubelet
● kubelet.service - kubelet: The Kubernetes Node Agent
Loaded: loaded (/etc/systemd/system/kubelet.service; disabled; vendor preset: disabled)
Drop-In: /etc/systemd/system/kubelet.service.d
└─10-kubeadm.conf
Active: active (running) since Tue 2019-02-19 02:10:31 EST; 3min 20s ago
Docs: https://kubernetes.io/docs/
Main PID: 2099 (kubelet)
Tasks: 17
Memory: 37.3M
CGroup: /system.slice/kubelet.service
└─2099 /usr/bin/kubelet --bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf --config=/var/lib/kubelet/config.yaml --cgroup-driver=cgroupfs -...
Feb 19 02:13:48 localhost.localdomain kubelet[2099]: W0219 02:13:48.423482 2099 kubelet.go:1647] Deleting mirror pod "kube-apiserver-localhost.localdomain_kube-system(e5b3349f-3415-11e9-9...t is outdated
Feb 19 02:13:48 localhost.localdomain kubelet[2099]: W0219 02:13:48.423758 2099 kubelet.go:1647] Deleting mirror pod "etcd-localhost.localdomain_kube-system(e5b30354-3415-11e9-9138-080027...t is outdated
Feb 19 02:13:48 localhost.localdomain kubelet[2099]: W0219 02:13:48.423926 2099 kubelet.go:1647] Deleting mirror pod "kube-scheduler-localhost.localdomain_kube-system(e5b31fd5-3415-11e9-9...t is outdated
Feb 19 02:13:48 localhost.localdomain kubelet[2099]: W0219 02:13:48.424101 2099 kubelet.go:1647] Deleting mirror pod "kube-controller-manager-localhost.localdomain_kube-system(e5b32acb-34...t is outdated
Feb 19 02:13:50 localhost.localdomain kubelet[2099]: W0219 02:13:50.431977 2099 kubelet.go:1647] Deleting mirror pod "kube-scheduler-localhost.localdomain_kube-system(e6e55cb5-3415-11e9-9...t is outdated
Feb 19 02:13:50 localhost.localdomain kubelet[2099]: W0219 02:13:50.432249 2099 kubelet.go:1647] Deleting mirror pod "kube-apiserver-localhost.localdomain_kube-system(e6e56f52-3415-11e9-9...t is outdated
Feb 19 02:13:50 localhost.localdomain kubelet[2099]: W0219 02:13:50.432406 2099 kubelet.go:1647] Deleting mirror pod "kube-controller-manager-localhost.localdomain_kube-system(e6e59401-34...t is outdated
Feb 19 02:13:50 localhost.localdomain kubelet[2099]: W0219 02:13:50.432560 2099 kubelet.go:1647] Deleting mirror pod "etcd-localhost.localdomain_kube-system(e6e5802e-3415-11e9-9138-080027...t is outdated
Feb 19 02:13:51 localhost.localdomain kubelet[2099]: W0219 02:13:51.977049 2099 cni.go:203] Unable to update cni config: No networks found in /etc/cni/net.d
Feb 19 02:13:51 localhost.localdomain kubelet[2099]: E0219 02:13:51.977207 2099 kubelet.go:2192] Container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady messa...uninitialized
Hint: Some lines were ellipsized, use -l to show in full.
journalctl -u kubelet on master
[root@localhost ~]# journalctl -u kubelet
-- Logs begin at Tue 2019-02-19 01:31:20 EST, end at Tue 2019-02-19 02:14:27 EST. --
Feb 19 01:39:11 localhost.localdomain systemd[1]: Started kubelet: The Kubernetes Node Agent.
Feb 19 01:39:11 localhost.localdomain kubelet[13181]: Flag --cgroup-driver has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kuberne
Feb 19 01:39:11 localhost.localdomain kubelet[13181]: Flag --cgroup-driver has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kuberne
Feb 19 01:39:11 localhost.localdomain kubelet[13181]: F0219 01:39:11.716907 13181 server.go:244] unable to load client CA file /etc/kubernetes/pki/ca.crt: open /etc/kubernetes/pki/ca.crt: no such file or
Feb 19 01:39:11 localhost.localdomain systemd[1]: kubelet.service: main process exited, code=exited, status=255/n/a
Feb 19 01:39:11 localhost.localdomain systemd[1]: Unit kubelet.service entered failed state.
Feb 19 01:39:11 localhost.localdomain systemd[1]: kubelet.service failed.
Feb 19 01:39:21 localhost.localdomain systemd[1]: kubelet.service holdoff time over, scheduling restart.
Feb 19 01:39:21 localhost.localdomain systemd[1]: Stopped kubelet: The Kubernetes Node Agent.
Feb 19 01:39:21 localhost.localdomain systemd[1]: Started kubelet: The Kubernetes Node Agent.
Feb 19 01:39:22 localhost.localdomain kubelet[13189]: Flag --cgroup-driver has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kuberne
Feb 19 01:39:22 localhost.localdomain kubelet[13189]: Flag --cgroup-driver has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kuberne
Feb 19 01:39:22 localhost.localdomain kubelet[13189]: I0219 01:39:22.050655 13189 server.go:407] Version: v1.13.3
Feb 19 01:39:22 localhost.localdomain kubelet[13189]: I0219 01:39:22.050858 13189 plugins.go:103] No cloud provider specified.
Feb 19 01:39:22 localhost.localdomain kubelet[13189]: E0219 01:39:22.065072 13189 certificate_manager.go:348] Failed while requesting a signed certificate from the master: cannot create certificate signin
Feb 19 01:39:22 localhost.localdomain kubelet[13189]: I0219 01:39:22.110331 13189 server.go:666] --cgroups-per-qos enabled, but --cgroup-root was not specified. defaulting to /
Feb 19 01:39:22 localhost.localdomain kubelet[13189]: I0219 01:39:22.110567 13189 container_manager_linux.go:248] container manager verified user specified cgroup-root exists: []
Feb 19 01:39:22 localhost.localdomain kubelet[13189]: I0219 01:39:22.110585 13189 container_manager_linux.go:253] Creating Container Manager object based on Node Config: {RuntimeCgroupsName: SystemCgroups
Feb 19 01:39:22 localhost.localdomain kubelet[13189]: I0219 01:39:22.110663 13189 container_manager_linux.go:272] Creating device plugin manager: true
Feb 19 01:39:22 localhost.localdomain kubelet[13189]: I0219 01:39:22.110721 13189 state_mem.go:36] [cpumanager] initializing new in-memory state store
Feb 19 01:39:22 localhost.localdomain kubelet[13189]: I0219 01:39:22.111976 13189 kubelet.go:281] Adding pod path: /etc/kubernetes/manifests
Feb 19 01:39:22 localhost.localdomain kubelet[13189]: I0219 01:39:22.112038 13189 kubelet.go:306] Watching apiserver
Feb 19 01:39:22 localhost.localdomain kubelet[13189]: I0219 01:39:22.114437 13189 client.go:75] Connecting to docker on unix:///var/run/docker.sock
Feb 19 01:39:22 localhost.localdomain kubelet[13189]: I0219 01:39:22.114454 13189 client.go:104] Start docker client with request timeout=2m0s
Feb 19 01:39:22 localhost.localdomain kubelet[13189]: E0219 01:39:22.115604 13189 reflector.go:134] k8s.io/kubernetes/pkg/kubelet/kubelet.go:453: Failed to list *v1.Node: Get https://192.168.56.8:6443/api
Feb 19 01:39:22 localhost.localdomain kubelet[13189]: E0219 01:39:22.115643 13189 reflector.go:134] k8s.io/kubernetes/pkg/kubelet/kubelet.go:444: Failed to list *v1.Service: Get https://192.168.56.8:6443/
Feb 19 01:39:22 localhost.localdomain kubelet[13189]: E0219 01:39:22.115721 13189 reflector.go:134] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47: Failed to list *v1.Pod: Get https://192.168.56.8:6
Feb 19 01:39:22 localhost.localdomain kubelet[13189]: W0219 01:39:22.116751 13189 docker_service.go:540] Hairpin mode set to "promiscuous-bridge" but kubenet is not enabled, falling back to "hairpin-veth"
Feb 19 01:39:22 localhost.localdomain kubelet[13189]: I0219 01:39:22.116765 13189 docker_service.go:236] Hairpin mode set to "hairpin-veth"
Feb 19 01:39:22 localhost.localdomain kubelet[13189]: W0219 01:39:22.116832 13189 cni.go:203] Unable to update cni config: No networks found in /etc/cni/net.d
Feb 19 01:39:22 localhost.localdomain kubelet[13189]: W0219 01:39:22.119472 13189 cni.go:203] Unable to update cni config: No networks found in /etc/cni/net.d
Feb 19 01:39:22 localhost.localdomain kubelet[13189]: I0219 01:39:22.119494 13189 docker_service.go:251] Docker cri networking managed by cni
Feb 19 01:39:22 localhost.localdomain kubelet[13189]: I0219 01:39:22.139202 13189 docker_service.go:256] Docker Info: &{ID:ROIM:X2IR:DVOT:SQNQ:Z2F6:LH72:VGRC:FSH4:YMBJ:SJWP:RF4S:JY45 Containers:0 Containe
Feb 19 01:39:22 localhost.localdomain kubelet[13189]: I0219 01:39:22.139261 13189 docker_service.go:269] Setting cgroupDriver to cgroupfs
Feb 19 01:39:22 localhost.localdomain kubelet[13189]: I0219 01:39:22.163372 13189 kuberuntime_manager.go:198] Container runtime docker initialized, version: 18.09.2, apiVersion: 1.39.0
Feb 19 01:39:22 localhost.localdomain kubelet[13189]: I0219 01:39:22.167199 13189 server.go:999] Started kubelet
Feb 19 01:39:22 localhost.localdomain kubelet[13189]: E0219 01:39:22.167526 13189 kubelet.go:1308] Image garbage collection failed once. Stats initialization may not have completed yet: failed to get imag
Feb 19 01:39:22 localhost.localdomain kubelet[13189]: I0219 01:39:22.167913 13189 fs_resource_analyzer.go:66] Starting FS ResourceAnalyzer
Feb 19 01:39:22 localhost.localdomain kubelet[13189]: I0219 01:39:22.167935 13189 status_manager.go:152] Starting to sync pod status with apiserver
Feb 19 01:39:22 localhost.localdomain kubelet[13189]: I0219 01:39:22.167944 13189 kubelet.go:1829] Starting kubelet main sync loop.
Feb 19 01:39:22 localhost.localdomain kubelet[13189]: I0219 01:39:22.167954 13189 kubelet.go:1846] skipping pod synchronization - [container runtime status check may not have completed yet PLEG is not hea
Feb 19 01:39:22 localhost.localdomain kubelet[13189]: I0219 01:39:22.168027 13189 server.go:137] Starting to listen on 0.0.0.0:10250
Feb 19 01:39:22 localhost.localdomain kubelet[13189]: I0219 01:39:22.168439 13189 server.go:333] Adding debug handlers to kubelet server.
Feb 19 01:39:22 localhost.localdomain kubelet[13189]: I0219 01:39:22.169114 13189 volume_manager.go:248] Starting Kubelet Volume Manager
Feb 19 01:39:22 localhost.localdomain kubelet[13189]: E0219 01:39:22.169500 13189 event.go:212] Unable to write event: 'Post https://192.168.56.8:6443/api/v1/namespaces/default/events: dial tcp 192.168.56
Feb 19 01:39:22 localhost.localdomain kubelet[13189]: I0219 01:39:22.169922 13189 desired_state_of_world_populator.go:130] Desired state populator starts to run
Feb 19 01:39:22 localhost.localdomain kubelet[13189]: W0219 01:39:22.171070 13189 cni.go:203] Unable to update cni config: No networks found in /etc/cni/net.d
Feb 19 01:39:22 localhost.localdomain kubelet[13189]: E0219 01:39:22.171245 13189 kubelet.go:2192] Container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: netw
Feb 19 01:39:22 localhost.localdomain kubelet[13189]: E0219 01:39:22.269826 13189 kubelet.go:2266] node "localhost.localdomain" not found
Feb 19 01:39:22 localhost.localdomain kubelet[13189]: I0219 01:39:22.269846 13189 kubelet.go:1846] skipping pod synchronization - [container runtime status check may not have completed yet]
Feb 19 01:39:22 localhost.localdomain kubelet[13189]: I0219 01:39:22.269867 13189 kubelet_node_status.go:278] Setting node annotation to enable volume controller attach/detach
Feb 19 01:39:22 localhost.localdomain kubelet[13189]: I0219 01:39:22.272256 13189 kubelet_node_status.go:72] Attempting to register node localhost.localdomain
Feb 19 01:39:22 localhost.localdomain kubelet[13189]: E0219 01:39:22.272472 13189 kubelet_node_status.go:94] Unable to register node "localhost.localdomain" with API server: Post https://192.168.56.8:6443
Feb 19 01:39:22 localhost.localdomain kubelet[13189]: I0219 01:39:22.277225 13189 kubelet_node_status.go:278] Setting node annotation to enable volume controller attach/detach
Feb 19 01:39:22 localhost.localdomain kubelet[13189]: I0219 01:39:22.278536 13189 cpu_manager.go:155] [cpumanager] starting with none policy
Feb 19 01:39:22 localhost.localdomain kubelet[13189]: I0219 01:39:22.278544 13189 cpu_manager.go:156] [cpumanager] reconciling every 10s
status on node
[root@localhost ~]# systemctl status kubelet
● kubelet.service - kubelet: The Kubernetes Node Agent
Loaded: loaded (/etc/systemd/system/kubelet.service; enabled; vendor preset: disabled)
Drop-In: /etc/systemd/system/kubelet.service.d
└─10-kubeadm.conf
Active: active (running) since Tue 2019-02-19 02:13:23 EST; 5min ago
Docs: https://kubernetes.io/docs/
Main PID: 14859 (kubelet)
Tasks: 16
Memory: 36.3M
CGroup: /system.slice/kubelet.service
└─14859 /usr/bin/kubelet --bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf --config=/var/lib/kubelet/config.yaml --cgroup-driver=cgroupfs ...
Feb 19 02:18:25 localhost.localdomain kubelet[14859]: E0219 02:18:25.598922 14859 generic.go:277] PLEG: pod kube-proxy-4z575/kube-system failed reinspection: rpc error: code = Unknown desc...alid argument
Feb 19 02:18:26 localhost.localdomain kubelet[14859]: E0219 02:18:26.602125 14859 kuberuntime_manager.go:857] PodSandboxStatus of sandbox "2d9acc379432bdae0c9de5e6d99d26b8ea6e450a19767bd231778febef9aff...
Feb 19 02:18:26 localhost.localdomain kubelet[14859]: E0219 02:18:26.602146 14859 generic.go:247] PLEG: Ignoring events for pod kube-proxy-4z575/kube-system: rpc error: code = Unknown desc...alid argument
Feb 19 02:18:26 localhost.localdomain kubelet[14859]: E0219 02:18:26.603365 14859 kuberuntime_manager.go:857] PodSandboxStatus of sandbox "2d9acc379432bdae0c9de5e6d99d26b8ea6e450a19767bd231778febef9aff...
Feb 19 02:18:26 localhost.localdomain kubelet[14859]: E0219 02:18:26.603385 14859 generic.go:277] PLEG: pod kube-proxy-4z575/kube-system failed reinspection: rpc error: code = Unknown desc...alid argument
Feb 19 02:18:27 localhost.localdomain kubelet[14859]: E0219 02:18:27.606248 14859 kuberuntime_manager.go:857] PodSandboxStatus of sandbox "2d9acc379432bdae0c9de5e6d99d26b8ea6e450a19767bd231778febef9aff...
Feb 19 02:18:27 localhost.localdomain kubelet[14859]: E0219 02:18:27.606270 14859 generic.go:247] PLEG: Ignoring events for pod kube-proxy-4z575/kube-system: rpc error: code = Unknown desc...alid argument
Feb 19 02:18:27 localhost.localdomain kubelet[14859]: E0219 02:18:27.607863 14859 kuberuntime_manager.go:857] PodSandboxStatus of sandbox "2d9acc379432bdae0c9de5e6d99d26b8ea6e450a19767bd231778febef9aff...
Feb 19 02:18:27 localhost.localdomain kubelet[14859]: E0219 02:18:27.607880 14859 generic.go:277] PLEG: pod kube-proxy-4z575/kube-system failed reinspection: rpc error: code = Unknown desc...alid argument
Feb 19 02:18:27 localhost.localdomain kubelet[14859]: E0219 02:18:27.809433 14859 pod_workers.go:190] Error syncing pod 84186094-3415-11e9-9138-080027621cd9 ("kube-proxy-4z575_kube-system(84186094-3415...
Hint: Some lines were ellipsized, use -l to show in full.
[root@localhost ~]# journalctl -u kubelet
-- Logs begin at Tue 2019-02-19 01:31:23 EST, end at Tue 2019-02-19 02:19:06 EST. --
Feb 19 01:31:30 localhost.localdomain systemd[1]: Started kubelet: The Kubernetes Node Agent.
Feb 19 01:31:31 localhost.localdomain kubelet[2802]: F0219 01:31:31.353952 2802 server.go:189] failed to load Kubelet config file /var/lib/kubelet/config.yaml, error failed to read kubelet config file "/
Feb 19 01:31:31 localhost.localdomain systemd[1]: kubelet.service: main process exited, code=exited, status=255/n/a
Feb 19 01:31:31 localhost.localdomain systemd[1]: Unit kubelet.service entered failed state.
Feb 19 01:31:31 localhost.localdomain systemd[1]: kubelet.service failed.
Feb 19 01:31:41 localhost.localdomain systemd[1]: kubelet.service holdoff time over, scheduling restart.
Feb 19 01:31:41 localhost.localdomain systemd[1]: Stopped kubelet: The Kubernetes Node Agent.
Feb 19 01:31:41 localhost.localdomain systemd[1]: Started kubelet: The Kubernetes Node Agent.
Feb 19 01:31:41 localhost.localdomain kubelet[7337]: F0219 01:31:41.829265 7337 server.go:189] failed to load Kubelet config file /var/lib/kubelet/config.yaml, error failed to read kubelet config file "/
Feb 19 01:31:41 localhost.localdomain systemd[1]: kubelet.service: main process exited, code=exited, status=255/n/a
Feb 19 01:31:41 localhost.localdomain systemd[1]: Unit kubelet.service entered failed state.
Feb 19 01:31:41 localhost.localdomain systemd[1]: kubelet.service failed.
Feb 19 01:31:52 localhost.localdomain systemd[1]: kubelet.service holdoff time over, scheduling restart.
Feb 19 01:31:52 localhost.localdomain systemd[1]: Stopped kubelet: The Kubernetes Node Agent.
Feb 19 01:31:52 localhost.localdomain systemd[1]: Started kubelet: The Kubernetes Node Agent.
Feb 19 01:31:52 localhost.localdomain systemd[1]: kubelet.service: main process exited, code=exited, status=255/n/a
Feb 19 01:31:52 localhost.localdomain kubelet[11899]: F0219 01:31:52.188858 11899 server.go:189] failed to load Kubelet config file /var/lib/kubelet/config.yaml, error failed to read kubelet config file "
Feb 19 01:31:52 localhost.localdomain systemd[1]: Unit kubelet.service entered failed state.
Feb 19 01:31:52 localhost.localdomain systemd[1]: kubelet.service failed.
Feb 19 01:32:02 localhost.localdomain systemd[1]: kubelet.service holdoff time over, scheduling restart.
Feb 19 01:32:02 localhost.localdomain systemd[1]: Stopped kubelet: The Kubernetes Node Agent.
Feb 19 01:32:02 localhost.localdomain systemd[1]: Started kubelet: The Kubernetes Node Agent.
Feb 19 01:32:02 localhost.localdomain kubelet[13110]: F0219 01:32:02.524046 13110 server.go:189] failed to load Kubelet config file /var/lib/kubelet/config.yaml, error failed to read kubelet config file "
Feb 19 01:32:02 localhost.localdomain systemd[1]: kubelet.service: main process exited, code=exited, status=255/n/a
Feb 19 01:32:02 localhost.localdomain systemd[1]: Unit kubelet.service entered failed state.
Feb 19 01:32:02 localhost.localdomain systemd[1]: kubelet.service failed.
Feb 19 01:32:12 localhost.localdomain systemd[1]: kubelet.service holdoff time over, scheduling restart.
Feb 19 01:32:12 localhost.localdomain systemd[1]: Stopped kubelet: The Kubernetes Node Agent.
Feb 19 01:32:12 localhost.localdomain systemd[1]: Started kubelet: The Kubernetes Node Agent.
Feb 19 01:32:12 localhost.localdomain kubelet[13117]: F0219 01:32:12.854182 13117 server.go:189] failed to load Kubelet config file /var/lib/kubelet/config.yaml, error failed to read kubelet config file "
Feb 19 01:32:12 localhost.localdomain systemd[1]: kubelet.service: main process exited, code=exited, status=255/n/a
Feb 19 01:32:12 localhost.localdomain systemd[1]: Unit kubelet.service entered failed state.
Feb 19 01:32:12 localhost.localdomain systemd[1]: kubelet.service failed.
Feb 19 01:32:23 localhost.localdomain systemd[1]: kubelet.service holdoff time over, scheduling restart.
Feb 19 01:32:23 localhost.localdomain systemd[1]: Stopped kubelet: The Kubernetes Node Agent.
Feb 19 01:32:23 localhost.localdomain systemd[1]: Started kubelet: The Kubernetes Node Agent.
Feb 19 01:32:23 localhost.localdomain kubelet[13124]: F0219 01:32:23.098681 13124 server.go:189] failed to load Kubelet config file /var/lib/kubelet/config.yaml, error failed to read kubelet config file "
Feb 19 01:32:23 localhost.localdomain systemd[1]: kubelet.service: main process exited, code=exited, status=255/n/a
Feb 19 01:32:23 localhost.localdomain systemd[1]: Unit kubelet.service entered failed state.
Feb 19 01:32:23 localhost.localdomain systemd[1]: kubelet.service failed.
Feb 19 01:32:33 localhost.localdomain systemd[1]: kubelet.service holdoff time over, scheduling restart.
Feb 19 01:32:33 localhost.localdomain systemd[1]: Stopped kubelet: The Kubernetes Node Agent.
Feb 19 01:32:33 localhost.localdomain systemd[1]: Started kubelet: The Kubernetes Node Agent.
Feb 19 01:32:33 localhost.localdomain kubelet[13132]: F0219 01:32:33.350274 13132 server.go:189] failed to load Kubelet config file /var/lib/kubelet/config.yaml, error failed to read kubelet config file "
Feb 19 01:32:33 localhost.localdomain systemd[1]: kubelet.service: main process exited, code=exited, status=255/n/a
Feb 19 01:32:33 localhost.localdomain systemd[1]: Unit kubelet.service entered failed state.
Feb 19 01:32:33 localhost.localdomain systemd[1]: kubelet.service failed.
Feb 19 01:32:43 localhost.localdomain systemd[1]: kubelet.service holdoff time over, scheduling restart.
Feb 19 01:32:43 localhost.localdomain systemd[1]: Stopped kubelet: The Kubernetes Node Agent.
Feb 19 01:32:43 localhost.localdomain systemd[1]: Started kubelet: The Kubernetes Node Agent.
Feb 19 01:32:43 localhost.localdomain kubelet[13140]: F0219 01:32:43.602227 13140 server.go:189] failed to load Kubelet config file /var/lib/kubelet/config.yaml, error failed to read kubelet config file "
Feb 19 01:32:43 localhost.localdomain systemd[1]: kubelet.service: main process exited, code=exited, status=255/n/a
Feb 19 01:32:43 localhost.localdomain systemd[1]: Unit kubelet.service entered failed state.
Feb 19 01:32:43 localhost.localdomain systemd[1]: kubelet.service failed.
Feb 19 01:32:53 localhost.localdomain systemd[1]: kubelet.service holdoff time over, scheduling restart.
Feb 19 01:32:53 localhost.localdomain systemd[1]: Stopped kubelet: The Kubernetes Node Agent.
解决方案
You need to change the node hostname to something else rather than localhost, as kubelet resolves based on hostname and it can't be localhost. The way you can do it in kubeadm is using --node-name parameter.
The --node-name parameter doesn't work alone, you need to provide the --hostname-override option in kubelete confs. Then only it will work
So, your kubelet extra args(KUBELET_EXTRA_ARGS) at /etc/systemd/system/kubelet.service.d/10-kubeadm.conf should be --hostname-override=<name>. In addition to that while running init the cluster it should be:
kubeadm init --apiserver-advertise-address=192.168.56.8 --pod-network-cidr=10.244.0.0/16 --node-name=<name>
You also need to do same procedure on worker node kubelet.conf should have --hostname-override and the join command should have --node-name.
这篇关于节点加入但主节点仅显示kubernetes集群上的主节点的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
查看全文
