DEV Community: Sherdil IT Academy

The Kubernetes Exam Your Daily kubectl History Already Chose

Sherdil IT Academy — Mon, 31 Aug 2026 07:25:08 +0000

Every syllabus comparison of the CKA and the CKAD tells you the same thing: one is broader, one is narrower, both are two hours, both need 66%, both are 100% hands-on. None of that actually tells you which one to sit. What tells you is far simpler and sitting right there in your shell history: the commands you already run against a cluster every week.

Instead of another domain-by-domain breakdown, run this 5-command self-test. It takes less time than reading a syllabus PDF.

The self-test

Open your shell history (history | grep kubectl, or just think back to last week) and check off which of these five you actually typed, not which ones you know exist.

# 1. Node-level operations
kubectl drain node-3 --ignore-daemonsets
kubectl cordon node-3

# 2. Cluster state backup/restore
etcdctl snapshot save /backup/etcd-snap.db

# 3. Cluster-wide access control
kubectl create rolebinding dev-binding --role=dev-role --user=jane -n team-a

# 4. Rolling out an application change
kubectl set image deployment/api api=myorg/api:v2.3
kubectl rollout status deployment/api

# 5. Application-level debugging
kubectl describe pod api-7d9f8 | grep -A5 Events
kubectl logs api-7d9f8 --previous

Commands 1 through 3 are cluster-owner work: you are responsible for the machine underneath the workloads, not just the workloads. Commands 4 and 5 are the daily reality of shipping and debugging an application on infrastructure someone else keeps running.

Scoring it

If your real, honest history leans 1-2-3, that is a CKA profile. The exam's four domains, cluster architecture, workloads and scheduling, services and networking, and troubleshooting, are all written from the point of view of the person who owns the node, not just the pod running on it.

If your history leans 4-5, that is a CKAD profile. Its domains, application design, deployment configuration, observability, and application environment, assume the cluster is a given and test how fast and correctly you can ship and fix what runs on top of it.

Most engineers do not sit at either extreme. If you are close to even, the tiebreaker is not preference, it is the market: over 80% of Kubernetes job postings in Pakistan in 2026 name the CKA specifically, even for roles that lean closer to application deployment day-to-day. When the self-test is a genuine toss-up, that market data is the deciding vote, not a coin flip.

Why this beats a syllabus comparison

A syllabus tells you what is testable. It does not tell you what is natural. Two engineers can read the identical CKA domain list and one will find etcd restore drills intuitive because they have broken a cluster and fixed it before, while the other will find the same drills exhausting because their daily work never touches that layer. Preparation time roughly triples when you are studying a domain that is not already close to your muscle memory. The self-test above is really a proxy for that: it tells you which exam you can prepare for in 12 weeks without fighting your own instincts the whole way.

The certification is one line item, not the whole plan

Whichever exam the self-test points you to, it is worth remembering that a certification is a single, well-defined credential inside a much longer career arc, not a career plan by itself. If you are mapping out where a Kubernetes credential actually sits relative to the rest of the skill stack, from Linux fundamentals through to a lead or architect title, the complete DevOps Career Guide for Pakistan lays out the full seven-to-ten-year path and exactly where a CKA or CKAD pays off most along it.

I put the full comparison in one place: the 2026 PKR pricing for both exams, role-based recommendations, and the salary premium each certification carries in the Pakistani market, over here: Kubernetes Certification Pakistan: CKA vs CKAD.

Ran the self-test. Which side did your real history land on, and did the exam you sat match it? Drop it in the comments. 👇

A Free 16-Week Cloud and DevOps Syllabus for Karachi (2026)

Sherdil IT Academy — Mon, 17 Aug 2026 08:21:08 +0000

Every free resource you need to go from zero to a genuinely hireable cloud or DevOps skill set already exists, and most of it is free. The problem was never access. The problem is that nobody hands you an order, so people bounce between AWS Skill Builder, random YouTube tutorials, and a Udemy course they never finish, and eight months later they still could not tell you what job they are qualified for.

So here is a fixed syllabus. Sixteen weeks, entirely free resources, no ambiguity about what to do next. Follow it in order.

