Build · shipped
30 Days of Kubernetes (CKAD) — Day 01: Exam Environment, Kind on Linux & Fast CLI Setup
Day 01 of the 30-day CKAD hands-on series: setting up your Kind cluster on Linux (Minerva), Killercoda cloud sandbox, and imperative kubectl speed aliases.
Welcome to Day 01 of the 30-Day Kubernetes & CKAD Learning Series. Over the next 30 weekdays, we will cover every domain of the Certified Kubernetes Application Developer (CKAD) exam with a mix of concise architectural lessons and hands-on labs you can run locally on Linux (kind or k3s) or in a free browser sandbox.
1. The Lab Setup: Local Linux (kind) vs. Cloud Sandboxes
Local Linux (Minerva Node)
If you have Docker and kind installed on your Linux workstation, you can spin up a realistic 3-node cluster (1 control-plane + 2 workers) in under 45 seconds:
source labs/k8s-30-days/scripts/ckad-aliases.sh
./labs/k8s-30-days/scripts/minerva-kind-up.sh
Cloud Sandboxes (Zero Setup)
When away from your local Linux box, use a real browser-based Kubernetes terminal:
- Killercoda CKAD Playground: https://killercoda.com/areas/ckad
- Killer.sh (Official CKAD Simulator): 2 free timed sessions included with your exam registration.
2. CKAD Speed Setup (Muscle Memory)
You have 2 hours for ~15–20 performance-based tasks. Typing kubectl and hand-authoring boilerplate YAML will burn your clock. Set these three shortcuts at the start of every session:
alias k=kubectl
export do="--dry-run=client -o yaml"
export now="--force --grace-period=0"
Why $do and $now Matter
- Generate YAML instantly:
k run my-pod --image=nginx:1.27-alpine $do > pod.yaml - Delete stuck Pods immediately (skip the 30-second graceful termination wait):
k delete pod my-pod $now
3. Hands-On Lab: Day 01
Navigate to labs/k8s-30-days/day-01/ in the dforge repo and complete the exercise:
- Create a namespace named
ckad-day01imperatively. - Create a Pod named
fast-nginxinsideckad-day01using imagenginx:1.27-alpine, exposing port80, with labelsapp=web,tier=frontend. - Validate your solution:
./labs/k8s-30-days/day-01/verify.sh
Expected Result: PASS: Day 01 verification complete!