按照教程安装k8s version1.31.1 ,kubesphere4.1.2, kubeedge采用 1.31.1版本 。
部署情况是， 两台腾讯云ecs。内网互通有独立ip。
边缘采用实验室环境， 办公室网络没有固定ip， 网络配置也是内网ip 192.168.0.151
目前的问题是云端对边缘网络不通，无法通过kubectl logs 命令获取边缘端日志，如下图所示
边缘端calico-node无法启动
边缘节点加入后，网络不通。
补充一下kubesphere内的。截图
感谢提问
这个问题可以根据文档：https://kubesphere.io/zh/blogs/kubesphere-integrate-kubeedge/，边缘环境并不适合使用calico这样的组件，建议使用edgemesh来进行云边通信。
zuoxuesong 感谢回复， 我使用应用商店安装的edgemesh，还是存在不同的情况，这里有两个现象。
edgemesh-agent 容器并没有部署在edge边缘侧，反倒是work节点还有edgemesh容器
开启了edgemesh后， 监控没以后了数据
调度至工作节点的原因，是因为这个
- 已编辑
zuoxuesong 按照这个流程操作了，目前的情况是我的edgenode上只有一个edgemesh了，并且还是无法做云边通信。解释下下面的内容。 第一个图是我无法获取到边端上的日志。第二个图是按照上边的操作，执行了bash.sh后，我的edge节点失去了所有容器， 安装edgemesh后，只剩下edgemesh节点了。 之后我部署了个ngxin，但是无法跟nginx通信。
root@controlplane1:/home/ubuntu# kubectl logs nginx-8cd6f5f76-wx89k -n edge
Error from server: Get "https://192.168.1.155:10351/containerLogs/edge/nginx-8cd6f5f76-wx89k/container-uanjur": dial tcp 192.168.1.155:10351: i/o timeoutroot@controlplane1:/home/ubuntu# kubectl get pods -A -owide
edge helm-executor-install-edgemesh-abcvzl5cf3f-l4gzss-rh7lg 0/1 Completed 0 3h56m 10.233.96.28 node2 <none> <none>
edge nginx-8cd6f5f76-wx89k 1/1 Running 0 119m 10.88.0.10 edgenode-chlq <none> <none>
extension-metrics-server helm-executor-install-metrics-server-agent-pr7f92-b7zcp 0/1 Completed 0 3h28m 10.233.96.48 node2 <none> <none>
extension-metrics-server helm-executor-install-metrics-server-wjmxjb-5j69p 0/1 Completed 0 3h28m 10.233.96.47 node2 <none> <none>
extension-metrics-server metrics-server-8877fd5b5-zchct 1/1 Running 0 3h28m 10.233.96.49 node2 <none> <none>
extension-openpitrix helm-executor-install-openpitrix-shznmd-zdhbh 0/1 Completed 0 15h 10.233.96.17 node2 <none> <none>
extension-openpitrix openpitrix-apps-5f4499c7b7-vt54k 1/1 Running 0 15h 10.233.96.18 node2 <none> <none>
extension-whizard-telemetry helm-executor-install-whizard-telemetry-965tvg-wxrf8 0/1 Completed 0 15h 10.233.96.7 node2 <none> <none>
extension-whizard-telemetry whizard-telemetry-apiserver-5c68b6fd7c-hkkmn 1/1 Running 0 15h 10.233.96.8 node2 <none> <none>
kube-system calico-kube-controllers-55c67cb6cd-s7fws 1/1 Running 0 16h 10.233.96.1 node2 <none> <none>
kube-system calico-node-2djhk 1/1 Running 0 3h40m 172.21.32.4 controlplane1 <none> <none>
kube-system calico-node-xxcnq 1/1 Running 0 3h40m 172.21.32.13 node2 <none> <none>
kube-system coredns-5fd5f66546-hdjrg 1/1 Running 0 16h 10.233.96.2 node2 <none> <none>
kube-system coredns-5fd5f66546-vvmpp 1/1 Running 0 16h 10.233.96.3 node2 <none> <none>
kube-system kube-apiserver-controlplane1 1/1 Running 0 16h 172.21.32.4 controlplane1 <none> <none>
kube-system kube-controller-manager-controlplane1 1/1 Running 0 16h 172.21.32.4 controlplane1 <none> <none>
kube-system kube-proxy-b28bl 1/1 Running 0 3h40m 172.21.32.13 node2 <none> <none>
kube-system kube-proxy-bp4v5 1/1 Running 0 3h40m 172.21.32.4 controlplane1 <none> <none>
kube-system kube-scheduler-controlplane1 1/1 Running 0 16h 172.21.32.4 controlplane1 <none> <none>
kube-system nodelocaldns-rmr4w 1/1 Running 0 3h40m 172.21.32.13 node2 <none> <none>
kube-system nodelocaldns-xtgtn 1/1 Running 0 3h40m 172.21.32.4 controlplane1 <none> <none>
kubeedge cloud-iptables-manager-lvq4m 1/1 Running 0 15h 172.21.32.13 node2 <none> <none>
kubeedge cloudcore-758686898f-csfdv 1/1 Running 0 15h 10.233.96.21 node2 <none> <none>
kubeedge edgemesh-abcvzl5cf3f-agent-g758q 1/1 Running 0 3h23m 192.168.1.155 edgenode-chlq <none> <none>
kubeedge edgemesh-abcvzl5cf3f-agent-s5z9c 1/1 Running 0 3h56m 172.21.32.13 node2 <none> <none>
kubeedge edgemesh-abcvzl5cf3f-server-5cb7687d47-x9d5t 1/1 Running 0 3h56m 172.21.32.13 node2 <none> <none>
kubeedge helm-executor-install-kubeedge-sjjqzv-rldtt 0/1 Completed 0 15h 10.233.96.19 node2 <none> <none>
kubeedge kubeedge-proxy-9dd44848-mzh2q 1/1 Running 0 15h 10.233.96.20 node2 <none> <none>
kubesphere-logging-system helm-executor-install-vector-4xhd2r-ptkkz 0/1 Completed 0 3h48m 10.233.96.36 node2 <none> <none>
kubesphere-logging-system helm-executor-install-vector-agent-nnlzcj-bfp5p 0/1 Completed 0 3h45m 10.233.96.43 node2 <none> <none>
kubesphere-logging-system vector-agent-xl5l5 2/2 Running 0 3h45m 10.233.96.46 node2 <none> <none>
kubesphere-logging-system vector-agent-zt5w7 2/2 Running 0 3h45m 10.233.110.5 controlplane1 <none> <none>
kubesphere-logging-system vector-aggregator-0 2/2 Running 0 3h46m 10.233.96.42 node2 <none> <none>
kubesphere-monitoring-system helm-executor-install-whizard-monitoring-agent-7l9b2j-w8ncr 0/1 Completed 0 3h48m 10.233.96.32 node2 <none> <none>
kubesphere-monitoring-system helm-executor-install-whizard-monitoring-s8hkrl-r92gk 0/1 Completed 0 3h48m 10.233.96.31 node2 <none> <none>
kubesphere-monitoring-system kube-state-metrics-5f7d7848f7-lwk88 3/3 Running 0 3h48m 10.233.96.34 node2 <none> <none>
kubesphere-monitoring-system node-exporter-9wnrg 2/2 Running 0 3h48m 172.21.32.4 controlplane1 <none> <none>
kubesphere-monitoring-system node-exporter-phbrb 2/2 Running 0 3h48m 172.21.32.13 node2 <none> <none>
kubesphere-monitoring-system prometheus-k8s-0 2/2 Running 0 3h47m 10.233.96.39 node2 <none> <none>
kubesphere-monitoring-system prometheus-operator-6df549d644-l8lfx 1/1 Running 0 3h48m 10.233.96.35 node2 <none> <none>
kubesphere-system extensions-museum-84dd6f4db6-kxfl4 1/1 Running 0 14h 10.233.96.24 node2 <none> <none>
kubesphere-system ks-apiserver-7dcdb6779d-6smqf 1/1 Running 0 16h 10.233.110.2 controlplane1 <none> <none>
kubesphere-system ks-console-5c8686bf46-dzn77 1/1 Running 2 (15h ago) 16h 10.233.110.3 controlplane1 <none> <none>
kubesphere-system ks-controller-manager-669cbbb67c-569fc 1/1 Running 0 16h 10.233.110.1 controlplane1 <none> <none>
kubesphere-system restart-extensions-museum-28885920-qw4hb 0/1 Completed 0 14h 10.233.96.23 node2 <none> <none>
1 个月 后
如果您这边安装edgemesh是通过应用商店相关指引安装的话，请务必要注意安装的edgemesh-agent和edgemesh-server的镜像版本。商店内安装默认版本号是latest，这边建议是修改为1.9.0然后再重试一下