Edit invoker.env as needed to set the appropriate values for your deployment, then create the configmap invoker.config:
kubectl -n openwhisk create cm invoker.config --from-env-file=invoker.env
When deploying the Invoker, it needs to be deployed via a DaemonSet. This is because there should only ever be at most 1 Invoker instance per Kube Node. To set these restrictions, it will be up to the Kubernetes deployment operator to properly apply the correct labels and taints to each required Kube node.
With the defaults in the current invoker.yml, you can setup a
node to run only Invoker pods with:
kubectl label nodes [node name] openwhisk=invoker
$ kubectl label nodes 127.0.0.1 openwhisk=invoker
Once the invoker label is applied, you can create the invokers with:
kubectl apply -f invoker.yml
Important
OpenWhisk relies on part of the underlying infrastructure that Kube is running on. When deploying the Invoker for OpenWhisk, it mounts the hosts Docker socket and a number of other components. This way OpenWhisk can quickly provision actions and does not have to run Docker inside of Docker. However, this also means that a number of the default mount options assume that the Kubernetes host image is Ubuntu. During the deploy there could be an issue and if the Invoker fails to deploy, see the Troubleshooting section below.
Verify that you actually have nodes with the label openwhisk=invoker.
Unfortunately when Deploying OpenWhisk on Kubernetes it currently mounts some of the host OS files for the Invoker process and needs to make some assumptions. Because of this, some failures are known to happen on certain Linux versions, like CoreOs. If you see an error like:
Failed to start container with id 8d9125bf2d3711312a98a8b98de15306e495883cc470a03beb6689b34895791f with error: rpc error: code = 2 desc = failed to start container "8d9125bf2d3711312a98a8b98de15306e495883cc470a03beb6689b34895791f": Error response from daemon: {"message":"mkdir /usr/lib/x86_64-linux-gnu: read-only file system"}
Error syncing pod, skipping: failed to "StartContainer" for "Invoker" with rpc error: code = 2 desc = failed to start container "8d9125bf2d3711312a98a8b98de15306e495883cc470a03beb6689b34895791f": Error response from daemon: {"message":"mkdir /usr/lib/x86_64-linux-gnu: read-only file system"}: "Start Container Failed"
Then you might need to modify some of the volume mounts in the invoker.yml. For example, the error above is trying to find something from the apparmor mount which makes no sense to CoreOS. To fix the issue, you just need to remove the mount.