Setting up a local cluster (minikube, kind) in Kubernetes - Step-by-Step CLI Walkthrough

Introduction

Sometimes you want to try Kubernetes on your own computer without needing a big cloud setup. Local clusters let you run Kubernetes right on your laptop to learn and test apps easily.

When you want to learn Kubernetes basics without using cloud resources

When you need to test your app in a Kubernetes environment before deploying to production

When you want to try out Kubernetes features quickly without waiting for cloud setup

When you want to develop and debug Kubernetes apps locally

When you want to practice Kubernetes commands and configurations safely

Commands

This command starts a local Kubernetes cluster using Minikube on your computer. It sets up all necessary components so you can run Kubernetes commands locally.

Terminal

minikube start

Expected Output

😄  minikube v1.30.1 on Ubuntu 22.04

✨  Using the docker driver based on user configuration

👍  Starting control plane node minikube in cluster minikube

🐳  Preparing Kubernetes v1.27.3 on Docker 24.0.5

🚜  Pulling images ...

🚀  Launching Kubernetes ...

⌛  Waiting for: apiserver

🏄  Done! kubectl is now configured to use "minikube"

→

--driver - Specify which virtualization driver to use (docker, virtualbox, etc.)

This command checks if the local Kubernetes cluster is running by listing the nodes. You should see one node named 'minikube' ready.

Terminal

kubectl get nodes

Expected Output

NAME       STATUS   ROLES           AGE   VERSION

minikube   Ready    control-plane   1m    v1.27.3

This command creates a local Kubernetes cluster named 'example-cluster' using Kind, which runs Kubernetes inside Docker containers.

Terminal

kind create cluster --name example-cluster

Expected Output

Creating cluster "example-cluster" ...

 ✓ Ensuring node image (kindest/node:v1.27.3) 🖼  

 ✓ Preparing nodes 📦 

 ✓ Writing configuration 📜 

 ✓ Starting control-plane 🕹️ 

 ✓ Installing CNI 🔌 

 ✓ Installing StorageClass 💾 



Cluster creation complete. You can now use 'kubectl' to interact with your cluster.

→

--name - Set a custom name for the Kind cluster

This command shows information about the Kind cluster to confirm it is running and accessible.

Terminal

kubectl cluster-info --context kind-example-cluster

Expected Output

Kubernetes control plane is running at https://127.0.0.1:6443

CoreDNS is running at https://127.0.0.1:6443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy

→

--context - Specify the Kubernetes context to use for the command

Key Concept

If you remember nothing else from this pattern, remember: local Kubernetes clusters let you safely learn and test Kubernetes on your own computer without cloud setup.

Common Mistakes

Not installing a virtualization driver like Docker or VirtualBox before starting Minikube

Minikube needs a driver to create virtual machines or containers; without it, the cluster won't start.

Install Docker or VirtualBox and ensure it runs before running 'minikube start'.

Running 'kubectl' commands before the cluster is fully ready

The cluster components may not be ready yet, causing errors or empty outputs.

Wait for the 'minikube start' or 'kind create cluster' command to finish completely before using kubectl.

Using the wrong kubectl context after creating multiple clusters

kubectl commands may target the wrong cluster, causing confusion or errors.

Use 'kubectl config get-contexts' to check and 'kubectl config use-context' to switch to the correct cluster.

Summary

Use 'minikube start' or 'kind create cluster' to set up a local Kubernetes cluster on your computer.

Verify the cluster is running with 'kubectl get nodes' or 'kubectl cluster-info'.

Make sure your virtualization driver is installed and kubectl context is correct before running commands.

Practice

1. What is the main purpose of using minikube or kind in Kubernetes?

easy

A. To create a local Kubernetes cluster for learning and testing

B. To deploy applications directly to production

C. To replace Docker as a container runtime

D. To monitor live Kubernetes clusters remotely

Solution