Weeks 1 to 3: Linux and the command line

Nothing else on this list works without this foundation.

freeCodeCamp's Linux fundamentals content (YouTube) for the core commands, file permissions, and process management
Practice daily in a free-tier virtual machine or WSL, not just by watching

By the end of week 3 you should be comfortable navigating a server with no GUI, editing files in vim or nano, and managing basic services with systemctl.

# Daily practice habit, not optional
ssh into your VM every day, even for ten minutes
systemctl status <any-service>
journalctl -u <any-service> --since today

Weeks 4 to 6: Git and one programming language

freeCodeCamp again, this time for Python or JavaScript fundamentals
Git and GitHub, practiced by committing something daily, not just reading about branches

By week 6 you should have a GitHub profile with actual commit history, not a blank green square.

Weeks 7 to 10: Pick one cloud, go deep

This is the point where people scatter across AWS, Azure, and GCP at once and slow themselves down. Pick one.

AWS Skill Builder (free tier) if you are targeting the widest local hiring base
Google Cloud Skills Boost if your target companies run GCP
Microsoft Learn if you already know you are heading into a bank or an Azure shop

Whichever you pick, do the hands-on labs, not just the reading modules. Deploy something real: a static site, a small API, a database-backed app. Screenshot it working and write a short note on what you built and why.

Weeks 11 to 13: Containers and Kubernetes

KodeKloud's free YouTube content for Docker and Kubernetes fundamentals
TechWorld with Nana for the conceptual explanations that make Kubernetes click
Build a local cluster (Minikube or Kind) and deploy your week 7 to 10 project into it

# Minimum viable proof you understand the basics
kubectl get pods
kubectl describe pod <pod-name>
kubectl logs <pod-name>

By the end of week 13, you should be able to explain what a Pod, a Deployment, and a Service each do, and why you would use one over another.

Weeks 14 to 16: CI/CD and one real end-to-end project

GitHub Actions documentation and examples (free, and the most commonly used CI/CD tool for portfolio projects)
Wire your containerized app from weeks 11 to 13 into a pipeline: commit triggers build, build triggers deploy

This is the single most important project on the whole syllabus. One complete pipeline, end to end, on your GitHub, proves more than every certificate of completion combined.

What this syllabus does not include, on purpose

It does not include every free resource that exists. DigiSkills, NAVTTC, and the other government programs are worth exploring, but they overlap heavily with what is already listed here, and running two curricula at once is how people stall. Pick this syllabus or a government program, not both at the same time.

It also does not end with a certification, deliberately. This sequence builds the skill. What you do with it next, whether that is applying for jobs directly or adding a formal certification like the CKA to make the skill legible to recruiters, is a separate decision. If you finish this syllabus and want the credential that makes 80% of local Kubernetes job postings take you seriously, the full CKA certification prep guide for Pakistani engineers picks up exactly where week 16 leaves off.

The honest timeline

Following this syllabus at a genuine 10 to 12 hours a week, sixteen weeks gets you to a real, demonstrable skill level, not a finished career. Expect another few months of job searching and interview practice after that. It is slower than a paid bootcamp, and it costs nothing but the hours you put in.

This 16-week path is one route through it. I put together the complete list of every genuinely useful free program available in Karachi in 2026, government and vendor programs included, along with honest notes on where each one is weak, over here: "free IT courses in Karachi".

Where are you on this syllabus right now, and which phase has taken longer than you expected? Drop it in the comments. 👇

7 Questions to Ask Before Paying for an IT Course in Karachi

Sherdil IT Academy — Mon, 03 Aug 2026 07:18:20 +0000

Karachi does not have a shortage of IT courses. It has a shortage of good ones, buried inside a much larger pile of institutes selling outdated slide decks at bootcamp prices. With fees running anywhere from PKR 40,000 to 180,000 depending on the specialization, picking wrong is not a small mistake. It is months of time and real money.

I get asked "which institute should I join" often enough that I built a fixed checklist. It is not about brand names. It is seven questions that expose the difference between a course built for outcomes and a course built to fill seats.

