kk部署的时候报错，装了两次都是全新的环境。在虚拟化平台安装，3台master3台node

songmings

kk部署的时候报错，装了两次都是全新的环境。在虚拟化平台安装，3台master3台node。在三台master上检测kubelet状态都是没有启动，也无法启动

操作系统信息

虚拟机：centos7.9, 4c8g100gb，内核6.0.9-1.el7.elrepo.x86_64

Kubernetes版本信息
Client Version: version.Info{Major:“1”, Minor:“22”, GitVersion:“v1.22.12”, GitCommit:“b058e1760c79f46a834ba59bd7a3486ecf28237d”, GitTreeState:“clean”, BuildDate:“2022-07-13T14:59:18Z”, GoVersion:“go1.16.15”, Compiler:“gc”, Platform:“linux/amd64”}

容器运行时

docker version:20.10.8

KubeSphere版本信息
v3.3.1 在线安装。kk安装

问题是什么

安装完docker后报错，装了两次，都是全新的环境，在同一个地方失败了，错误信息：

[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory “/etc/kubernetes/manifests”. This can take up to 4m0s

[kubelet-check] Initial timeout of 40s passed.

    Unfortunately, an error has occurred:

            timed out waiting for the condition

    This error is likely caused by:

            - The kubelet is not running

            - The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)

    If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:

            - 'systemctl status kubelet'

            - 'journalctl -xeu kubelet'

    Additionally, a control plane component may have crashed or exited when started by the container runtime.

    To troubleshoot, list all containers using your preferred container runtimes CLI.

    Here is one example how you may list all Kubernetes containers running in docker:

            - 'docker ps -a | grep kube | grep -v pause'

            Once you have found the failing container, you can inspect its logs with:

            - 'docker logs CONTAINERID'

error execution phase wait-control-plane: couldn’t initialize a Kubernetes cluster

To see the stack trace of this error execute with –v=5 or higher: Process exited with status 1

15:55:20 CST retry: [master1]

我看了详细的错误，如下：

master1 kubelet[28187]: E1123 15:56:36.755679 28187 kubelet.go:2456] “Error getting node” err="node \“master1\” not found"

11月 23 15:56:36 master1 kubelet[28187]: E1123 15:56:36.856621 28187 kubelet.go:2456] “Error getting node” err="node \“master1\” not found"

11月 23 15:56:36 master1 kubelet[28187]: E1123 15:56:36.957529 28187 kubelet.go:2456] “Error getting node” err="node \“master1\” not found"

11月 23 15:56:37 master1 kubelet[28187]: E1123 15:56:37.058644 28187 kubelet.go:2456] “Error getting node” err="node \“master1\” not found"

11月 23 15:56:37 master1 kubelet[28187]: E1123 15:56:37.159162 28187 kubelet.go:2456] “Error getting node” err="node \“master1\” not found"

11月 23 15:56:37 master1 kubelet[28187]: E1123 15:56:37.260104 28187 kubelet.go:2456] “Error getting node” err="node \“master1\” not found"

11月 23 15:56:37 master1 kubelet[28187]: E1123 15:56:37.361050 28187 kubelet.go:2456] “Error getting node” err="node \“master1\” not found"

11月 23 15:56:37 master1 kubelet[28187]: E1123 15:56:37.461934 28187 kubelet.go:2456] “Error getting node” err="node \“master1\” not found"

11月 23 15:56:37 master1 kubelet[28187]: E1123 15:56:37.562343 28187 kubelet.go:2456] “Error getting node” err="node \“master1\” not found"

11月 23 15:56:37 master1 kubelet[28187]: E1123 15:56:37.663448 28187 kubelet.go:2456] “Error getting node” err="node \“master1\” not found"

11月 23 15:56:37 master1 kubelet[28187]: E1123 15:56:37.764189 28187 kubelet.go:2456] “Error getting node” err="node \“master1\” not found"

11月 23 15:56:37 master1 kubelet[28187]: E1123 15:56:37.854265 28187 controller.go:144] failed to ensure lease exists, will retry in 7s, error: Get "https://lb.kubesphere.local:6443/apis/coor

