macOs 使用kk部署单节点集群问题

SxunS · 2021年1月15日

** 操作系统信息：
物理机：Macbook/Big sur 8c/32G

** Kubernetes版本信息:
单节点，当前kubekey默认安装的版本(v1.17.9)

** KubeSphere版本信息 v3.0.0。

问题：
使用./kk create cluster 创建单节点集群时，无法连接到 192.168.8.126

src/kubekey [ sudo ./kk create cluster                                                          master * ] 12:10 下午
Password:
ERRO[12:19:17 CST] Failed to connect to 192.168.8.162: could not establish connection to 192.168.8.162:22: dial tcp 192.168.8.162:22: connect: connection refused  node=192.168.8.162
WARN[12:19:17 CST] Task failed ...
WARN[12:19:17 CST] error: interrupted by error
Error: Failed to precheck: 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 (default "v1.17.9")
      --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)
      --in-cluster   Running inside the cluster

Failed to precheck: interrupted by error

当前机器网络情况

src/kubekey [ ifconfig                                                                          master * ] 12:19 下午
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
	options=1203<RXCSUM,TXCSUM,TXSTATUS,SW_TIMESTAMP>
	inet 127.0.0.1 netmask 0xff000000
	inet6 ::1 prefixlen 128
	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
	nd6 options=201<PERFORMNUD,DAD>
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
XHC0: flags=0<> mtu 0
XHC1: flags=0<> mtu 0
XHC20: flags=0<> mtu 0
VHC128: flags=0<> mtu 0
en5: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	ether ac:de:48:00:11:22
	inet6 fe80::aede:48ff:fe00:1122%en5 prefixlen 64 scopeid 0x8
	nd6 options=201<PERFORMNUD,DAD>
	media: autoselect (100baseTX <full-duplex>)
	status: active
en1: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
	options=460<TSO4,TSO6,CHANNEL_IO>
	ether 82:25:2b:e8:5c:01
	media: autoselect <full-duplex>
	status: inactive
en2: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
	options=460<TSO4,TSO6,CHANNEL_IO>
	ether 82:25:2b:e8:5c:00
	media: autoselect <full-duplex>
	status: inactive
en3: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
	options=460<TSO4,TSO6,CHANNEL_IO>
	ether 82:25:2b:e8:5c:05
	media: autoselect <full-duplex>
	status: inactive
en4: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
	options=460<TSO4,TSO6,CHANNEL_IO>
	ether 82:25:2b:e8:5c:04
	media: autoselect <full-duplex>
	status: inactive
ap1: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
	options=400<CHANNEL_IO>
	ether 3a:f9:d3:de:a8:7c
	media: autoselect
	status: inactive
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	options=400<CHANNEL_IO>
	ether 38:f9:d3:de:a8:7c
	inet6 fe80::1895:7933:ee98:3a48%en0 prefixlen 64 secured scopeid 0xe
	inet6 240e:46d:3440:324b:100d:5f23:d4fa:f846 prefixlen 64 autoconf secured
	inet6 240e:46d:3440:324b:2d99:ae51:1a3a:a792 prefixlen 64 autoconf temporary
	inet6 fd5c:c307:ca39:8e00:1ca9:e573:7438:45db prefixlen 64 autoconf secured
	inet6 fd5c:c307:ca39:8e00:98ab:1ab7:40c2:5be3 prefixlen 64 autoconf temporary
	inet6 240e:46d:3440:324b:5cc3:7ca:398e:2 prefixlen 64 dynamic
	inet 192.168.8.162 netmask 0xffffff00 broadcast 192.168.8.255
	nd6 options=201<PERFORMNUD,DAD>
	media: autoselect
	status: active
awdl0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
	options=400<CHANNEL_IO>
	ether 62:53:e2:35:30:78
	inet6 fe80::6053:e2ff:fe35:3078%awdl0 prefixlen 64 scopeid 0xf
	nd6 options=201<PERFORMNUD,DAD>
	media: autoselect
	status: active
llw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	options=400<CHANNEL_IO>
	ether 62:53:e2:35:30:78
	inet6 fe80::6053:e2ff:fe35:3078%llw0 prefixlen 64 scopeid 0x10
	nd6 options=201<PERFORMNUD,DAD>
	media: autoselect
	status: active
