This repo can be used to deploy OpenWhisk to a Kubernetes cluster. To accomplish this, we have created a Kubernetes job responsible for deploying OpenWhisk from inside of Kubernetes. This job runs through the OpenWhisk Ansible playbooks with some modifications to “Kube-ify” specific actions. The reason for this approach is to try and streamline a one size fits all way of deploying OpenWhisk.
Currently, the OpenWhisk deployment is going to be a static set of Kube yaml files. It should be easy to use the tools from this repo to build your own OpenWhisk deployment job, allowing you to set up your own configurations if need be.
The scripts and Docker images should be able to:
At this time, we are not sure as to the total number of resources required to deploy OpenWhisk On Kubernetes. Once all of the process are running in Pods we will be able to list those.
To deploy OpenWhisk on Kubernetes, you will need to target a Kubernetes environment. If you do not have one up and running, then you can look at the Local Kube Development section for setting one up. Once you are successfully targeted, you will need to create a create a namespace called openwhisk. To do this, you can just run the following command.
kubectl apply -f configure/openwhisk_kube_namespace.yml
From here, you should just need to run the Kubernetes job to setup the OpenWhisk environment.
kubectl apply -f configure/configure_whisk.yml
The Docker image responsible for deploying OpenWhisk can be built using following command:
docker build .
This image must then be re-tagged and pushed to a public docker repo. Currently, while this project is in development, the docker image is built and published here, until an official repo is set up. If you would like to change this image to one you created, then make sure to update the configure_whisk.yml with your image.
for Kubernets, all of the whisk images need to be public Docker files. For this, there is a helper script that will run gradle build for the main openwhisk repo and retag all of the images for a custom docker hub user.
Note: This scripts assumes that you already have push access to dockerhub, or some other repo and are already targeted. To do this, you will need to run the docker login command.
This script has 2 arguments:
The name of the dockerhub repo where the images will be published. For example:
docker/build.sh <danlavine>
will retage the whisk/invoker docker image built by gradle and publish it to danlavine/whisk_invoker.
(OPTIONAL) This argument is the location of the OpenWhisk repo. By default this repo is assumed to live at $HOME/workspace/openwhisk
The current Kube Deployment and Services files that define the OpenWhisk cluster can be found here. Only one instance of each OpenWhisk process is created, but if you would like to increase that number, then this would be the place to do it. Simply edit the appropriate file and rebuild the Docker File That Deploys OpenWhisk
There are a couple ways to bring up Kubernetes locally and currently we are using kubeadm with Callico for the network. By default kubeadm runs with Kube-DNS already enabled and the instructions will install a Kube version greater the v1.5. Using this deployment method everything is running on one host and nothing special has to be done for network configurations when communicating with Kube Pods.
When in the process of creating a new deployment, it is nice to run things by hand to see what is going on inside the container and not have it be removed as soon as it finishes or fails. For this, you can change the command of configure_whisk.yml to command: [ "tail", "-f", "/dev/null" ]. Then just run the original command from inside the Pod's container.
As part of the development process, you might need to cleanup the Kubernetes environment at some point. For this, we want to delete all the Kube deployments, services and jobs. For this, you can run the following script:
./kube_environment/cleanup.sh