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.
Challenges contributed by the community members sharing their knowledge and expertise.
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.
Use LimitRange to set per-pod resource defaults and ResourceQuota to cap total namespace consumption.
Use PriorityClass to guarantee critical pods get scheduled even when the cluster is under resource pressure.
See why taints and tolerations alone or node affinity alone are not enough to fully control pod placement on dedicated nodes.
Learn how to taint a node, schedule a Pod using nodeSelector and tolerations, and share the host network, PID, and IPC namespaces with the Pod.
A Kubernetes cluster has an existing database Deployment running. Configure a new web Deployment to schedule its pods only on nodes where the database pods are already running using required pod affinity.
A Kubernetes cluster has tainted nodes to restrict pod scheduling. Configure a Deployment to schedule pods exclusively on a specific tainted node using both tolerations and required node affinity.