1. Who is teaching, and are they still doing the work?

Ask for the instructor's current job title, not their job title from five years ago. Cloud, DevOps, and security move fast, and an instructor who has not touched a production system recently is teaching from memory, not from practice. A quick LinkedIn check settles this in two minutes.

2. Is the curriculum hands-on or slide-based?

Ask what percentage of class time is lab work versus lecture. For technical fields like AWS, Kubernetes, or cloud security, anything below 60 percent hands-on is a red flag. You are not paying to watch slides; you can get slides for free. You are paying for guided practice on real environments with someone there to unblock you when something breaks.

3. What do graduates actually build?

Ask to see finished student projects, not marketing testimonials. A real program produces a portfolio: a deployed app, a hardened cluster, a CI/CD pipeline someone can point to in an interview. If the institute cannot show you specific student work, they likely are not producing it.

4. Does the fee include the certification exam?

Certification vouchers (AWS, CKA, AZ-500) cost real money on top of the course itself. Some providers bundle the exam fee; many do not, and only mention that after you have paid. Get this in writing before you enroll, because it can add tens of thousands of rupees to what looked like a fixed price.

5. Is there any placement or interview support?

A course that ends the day the class ends is teaching, not career support. Ask specifically what happens after: mock interviews, resume review, referrals, or a portfolio review session. Programs that treat placement as part of the product, not an afterthought, tend to be run by people who actually track outcomes.

6. What is the batch size, and who answers questions?

A 60-person batch with one instructor means you are mostly on your own. Ask the actual student-to-mentor ratio, not the marketing number. This single detail predicts more about your experience than almost anything else on this list.

7. Can they show you a hiring outcome, specifically?

Not "our students get placed." Ask for a specific example: a name, a company, a rough timeline from course completion to offer. Vague claims are cheap to make. Specific, checkable ones are not.

Reading the answers together

No single answer disqualifies a provider on its own. But if you ask all seven and get vague or dodged answers on more than two or three, that is your answer. The Karachi IT training market has genuinely strong providers in it. It also has a lot of noise. This checklist is how you tell them apart before you pay, not after.

Where this actually leads

The reason to be this careful is that the destination is real. Cloud, DevOps, and especially cloud security remain some of the most underserved technical niches in Pakistan's job market right now, and the pay gap between a well-trained engineer and a self-taught one closes fast once you can prove hands-on skill. If security is the direction you are weighing, it is worth understanding [what the cloud security career path actually looks like in Pakistan][INTERNAL] before you pick a course, since the right training decision depends on which of those roles you are actually aiming for.

*I put the full picture together in one place: fee ranges by specialization, the specific in-demand courses for 2026, and a deeper breakdown of free versus paid options, over here: IT courses in Karachi for 2026.

Which of these seven questions have you never thought to ask before enrolling somewhere? Drop it in the comments. 👇

The Cloud Engineer Salary Negotiation Playbook (Pakistan, 2026)

Sherdil IT Academy — Thu, 02 Jul 2026 10:10:56 +0000

Most cloud engineers in Pakistan lose the salary negotiation before it starts, and not because their skills are weak. They lose it because they treat the offer as a fixed number instead of a set of levers. The recruiter says a figure, the engineer says "okay," and thousands of rupees a month quietly disappear.

This is the practical playbook I wish someone had handed me earlier: the numbers to anchor to, the levers that still move after the base is "locked," and the exact lines to say. No theory, no motivation. Just the mechanics.

Step 1: Anchor to the market, not your last payslip

The single most expensive mistake is anchoring your ask to your current salary. Employers love it when you do, because a 20 percent bump on a low base is still a low base. Anchor to what the role pays in 2026 instead.

Level	Monthly base (PKR)	Remote (USD/mo)
Junior cloud engineer	60,000 to 130,000	800 to 1,500
Mid-level cloud/DevOps	130,000 to 280,000	1,500 to 3,000
Senior / platform	280,000 to 550,000	3,000 to 6,000

