Cluster Setup


Lightbend Orchestration is no longer actively developed and will reach its End of Life on April 15, 2020.

We recommend Migrating to the Improved Kubernetes Deployment Experience.


When deploying to Kubernetes, you’ll first need to setup your Kubernetes cluster. Below, you’ll find information on how to do this on your own local cluster, Minikube, as well as IBM’s Cloud offerings. If you have access to a different Kubernetes environment, ensure that you’ve setup kubectl and docker to point at your cluster and docker registry.


Minikube provides a way for you to run a local Kubernetes cluster for development purposes. The command below will reset your Minikube and ensure that kubectl and docker can communicate with it.

Reset your Minikube (Optional)

If you wish to start with a fresh Minikube, run the command below. This will remove your existing Minikube and all of its data.

minikube delete

Start Minikube

macOS / Linux
minikube start
eval $(minikube docker-env)
minikube start
minikube docker-env | Invoke-Expression

IBM Cloud

IBM Cloud offers Kubernetes clusters that can be used in production environments. To use your IBM Cloud cluster, follow the instructions on their website. You’ll need to setup both the Container Service and the Container Registry. The IBM Cloud console will guide you through creating a cluster, installing the bx tool, and using that to configure kubectl.

IBM Cloud Private

IBM Cloud Private is an on-prem deployment of IBM Cloud. To deploy to your IBM Cloud Private cluster, you’ll need a working deployment of IBM Cloud Private and access to a Docker Registry.

Once you’ve configured your Kubernetes environment, you should be able to verify access with the following command:

kubectl get nodes


When deploying to DC/OS, you’ll need to make sure that the dcos command line application is on your PATH and setup to point to your DC/OS cluster.

DC/OS Vagrant

DC/OS Vagrant can be used to quickly provision a DC/OS cluster on a local machine. Consult its README to get started.

Once you’ve configured your DC/OS environment, you should be able to verify access with the following command:

dcos node