Challenge on ,
Reach a Distroless Container's Debug Endpoint From a Sidecar Container
A distroless container serves a debug interface on its own loopback address. Can you reach this debug endpoint using nothing but standard Docker commands?
Challenges
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.
Challenge on ,
Call an HTTP API with curl: Creating, Updating, and Deleting Resources
Practice calling HTTP APIs from the command line: send JSON bodies with POST, PUT, and PATCH, upload a file, delete a resource, and read the status codes the server answers with.
Challenge on ,
Identify the Source of Unexpected Requests in an On-Prem Network
An internal service started receiving requests from unexpected IP addresses. Identify the unexpected sources and find out which systems are behind them.
Challenge on ,
Copy Config Files from a Running Pod
by Omkar Shelke
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.
Challenge on
Automate Drive Provisioning With a Shell Script
Turn the manual storage provisioning workflow into an automation script: partition, format, mount, and persist a blank drive with a single non-interactive script.
Challenge on ,
Extend kubectl with a Custom Image-Inspection Plugin
by Omkar Shelke
A helper script that lists every container image running in the cluster — along with its on-disk size and the workload that uses it — has been downloaded to cplane-01. Install it as a kubectl plugin named kubectl-images so that kubectl images works from any directory.
Challenge on ,
Write a C Program Without a main() Function
by Başar Subaşı
Produce a valid ELF binary that runs and exits cleanly, but does not define a main() function.
Challenge on ,
Reach a Remote Loopback Port Through an SSH Jump Host
An inventory service lives inside a private VPC and keeps its debugging port bound to 127.0.0.1. Use SSH local port forwarding with a jump-only bastion to query the debugging port from your workstation.
Challenge on ,
Reach Internal Servers Through a "No Shell" SSH Bastion
The application fleet lives inside a private VPC, reachable only through a locked-down bastion that refuses to give you a shell. Find a way to jump through the bastion and place a maintenance lock on two misbehaving servers.
Challenge on ,
Reach a Private VPC Service Through an SSH Bastion
A production search cluster lives inside a private VPC and is reachable only from within it. Use SSH local port forwarding through a public-facing bastion host to query the cluster's API from your dev machine.