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 new intern learning about probes wrote a small Pod manifest. The exec command and the application are both correct, but the Pod never becomes Ready because one probe parameter is missing. Find it and add it.
Every kubectl command against a kubeadm cluster fails, and the workload is still serving. With no API to query, the usual tools tell you nothing. Work from the node itself to find what broke and bring the control plane back.
A new service needs to run in your development environment, but the port it requires is already in use by another app that has to keep working. Diagnose the conflict, free the port without taking the other app down, and get both services running side by side - a realistic exercise in untangling local port conflicts.
A daemon exposes a Unix domain socket that every local user can talk to. Protect it so that only root and members of a dedicated group may connect - the same way Docker restricts access to /var/run/docker.sock.
A deployment is failing because the application cannot load its TLS certificate. Create the missing secret and mount it into the deployment so the Flask app can serve TLS traffic.
A Pod is failing in the japan namespace. Investigate the issue, identify the root cause, and fix it to get the Pod running.
Two monitoring applications are failing due to missing RBAC permissions. Fix both by creating ServiceAccounts, Roles, and RoleBindings.
A Deployment is failing because its ServiceAccount lacks permissions to list pods. Fix the issue by binding an existing Role to the ServiceAccount.
Debug and fix a Pod that fails to deploy due to resource constraint violations in a namespace with ResourceQuota and LimitRange policies.
This challenge focuses on debugging memory usage issues in a Go application deployed in a Kubernetes cluster. The goal is to ensure the application can handle moderate traffic without crashing, even when it runs with significantly constrained memory resources.