1. Step 1: Understand the role of minikube and kind

   Both tools create local Kubernetes clusters on your computer for practice and development.

2. Step 2: Differentiate from production tools

   They are not meant for production deployment or monitoring but for local testing environments.

3. Final Answer:

   To create a local Kubernetes cluster for learning and testing -> Option A

4. Quick Check:

   Local cluster setup = D [OK]

Hint: Minikube and kind create local clusters for practice [OK]

Common Mistakes:

• Thinking minikube deploys to production
• Confusing kind with monitoring tools
• Assuming they replace Docker runtime

2. Which command correctly starts a local Kubernetes cluster using kind?

easy

A. kubectl start kind

B. minikube start cluster

C. kind create cluster

D. docker run kind cluster

Solution

1. Step 1: Recall the kind cluster creation command

   The official command to start a kind cluster is kind create cluster.

2. Step 2: Check other options for correctness

   minikube start cluster is invalid; kubectl does not start clusters; docker run kind cluster is incorrect syntax.

3. Final Answer:

   kind create cluster -> Option C

4. Quick Check:

   kind cluster start = kind create cluster [OK]

Hint: Use 'kind create cluster' to start kind clusters [OK]

Common Mistakes:

• Using 'minikube start cluster' instead of 'minikube start'
• Trying to start cluster with kubectl
• Running kind as a docker container directly

3. After running minikube start, what command shows the status of the cluster?

medium

A. kubectl get nodes

B. docker ps

C. kind status

D. minikube status

Solution

1. Step 1: Identify minikube status command

   The command minikube status shows the current state of the minikube cluster.

2. Step 2: Understand other commands' roles

   kubectl get nodes lists nodes but doesn't show cluster health; kind status is not a valid command; docker ps shows running containers, not cluster status.

3. Final Answer:

   minikube status -> Option D

4. Quick Check:

   Check minikube cluster state = minikube status [OK]

Hint: Use 'minikube status' to check cluster health [OK]

Common Mistakes:

• Using 'kubectl get nodes' to check cluster status
• Trying 'kind status' which doesn't exist
• Checking docker containers instead of cluster status

4. You ran kind create cluster but get an error: docker: command not found. What is the most likely fix?

medium

A. Reinstall kind with admin rights

B. Install Docker and ensure it is running

C. Run 'minikube start' instead

D. Update kubectl to the latest version

Solution

1. Step 1: Understand kind's dependency on Docker

   kind uses Docker containers to create clusters, so Docker must be installed and running.

2. Step 2: Analyze the error message

   The error docker: command not found means Docker is missing or not in the system path.

3. Final Answer:

   Install Docker and ensure it is running -> Option B

4. Quick Check:

   kind needs Docker installed = Install Docker [OK]

Hint: kind requires Docker; install and start Docker first [OK]

Common Mistakes:

• Thinking kind works without Docker
• Trying to fix by reinstalling kind
• Confusing kubectl version with Docker requirement

5. You want to create a kind cluster with a custom configuration file named kind-config.yaml. Which command is correct?

hard

A. kind create cluster --config=kind-config.yaml

B. kind start cluster -f kind-config.yaml

C. minikube start --config kind-config.yaml

D. kubectl apply -f kind-config.yaml

Solution

1. Step 1: Recall kind cluster creation with config

   kind uses the command kind create cluster --config=filename to specify a config file.

2. Step 2: Check other options for correctness

   kind start cluster is invalid; minikube start does not accept --config this way; kubectl apply applies Kubernetes manifests, not cluster configs.

3. Final Answer:

   kind create cluster --config=kind-config.yaml -> Option A

4. Quick Check:

   kind config file = kind create cluster --config= [OK]

Hint: Use 'kind create cluster --config=filename' for custom config [OK]

Common Mistakes:

• Using 'kind start cluster' instead of 'kind create cluster'
• Trying to pass config to minikube with --config
• Applying config file with kubectl instead of kind