|
| 1 | +This guide covers how to install Sedna on existing KubeEdge environment, i.e. its two main components: [GM(GlobalManager)](/README.md#globalmanager) and [LC(LocalController)](/README.md#localcontroller). |
| 2 | + |
1 | 3 | ### Prerequisites
|
2 | 4 | - [Kubectl][kubectl] with right kubeconfig
|
3 | 5 | - [Kubernetes][kubernetes] 1.16+ cluster running
|
4 |
| -- [KubeEdge][kubeedge] v.15+ running |
5 |
| - |
6 |
| -GM will be deployed to a node which has satisfied these requirements: |
7 |
| -1. Has a IP address which the edge can access to. |
| 6 | +- [KubeEdge][kubeedge] v1.5+ running |
8 | 7 |
|
9 |
| -Simply you can use the node which `cloudcore` of `kubeedge` is deployed at. |
10 | 8 |
|
11 | 9 | #### Deploy Sedna
|
12 | 10 |
|
13 |
| -Currently we need to deploy GM to a k8s node which edge node can access to. |
| 11 | +Currently GM is deployed as a [`deployment`][deployment], and LC is deployed as a [`daemonset`][daemonset]. |
| 12 | + |
| 13 | +Because LC needs to connnect to GM, and the limit connection between cloud `Pod` and edge `Pod`, GM will be deployed to a cloud node where the edge node can access to. |
14 | 14 |
|
15 |
| -More specifically, the k8s node has a INTERNAL-IP or EXTERNAL-IP where edge node can access to. |
| 15 | +More specifically, the GM node has a INTERNAL-IP or EXTERNAL-IP where edge node can access to directly. |
16 | 16 |
|
17 | 17 | For example, in a kind cluster `kubectl get node -o wide`:
|
18 | 18 | ```shell
|
@@ -69,3 +69,5 @@ curl https://raw.githubusercontent.com/kubeedge/sedna/main/scripts/installation/
|
69 | 69 | [kubectl]:https://kubernetes.io/docs/tasks/tools/install-kubectl-linux/#install-kubectl-binary-with-curl-on-linux
|
70 | 70 | [kubeedge]:https://github.com/kubeedge/kubeedge
|
71 | 71 | [kubernetes]:https://kubernetes.io/
|
| 72 | +[deployment]: https://kubernetes.io/docs/concepts/workloads/controllers/deployment/ |
| 73 | +[daemonset]: https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/ |
0 commit comments