Walk in with a range, state the top of it first, and back it with evidence: certifications, a GitHub portfolio, and specific things you have shipped. When you name a number, stop talking. Silence is a tool, not a gap you need to fill.

Step 2: Know your levers before the call

"The base is fixed" is almost never the end of the conversation. It just means the money moved somewhere else. Here is the full menu of what is actually negotiable, roughly in order of how often it works:

Signing bonus. One-time cost, off the recurring payroll line, so approvals are easier.
Performance review at 3 to 6 months with a pre-agreed raise band written into the offer.
Remote or hybrid days, which is real money once you price in commute and time.
Certification and training budget (AWS, CKA, Terraform). Ask them to pay the exam fees.
Annual leave and flexible hours.
Title. A better title compounds into every future offer you ever get.
Equipment allowance for a laptop and a home-office setup.

The point: if you only negotiate base, you are playing one square on a board that has eight.

Step 3: The scripts

You do not need to be aggressive. You need to be specific and calm. Here are lines you can adapt word for word.

When they ask your expected salary first:

"Based on the market range for this role and my experience with [AWS, Kubernetes, Terraform], I am targeting PKR [top of your range]. I am open to discussing how we structure that."

When they say the base is fixed:

"I understand the base is set. In that case, can we look at a signing bonus and a documented performance review at six months? If the base cannot move now, I would like a clear path for it to move soon."

When they lowball you:

"That is below what I have seen for this scope of work in 2026. Help me understand what is driving the number, and let us see where there is room, whether that is base, bonus, or review timing."

When you already have another offer:

"I have another offer on the table, and I would genuinely prefer to work here. If we can close the gap on [base / bonus / remote days], I am ready to sign."

Never invent a competing offer you do not have. It is easy to get caught, and it ends the relationship. If you have one, use it plainly. If you do not, lean on the market data instead.

Step 4: Do the total-comp math

Two offers with the same base are rarely equal. Compare the whole package, not the headline number.

Lever	Offer A	Offer B
Monthly base	200,000	190,000
Signing bonus	0	150,000
Remote days/week	0	3
Cert budget	0	100,000/yr
6-month review	No	Yes

Offer B has the lower base and is clearly the stronger deal once you add the bonus, the saved commute, and the funded certifications. This is exactly the math most engineers skip, and it is where quiet money hides.

Step 5: Get it in writing

A verbal "we will sort the raise out later" is worth nothing. Once you agree on the terms, ask for the offer letter to state the base, the bonus, the review date, and the raise band. If it is not written, it did not happen. Polite, firm, and documented wins every time.

The mindset shift

Negotiating is not being difficult. Every good manager expects it, and many quietly respect the engineers who do it well because it signals you will advocate for the team and the budget too. The engineers who stay underpaid in Pakistan are almost never the least skilled. They are the ones who never ran the play.

I put the full framework, including the complete lever checklist, more scripts for tricky moments, and the total-comp calculator, into a Pakistan-specific guide over here: how to negotiate a cloud engineer salary in Pakistan.

What is the one lever you have never tried to negotiate: bonus, review timing, or remote days? Drop it in the comments. 👇

The Cloud Security Toolchain Every Engineer Should Know (2026)

Sherdil IT Academy — Sat, 27 Jun 2026 11:09:58 +0000

Cloud security interviews don't reward people who can define the shared-responsibility model. They reward people who've actually run the tools. So instead of theory, here's the practical toolchain I'd expect a working cloud security engineer to be comfortable with in 2026 - grouped by where it sits in the pipeline.

(Quick note on why this skill set is worth building: in markets like Pakistan, cloud security is currently the most underserved technical niche - regulators are forcing banks and fintechs to staff it, and the salary premium reflects how few people can actually do the work.)

1. Catch misconfigurations before they ship (IaC scanning)

Most cloud breaches start as a misconfiguration in a Terraform file, not a zero-day. Scan infrastructure-as-code in CI before it ever reaches an account:

Checkov
tfsec
Terrascan

# Scan a Terraform directory with Checkov
checkov -d ./infra

# Scan the same directory with tfsec
tfsec ./infra

Wire one of these into your pipeline so a misconfigured security group fails the build instead of reaching production.

