Create a Cluster

Pulling the code #

You know the drill. We’ll move into the directory with the vfarcic/k8s-specs repository, we’ll pull the latest version of the code just in case I pushed something recently, and we’ll create a new cluster unless you already have one at hand.

🔍 All the commands from this chapter are available in the 07-logging.sh Gist.

cd k8s-specs

git pull

Gists and specifications #

Choose the flavor you want and run the commands from its .sh file to create the cluster and the required specifications needed in this chapter.

NOTE: In the end, you will see a command to DELETE the cluster too. Don’t execute that command. Use the DELETE command only when you need to delete the cluster, preferably at the end of the chapter.

This time, the requirements for the cluster changed. We need much more memory than before. The main culprit is ElasticSearch which is very resource hungry.

If you’re using Docker For Desktop or minikube, you’ll need to increase the memory dedicated to the cluster to 10 GB. If that’s too much for your laptop, you might choose to read the Exploring Centralized Logging Through without running the examples or you might have to switch to one of the Cloud providers (AWS, GCP, or Azure).

In the case of EKS and AKS, we’ll need bigger nodes. For EKS we’ll use t2.large and for AKS Standard_B2ms. Both are based on 2 CPUs and 8 GB RAM.

GKE requirements are the same as before.

On top of new requirements, it should be noted that we do NOT need Prometheus in this chapter, so I removed it from the Gists.

Feel free to use one of the Gists that follow to create a new cluster, or to validate that the one you’re planning to use meets the requirements.