| commit | e64daa1e8c8bea5e58229c3254407912fbcc20da | [log] [tgz] |
|---|---|---|
| author | David Grove <dgrove-oss@users.noreply.github.com> | Fri May 11 11:21:36 2018 -0400 |
| committer | Carlos Santana <csantanapr@apache.org> | Fri May 11 11:21:36 2018 -0400 |
| tree | 1119863c2c39d2b4bc1eaf1fd4e07ac3b6de2467 | |
| parent | d61f5ddf724b3d8828c76f7c5a2f5711c2ea0b65 [diff] |
Flatten and simplify Helm charts (#193)
This repository can be used to deploy OpenWhisk to a Kubernetes cluster.
Several requirements must be met for OpenWhisk to deploy on Kubernetes.
Kubernetes
hairpin-mode must not be none).For local development and testing, we recommend using Minikube with the docker network in promiscuous mode. Not all combinations of Minikube and Kubernetes versions will work for running OpenWhisk. Although other combinations may work, we recommend at least initially using a combination from the table below that is verified by our Travis CI testing.
| Kubernetes Version | Minikube Version |
|---|---|
| 1.7.4 | 0.23.0 |
| 1.8.0 | 0.25.2 |
| 1.9.0 | 0.25.2 |
For details on setting up Minikube, see these instructions.
You can also provision a Kubernetes cluster from a cloud provider, subject to the cluster meeting the requirements above.
The first time you deploy OpenWhisk on Kubernetes, we recommend following the steps below manually so you can inspect the results and debug your setup. After you are confident that OpenWhisk deploys smoothly on your cluster, you might find it useful to drive your deployments using the script build.sh that we use to deploy OpenWhisk on Kubernetes for our Travis CI testing.
Do one of the following:
To deploy OpenWhisk on Kubernetes, you must deploy its components in an order that respects their dependencies. Detailed instructions and the supporting configuration files can be found in the kubernetes directory tree. Follow the instructions for each step in order.
Your OpenWhisk installation should now be usable. You can test it by following these instructions to define and invoke a sample OpenWhisk action in your favorite programming language.
Note: if you installed self-signed certificates when you configured Nginx, you will need to use wsk -i to suppress certificate checking. This works around cannot validate certificate errors from the wsk CLI.
At some point there might be a need to cleanup the Kubernetes environment. For this, we want to delete all the OpenWhisk deployments, services, jobs and whatever else might be there. This is easily accomplished by deleting the openwhisk namespace and all persistent volumes labeled with pv-owner=openwhisk:
kubectl delete namespace openwhisk kubectl delete persistentvolume -lpv-owner=openwhisk
We are also working on developing Helm charts to deploy OpenWhisk on Kubernetes. Currently, the Helm charts do not support all of the configuration options of the more manual deployment process described above. However, they are sufficient for deploying the core OpenWhisk system on Minikube. Please see helm/README.md for more details.
Report bugs, ask questions and request features here on GitHub.
You can also join our slack channel and chat with developers. To get access to our slack channel, request an invite here.