请问可以在银河麒麟V10环境部署KubeSphere吗?谢谢!
KubeKey 离线环境部署 KubeSphere v3.0.0
我在部署离线部署kubesphere时,碰见一下这个报错,请问有人遇到过吗,怎么解决的,谢谢~
1 个月 后
- 已编辑
centos 7.8 systemctl stop firewalld && systemctl disable firewalld 得关闭防火墙。。。 不然etcd
etcd无法建立连接
Waiting for etcd to start
Waiting for etcd to start
Waiting for etcd to start
Waiting for etcd to start
Waiting for etcd to start
Waiting for etcd to start
Waiting for etcd to start
Waiting for etcd to start
Waiting for etcd to start
Waiting for etcd to start
Waiting for etcd to start
Waiting for etcd to start
Waiting for etcd to start
ERRO[23:42:24 CST] Failed to start etcd cluster: Failed to exec command: sudo -E /bin/sh -c "export ETCDCTL_API=2;export ETCDCTL_CERT_FILE='/etc/ssl/etcd/ssl/admin-lisen-master01.pem';export ETCDCTL_KEY_FILE='/etc/ssl/etcd/ssl/admin-lisen-master01-key.pem';export ETCDCTL_CA_FILE='/etc/ssl/etcd/ssl/ca.pem';/usr/local/bin/etcdctl --endpoints=https://172.19.70.80:2379,https://172.19.70.81:2379,https://172.19.70.82:2379 cluster-health | grep -q 'cluster is healthy'"
Error: client: etcd cluster is unavailable or misconfigured; error #0: dial tcp 172.19.70.82:2379: connect: no route to host
; error #1: client: endpoint https://172.19.70.80:2379 exceeded header timeout
; error #2: dial tcp 172.19.70.81:2379: connect: no route to host
error #0: dial tcp 172.19.70.82:2379: connect: no route to host
error #1: client: endpoint https://172.19.70.80:2379 exceeded header timeout
error #2: dial tcp 172.19.70.81:2379: connect: no route to host: Process exited with status 1 node=172.19.70.80
Waiting for etcd to start
ERRO[23:42:27 CST] Failed to start etcd cluster: Failed to exec command: sudo -E /bin/sh -c "export ETCDCTL_API=2;export ETCDCTL_CERT_FILE='/etc/ssl/etcd/ssl/admin-lisen-master03.pem';export ETCDCTL_KEY_FILE='/etc/ssl/etcd/ssl/admin-lisen-master03-key.pem';export ETCDCTL_CA_FILE='/etc/ssl/etcd/ssl/ca.pem';/usr/local/bin/etcdctl --endpoints=https://172.19.70.80:2379,https://172.19.70.81:2379,https://172.19.70.82:2379 cluster-health | grep -q 'cluster is healthy'"
Error: client: etcd cluster is unavailable or misconfigured; error #0: dial tcp 172.19.70.80:2379: connect: no route to host
; error #1: dial tcp 172.19.70.81:2379: connect: no route to host
; error #2: client: endpoint https://172.19.70.82:2379 exceeded header timeout
error #0: dial tcp 172.19.70.80:2379: connect: no route to host
error #1: dial tcp 172.19.70.81:2379: connect: no route to host
error #2: client: endpoint https://172.19.70.82:2379 exceeded header timeout: Process exited with status 1 node=172.19.70.82
Waiting for etcd to start
ERRO[23:42:31 CST] Failed to start etcd cluster: Failed to exec command: sudo -E /bin/sh -c "export ETCDCTL_API=2;export ETCDCTL_CERT_FILE='/etc/ssl/etcd/ssl/admin-lisen-master02.pem';export ETCDCTL_KEY_FILE='/etc/ssl/etcd/ssl/admin-lisen-master02-key.pem';export ETCDCTL_CA_FILE='/etc/ssl/etcd/ssl/ca.pem';/usr/local/bin/etcdctl --endpoints=https://172.19.70.80:2379,https://172.19.70.81:2379,https://172.19.70.82:2379 cluster-health | grep -q 'cluster is healthy'"
Error: client: etcd cluster is unavailable or misconfigured; error #0: dial tcp 172.19.70.80:2379: connect: no route to host
; error #1: client: endpoint https://172.19.70.81:2379 exceeded header timeout
; error #2: dial tcp 172.19.70.82:2379: connect: no route to host
error #0: dial tcp 172.19.70.80:2379: connect: no route to host
error #1: client: endpoint https://172.19.70.81:2379 exceeded header timeout
error #2: dial tcp 172.19.70.82:2379: connect: no route to host: Process exited with status 1 node=172.19.70.81
WARN[23:42:31 CST] Task failed ...
WARN[23:42:31 CST] error: interrupted by error
Error: Failed to refresh etcd configuration: interrupted by error
Usage:
kk create cluster [flags]
Flags:
-f, --filename string Path to a configuration file
-h, --help help for cluster
--skip-pull-images Skip pre pull images
--with-kubernetes string Specify a supported version of kubernetes
--with-kubesphere Deploy a specific version of kubesphere (default v3.0.0)
-y, --yes Skip pre-check of the installation
Global Flags:
--debug Print detailed information (default true)
Failed to refresh etcd configuration: interrupted by error
在这提几点建议:
1、每台机器手动去 关防火墙也是件麻烦事,不能自动做了?
2、离线包 导了很多 无关东西,时间太久了 k8s版本都好几个了,是不是可以做下判断。。。没开启的插件相关是不是可以选择不导入?
3、bash-completion 安装也加下 不能tab也头痛
可以在2.1.1的基础上直接升级至3.0吗?
JeffK零SK壹S
- 已编辑
zhq5101 应该是完成兼容认证了
12 天 后
请问怎么指定docker和kubelet的目录, 能不能在config文件中指定?
10 天 后
这个离线包完全跑步起来啊,一直找8080端口apiserver的,但是apiserver不是8080端口啊
FeynmanK零SK贰SK壹S
matthew 先关闭防火墙再安装吧,另外,官方文档可以参考 https://kubesphere.com.cn/docs/installing-on-linux/introduction/air-gapped-installation/
Tip: 论坛的文章仅作为实验性参考
Jeff 锁定此帖
7 个月 后
Feynman 取消置顶