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.
Challenges crafted by iximiuz Labs to help you master DevOps and Server Side topics.
Turn the manual storage provisioning workflow into an automation script: partition, format, mount, and persist a blank drive with a single non-interactive script.
A newly provisioned server is reachable as root with a shared seed password. Create a sudoer admin user, switch SSH to key-based access, disable password and root logins, and retire the seed credential.
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.
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.
Challenges from outstanding independent authors proudly hosted by iximiuz Labs.
Did you know that pods can become invisible? Can you figure out how?
In this challenge, you’ll debug and fix a deliberately “broken” eBPF program, then prove it’s running by identifying its program and map IDs. Along the way, you’ll explore bpftool, check which helpers are supported, and dig into details like the UID of the loader. Finally, you’ll test your knowledge of eBPF maps by recalling the flag that only inserts a key if it doesn’t already exist.
Get hands-on with reading secrets from different providers and using them in your Dagger pipelines.
Challenges contributed by the community members sharing their knowledge and expertise.
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.
Export an Alpine container rootfs using crane, set up a chroot environment, and execute a musl-linked binary that fails to run on the host system.
Build a StatefulSet with a headless Service, watch ordered Pod creation, verify per-replica PVC naming, scale down and back up, prove stable identity, then roll an image update and roll back using ControllerRevision history.
The cluster is broken again. Get the Klustered deployment healthy and serving a quote, then ship the v2 image to unlock the victory dance.
