Focused, hands-on problems for sharpening your DevOps and server-side skills. Some teach specific concepts while others mirror real-world scenarios. Every challenge includes hints, feedback, and automated solution checks.
node-02 is back from a kernel upgrade but still shows Ready,SchedulingDisabled, and the Pods that can only run on it are stuck in Pending. Bring the node back into service and get the workload running, without touching the workload itself.
A storefront needs eight replicas, and the platform team wants them split down the middle between the two availability zones. An uneven split must be refused by the scheduler rather than quietly tolerated.
Create a PriorityClass for production workloads and patch an existing deployment to use it, ensuring critical services get scheduled first during resource contention.
Deploy a multi-container Kubernetes Deployment and ensure that no more than one Pod runs on the same worker node, without using a DaemonSet.
Troubleshoot and update a Kubernetes DaemonSet so that its Pods run on all nodes in the cluster, including the control plane.
Create a CronJob, trigger Jobs manually, limit job history, suspend the schedule, and observe all three concurrencyPolicy modes: Allow, Forbid, and Replace.
Start with nodeSelector for simple node targeting, then upgrade to node affinity for expressive matching that nodeSelector cannot handle.
Use LimitRange to set per-pod resource defaults and ResourceQuota to cap total namespace consumption.
See how Kubernetes determines BestEffort, Burstable, and Guaranteed classes from resource configuration - and which pods get evicted first under pressure.
See how CPU and memory requests influence where pods land - and what happens when no node can fit them.