2. Secure the containers and the cluster

Two different jobs here: scanning images for known vulnerabilities, and watching runtime behaviour.

Image scanning - Trivy, Snyk:

# Scan a container image for vulnerabilities
trivy image myorg/payments-api:latest

Runtime threat detection — Falco watches for suspicious syscalls inside running containers (a shell spawned in a container, unexpected writes to sensitive paths, etc.).

Kubernetes hardening is its own competency: RBAC done properly, PodSecurityAdmission, and NetworkPolicies to stop flat east-west traffic. If everything in your cluster can talk to everything else, you don't have segmentation — you have a single blast radius.

3. Stop hardcoding secrets

Secrets in env files and Git history are still one of the most common findings. Manage them properly:

HashiCorp Vault for dynamic secrets and central policy
Kubernetes Secrets with encryption at rest enabled (it isn't on by default in every setup - check)

4. Use the cloud's native detection (it's already there)

Each major cloud ships strong detection tooling that teams routinely leave half-configured:

AWS - GuardDuty, Security Hub, Macie, CloudTrail, Config
Azure - Defender for Cloud, Sentinel, Azure Monitor
GCP - Security Command Center

Knowing how to turn these on, tune the noise, and route findings somewhere a human will see them is a genuinely marketable skill.

5. The non-tool skill that ties it together: IAM

Every item above sits on top of identity. If your IAM policies are sloppy - wildcards everywhere, long-lived keys, no least-privilege - no scanner saves you. Designing tight IAM policies and understanding the shared-responsibility model is the core competency hiring managers probe hardest, because it's the one you can't fake with a dashboard.

Where this leads (the part that pays)

Put this toolchain together with real hands-on practice and you're qualified for roles that are, frankly, underfilled. Typical 2026 ranges in the Pakistani market:

Role	PKR/month	Remote (USD)
Cloud Security Engineer	150,000-320,000	$1,500-$3,000
DevSecOps Engineer	180,000-380,000	$2,000-$3,800
Cloud Security Architect	350,000-700,000	$3,500-$6,000

The fastest way in, if you already have 1-2 years of cloud/DevOps experience, is about 4–8 months of focused work on exactly the tools above - and it tends to lift your salary 25-40%. Build a GitHub portfolio with real security scenarios; that beats any certificate on its own.

I wrote a full, Pakistan-specific career breakdown - all seven cloud-security role types, the certification order and costs, and the three entry paths - over here: Cloud Security Careers in Pakistan.

Which of these tools is already in your pipeline, and which one are you avoiding? Drop it in the comments. 👇

How I'd Pass the CKA in 12 Weeks (Performance-Based, No Multiple Choice)

Sherdil IT Academy — Tue, 09 Jun 2026 12:16:17 +0000

The Certified Kubernetes Administrator (CKA) is not a multiple-choice exam, and that single fact changes everything about how you should prepare for it. There's no bluffing, no "process of elimination," no memorizing a question bank. You get 2 hours, 15–20 tasks, and a live Kubernetes cluster, and you need 66% to pass.

If you're a DevOps or platform engineer sitting this exam, here's the 12-week, lab-first plan I'd follow — plus the exam-day setup that quietly saves you the most time.

What you're actually walking into

The domains are weighted, and the weighting tells you exactly where to spend your hours:

Domain	Weight
Troubleshooting	30%
Cluster Architecture & Installation	25%
Services & Networking	20%
Workloads & Scheduling	15%
Storage	10%

Troubleshooting is the highest-weighted domain at 30% — and it's the one most candidates underestimate. You can't grind it with flashcards; you have to break clusters and fix them until CrashLoopBackOff, NodeNotReady, and broken DNS stop scaring you.

The exam costs $395 (~PKR 110,600) and includes one free retake within 12 months. It tests your ability to work efficiently with the docs, not to memorize every YAML field — but the clock is real.

The 12-week, lab-first plan

Target ~180–200 hours total: 2–3 hours on weekdays, 5–6 on weekends. The ratio that matters most: 20% concept review, 80% hands-on labs.

