Kubernetes Challenges 🏆

This exercise tests your ability to safely upgrade a multi-node Kubernetes cluster from version 1.30 to 1.31 following the standard upgrade procedure.

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.

This exercise tests your ability to configure kubernetes network policies to make sure only pods with specific labels can communicate with each other.

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.

Practice copying files to/from running Kubernetes Pods that don'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?

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 an application running as a Kubernetes pod.

Learn how to send a signal to a Kubernetes app running in an unprivileged container without shell.

Learn how to send a signal to a Kubernetes app running in a container without shell.

Identify what causes the Pod initialization to fail and fix it while keeping the Pod images unchanged.

Identify what causes the Pod initialization to fail and fix it while keeping the Pod images unchanged.