bridge0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	options=63<RXCSUM,TXCSUM,TSO4,TSO6>
	ether 82:25:2b:e8:5c:01
	Configuration:
		id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
		maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
		root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
		ipfilter disabled flags 0x0
	member: en1 flags=3<LEARNING,DISCOVER>
	        ifmaxaddr 0 port 9 priority 0 path cost 0
	member: en2 flags=3<LEARNING,DISCOVER>
	        ifmaxaddr 0 port 10 priority 0 path cost 0
	member: en3 flags=3<LEARNING,DISCOVER>
	        ifmaxaddr 0 port 11 priority 0 path cost 0
	member: en4 flags=3<LEARNING,DISCOVER>
	        ifmaxaddr 0 port 12 priority 0 path cost 0
	nd6 options=201<PERFORMNUD,DAD>
	media: <unknown type>
	status: inactive
utun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380
	inet6 fe80::16c8:3b09:708c:f455%utun0 prefixlen 64 scopeid 0x12
	nd6 options=201<PERFORMNUD,DAD>
utun1: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 2000
	inet6 fe80::56f2:a96:8225:1080%utun1 prefixlen 64 scopeid 0x13
	nd6 options=201<PERFORMNUD,DAD>
utun2: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380
	inet6 fe80::47ca:14fb:9425:cf8f%utun2 prefixlen 64 scopeid 0x14
	nd6 options=201<PERFORMNUD,DAD>
utun3: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380
	inet6 fe80::82f:73bd:7f8d:17f1%utun3 prefixlen 64 scopeid 0x15
	nd6 options=201<PERFORMNUD,DAD>
utun4: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380
	inet6 fe80::603f:1916:94cb:24d5%utun4 prefixlen 64 scopeid 0x16
	nd6 options=201<PERFORMNUD,DAD>
utun5: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380
	inet6 fe80::b49b:9eff:c095:a16b%utun5 prefixlen 64 scopeid 0x17
	nd6 options=201<PERFORMNUD,DAD>
utun6: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380
	inet6 fe80::ac21:2954:dbed:9a37%utun6 prefixlen 64 scopeid 0x18
	nd6 options=201<PERFORMNUD,DAD>

Forest-L · 2021年1月15日

SxunS 执行脚本的机器ssh 连不上192.168.8.162 这台机器
手动ssh试下。

SxunS · 2021年1月15日

Forest-L
Failed to load kube binaries: Failed to check SHA256 of /Users/lee/go/src/kubekey/output/kubekey/v1.17.9/amd64/kubeadm: exit status 127 能帮忙看下这个是什么问题吗？

环境如上所示。

SxunS · 2021年1月15日

我知道是文件完整性校验没给过，但是我试了很多次，每次都是这样。代理也挂了，还是没有用…….

Feynman · 2021年1月16日

SxunS Hi，还是第一次见有用户在 MacOS BigSur 安装的。

你下载的 kk 可以参考安装文档尝试用这样的方式下载：

第二，我看表格里还有 5 项依赖你没安装，建议把这些依赖也安装上，文档中也有说明。

SxunS · 2021年1月17日

Feynman
感谢回复

我是看了你们B站的前后端讲解的那个视频，感觉很有意思，打算本地先装下环境，熟悉下开发环境，希望以后能为社区做点贡献。

我还以为社区的开发者们都会在本地有一套开发环境呢。如果用的是苹果系统，在本地使用kk装一个本地环境不是很正常吗？为什么我会是第一个尝试在mac 上安装 kubesphere 的啊 o(╥﹏╥)o

Feynman · 2021年1月17日

SxunS 哈哈，有心了~ 由于 Kubernetes 不支持 Mac 上运行，所以kk不支持 MacOS 安装(官方还没有测试过)。那个视频是用 minikube 演示的，你可以用 minikube 或 kind 在本地先安装一个 K8s，然后再在 K8s 上面安装 KubeSphere

Feynman · 2021年1月17日

SxunS 还有用 Docker Desktop 起本地 K8s 然后安装 KubeSphere 的开发者，不过他是用 KubeSphere 2.1.1 作为安装演示： https://kubesphere.com.cn/forum/d/495-macos-ks-installer-kubesphere

macOs 使用kk部署单节点集群问题

SxunS

Forest-LK零S

SxunS

SxunS

FeynmanK零SK贰SK壹S

SxunS

FeynmanK零SK贰SK壹S

FeynmanK零SK贰SK壹S