创建部署问题时,请参考下面模板,你提供的信息越多,越容易及时获得解答。如果未按模板创建问题,管理员有权关闭问题。
确保帖子格式清晰易读,用 markdown code block 语法格式化代码块。
你只花一分钟创建的问题,不能指望别人花上半个小时给你解答。
操作系统信息
虚拟机 阿里云ECS,CentOS7.9 4C/8G
Kubernetes版本信息
将 kubectl version
命令执行结果贴在下方
v3.3.0中默认版本
容器运行时
将 docker version
/ crictl version
/ nerdctl version
结果贴在下方
v3.3.0中默认版本
KubeSphere版本信息
v3.3.0
部署概况
- 情况1:阿里云中使用一台堡垒机(同时使用nexus作为私有仓库),外带3台master节点,3台node节点,同时配置两台keepalive+haproxy作为负载均衡;
- 情况2:阿里云中使用一台堡垒机(同时使用nexus作为私有仓库),外带3台master节点,3台node节点,使用阿里云自有的SLB作为负载均衡安装。
目的:练习kubesphere离线安装
实施过程及关键报错
本人按照文档步骤,采用离线安装方法,结合阿里云ECS中的config.yaml中有关网络配置(增加IPIP和vxlan),进行安装,以下是安装工步打印报错部分:
[certs] Generating "sa" key and public key
[kubeconfig] Using kubeconfig folder "/etc/kubernetes"
[kubeconfig] Writing "admin.conf" kubeconfig file
[kubeconfig] Writing "kubelet.conf" kubeconfig file
[kubeconfig] Writing "controller-manager.conf" kubeconfig file
[kubeconfig] Writing "scheduler.conf" kubeconfig file
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Starting the kubelet
[control-plane] Using manifest folder "/etc/kubernetes/manifests"
[control-plane] Creating static Pod manifest for "kube-apiserver"
[control-plane] Creating static Pod manifest for "kube-controller-manager"
[control-plane] Creating static Pod manifest for "kube-scheduler"
[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
进入master节点使用journalctl -xeu kubelet 查看如下:
//
// journalctl -xeu kubelet
//
May 09 11:11:34 master1 kubelet[36412]: I0509 11:11:34.652279 36412 cni.go:239] "Unable to update cni config" err="no networks found in /etc/cni/net.d"
May 09 11:11:34 master1 kubelet[36412]: E0509 11:11:34.673546 36412 kubelet.go:2291] "Error getting node" err="node \"master1\" not found"
May 09 11:11:34 master1 kubelet[36412]: E0509 11:11:34.774040 36412 kubelet.go:2291] "Error getting node" err="node \"master1\" not found"
May 09 11:11:34 master1 kubelet[36412]: E0509 11:11:34.874304 36412 kubelet.go:2291] "Error getting node" err="node \"master1\" not found"
May 09 11:11:34 master1 kubelet[36412]: E0509 11:11:34.975123 36412 kubelet.go:2291] "Error getting node" err="node \"master1\" not found"
May 09 11:11:35 master1 kubelet[36412]: E0509 11:11:35.075761 36412 kubelet.go:2291] "Error getting node" err="node \"master1\" not found"
May 09 11:11:35 master1 kubelet[36412]: E0509 11:11:35.176588 36412 kubelet.go:2291] "Error getting node" err="node \"master1\" not found"
May 09 11:11:35 master1 kubelet[36412]: E0509 11:11:35.277089 36412 kubelet.go:2291] "Error getting node" err="node \"master1\" not found"
May 09 11:11:35 master1 kubelet[36412]: E0509 11:11:35.377595 36412 kubelet.go:2291] "Error getting node" err="node \"master1\" not found"
May 09 11:11:35 master1 kubelet[36412]: E0509 11:11:35.478240 36412 kubelet.go:2291] "Error getting node" err="node \"master1\" not found"
May 09 11:11:35 master1 systemd[1]: Stopping kubelet: The Kubernetes Node Agent...
-- Subject: Unit kubelet.service has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit kubelet.service has begun shutting down.
May 09 11:11:35 master1 kubelet[36412]: I0509 11:11:35.495745 36412 dynamic_cafile_content.go:182] Shutting down client-ca-bundle::/etc/kubernetes/pki/ca.crt
May 09 11:11:35 master1 systemd[1]: Stopped kubelet: The Kubernetes Node Agent.
-- Subject: Unit kubelet.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit kubelet.service has finished shutting down.
lines 956-1011/1011 (END)
备注