FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -o yaml'
error execution phase preflight: unable to fetch the kubeadm-config ConfigMap: failed to get component configs: could not download the kubelet configuration from ConfigMap "kubelet-config": configmaps "kubelet-config" is forbidden: User "system:bootstrap:y89j06" cannot get resource "configmaps" in API group "" in the namespace "kube-system
出现原因:
kubeadm和kubelet版本与集群不一致。
解决方法:
卸载cri-tools和kubelet,并重新安装kubeadm和kubelet正确的版本,版本应依据master的版本来安装,不应高于master的版本。(如果kubelet版本高于kubeadm,则加入节点成功之后会一直处于NotReady状态)
————————————————
检查集群的版本:
[root@master01 kube-controller-manager]# kubeadm version
kubeadm version: &version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.3", GitCommit:"ca643a4d1f7bfe34773c74f79527be4afd95bf39", GitTreeState:"clean", BuildDate:"2

本文详细阐述了kubeadm和kubelet版本不匹配导致的问题,涉及禁用、删除旧版本、升级到集群对应版本的操作,并介绍了修复kubelet网络配置和加入集群过程中遇到的unknownflag错误。重点在于确保master和node节点的同步,包括修改docker配置和执行正确的kubeadm join命令。
最低0.47元/天 解锁文章
3801

被折叠的 条评论
为什么被折叠?



