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.
A Job manifest at /home/laborant/batch-job.yaml is exiting with a non-zero exit status. The Job has limited retries configured. Inspect the cluster and the manifest to find the bug, fix it, and reapply.
A webapp deployment in the prod namespace is stuck in CrashLoopBackOff. The application's startup probe checks that its existing config directory is intact before the container is marked healthy. Fix the deployment so configuration is injected correctly and the pod reaches Running state with its health check endpoint responding on port 8080.
A Deployment is stuck with Pods in ContainerCreating state because the required ConfigMap was not created. Fix the issue to make the application accessible.
Troubleshoot and update a Kubernetes DaemonSet so that its Pods run on all nodes in the cluster, including the control plane.
A web application is deployed but the website is not accessible. Investigate and fix the issue.
An ultimate Kubernetes debugging challenge: can you copy files to/from a running Pod that doesn't have a shell or other command line tools installed?
Practice copying files to/from running Kubernetes Pods to become a Kubernetes troubleshooting ninja.
Can you edit a file in a running Kubernetes pod? What if there is no shell inside and the container's user lacks the write permission?
Be a networking Sherlock Holmes - find out which port a Kubernetes app uses and send a request to it.
Learn how to send a signal to an application running as a Kubernetes pod.
