|
|
||
|---|---|---|
| .. | ||
| ha | ||
| 01-namespace.yaml | ||
| 02-serviceaccount.yaml | ||
| 03-clusterrole.yaml | ||
| 04-clusterrolebinding.yaml | ||
| 05-configmap.yaml | ||
| 07-deployment.yaml | ||
| 08-service.yaml.example | ||
| Dockerfile | ||
| README.md | ||
| README_zh.md | ||
Deploy the cloud part into a k8s cluster
This method will guide you to deploy the cloud part into a k8s cluster,
so you need to login to the k8s master node (or where else if you can
operate the cluster with kubectl).
The manifests and scripts in github.com/kubeedge/kubeedge/build/cloud
will be used, so place these files to somewhere you can kubectl with.
Prepare cloud image
Ensure your k8s cluster can pull edge controller image. If the image not exist. We can make one, and push to your registry.
cd $GOPATH/src/github.com/kubeedge/kubeedge
make image WHAT=cloudcore
Create secret(Optional)
For version lower than 1.3.0, we need to generate the tls certs and create
06-secret.yaml based on it.
cd build/cloud
../tools/certgen.sh buildSecret | tee ./06-secret.yaml
Configure IP addresses(Optional)
From KubeEdge 1.3.0, we can configure all the IP addresses of CloudCore which are exposed to the edge nodes(like floating IP) in the 05-configmap.yaml, which will be added to SANs in cert of cloudcore.
modules:
cloudHub:
advertiseAddress:
- 10.1.11.85
Update config
Based on 08-service.yaml.example, create your own service 08-service.yaml,
to expose cloud hub to outside of k8s cluster, so that edge core can
connect to.
Also check the content of each manifest to make sure it meets your environment.
Create cloud resources
Create k8s resources from the manifests in name order.
for resource in $(ls *.yaml); do kubectl create -f $resource; done