11月 23 15:56:37 master1 kubelet[28187]: E1123 15:56:37.865269 28187 kubelet.go:2456] “Error getting node” err="node \“master1\” not found"

11月 23 15:56:37 master1 kubelet[28187]: E1123 15:56:37.965589 28187 kubelet.go:2456] “Error getting node” err="node \“master1\” not found"

11月 23 15:56:38 master1 kubelet[28187]: E1123 15:56:38.066360 28187 kubelet.go:2456] “Error getting node” err="node \“master1\” not found"

11月 23 15:56:38 master1 kubelet[28187]: E1123 15:56:38.167156 28187 kubelet.go:2456] “Error getting node” err="node \“master1\” not found"

11月 23 15:56:38 master1 kubelet[28187]: E1123 15:56:38.267869 28187 kubelet.go:2456] “Error getting node” err="node \“master1\” not found"

11月 23 15:56:38 master1 kubelet[28187]: I1123 15:56:38.363757 28187 kubelet_node_status.go:71] “Attempting to register node” node=“master1”

11月 23 15:56:38 master1 kubelet[28187]: E1123 15:56:38.364898 28187 kubelet_node_status.go:93] “Unable to register node with API server” err="Post \"https://lb.kubesphere.local:6443/api/v1/n

11月 23 15:56:38 master1 kubelet[28187]: E1123 15:56:38.368074 28187 kubelet.go:2456] “Error getting node” err="node \“master1\” not found"

11月 23 15:56:38 master1 kubelet[28187]: E1123 15:56:38.468242 28187 kubelet.go:2456] “Error getting node” err="node \“master1\” not found"

11月 23 15:56:38 master1 kubelet[28187]: E1123 15:56:38.569405 28187 kubelet.go:2456] “Error getting node” err="node \“master1\” not found"

11月 23 15:56:38 master1 kubelet[28187]: E1123 15:56:38.669670 28187 kubelet.go:2456] “Error getting node” err="node \“master1\” not found"

11月 23 15:56:38 master1 kubelet[28187]: E1123 15:56:38.770508 28187 kubelet.go:2456] “Error getting node” err="node \“master1\” not found"

11月 23 15:56:38 master1 kubelet[28187]: E1123 15:56:38.793973 28187 event.go:273] Unable to write event: '&v1.Event{TypeMeta:v1.TypeMeta{Kind:"“, APIVersion:”"}, ObjectMeta:v1.ObjectMeta{Nam

11月 23 15:56:38 master1 kubelet[28187]: E1123 15:56:38.871693 28187 kubelet.go:2456] “Error getting node” err="node \“master1\” not found"

11月 23 15:56:38 master1 kubelet[28187]: E1123 15:56:38.971917 28187 kubelet.go:2456] “Error getting node” err="node \“master1\” not found"

11月 23 15:56:39 master1 kubelet[28187]: E1123 15:56:39.072329 28187 kubelet.go:2456] “Error getting node” err="node \“master1\” not found"

11月 23 15:56:39 master1 kubelet[28187]: E1123 15:56:39.173417 28187 kubelet.go:2456] “Error getting node” err="node \“master1\” not found"

11月 23 15:56:39 master1 kubelet[28187]: I1123 15:56:39.189754 28187 cni.go:239] “Unable to update cni config” err=“no networks found in /etc/cni/net.d”

24sama

贴一下kk config文件内容呢，看日志应该是kubelet连不上kube-apiserver。看下是不是你的lb有问题

Lock

我这边是部署成功了，用了10分钟，然后pod就建不出来了，kubelet也报错

kubelet.go:2456] “Error getting node” err="node \“xxx\” not found"

xxx可以ping通

24sama

Lock
你这个问题应该是cni（比如 calico）的pod挂了还没起来

kevin-king

这个问题我也遇到了。可以先检查下/etc/hosts 是否有IP和主机名。另外如果使用config.yaml模板，注意kk3.3. 默认使用的容器运行时是containerd，需要调整下containerManager: docker。