A local cluster is included for rapid prototyping, debugging and non-production work. Currently two local deployment options are available – Docker Desktop and Minikube. It is strongly advised to use Docker Desktop, since Minikube is only included for running integration tests.

Attention to resource handling is required when deploying a local kaos cluster since performance is directly linked to available isolated resources (within Docker).

It only takes approximately 1 minute to successfully deploy a local kaos cluster

Docker Desktop

A correctly running local kubernetes cluster is absolutely necessary prior to deploying kaos. The following steps are required before building kaos.

1) Local Kubernetes Cluster

A local kubernetes cluster within Docker Desktop must be enabled.

Docker Desktop does not enable a Kubernetes cluster by default

The following resource requirements are suggested for running the Quick Start locally.

2) Set Kubernetes Context

Kubernetes conveniently organizes groups of configuration parameters under a specific name, a context, in order to communicate with the desired cluster. Therefore, the correct cluster context associated with Docker Desktop needs to be set.

$ kubectl config current-context

Success! Kubernetes is set to communicate with Docker Desktop.

A successfully running local cluster with Docker Desktop will yield the following response.

$ kubectl get all
service/kubernetes ClusterIP <none> 443/TCP 2m

Lastly, a local kaos cluster with Docker Desktop is built and destroyed as follows.

kaos build deploy -c DOCKER -v
kaos destroy -c DOCKER -v


Only used for running integration tests - use Docker Desktop for deploying a local cluster

kaos can be built and destroyed within minikube with the following commands.

kaos build deploy -c MINIKUBE -v
kaos destroy -c MINIKUBE -v

The running kaos backend endpoint (via ambassador as an API gateway) can only be accessed after configuring the necessary port forwarding.

kubectl port-forward svc/ambassador 30123:80 &