Skip to main content

Multi-cluster with KinD

System setup

For this workshop, we'll use Kratix on two local Kubernetes clusters. Install the prerequisites listed below if they aren't already on your system.

  1. kind CLI / Kubernetes-in-Docker (KinD): Used to create and manage local Kubernetes clusters in Docker. See the quick start guide to install.
  2. docker CLI / Docker: Used to orchestrate containers. kind (above) requires that you have Docker installed and configured. See Get Docker to install.
  3. kubectl / Kubernetes command-line tool: The CLI for Kubernetes — allows you to run commands against Kubernetes clusters. See the install guide.

Installing Kratix


You can also run ./scripts/ from the root of the Kratix repository.

Set up a Platform Cluster

Create your platform cluster and install Kratix and MinIO. MinIO will be the repository for the GitOps toolkit. You can try Kratix with Git by following this guide. For production installations, MinIO can be replaced by Git or any other S3-compatible storage, depending on your preference.

kind create cluster --name platform

# Install Kratix
kubectl apply --context kind-platform --filename

# Install MinIO
kubectl apply --context kind-platform --filename

Set up your Worker Cluster

Create your Kratix worker cluster and install Flux. This will create a cluster for running the X as-a-Service workloads:

kind create cluster --name worker

# Register the Worker Cluster with the Platform Cluster
kubectl apply --context kind-platform --filename

# Install flux on the worker
kubectl apply --context kind-worker --filename
kubectl apply --context kind-worker --filename

Flux will eventually reconcile the clusters state, making the worker cluster ready to receive workloads. You can verify its readiness by observing the kratix-worker-system namespace appearing in the worker cluster:

$ kubectl --context kind-worker get namespaces
kratix-worker-system Active 1m

🎉 Congratulations! Kratix is now ready to receive workloads. Jump to Installing and using a Promise to spin up your first as-a-service workload.