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 Go service that has always been shipped as a static binary in a scratch-y image suddenly fails to start in a container, while the local build works as before. Find what recent changes caused it and fix the image without reverting them.
A distroless pod running in the cherry namespace has no shell or debugging tools. Use kubectl debug to attach an ephemeral container, test connectivity to the request-logger service, and verify the request was received in its logs.
Leverage your knowledge of Linux namespaces to reach an application's internal debug interface without installing anything into the container.
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?
Can you edit a file in a running container? What if there is no shell?
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?
Not all distroless images are created equal. Can you find the right base image for the application in this challenge?
Learn on practice the limitations of FROM scratch images and the ways to mitigate them.
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 a Kubernetes app running in an unprivileged container without shell.
