Introduction
I’m Tani, a software engineer with 6 years of programming experience and 4 years working professionally.
Kubernetes confused me at first, until I started thinking about it like a computer lab.
KUBERNETES WORKLOAD
Overview
Think of Kubernetes as a computer lab filled with multiple laptops (nodes).
Your job is to run applications on these laptops, without manually managing each one.
Pods
Pods are the smallest runnable unit in Kubernetes, usually one or more containers running together.
Imagine images as a laptop placed in the store, and pods as a laptop you have bought and have powered up, and are currently using it in relation to a software application (a standalone runnable piece of software)
Sets
Rather than managing every individual pod yourself, you use a “Set” to tell Kubernetes your desired state, and it handles the heavy lifting of keeping that state alive.
Deployements
A Deployment is like:
“Here’s the exact laptop spec we want — now manage it for me.”
It:
- Decides how many laptops (pods) should run
- Replaces broken ones
- Updates software safely
Analogy:
Like giving IT a standard laptop configuration, and they handle everything else.
Deamon Sets
DaemonSets ensure:
“Every laptop must have this tool installed and running”.
One pod per node
Example:
- Antivirus
- Monitoring software
Stateful Sets
StatefulSets are for laptops where:
Identity matters (Laptop-1, Laptop-2…)
Data must persist
Analogy:
These are personal laptops assigned to specific users, not replaceable like generic ones.
If Laptop-1 restarts -> it’s still Laptop-1 with its files intact.
Replica Sets
ReplicaSets are the system that ensures:
“We must always have 3 working laptops.”
If one laptop crashes -> it gets replaced immediately
Analogy:
Like an auto-repair + replacement system in your lab.
Replication Controllers
A replication controller is the older version of the replica set that was used in the early versions of Kubernetes to ensure a specified number of pods were running at any given time
Jobs
A Job is like:
“Turn on a laptop, run this task, then shut it down.”
Example:
- Install software
- Process a file
Once done -> it stops.
Cron Jobs
CronJobs are:
“Run this task on a laptop every day at 2 AM”.
Same as Jobs, but repeated on a schedule.
If you remember nothing else, remember this:
- Pods are your laptops
- Controllers are your IT rules
- Kubernetes is your automated IT department
Once you see it this way, everything starts to click. Ok, bye, I have to get back to work…