kubeless/README.md

35 lines
1.8 KiB
Markdown
Raw Normal View History

2019-03-05 18:33:23 +01:00
# Kubernetes Cluster Deployer and Withdrawer
---
2019-04-17 16:11:27 +02:00
## Available CNI plugins
2019-03-05 18:33:23 +01:00
* Calico
* Cilium
* Flannel
* WeawNet
---
## User's Manual
### Preparations
The commands must be run as root on the (future) master node. The SSH-key of the master node must be uploaded on the worker node for root, so it can run seamlessly.
Create a `worker.list` file and add the hostname or the IP address of the worker nodes in it line-by-line as you can see in the example file.
2019-04-03 12:14:11 +02:00
Create a `docker.version` file containing the desired version of the docker package you would like to deploy, or alternatively run the `package-latest` command, which will create this file for you.
2019-04-03 12:11:38 +02:00
2019-04-03 12:14:41 +02:00
Create a `kubernetes.version` file containing the desired version of the kubernetes package you would like to deploy, or alternatively run the `./package-latest` command, which will create this file for you.
2019-04-03 12:11:38 +02:00
2019-03-05 18:33:23 +01:00
### Deploying Kubernetes Cluster
To install the cluster run the `./cluster-deploy <CNI>` command. A Kubernetes CNI plugin name must be given as an argument. If you give the word `help` as an argument, you will get the available CNI plugins.
### Withdraw Kubernetes Cluster
To undo the cluster installation run the `./cluster-withdraw` command and it will clean up the configurations on all nodes including the master as well. Command will purge all Kubernetes setups from nodes enlisted in the `worker.list` file!
2019-04-02 23:40:17 +02:00
### Deploy function to kubeless
2019-04-02 23:52:58 +02:00
To deploy a function to kubeless run the `./function/deploy_function.sh <RUNTIME> <FILENAME> <FUNCTION NAME> <HANDLER NAME>` command with the appropriate parameters. You need to have the function available in a file next to the script.
2019-03-05 18:33:23 +01:00
2019-04-02 23:40:17 +02:00
### Benchmark the cluster
Benchmarking is pretty turnkey. Edit the appropriate variables in `./benchmark/benchmark.sh` file, then run it!