github.com/midokura/kubeedge@v1.2.0-mido.0/build/edge/kubernetes/README.md (about) 1 ## Deploy the edge part into a k8s cluster 2 3 This method will guide you to deploy the edge part into a k8s cluster, 4 so you need to login to the k8s master node (or where else if you can 5 operate the cluster with `kubectl`). 6 7 The manifests and scripts in `github.com/kubeedge/kubeedge/build/edge/kubernetes` 8 will be used, so place these files to somewhere you can kubectl with. 9 10 First, ensure your k8s cluster can pull edge core image. If the 11 image not exist. We can make one, and push to your registry. 12 13 - Check the container runtime environment 14 15 ```bash 16 cd $GOPATH/src/github.com/kubeedge/kubeedge/build/edge 17 ./run_daemon.sh prepare 18 ``` 19 20 - Build edge core image 21 22 ```bash 23 cd $GOPATH/src/github.com/kubeedge/kubeedge 24 make edgeimage 25 ``` 26 27 We create k8s resources from the manifests in name order. Before 28 creating, check the content of each manifest to make sure it meets your 29 environment. 30 31 Firstly you need to copy edge certs including `edge.crt` and `edge.key` into the folder 32 `/etc/kubeedge/certs/` on the k8s nodes where you want to deploy edge part. 33 34 On the other side, you need to replace `0.0.0.0:10000` with your kubeedge cloud web socket url. 35 * [url](03-configmap-edgenodeconf.yaml#L20) 36 37 The default edge node name is `edgenode1`, 38 if you want to change edge node name or add new edge node, 39 you need to replace the following places with your new edge node name. 40 41 * [name in 02-edgenode.yaml](02-edgenode.yaml#L4) 42 * [url in 03-configmap-edgenodeconf.yaml](03-configmap-edgenodeconf.yaml#L20) 43 * [node-id in 03-configmap-edgenodeconf.yaml](03-configmap-edgenodeconf.yaml#L33) 44 * [hostname-override in 03-configmap-edgenodeconf.yaml](03-configmap-edgenodeconf.yaml#L36) 45 * [name in 04-deployment-edgenode.yaml](04-deployment-edgenode.yaml#L4) 46 47 ```bash 48 for resource in $(ls *.yaml); do kubectl create -f $resource; done 49 ```