Identify the Source of Unexpected Requests in a Kubernetes Cluster
An internal service started receiving requests from unexpected IP addresses. Identify the unexpected sources and find out which workloads and teams are behind them.
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.
An internal service started receiving requests from unexpected IP addresses. Identify the unexpected sources and find out which workloads and teams are behind them.
The production Kubernetes cluster lives inside a private VPC, and its API server has no public endpoint. Turn an SSH connection to the bastion host into a SOCKS proxy and teach kubectl to use it, so the cluster becomes manageable from your workstation.
Use Kubernetes image volumes to mount a static HTML artifact into an nginx Pod without an init container or a custom nginx image.
Practice configuring Kubernetes to pull images from a private registry and run Pods with authenticated registry access.
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.
Hack your way through this challenge making the OOM kills invisible again.
Prove your SRE skills - deploy a resource-greedy application to a Kubernetes cluster and make it run for a while without disrupting the service.
An ultimate Kubernetes troubleshooting challenge: can you copy files to/from a running Pod that doesn't have a shell or other command line tools installed?
Practice copying files to/from running Kubernetes Pods to become a Kubernetes troubleshooting ninja.
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?