Kubernetes Simplified: A Beginner’s Guide

---

Introduction

Kubernetes can feel overwhelming at the beginning.

You hear terms like:

• Pods
• Nodes
• Deployments
• Clusters

But it’s not always clear what they actually mean in practice.

This blog explains Kubernetes from scratch, focusing only on what matters when you’re starting.

No complex theory — just a simple understanding you can build on.

---

1. What is Kubernetes in simple terms?

Kubernetes is a system that helps you:

👉 Run and manage applications inside containers.

Instead of running containers manually, Kubernetes takes care of:

• Starting containers
• Restarting them if they fail
• Scaling them
• Distributing them across machines

---

2. Why do we need Kubernetes?

Without Kubernetes:

• You run containers manually
• If one crashes → you restart it
• If traffic increases → you manually add more

With Kubernetes:

• It automatically handles failures
• It automatically handles scaling
• It distributes load across systems

---

3. What is a Cluster?

A Kubernetes cluster is simply:

👉 A group of machines working together to run your applications

It has two main parts:

• Control Plane → makes decisions
• Worker Nodes → run your applications

---

4. What is a Node?

A Node is a machine (VM or server) where your applications run.

Each node has:

• CPU
• Memory
• Storage

Kubernetes uses multiple nodes to:

• Distribute workloads
• Avoid single point of failure

---

5. What is a Pod?

A Pod is the smallest unit in Kubernetes.

👉 It is where your container actually runs.

Think of it like:

• Docker container → inside a Pod
• Pod → managed by Kubernetes

Example:

kubectl get pods

This shows all running Pods.

---

6. What is a Deployment?

A Deployment helps you manage Pods.

Instead of creating Pods manually, you tell Kubernetes:

👉 “I want 3 copies of my app running”

Kubernetes ensures:

• 3 Pods are always running
• If one fails → it creates another

---

7. What is a Service?

Pods are temporary and can change.

A Service provides:

👉 A stable way to access your application

Instead of connecting directly to a Pod, you connect to the Service.

Example:

kubectl get svc

---

8. Basic workflow (very important)

This is how Kubernetes actually works:

1. You define what you want (YAML file)
2. Kubernetes receives the request
3. It creates Pods
4. It schedules them on Nodes
5. It keeps checking if everything is running

Basic command example:

kubectl apply -f deployment.yaml

---

9. Key idea beginners must understand

Kubernetes is not executing commands step-by-step.

It is constantly doing:

👉 Compare → Fix → Repeat

Example:

• You say: 3 Pods
• Only 2 running

👉 Kubernetes automatically creates 1 more

---

10. Common beginner mistakes

---

❌ Expecting immediate results

Kubernetes works in loops, not instantly.

---

❌ Checking logs too early

If Pod is not running, logs won’t exist.

---

❌ Confusing Pod with container

• Pod → Kubernetes object
• Container → runs inside Pod

---

11. Simple command set to start with

kubectl get pods
kubectl get nodes
kubectl get deployments
kubectl get svc

👉 These are enough to understand what’s running.

---

12. What should you learn next?

After this, focus on:

• Pods lifecycle
• Deployments
• Services
• Debugging issues

Then move to:

• StatefulSet
• DaemonSet
• Storage

---

🚀 InfraDecode Takeaway

Kubernetes is not complicated — it just manages containers at scale.
Start by understanding Pods, Nodes, and Deployments first.
Everything else builds on top of these basics.
Focus on flow, not definitions — and learning becomes easier.