29 — The 10-Day Confidence Sprint: Revise · Do · Prove¶
Ye chapter kab padhen: Jab concepts clear ho chuke hain aur ab haath ka bharosa (confidence) chahiye — real project pe karke, recall karke, bol ke. Ye 27 — 10-Day Learning Plan ka agla step hai.
- 27 — Learning Plan = pehli baar — restaurant analogy se sab connect karo (understand).
- 29 (yeh) — Confidence Sprint = dusri baar — padhna band, karo + recall karo + bolo (drill).
The one honest truth about this sprint¶
Tera content gap mein nahi hai — execution mein hai.
Is handbook mein 28 module hain: recall gates, flashcards, incident playbook (26 issues), 2 capstones, chaos engineering. Ye kisi paid bootcamp se behtar hai. Par agar progress.md ke checkbox untick hain aur spaced-review log khaali hai — to matlab padha bahut, drill nahi kiya. Aur confidence content se nahi, reps se aata hai.
Ye 10 din isi ek cheez ke liye hain: har concept ko apne do real projects pe karo — VANTA-Boutique (kind, local) aur Billfree-techops (AWS, production) — padho mat, karo.
Before Day 1 — dono projects chalte hue chahiye
Ye sprint maanta hai ki VANTA aur Billfree tumhare paas clone + running hain. Agar nahi: pehle Lab A · BillFree ke Part 1–3 (clone → local run → Docker) aur Lab B · VANTA ka kind-cluster setup karo — wahi guided path hai in repos ke liye. Bina running project ke sprint "padhna" ban jaayega — exactly jo hum avoid kar rahe hain.
🎨 Visual dashboard
Isi sprint ka ek interactive, daily-open dashboard bhi hai: 10_Day_Confidence_Sprint.html (repo root). Roz kholo, aaj ka din expand karo, 3 lanes karo, tick karo. Ye chapter reference + progress tracking ke liye; wo daily driver ke liye.
Gap analysis — saaf baat (jo actually gaps hain)¶
| Bucket | Kya | Sprint mein |
|---|---|---|
| ✅ Poora + gehra | Linux, Git, Docker, K8s core+config+storage, CI/CD, GitOps, Helm, Kustomize, Terraform, Ansible, Observability, Incident playbook, Chaos | Bas drill karo |
| ⚠️ Patla (concept hai, hands-on kam) | Secrets maturity (Vault / SealedSecrets / External Secrets), Service mesh (Istio/mTLS), Azure/AZ-900 | Ek mini-lab / abhi optional |
| ⏭️ Abhi skip (10-din ke baad) | Roadmap M11–M18 — progressive delivery, supply-chain security, distributed systems | Baad mein |
🇮🇳 Hinglish intuition: Tere paas gadi (content) already hai — bas chalayi nahi. Ye sprint driving lessons hai, nayi gadi kharidna nahi.
Har din ka format — 3 lanes¶
Har din yehi teen lanes, isi order mein. Kabhi sirf padho mat.
| Lane | Time | Kya |
|---|---|---|
| ↩️ Revise | ~15 min | Us din ke chapter ka recall gate memory se — dobara padho nahi, dobara nikaalo. Yehi active recall hai (spaced-review system). |
| ▸ Do | 60–90 min | Terminal kholo. VANTA/Billfree pe actual commands. Todo, banao, badlo. Haath se — koi tumhare liye execute na kare. |
| ✅ Prove | ~15 min | Blank page pe diagram banao, ya loud bolo jaise interview mein. Atka? Wahi kal ka revise. |
The 10-day map¶
flowchart LR
D1["Day 1\nLinux·Git·Docker"]:::a
D2["Day 2\nK8s Core"]:::a
D3["Day 3\nConfig·Secret·Storage"]:::b
D4["Day 4\nNetworking"]:::c
D5["Day 5\nCI/CD"]:::c
D6["Day 6\nGitOps·Helm"]:::d
D7["Day 7\nTerraform·Ansible"]:::e
D8["Day 8\nObservability"]:::b
D9["Day 9\nBreak & Fix"]:::e
D10["Day 10\nEnd-to-end + Interview"]:::c
D1-->D2-->D3-->D4-->D5-->D6-->D7-->D8-->D9-->D10
classDef a fill:#e8f5e9,stroke:#2e7d32,color:#1b5e20
classDef b fill:#fff3e0,stroke:#e65100,color:#bf360c
classDef c fill:#e3f2fd,stroke:#1565c0,color:#0d47a1
classDef d fill:#f3e5f5,stroke:#6a1b9a,color:#4a148c
classDef e fill:#fce4ec,stroke:#880e4f,color:#880e4f
Day 1 — Fundamentals drill: Linux · Git · Docker¶
zameen pakki karo
- 21 — Linux toolkit + 04 — Docker ke recall gates, memory se
- Ek line: image vs container vs registry vs layer?
- VANTA: frontend ka Dockerfile padho →
docker build→docker run→ browser docker exec -it <id> sh— andar ghuso, files/env dekho- Linux debug drill:
top,df -h,ss -tlnp,journalctl,tail -f - Git: branch banao → change → commit → merge →
git log --oneline
- Blank page:
Dockerfile → build → image → run → containerflow likho - Loud bolo: "layer caching se rebuild fast kaise hota hai?"
📖 21-linux-toolkit · 04-M3-docker · 22-command-cheatsheets
Day 2 — Kubernetes Core: self-heal, scale, rollout¶
cook + manager + counter
- 05 — K8s Core + 26 — Objects map recall gates
- Pod vs ReplicaSet vs Deployment — kaun kya, labels ka role?
- VANTA (kind ready hai):
kubectl get pods,deploy,svc,rs -L app— label flow dekho - Self-heal:
kubectl delete pod <frontend-pod>→ khud wapas aata hai - Scale:
kubectl scale deploy frontend --replicas=4→ watch - Rollout: image badlo →
kubectl set image→kubectl rollout status→kubectl rollout undo
- Blank page: self-heal loop (desired vs actual → controller → new pod)
- Loud: "rolling update mein zero downtime kaise?"
📖 05-M4-kubernetes-core · 26-k8s-objects-map
Day 3 — Config · Secret · Storage: break & fix¶
masala + pantry
- ConfigMap vs Secret vs PVC — kab kaun? (visual:
Helm_ConfigMap_Secret_Init_samjho.html)
- VANTA: ek ConfigMap banao, frontend env usse inject karo, restart, verify
- Secret banao
kubectl create secret generic→ Pod meinsecretRef - Billfree: postgres StatefulSet +
volumeClaimTemplatespadho — PVC lifecycle - Break: galat secret key do → Pod fail →
describe/logsse fix
- Loud: "Secret Git mein kyun nahi? base64 encryption kyun nahi?"
- Pod restart pe PVC ka data kyun bacha rehta hai — samjhao
📖 05-M4-kubernetes-core (config/storage) · 11-M9-advanced-k8s-internals
Day 4 — Networking: Service · Ingress · DNS · NetworkPolicy¶
request → pod tak
- Service 4 types, CoreDNS, kube-proxy, Calico
- VANTA: pod-to-pod — ek pod mein
exec→wget cartservice:7070— DNS se baat kubectl get svc,endpoints— Service ke peeche kaunse pod IPs- Billfree: ingress-nginx + host/path routing padho; NetworkPolicy yaml
- Break: Service ka selector label galat karo → traffic gir jaye → fix
- Blank page: User → DNS → Ingress → Service → Pod — poora hop draw
- Loud: "Calico vs Service — kaun packet ko kahan pahunchata?"
📖 11-M9-advanced-k8s-internals · 20-confusions-and-tradeoffs
Day 5 — CI/CD: follow one commit¶
test kitchen
- CI vs CD, runner, image tag handoff, Trivy scan — kyun zaroori
- Billfree:
.github/workflowspadho — test → build → push → tag update - Ek chhota code change → push → GitHub Actions run live dekho
- Trace: image kahan build/push hui, config repo mein tag kaise badla
- VANTA (local):
docker build→kind load→kubectl set image
- Loud: "CI cluster ko touch kyun nahi karta? handoff kahan hai?"
- Blank page: git push → … → running pod (har box likho)
📖 07-M6-cicd · 19-cicd-hands-on-flow
Day 6 — GitOps + Helm: ArgoCD sync & drift¶
manager + meal deal
- Pull vs push CD, auto-sync, self-heal, prune; Helm chart vs values (visual:
Helm_ConfigMap_Secret_Init_samjho.html)
- VANTA: ArgoCD
kindpe install → Application connect → sync dekho - Drift test:
kubectl scalese manually badlo → ArgoCD wapas Git jaisa kar de - Billfree: Helm chart + values structure padho;
helm templatese rendered YAML - ApplicationSet + app-of-apps pattern samjho
- Loud: "rollback GitOps mein kaise? (git revert)"
- Kustomize vs Helm — ek line mein farak
📖 08-M7-gitops · 28-helm-real-projects
Day 7 — Outer loop: Terraform · Ansible · AWS¶
building banao
- IaC kyun, state file, plan-before-apply, idempotency, push vs pull
- Billfree:
infra/terraformpadho — compute, network, cloud-init (kubeadm) terraform planchalao — kya banega, state kya kehti hai- Safe lab: ek S3 bucket
apply→ verify →destroy - Ansible playbook padho — nodes pe kya configure hota (containerd, kubeadm)
- Loud: "Terraform → Ansible → K8s — kaun kya banata, handoff kahan?"
- tfstate delete ho jaye to kya hota — samjhao
📖 02-M1-terraform · 03-M2-ansible · 06-M5-sizing-and-cost
Day 8 — Observability & SRE: 2 a.m. drill¶
health inspector
- RED vs USE metrics, logs vs metrics vs traces, SLO/alert
- VANTA:
kube-prometheus-stackHelm se install → Grafana port-forward - 4 dashboards: compute, networking, node-exporter, ArgoCD
- Billfree: ServiceMonitor + PrometheusRule padho — thresholds (error 5%, p95 1s)
- Load daalo (loadgenerator) → CPU/latency graph move karte dekho
- Loud: "app slow hai — main pehle kya dekhun, kis order mein?"
Day 9 — Break & fix: Incident + Chaos¶
yahi confidence deta hai
- Debug order:
describe→ events →logs --previous→ root cause - Exit codes: 137 (OOM/SIGKILL), 1, 0 — kya matlab
- VANTA — CrashLoop: liveness timeout 1s karo → CrashLoop → diagnose → fix
- OOMKilled: memory limit bahut kam karo → 137 → badhao
- ImagePullBackOff: galat image tag → describe se pakdo
- PVC Pending / Service no endpoints: playbook ke 26 issues mein se 5 chuno
- Har issue: symptom → diagnose command → fix → prevent — likho
- Ye war-stories interview mein sona hai
📖 23-production-incident-playbook · 25-production-gauntlet-chaos
Day 10 — Grand opening: end-to-end + interview¶
sab jodo, bolo
- 09 — Connected System: 2 loops + 8 bridges + 5 golden threads
- Billfree: ek chhota change → push → CI green → ArgoCD sync → Grafana check — poora flow ek baar khud
- VANTA + Billfree dono ka README/docs polish — portfolio ready
- Blank page (no notes): 2 loops + 8 bridges + 5 threads draw karo
- Whiteboard talk: "git push se user tak" 10 min bolo, loud
- STAR stories: VANTA aur Billfree se 3 real "maine kya kiya" answers likho
📖 09-connected-system · 14-interview-bank · 18-career-job-ready
Har din chalta rahega — the recall habit¶
🔁 5-min daily recall (ye chhodna mat)
| Kab | Kya |
|---|---|
| Subah | Kal wale din ka recall gate — memory se, 5 min |
| Din mein | Aaj ka Do lane — haath se, terminal pe |
| Raat | 17 — Flashcards — us din ke module ke, 5 min |
| progress.md | Aaj ke checkbox tick karo — dikhta progress hi motivation hai |
10 din baad — "confident" ka matlab¶
- Padha nahi — kiya. Har din progress tick hua, har concept apne project pe chala.
- Recall aaya. Blank page pe 2 loops + 8 bridges bina notes ke bana sakte ho.
- Bol sakte ho. "git push se user tak" 10 min whiteboard pe, + VANTA/Billfree ki 3 STAR stories.
- Toota, phir theek kiya. CrashLoop/OOM/502 khud banaye aur fix kiye — yehi "2.5-saal experience" dikhna hai.
🇮🇳 Final baat: Ye sprint ka maqsad naya seekhna nahi — jo aata hai use haath aur zubaan mein laana hai. Har din: revise karo (memory), karo (terminal), prove karo (blank page + loud). 10 din baad tum confident nahi mehsoos karoge — confident hoge.
Connected pages: 27 — 10-Day Learning Plan (conceptual) · 09 — Connected System · 23 — Incident Playbook · 17 — Flashcards · progress.md