Fission Installation Guide

Welcome! This guide will get you up and running with Fission on a Kubernetes cluster.

Cluster preliminaries

If you don’t have a Kubernetes cluster, here’s a quick guide to set one up.

Let’s ensure you have the Kubernetes CLI and Helm installed and ready. If you already have helm, skip ahead to the fission install.

Kubernetes CLI

Ensure you have the Kubernetes CLI.

You can get the Kubernetes CLI for OSX like this:

$ curl -LO$(curl -s && chmod +x kubectl && sudo mv kubectl /usr/local/bin

Or, for Linux:

$ curl -LO$(curl -s && chmod +x kubectl && sudo mv kubectl /usr/local/bin

Ensure you have access to a cluster; use kubectl to check your Kubernetes version:

$ kubectl version

We need at least Kubernetes 1.6 (older versions may work, but we don’t test them).


Helm is an installer for Kubernetes. If you already use helm, skip to the next section.

First, you’ll need the helm CLI:

On OS X:

$ curl -LO

$ tar xzf helm-v2.6.1-darwin-amd64.tar.gz

$ mv darwin-amd64/helm /usr/local/bin

On Linux:

$ curl -LO

$ tar xzf helm-v2.6.1-linux-amd64.tar.gz

$ mv linux-amd64/helm /usr/local/bin

Next, install the Helm server on your Kubernetes cluster:

$ kubectl -n kube-system create sa tiller

$ kubectl create clusterrolebinding tiller --clusterrole cluster-admin --serviceaccount=kube-system:tiller

$ helm init --service-account tiller

(The first two commands are there to make sure that helm is allowed to install stuff on Kubernetes, in the common case that your cluster has role-based access control.)

Install Fission


$ helm install --namespace fission --set serviceType=NodePort

The serviceType variable allows configuring the type of Kubernetes service outside the cluster. You can use ClusterIP if you don’t want to expose anything outside the cluster.

Cloud hosted clusters (GKE, AWS, Azure etc.)

$ helm install --namespace fission

Minimal version

The fission-all helm chart installs a full set of services including the NATS message queue, influxDB for logs, etc. If you want a more minimal setup, you can install the fission-core chart instead:

$ helm install --namespace fission

Install the Fission CLI


Get the CLI binary for Mac:

$ curl -Lo fission && chmod +x fission && sudo mv fission /usr/local/bin/


$ curl -Lo fission && chmod +x fission && sudo mv fission /usr/local/bin/


For Windows, you can use the linux binary on WSL. Or you can download this windows executable: fission.exe

Set environment vars

Set the FISSION_URL and FISSION_ROUTER environment variables. FISSION_URL is used by the fission CLI to find the server. (FISSION_ROUTER is only needed for the examples below to work.)


If you’re using minikube, use these commands:

  $ export FISSION_URL=http://$(minikube ip):31313
  $ export FISSION_ROUTER=$(minikube ip):31314

Cloud setups

Save the external IP addresses of controller and router services in FISSION_URL and FISSION_ROUTER, respectively. Wait for services to get IP addresses (check this with kubectl --namespace fission get svc). Then:

  $ export FISSION_URL=http://$(kubectl --namespace fission get svc controller -o=jsonpath='{..ip}')
  $ export FISSION_ROUTER=$(kubectl --namespace fission get svc router -o=jsonpath='{..ip}')

Run an example

Finally, you’re ready to use Fission!

$ fission env create --name nodejs --image fission/node-env:v0.2.1

$ curl -LO

$ fission function create --name hello --env nodejs --code hello.js

$ fission route create --method GET --url /hello --function hello

$ curl http://$FISSION_ROUTER/hello
Hello, world!

What’s next?

If something went wrong, we’d love to help – please drop by the slack channel and ask for help.

Check out the examples for some example functions.