Weeks	Focus	Lab goal
1–2	Core architecture: Pods, ReplicaSets, Deployments, Namespaces, kubectl	Deploy 10+ apps via CLI only
3–4	Workloads & scheduling: limits, taints/tolerations, affinity, DaemonSets, CronJobs	Schedule pods on specific nodes; set resource quotas
5–6	Services & networking: ClusterIP, NodePort, LoadBalancer, Ingress, NetworkPolicies, CoreDNS	Configure Ingress with TLS; write a NetworkPolicy
7–8	Storage: PVs, PVCs, StorageClasses, access modes	Provision storage for a stateful app; resize a PVC
9–10	Cluster architecture: kubeadm init/join, RBAC, etcd backup/restore, certs	Build a multi-node cluster; back up and restore etcd
11	Troubleshooting: NotReady nodes, CrashLoopBackOff, DNS, apiserver failures	2 Killer.sh exams, target 70%+ each
12	Full timed simulation across all domains	2 Killer.sh + 1 KodeKloud mock

The resources that are actually worth it

Non-negotiable:

KodeKloud CKA course + labs — the best structured prep available. Pro is ~$16/mo; two months is enough.
Killer.sh simulator — two free full-length sessions come with your exam registration. It's harder than the real thing on purpose. Widely regarded as the most accurate simulation.
Official Kubernetes docs (kubernetes.io/docs) — allowed during the exam, but you won't have time to read pages end-to-end. Practice navigating them fast.

Skip: brain-dump sites, video-only prep with no labs, and theory without timed practice.

Exam-day setup (do this in the first 2 minutes)

Before touching a single task, configure your environment. These shortcuts pay for themselves many times over:

# Alias kubectl -> k
alias k=kubectl

# Dry-run template generator
export do='--dry-run=client -o yaml'

# Now you can scaffold YAML instead of typing it by hand:
k create deployment web --image=nginx $do > web.yaml

And set up vim for clean YAML editing:

" ~/.vimrc
set expandtab
set tabstop=2
set shiftwidth=2

The single most expensive mistake people make: forgetting to switch cluster context. Every question specifies its cluster. Do this first, every time:

kubectl config use-context <cluster-name>

Then work the exam strategically:

Read all tasks first (~3–4 minutes) and prioritise by weight.
Generate YAML with --dry-run=client -o yaml instead of writing it from scratch.
Flag and skip anything you get stuck on — come back later.
Verify before moving on: kubectl get, kubectl describe, kubectl logs.

One Pakistan-specific note: book a Pearson VUE test centre if you can. Remote proctoring needs a stable 5 Mbps+ line, a webcam, and a clean private room — test your home connection at your exam time a few days ahead, and have a different-carrier mobile hotspot as backup.

Is it worth the PKR 110,600?

For the Pakistani market in 2026, yes — the salary data is hard to argue with:

Role	Without CKA	With CKA	Uplift
DevOps (mid)	PKR 120–180K	PKR 180–280K	30–40%
Platform/K8s (mid)	PKR 200–320K	PKR 320–550K	40–50%
Platform/K8s (senior)	PKR 350–500K	PKR 500–800K	25–30%

And the remote ceiling is higher still: a CKA-certified engineer with 3–4 years of hands-on Kubernetes can realistically target $2,000–$3,500/month remote — roughly PKR 700,000/month at $2,500. Plenty of engineers have some Kubernetes experience; far fewer have the breadth the CKA forces you to build.

The honest prerequisite check

Don't book it yet if you have no Linux command-line comfort or zero hands-on infrastructure exposure — the CKA assumes both. If you're a pure app developer with no infra interest, look at the CKAD instead. But if you've got 1–2 years of Docker/CI-CD/Linux under your belt, 12 disciplined weeks is enough.

I wrote a full, Pakistan-specific breakdown of this — payment methods that work with local cards, a deeper resource tier list, and the complete week-by-week labs — over here: the complete CKA certification guide for Pakistani engineers".

What tripped you up most in your CKA prep — troubleshooting speed, or just finishing in time? Drop it in the comments. 👇