Challenge on ,
Troubleshoot an Ingress That Returns 503 Service Unavailable
by Omkar Shelke
A railway app publishes two endpoints through an Ingress, and both return 503. Find out why and make both endpoints answer again.
Challenges
Focused, hands-on DevOps and server-side problems with hints, feedback, and automated solution checks.
Community Collection
Challenges contributed by the community members sharing their knowledge and expertise.
Challenge on ,
Troubleshoot an Ingress That Returns 404 Not Found
by Omkar Shelke
An nginx Deployment runs fine, but its address returns an error. Trace the path from the Ingress to the Pod and fix the manifests.
Challenge on , ,
Pick and Deploy the Least Permissive NetworkPolicy
by Omkar Shelke
The security team left five NetworkPolicy files on the workstation. Only one of them lets the frontend reach the backend while granting nothing more. Identify it and deploy it, unchanged.
Challenge on ,
Port-Forward a Kubernetes Service to localhost
by Omkar Shelke
A Deployment running a distroless Chainguard nginx image (cgr.dev/chainguard/nginx) is deployed in the namespace webapps, fronted by a ClusterIP Service. Port-forward that Service to localhost port 3333 on cplane-01, use curl to save the response body to /home/laborant/index.html, and verify the file is accessible and contains the expected content.
Challenge on ,
Access the Kubernetes API Server via kubectl proxy
by Omkar Shelke
Use kubectl proxy to open a local, already authenticated HTTP endpoint to the Kubernetes API server, then use curl to list every Secret in the gliese-581 namespace and save the raw JSON response to /home/laborant/secret-list.json.
Challenge on ,
Extend the Cluster with an Additional Service CIDR for the dev Team
by Omkar Shelke
Add a new, separate Service CIDR range for the dev team using the ServiceCIDR API object — without touching or restarting the cluster's default Service CIDR — then create a Service with an explicit ClusterIP inside that new range and verify DNS resolution.
Challenge on ,
Pin a Client to the Same Pod Using Service Session Affinity
by Omkar Shelke
Configure a Kubernetes Service so that requests from the same client IP are always routed to the same backend Pod for a sustained period, using ClientIP-based session affinity.
Challenge on ,
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.
Challenge on ,
Configure Ingress Routing with Traefik for a Multi-Service Shop Application
by Omkar Shelke
Create an Ingress resource for a shop application with path-based routing to multiple backend services and configure /etc/hosts for local DNS resolution.
Challenge on ,
Resolve a Container Port Conflict and Expose Multiple Ports Through a Single Service
by Omkar Shelke
A Deployment with two nginx containers has a port conflict — both containers use port 80. Fix the conflict by updating the ConfigMap, mounting it into the second container, updating the containerPort, and exposing both containers via a NodePort Service.