Saqib Chaudhary

17/08/2026

Day 05/30 — Desired State in Kubernetes ☸️

One of the biggest mindset shifts in Kubernetes is this:

You don’t tell the system how to do every step.
You tell it what you want, and Kubernetes keeps working to make reality match that desired state.

That is the power of the declarative model.

Today’s key ideas:

• Define the desired state in YAML
• Kubernetes stores that intent and keeps watching the cluster
• Controllers compare desired state vs current state
• If something drifts, Kubernetes works to reconcile it
• The goal is not manual control — the goal is consistent outcomes

This is why Kubernetes can be:
• More reproducible
• Easier to review
• More self-healing
• Better for scale

The real lesson:

Stop asking “What commands should I run?”
Start asking “What state do I want the system to guarantee?”

That mindset changes everything.

📌 Save this for revision
➕ Follow my 30 Days to KCNA journey
🌐 saqibchaudhary.com
💬 Message me for Kubernetes, DevOps, and Cloud discussions

Day 05 complete. See you in Day 06.

15/08/2026

**Day 04/30 — Kubernetes Architecture ⚙️☸️**

Kubernetes is not “just containers.”

It is a **system of components working together** to keep your applications running the way you declared.

Today’s core architecture:

• **API Server** — the front door of the cluster
• **etcd** — stores cluster state and configuration
• **Scheduler** — decides where Pods should run
• **Controller Manager** — continuously works to keep actual state aligned with desired state
• **kubelet** — makes sure workloads run correctly on each node
• **kube-proxy** — handles Service networking and traffic rules
• **Container Runtime** — actually runs the containers

The key mindset:

**Desired State → Observe → Compare → Reconcile → Desired State**

You declare what you want.

Kubernetes keeps checking reality and works to close the gap automatically.

That is why concepts like **self-healing, scaling, scheduling, and automation** become possible.

📌 Save this for revision
➕ Follow my **30 Days to KCNA** journey
🌐 saqibchaudhary.com
💬 Message me for Kubernetes, DevOps, or Cloud discussions

**Understand the architecture, and Kubernetes becomes much easier to troubleshoot.**

See you in **Day 05**.

14/08/2026

**Day 03/30 — Container Images 📦**

“It works on my machine” usually means the **code moved, but the environment didn’t**.

That is exactly where container images change the game.

A container image packages:
• Your application
• Dependencies and libraries
• Runtime
• Base OS files

The key idea is simple:

**An image is the blueprint.
A container is a running instance of that image.**

Build the image once, then run the **same version across development, CI, and production**.

And one important mindset shift:

❌ Don’t patch running containers manually.
✅ Update the image, rebuild, and redeploy.

That gives you:
• Consistent environments
• Safer rollbacks
• Less configuration drift
• More predictable deployments

**Containers are replaceable units, not tiny servers.**

📌 Save this for revision
➕ Follow my **30 Days to KCNA** journey
🌐 saqibchaudhary.com
💬 Message me if you want to discuss Kubernetes, DevOps, or Cloud

**See you in Day 04.**

12/08/2026

Cloud native is not about moving servers to the cloud. It’s about changing how systems are built, deployed, scaled, and recovered.

Day 01 of my 30 Days to KCNA series starts with one of the most important foundations: Cloud Native.

In this I break down:

Why cloud-hosted does not automatically mean cloud native
The core pillars behind cloud-native architecture
How Kubernetes reconciliation and self-healing actually work
Why the cattle, not pets mindset matters
How enterprises gain scalability, resilience, and safer deployments
A simple self-check to see whether your system is truly cloud native

The biggest mindset shift:

Stop designing systems only to avoid failure.
Start designing them to recover from failure automatically.

That principle sits at the heart of Kubernetes and modern platform engineering.

I’m sharing this journey publicly one concept at a time, with practical explanations that go beyond certification questions and into real-world engineering.

If this helped you:

🔖 Save it for revision
➕ Follow for Day 02
🌐 Visit saqibchaudhary.com
💬 Message me if you want to discuss Kubernetes, DevOps, Cloud, or Platform Engineering

Saqib Chaudhary

11/08/2026

11/08/2026

Trends keep changing. The engineers who stay relevant are the ones who keep strengthening the fundamentals underneath every new tool.
Tools evolve. Fundamentals compound.
What would you add to the 2026 list?

10/08/2026

DevOps feels overwhelming when you try to learn every tool at once.

I made that mistake too.

If I had to start again, I would focus on the foundations first and add tools only when I understood the problem they were solving.

My order would be:

Linux → Git → Networking → Containers → CI/CD → Kubernetes → IaC → Monitoring → Production

The goal is not to collect tools.

The goal is to understand how modern software moves from code to production.

I put the complete roadmap into the carousel.

Save it for later.

Which stage are you currently learning?

05/01/2025

05/01/2025

اگر ! کوئی آپ کو اپنی تکلیف بتائے تو اُس سے اچھے طریقے سے پیش آئیے کیونکہ آپ صرف سُن رہے ہیں لیکن وہ محسوس کر رہا ہے

04/01/2025

Check out saqibmustafaofficial’s video.