Cloud & DevOps · Kubernetes Basics
Kubernetes Basics Explained in Plain Simple Language
Quick summary — Kubernetes basics in plain English
Kubernetes is like a manager for your containers. You tell it what you want running, and it makes sure it stays running — restarting things that crash, adding more when traffic grows, and moving workloads around when machines fail.
In this guide you will learn:
- Phase 1: Core Concepts — what Kubernetes is, pods, nodes, clusters, and kubectl.
- Phase 2: Workloads & Networking — deployments, services, ConfigMaps, and Ingress.
- Phase 3: Operations & Practice — scaling, health checks, logs, and a capstone deployment.
- kubectl cheatsheet & templates — real commands and a starter YAML.
- Support & accountability — how Uncodemy helps you practise safely.
SECTION 01What is Kubernetes? (in plain English)
Kubernetes is a container orchestrator. In simple words: you package your app in a container, hand it to Kubernetes, and it figures out where to run it, how to keep it running, and how to let other services reach it. Here's the 4-week breakdown of the core concepts:
| Week | Focus | Plain-English Explanation | Weekly Goal |
|---|---|---|---|
| Week 1 | Why Kubernetes? | A manager for containers — restarts crashes, handles scale | Explain K8s in 3 sentences |
| Week 2 | Pods, Nodes, Clusters | Pod = container wrapper; Node = machine; Cluster = machines together | Draw a cluster diagram |
| Week 3 | kubectl basics | The remote control for your cluster | Run 10 kubectl commands |
| Week 4 | Your first deployment | Tell Kubernetes "run 3 copies of my app" | Deploy an app locally |
Phase 1 — Daily Schedule:
7:00 AM — Wake up, exercise (30 min)
8:00 AM — Review the day's learning goals
9:00 AM — Learn + practice (2 hours)
- Week 1: Why Kubernetes?
- Week 2: Pods, nodes, clusters
- Week 3: kubectl basics
- Week 4: First deployment
12:00 PM — Lunch break
1:00 PM — Hands-on practice (2 hours)
- Draw diagrams, run kubectl, deploy demo apps
3:00 PM — Mentor check-in / doubt session (30 min)
4:00 PM — Assignment work (1 hour)
5:00 PM — Review notes, plan tomorrow
6:00 PM — Break / exercise
8:00 PM — Read Kubernetes docs / blogs (30 min)
10:00 PM — Wind down
Week 1 Review:
□ Can I explain Kubernetes in plain English?
□ Do I know the difference between containers and VMs?
□ Do I understand what a cluster is?
Week 2 Review:
□ Do I understand what a pod is?
□ Do I understand what a node is?
□ Can I draw a cluster diagram?
Week 3 Review:
□ Can I install kubectl?
□ Can I run kubectl get pods / nodes / cluster-info?
□ Do I understand namespaces?
Week 4 Review:
□ Have I deployed an app?
□ Can I scale it to 3 replicas?
□ Can I delete a deployment cleanly?
SECTION 02Workloads & networking made simple
Once you understand pods and nodes, the next step is workloads (what runs) and networking (how things talk). Here's how the weeks break down:
| Week | Focus | Plain-English Explanation | Weekly Goal |
|---|---|---|---|
| Week 5 | Deployments | "Run 3 copies and update them safely" | Roll out a new version |
| Week 6 | Services | "Give these pods a stable address" | Expose an app to the browser |
| Week 7 | ConfigMaps & Secrets | "Store settings and passwords safely" | Move config out of code |
| Week 8 | Ingress | "One front door for many services" | Route two apps by path |
Phase 2 — Daily Schedule:
7:00 AM — Wake up, exercise (30 min)
8:00 AM — Review the day's learning goals
9:00 AM — Learn + practice (2 hours)
- Week 5: Deployments
- Week 6: Services
- Week 7: ConfigMaps & secrets
- Week 8: Ingress
12:00 PM — Lunch break
1:00 PM — Hands-on practice (2 hours)
- Roll out updates, expose apps, wire up ingress
3:00 PM — Mentor check-in / doubt session (30 min)
4:00 PM — Assignment work (1 hour)
5:00 PM — Review notes, plan tomorrow
6:00 PM — Break / exercise
8:00 PM — Read Kubernetes docs / blogs (30 min)
10:00 PM — Wind down
Week 5 Review:
□ Do I understand what a Deployment does?
□ Can I scale a deployment to 3 replicas?
□ Can I roll out a new image safely?
Week 6 Review:
□ Can I create a Service for my app?
□ Do I understand ClusterIP vs NodePort vs LoadBalancer?
□ Have I exposed an app to my browser?
Week 7 Review:
□ Can I create a ConfigMap?
□ Can I create a Secret?
□ Have I moved config out of my image?
Week 8 Review:
□ Do I understand what Ingress does?
□ Have I set up path-based routing?
□ Have I routed two apps?
SECTION 03Operations & hands-on practice
The last phase is about keeping things healthy in production. Here's how the weeks break down:
| Week | Focus | Plain-English Explanation | Weekly Goal |
|---|---|---|---|
| Week 9 | Scaling | "Add more pods when traffic grows" | Set up HPA |
| Week 10 | Health Checks | "Restart pods that stop responding" | Add liveness & readiness |
| Week 11 | Logs & Metrics | "See what's happening inside the cluster" | Read logs and metrics |
| Week 12 | Capstone | "Deploy one real app end-to-end" | Ship a real deployment |
Phase 3 — Daily Schedule:
7:00 AM — Wake up, exercise (30 min)
8:00 AM — Review the day's learning goals
9:00 AM — Learn + practice (2 hours)
- Week 9: Scaling
- Week 10: Health checks
- Week 11: Logs & metrics
- Week 12: Capstone
12:00 PM — Lunch break
1:00 PM — Hands-on practice (2 hours)
- Scale apps, add probes, tail logs, ship capstone
3:00 PM — Mentor check-in / doubt session (30 min)
4:00 PM — Assignment work (1 hour)
5:00 PM — Review notes, plan tomorrow
6:00 PM — Break / exercise
8:00 PM — Read Kubernetes docs / blogs (30 min)
10:00 PM — Wind down
Week 9 Review:
□ Do I understand Horizontal Pod Autoscaler?
□ Have I scaled on CPU or memory?
□ Have I seen pods increase when load grows?
Week 10 Review:
□ Do I understand liveness probes?
□ Do I understand readiness probes?
□ Have I added both to a deployment?
Week 11 Review:
□ Can I tail pod logs?
□ Can I read basic metrics?
□ Do I understand what happens when a pod crashes?
Week 12 Review:
□ Is my capstone app deployed?
□ Is it documented with YAML files?
□ Is it on GitHub?
SECTION 04kubectl cheatsheet & starter YAML
Use these quick references to practise daily:
kubectl cheatsheet — the 15 commands you actually use:
# See what's running
kubectl get pods
kubectl get deployments
kubectl get services
kubectl get nodes
# Look closer at a resource
kubectl describe pod
kubectl logs
kubectl logs -f
# Apply changes
kubectl apply -f my-app.yaml
# Scale
kubectl scale deployment my-app --replicas=5
# Roll out a new image
kubectl set image deployment/my-app my-app=my-app:v2
# Clean up
kubectl delete -f my-app.yaml
# Debug
kubectl exec -it -- sh
kubectl port-forward svc/my-app 8080:80
# Context (which cluster am I talking to?)
kubectl config current-context
Starter deployment YAML — my-app.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
name: my-app
spec:
replicas: 3
selector:
matchLabels:
app: my-app
template:
metadata:
labels:
app: my-app
spec:
containers:
- name: my-app
image: nginx:latest
ports:
- containerPort: 80
readinessProbe:
httpGet:
path: /
port: 80
initialDelaySeconds: 5
livenessProbe:
httpGet:
path: /
port: 80
initialDelaySeconds: 15
---
apiVersion: v1
kind: Service
metadata:
name: my-app
spec:
selector:
app: my-app
ports:
- port: 80
targetPort: 80
type: NodePort
# Apply with: kubectl apply -f my-app.yaml
Weekly Learning Tracker:
Week: _____
Topics covered:
1.
2.
3.
kubectl commands practised: _____
YAML files written: _____
Issues hit & fixed:
1.
2.
What I learned:
1.
2.
Next week's focus:
_______________________________
SECTION 05Support & accountability
Here's how Uncodemy keeps you accountable while you learn Kubernetes:
- Mentor check-ins — weekly 1:1 sessions with your mentor to review progress.
- Live labs — practise on real clusters with guided labs.
- Mock interviews — practice with DevOps hiring managers from partner companies.
- Placement drives — attend exclusive drives with hiring partners.
- Lifetime access — revisit recordings, templates, and resources anytime.
SECTION 06Interview Q&A — Kubernetes basics
Q1Do I need to know Docker before Kubernetes?
Yes — Kubernetes runs containers, and Docker is the most common way to build them. Learn the basics of building and running containers first.
Q2What's the difference between a pod and a container?
A container is the packaged app. A pod is the smallest unit Kubernetes manages — usually one container, but sometimes a few that need to run together.
Q3What does a Service actually do?
A Service gives a stable network address to a set of pods, so other apps can reach them even as pods come and go.
Q4How long does it take to learn Kubernetes basics?
Around 6–8 weeks for a comfortable beginner level if you already know Docker and Linux basics. Deep production knowledge takes longer.
Q5Do I need a cloud account to practice?
No — you can run a local cluster with minikube or kind on your laptop. Cloud accounts are useful for real-world scenarios but not required to start.
SECTION 07Test yourself — Kubernetes basics
Five questions. No sign-up.
0 / 5Pick an answer to see why it is right or wrong.
SECTION 08Frequently asked questions
What is Kubernetes in one sentence?
Kubernetes is a container orchestrator — it runs your containers for you, keeps them healthy, and lets other apps reach them.
Do I need to know Linux before Kubernetes?
Basic Linux is essential — navigating files, running commands, reading logs. You don't need to be a Linux expert, but you need the basics.
Is Kubernetes hard to learn?
The vocabulary is the hard part. Once you understand pods, nodes, clusters, deployments, and services, the rest follows naturally.
What is minikube?
Minikube is a tool that runs a single-node Kubernetes cluster on your laptop — perfect for learning and testing.
Do I need a certificate to get a Kubernetes job?
A CKA (Certified Kubernetes Administrator) certificate helps, but real projects and hands-on experience matter more. Start with the basics, build a project, then consider certification.
SECTION 09Related reads
Classroom & online · Noida
Learn Kubernetes the hands-on way with Uncodemy
Our Kubernetes Training Course is designed for beginners — with live clusters, guided labs, and placement support.
₹19,500 · full programme- Complete Kubernetes basics roadmap
- Live clusters & guided labs
- Capstone deployment project
- Mock interviews & placement support