Setting up a local cluster (minikube, kind) in Kubernetes - Visual Walkthrough

Process Flow - Setting up a local cluster (minikube, kind)

Install tool (minikube/kind)

↓

Start local cluster

↓

Verify cluster status

↓

Use kubectl to interact

↓

Stop or delete cluster when done

This flow shows the steps to set up a local Kubernetes cluster using minikube or kind: install, start, verify, use, and stop/delete.

Execution Sample

Kubernetes

minikube start
kubectl get nodes
minikube status
minikube stop

Starts a minikube cluster, checks nodes, verifies status, then stops the cluster.

Process Table

Step	Command	Action	Result/Output
1	minikube start	Starts local Kubernetes cluster	Starting control plane node... Cluster is running
2	kubectl get nodes	Lists nodes in cluster	NAME STATUS ROLES AGE VERSION minikube Ready control-plane 1m v1.27.0
3	minikube status	Shows cluster status	host: Running kubelet: Running apiserver: Running kubeconfig: Configured
4	minikube stop	Stops the cluster	Stopping local Kubernetes cluster...
5			Cluster stopped, no longer running

💡 Cluster stopped, no further commands executed

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	Final
Cluster State	Not running	Running	Running	Running	Stopped	Stopped
kubectl Nodes	None	One node (starting)	One node Ready	One node Ready	None (cluster stopped)	None (cluster stopped)

Key Moments - 3 Insights

Why does 'kubectl get nodes' show no nodes before starting minikube?

Because the cluster is not running yet (see Step 1 in execution_table). Nodes appear only after 'minikube start' creates the cluster.

What does 'minikube status' tell us about the cluster?

'minikube status' shows if the cluster components like host, kubelet, and apiserver are running (Step 3). It confirms cluster health.

Why do we need to stop the cluster with 'minikube stop'?

Stopping frees system resources and pauses the cluster (Step 4). Without stopping, the cluster keeps running in the background.

Visual Quiz - 3 Questions

Look at the execution table, what is the cluster state after Step 1?

A Not running

B Stopped

C Running

D Unknown

💡 Hint

Check the 'Cluster State' row in variable_tracker after Step 1

At which step does 'kubectl get nodes' show the node as Ready?

A Step 1

B Step 2

C Step 3

D Step 4

💡 Hint

Look at the 'kubectl get nodes' output in execution_table row for Step 2

If you skip 'minikube stop', what happens to the cluster state?

A Cluster remains running

B Cluster stops automatically

C Cluster is deleted

D Cluster status unknown

💡 Hint

Refer to variable_tracker 'Cluster State' after Step 4 and exit_note

Concept Snapshot

Setting up a local Kubernetes cluster:
1. Install minikube or kind.
2. Start cluster with 'minikube start' or 'kind create cluster'.
3. Verify nodes with 'kubectl get nodes'.
4. Check status with 'minikube status'.
5. Stop cluster with 'minikube stop' to free resources.

Full Transcript

To set up a local Kubernetes cluster, first install a tool like minikube or kind. Then start the cluster using 'minikube start' or 'kind create cluster'. Once started, use 'kubectl get nodes' to see the cluster nodes and 'minikube status' to check cluster health. When finished, stop the cluster with 'minikube stop' to free system resources. This process helps you run Kubernetes locally for learning and testing.

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