云端安装k8环境之后,使用kubectl get nodes 发现master 节点不是running 而是ready
接着部署云端cloudcore 与 边端 edgecore
边端执行完 keadm join 之后 云端测试
接着测试example(kubeedge-counter 项目)
修改 kubeedge-counter-instance.yaml
验证 docker 镜像
云端
边端
云端执行 root@master:~/examples/kubeedge-counter-demo/crds# kubectl apply -f .
云端发现node状态还是ready
root@master:~/examples/kubeedge-counter-demo/crds# kubectl get node
NAME STATUS ROLES AGE VERSION
master Ready control-plane,master 16h v1.21.6
node1-edge Ready agent,edge 39m v1.19.3-kubeedge-v1.8.2
边端发现docker ps 并没有启动kubeedge-pi-counter这个镜像
root@node1-edge:~/jx_file# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
597f92203194 kubeedge/pause:3.1 “/pause” 20 minutes ago Up 20 minutes k8s_POD_kubeedge-pi-counter-68c86dc747-4k64k_default_33cff648-9ec4-43b1-bc5e-1c27aee61c51_0
2e7e3a36f8e3 registry.aliyuncs.com/google_containers/kube-proxy “/usr/local/bin/kube…” 41 minutes ago Up 41 minutes k8s_kube-proxy_kube-proxy-c6rlr_kube-system_5f6e3b07-ea5d-4a56-8257-6c9d5d08a6c5_0
a0382baf806c kubeedge/pause:3.1 “/pause” 41 minutes ago Up 41 minutes k8s_POD_kube-proxy-c6rlr_kube-system_5f6e3b07-ea5d-4a56-8257-6c9d5d08a6c5_0