GeekCoding101 make your way to geek

Kubernetes Cluster Tutorials: Build a Multi-Node Lab on a Mac

3 posts on cluster, newest first.

3posts
2025first post

Everything tagged #cluster on GeekCoding101 belongs to one hands-on series: building a multi-node Kubernetes cluster on a Mac, from a blank VM to a running cluster with Flannel networking. Read it in order, Part 1 → Part 2 → Part 3. Each part builds on the machines you set up in the one before.

The series in reading order

PartPostWhat you doRead time
1Kubernetes Tutorial Part 1: Multi-Node Cluster on a MacPlan the cluster and networking, create a Rocky Linux 9 base VM in VMware Fusion, prepare the nodes22 min
2Ultimate Kubernetes Tutorial Part 2: DNS server and NTP server ConfigurationClone the base image and set up a local DNS server and NTP server7 min
3Ultimate Kubernetes Tutorial Part 3: A Streamlined Kubernetes cluster setupBring up the Kubernetes cluster with Flannel18 min

Total reading time is about 47 minutes. Doing the steps yourself takes longer.

What you’ll work with

  • A Mac running VMware Fusion to host the virtual machines
  • Rocky Linux 9 as the base image for the nodes
  • A local DNS and NTP server, so the nodes can find each other by name and keep their clocks in sync
  • Flannel as the pod network
  • Ansible, which appears in the posts’ tags, for automating node setup

Control plane vs worker nodes: what you’re building

A Kubernetes cluster has two kinds of machines:

  • Control plane. This runs the parts that manage the cluster: the API server (kube-apiserver), the cluster’s key-value store (etcd), the scheduler and the controller manager. It decides what runs where.
  • Worker nodes. These run your workloads. Each one runs the kubelet, kube-proxy and a container runtime.

A multi-node lab like the one in this series lets you see both roles on separate machines. A single all-in-one install hides that split.

Why DNS and NTP come before Kubernetes

It’s tempting to skip straight to kubeadm, but Part 2 exists for a reason. Cluster components talk to each other by hostname and rely on TLS certificates. Unresolvable names or drifting clocks lead to confusing failures later. Sorting out both first saves debugging time in Part 3.

Frequently asked questions

What order should I read the #cluster posts in? Start with Part 1 and finish with Part 3. The list above shows the newest post first, so the series runs from the bottom up.

What do I need to follow along? You need a Mac with VMware Fusion and a Rocky Linux 9 image. Part 1 walks through creating the base VM and preparing the nodes.

Which network plugin does the series use? Flannel. The cluster setup with Flannel is covered in Part 3.

Do I need a DNS and NTP server for a home Kubernetes lab? It’s strongly recommended. The nodes need to resolve each other’s names and keep their clocks in sync. Part 2 sets up both locally.

Is it free to read? Yes. Every GeekCoding101 post is free, with no sign-up.