Installing Fission

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

Cluster preliminaries

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

If you cannot (or don’t want to) use Helm, there is an alternative installation method possible; see installing without Helm.

Kubernetes Cluster

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

Kubectl

Kubectl is a command line interface for running commands against Kubernetes clusters, visit here to see how to install it.

See how to setup config correctly on different platforms Next, ensure you have access to a cluster. Do this by using kubectl to check your Kubernetes version:

$ kubectl version

Helm

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

To install helm, first you’ll need the helm CLI. Visit here to see how to install it.

Next, install the Helm server on your Kubernetes cluster. Before you do that, you have to give helm’s server privileges to install software on your cluster.

For example, you can use the following steps to install helm using a dedicated service account with full cluster admin privileges.

$ kubectl create serviceaccount --namespace kube-system tiller
$ kubectl create clusterrolebinding tiller-cluster-rule \
    --clusterrole=cluster-admin --serviceaccount=kube-system:tiller
$ helm init --service-account tiller

Or, if your cluster is already set up with a permissive service account (this varies by version and how your Kubernetes was installed), you can simply do:

$ helm init

Install Fission

What version should I use: All vs Core

• fission-all (Recommend)

  • Install a full set of services including the NATS message queue, influxDB for logs, etc. and enable all Fission features. It’s suitable for people who want to try all the cool features Fission has and for companies that use features that don’t include in the core version.

• fission-core

  • Install core components for creating and serving a function.

Following, we will use fission-all to demonstrate how to install Fission.

List of all supported configurations for the charts fission-all and fission-core can be found here.

With Helm

Clusters without LoadBalancer support

The environment like Minikube that doesn’t support service type LoadBalancer should use NodePort instead. You can check it by creating a service with LoadBalancer type to see if it shows <pending> and never changes.

$ kubectl get svc
NAME                                    TYPE           CLUSTER-IP       EXTERNAL-IP   PORT(S)        AGE
router                                  LoadBalancer   10.109.61.85     <pending>     80:31972/TCP   25h

$ helm install --name fission --namespace fission \
    --set serviceType=NodePort,routerServiceType=NodePort \
    https://github.com/fission/fission/releases/download/1.11.0/fission-all-1.11.0.tgz

$ export FISSION_NAMESPACE="fission"
$ kubectl create namespace $FISSION_NAMESPACE
$ helm install --namespace $FISSION_NAMESPACE --name-template fission \
    https://github.com/fission/fission/releases/download/1.11.0/fission-all-1.11.0.tgz

$ helm install --name fission --namespace fission \
    --set serviceType=NodePort,routerServiceType=NodePort,logger.enableSecurityContext=true,prometheus.enabled=false \
    https://github.com/fission/fission/releases/download/1.11.0/fission-all-1.11.0.tgz

$ export FISSION_NAMESPACE="fission"
$ kubectl create namespace $FISSION_NAMESPACE
$ helm install --namespace $FISSION_NAMESPACE --name-template fission \
    --set serviceType=NodePort,routerServiceType=NodePort,logger.enableSecurityContext=true,prometheus.enabled=false \
    https://github.com/fission/fission/releases/download/1.11.0/fission-all-1.11.0.tgz

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, AKS, EKS)

See how to add token to kubeconfig if you’re not able to connect to cluster.

$ helm install --name fission --namespace fission \
    https://github.com/fission/fission/releases/download/1.11.0/fission-all-1.11.0.tgz

$ export FISSION_NAMESPACE="fission"
$ kubectl create namespace $FISSION_NAMESPACE
$ helm install --namespace $FISSION_NAMESPACE --name-template fission \
    https://github.com/fission/fission/releases/download/1.11.0/fission-all-1.11.0.tgz

$ helm install --name fission --namespace fission \
    --set logger.enableSecurityContext=true,prometheus.enabled=false \
    https://github.com/fission/fission/releases/download/1.11.0/fission-all-1.11.0.tgz

$ export FISSION_NAMESPACE="fission"
$ kubectl create namespace $FISSION_NAMESPACE
$ helm install --namespace $FISSION_NAMESPACE --name-template fission \
    --set logger.enableSecurityContext=true,prometheus.enabled=false \
    https://github.com/fission/fission/releases/download/1.11.0/fission-all-1.11.0.tgz

Without helm

This method uses kubectl apply to install Fission. You can edit the YAML file before applying it to your cluster, if you want to change anything in it. Create namespace for fission installation.

$ kubectl create namespace fission 

Choose one of the following commands to run:

• You can choose to use fission-all or fission-core. Here, we use fission-all to demonstrate the installation.

$ kubectl apply -f \
    https://github.com/fission/fission/releases/download/1.11.0/fission-all-1.11.0.yaml

$ kubectl apply -f \
    https://github.com/fission/fission/releases/download/1.11.0/fission-all-1.11.0-minikube.yaml

$ kubectl -n fission apply -f \
    https://github.com/fission/fission/releases/download/1.11.0/fission-core-1.11.0-openshift.yaml

Install Fission CLI

$ curl -Lo fission https://github.com/fission/fission/releases/download/1.11.0/fission-cli-osx \
    && chmod +x fission && sudo mv fission /usr/local/bin/

$ curl -Lo fission https://github.com/fission/fission/releases/download/1.11.0/fission-cli-linux \
    && chmod +x fission && sudo mv fission /usr/local/bin/

Run an example

Finally, you’re ready to use Fission!

$ fission env create --name nodejs --image fission/node-env:1.11.0

$ curl -LO https://raw.githubusercontent.com/fission/fission/master/examples/nodejs/hello.js

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

$ fission function test --name hello
Hello, world!

For more language tutorials, visit Language.

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.