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 Deployment is running in the platform namespace with 3 replicas. Each pod has configuration files at /app/config/. Copy those files to /home/laborant/config/ on the local machine.
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.
Update a production NGINX ConfigMap to restrict TLS to v1.3 only, then verify the change enforces the security policy.
Combine an existing ConfigMap and Secret into one volume and mount them at a single path inside a Pod — using only one volume definition.
A Deployment is stuck with Pods in ContainerCreating state because the required ConfigMap was not created. Fix the issue to make the application accessible.
A Deployment is failing because application configuration is missing. Mount only specific keys from an existing ConfigMap as files inside the Pod at the correct path so the application can start successfully.
A Pod is failing in the japan namespace. Investigate the issue, identify the root cause, and fix it to get the Pod running.
Create a Pod with ConfigMap volume mount, expose it via ClusterIP Service, and test connectivity from another namespace. This combines multiple Kubernetes concepts.
Create a ConfigMap, mount it into a Deployment as individual files, and validate the mounted values using a readiness probe.
Inject ConfigMap values as environment variables into a Kubernetes Pod.