DEV Community

Cover image for How to Use a Homelab for Kubernetes Practice (Free Setup Guide)
Raphael Ben Hamo
Raphael Ben Hamo

Posted on

How to Use a Homelab for Kubernetes Practice (Free Setup Guide)

#kubernetes #devops #homelab #beginners

Cloud-based Kubernetes — EKS, AKS, GKE — is expensive to learn on. Every minute a managed cluster runs costs money, and experimenting means breaking things. A homelab eliminates that entirely: run Kubernetes on your own machine, destroy and rebuild clusters without a billing meter, and see every layer of the stack that managed services hide.

Tool Comparison

Feature Minikube K3s Kind
Best for Beginners Multi-node / edge Fast testing / CI
Setup speed Moderate Fast Very fast
Multi-node Limited Native Native via config
Resource usage Medium Low Low
Offline support Yes Yes Yes

Start with Minikube if you're new. It's the official Kubernetes tool, has built-in add-ons, and mirrors a standard cluster closely.

Quick Setup With Minikube

Install on macOS:

brew install minikube
Enter fullscreen mode Exit fullscreen mode

Install on Linux:

curl -LO https://storage.googleapis.com/minikube/releases/latest/minikube-linux-amd64
sudo install minikube-linux-amd64 /usr/local/bin/minikube
Enter fullscreen mode Exit fullscreen mode

Start your cluster:

minikube start
Enter fullscreen mode Exit fullscreen mode

Verify it's running:

kubectl get nodes
# NAME       STATUS   ROLES           AGE   VERSION
# minikube   Ready    control-plane   30s   v1.31.0
Enter fullscreen mode Exit fullscreen mode

Three Exercises to Build Real Skills

1. Deployments and Scaling 

kubectl create deployment nginx --image=nginx --replicas=3
kubectl scale deployment nginx --replicas=5
Enter fullscreen mode Exit fullscreen mode

Delete a pod manually — Kubernetes recreates it automatically. This is the Deployment controller maintaining desired state.

kubectl delete pod <pod-name>
kubectl get pods --watch
Enter fullscreen mode Exit fullscreen mode

2. ConfigMaps 

kubectl create configmap app-config \
  --from-literal=ENV=staging \
  --from-literal=LOG_LEVEL=debug
Enter fullscreen mode Exit fullscreen mode

Mount it into a pod:

# pod-with-config.yaml
apiVersion: v1
kind: Pod
metadata:
  name: app-pod
spec:
  containers:
  - name: app
    image: nginx
    envFrom:
    - configMapRef:
        name: app-config
Enter fullscreen mode Exit fullscreen mode 
kubectl apply -f pod-with-config.yaml
kubectl exec app-pod -- env | grep -E 'ENV|LOG_LEVEL'
Enter fullscreen mode Exit fullscreen mode

3. Services and Networking 

# ClusterIP — cluster-internal only
kubectl expose deployment nginx --port=80 --type=ClusterIP --name=nginx-clusterip

# NodePort — accessible from your machine
kubectl expose deployment nginx --port=80 --type=NodePort --name=nginx-nodeport

# Open in browser via Minikube
minikube service nginx-nodeport
Enter fullscreen mode Exit fullscreen mode

Understanding how traffic moves through ClusterIP → NodePort → LoadBalancer is one of the most valuable Kubernetes networking skills you can build.

Want all 6 exercises — including RBAC, Helm charts, and multi-node K3s configs? Get the full free guide on korpro.io →

From Homelab to Production Thinking

The homelab is where instinct forms. Before you move to production, practice the questions that always come up: How do you monitor workloads? (Install Prometheus + Grafana.) How do you handle persistent data? (Test PersistentVolumeClaims and pod rescheduling.) How do you manage secrets securely? (Try Sealed Secrets or External Secrets Operator.)

Every hour spent breaking and rebuilding a local cluster translates directly to faster debugging and better decisions in production.

Running Kubernetes in Production?

Cost and waste become real problems at scale. KorPro automatically finds orphaned resources, unused ConfigMaps, over-provisioned workloads, and idle services across all your clusters — before they become surprise invoices.

Start free on KorPro →

Top comments (0)