- GIT
- KUBECTL with right kubeconfig
- Kubernetes 1.16+ cluster running
- KubeEdge v.15+ running
GM will be deployed to a node which has satisfied these requirements:
- Has a IP address which the edge can access to.
Simply you can use the node which cloudcore
of kubeedge
is deployed at.
Currently we need to deploy GM to a k8s node which edge node can access to.
More specifically, the k8s node has a INTERNAL-IP or EXTERNAL-IP where edge node can access to.
For example, in a kind cluster kubectl get node -o wide
:
NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
edge-node Ready agent,edge 3d21h v1.19.3-kubeedge-v1.6.1 192.168.0.233 <none> Ubuntu 18.04.5 LTS 4.15.0-128-generic docker://20.10.2
sedna-control-plane Ready control-plane,master 3d21h v1.20.2 172.18.0.2 <none> Ubuntu 20.10 4.15.0-128-generic containerd://1.5.0-beta.3-24-g95513021e
In this example the node sedna-control-plane
has a internal-ip 172.18.0.2, and edge-node
can access it.
So we can set SEDNA_GM_NODE=sedna-control-plane
in below instructions:
# set the right node where edge node can be access
# SEDNA_GM_NODE=sedna-control-plane
SEDNA_GM_NODE=CHANGE-ME-HERE
curl https://raw.githubusercontent.com/kubeedge/sedna/main/scripts/installation/install.sh | SEDNA_GM_NODE=$SEDNA_GM_NODE bash -
1. Check the GM status:
kubectl get deploy -n sedna gm
2. Check the LC status:
kubectl get ds lc -n sedna
3. Check the pod status:
kubectl get pod -n sedna
# set the right node where edge node can be access
# SEDNA_GM_NODE=sedna-control-plane
SEDNA_GM_NODE=CHANGE-ME-HERE
curl https://raw.githubusercontent.com/kubeedge/sedna/main/scripts/installation/install.sh | SEDNA_GM_NODE=$SEDNA_GM_NODE SEDNA_ACTION=delete bash -