Kubernetes Ingress: Expose Multiple HTTP Backends the Imperative Way
Managing HTTP routing with Kubernetes Ingress resources the imperative way - host-based routing across namespaces, path-based routing, and a catch-all rule.
Challenges
Focused hands-on problems designed to help you hone your DevOps or Server Side skills. Some challenges are more educational, while others are based on real-world scenarios. The platform provides hints and feedback for each challenge, including automated solution checks.
Community Collection
Challenges contributed by the community members sharing their knowledge and expertise.
Challenge, Easy, on
Configure a Memory-Backed emptyDir Volume with a Size Limit
by Omkar Shelke
A Deployment is using a disk-backed emptyDir volume. Convert it to a memory-backed tmpfs volume for better performance — but make sure to set a size limit to prevent the Pod from exhausting the node's RAM.
Submissions: 21/26
Challenge, Easy, on
Kubernetes - Normalize Application Output with an Adapter Container
Use an adapter container to transform a custom pipe-delimited log format into space-separated output.
Submissions: 13/13
Challenge, Easy, on
Copy a File into a Running Pod to Serve a Custom NGINX Page
by Omkar Shelke
A Pod is running nginx and exposed via NodePort. Copy a local HTML file into the running Pod so NGINX serves it as the default homepage using only imperative commands.