Setting up a local cluster (minikube, kind) in Kubernetes - Practice Exercises

Challenge - 5 Problems

💻 Command Output

intermediate

Minikube Start Command Output

What is the expected output when you run minikube start on a system with Docker installed and no existing cluster?

Kubernetes

minikube start

A

😄  minikube v1.30.1 on Ubuntu 22.04
✨  Using virtualbox driver
❌  VirtualBox is not installed

B Error: minikube: command not found

C

😄  minikube v1.30.1 on Ubuntu 22.04
❌  Unable to start cluster: Docker daemon not running

D

😄  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 base image ...

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

💡 Hint

Think about what happens when minikube starts successfully with Docker driver.

When minikube starts successfully with Docker driver, it shows messages about using Docker, preparing Kubernetes, and ends with a success message configuring kubectl.

🧠 Conceptual

intermediate

Kind Cluster Configuration File Purpose

What is the main purpose of a kind cluster configuration YAML file?

A To define the Kubernetes version, node roles, and networking settings for the local cluster

B To configure the minikube VM resources like CPU and memory

C To specify Docker container images to be deployed inside the cluster

D To set up the kubeconfig file location for kubectl

💡 Hint

Think about what you control when creating a kind cluster with a config file.

Kind uses the config file to define cluster details like Kubernetes version, how many nodes, their roles, and network settings.

❓ Troubleshoot

advanced

Diagnosing Minikube Docker Driver Failure

You run minikube start --driver=docker but get the error: Docker daemon not running. What is the most likely cause?

A Minikube does not support Docker driver on your OS

B Your kubectl version is incompatible with minikube

C Docker service is not running on your machine

D You need to install VirtualBox to use Docker driver

💡 Hint

Check if Docker is running before starting minikube with Docker driver.

The error means minikube cannot connect to Docker because the Docker service is stopped or not installed.

🔀 Workflow

advanced

Kind Cluster Creation Steps

Which sequence correctly describes the steps to create and use a kind cluster?

A 1,2,3,4

B 2,1,3,4

C 1,3,2,4

D 2,3,1,4

💡 Hint

Think about what you do first before creating the cluster.

You optionally write a config file, then create the cluster, check it is running, then deploy apps.

✅ Best Practice

expert

Best Practice for Persistent Storage in Minikube

What is the best practice to enable persistent storage for applications running in a minikube cluster?

A Store data inside container writable layers

B Use minikube's built-in hostPath provisioner with a PersistentVolume and PersistentVolumeClaim

C Use ephemeral emptyDir volumes for all storage needs

D Install a cloud provider storage plugin inside minikube

💡 Hint

Think about how to keep data safe even if pods restart in minikube.

Minikube supports hostPath volumes which map to local disk, allowing data to persist beyond pod lifecycle.

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