Here comes your first task. Get a Kubernetes cluster. If you already have one, whichever it is, you can use it for the exercises. If you do not have a Kubernetes cluster, and you know how to create one, just go and create it. However, if you do not have a Kubernetes cluster and you want me to help you create one, then the Gists with the commands for creating a cluster are available below.

You can choose between Minikube, Docker Desktop, AKS, EKS, and GKE. In other words, the most commonly used Kubernetes flavors are available as Gists. If you don’t like any of them, create your own cluster. As long as you have one, you should be fine.

If you follow my commands to create a cluster, you will see that they’re all single zone clusters, at least those in Google, Amazon, and Azure. They’re running in a single zone, and they have a single node outside the control plane. It’s a very simple cluster, and it’s very small. It’s just big enough for what we need. We’ll see later whether these are well-defined clusters. Chaos experiments will help us with that.

All in all, use my instructions to create a cluster, create a cluster any other way you like, or use an existing cluster. It’s up to you.

Note for Minikube and Docker Desktop users

Istio Ingress Gateway

Gists for different Kubernetes flavors

As always, we will need a cluster. However, this time, it is going to be a bit better defined than before. In the previous section, we gained some insights that should help us create a more robust cluster. It will be regional and scalable. Or, to be more precise, it will be like that if that’s possible.