A FaaS for Kubernetes
See Getting started on Minikube or Getting started on GKE for how to install riff with a Helm Chart, and how to install the riff CLI.
See Installing the riff development version using Helm to install the latest unreleased builds (git master branch) of riff.
This is the best option if you want to modify the riff components.
You need:
-
A working Go environment
-
A local 1.7+ Kubernetes cluster
-
A docker daemon
To build images with docker in minikube use
eval $(minikube docker-env)If you want to quickly standup a development copy of riff:
|
Note
|
Starting with with Minikube v0.26.0 the default for Minikube is to use the kubeadm bootstrapper which enables RBAC. The older localkube bootstrapper is now deprecated. The following instructions assume that your cluster is running with RBAC enabled. It is still possible to install riff without RBAC roles by omitting the rbac target from the make command.
|
make dev-setup rbacWhich will:
-
Create a
riff-systemnamespace -
Deploy a non-replicated Kafka broker
-
Install riff CRDs and system components
-
Create a riff service account
-
Install riff roles and rolebindings
Sample functions are typically found in the corresponding invoker repositories. See the projectriff invoker repositories for example.
To run all riff’s unit and integration tests, ensure Kafka (with auto.create.topics.enable=true, which
is the default) and Zookeeper are running locally, then issue:
KAFKA_BROKERS=localhost:9092 KAFKA_BROKER=localhost:9092 make testPlease refer to the Contributors' Guide.
Please refer to the Maintainers' Guide.