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.
Kubernetes - Build and Deploy a Production-Ready Container Image
Combine multi-stage builds, build-time arguments, non-root users, and Pod security context into a single production-grade image pipeline.
Submissions: 8/12
Challenge, Medium, on
Kubernetes - Proxy Outbound Traffic with an Ambassador Container
Use an ambassador container to intercept and forward outbound requests from the main app container via localhost.
Submissions: 11/19
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: 16/16
Expose Internal Services Using NGINX Kubernetes Gateway API
by Omkar Shelke
Configure a Kubernetes Gateway API setup to expose aviation platform services using path-based routing for flight and booking services.
Submissions: 29/49
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.
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.
Submissions: 16/26
Challenge, Medium, on
Why LimitRange Is Not Injecting Default Requests and Limits into Running Pods
by Omkar Shelke
A LimitRange exists in the namespace but Pods are not receiving default resource requests and limits. Investigate the root cause and fix it.
Submissions: 10/11
Enforce a NetworkPolicy to Block All Traffic Except DNS
by Omkar Shelke
A Pod must be fully isolated from the cluster network. Deny all incoming traffic and block all outgoing traffic except DNS queries on port 53.
Submissions: 11/12
Challenge, Medium, on
Mount Specific ConfigMap Keys as Files into a Node.js Deployment
by Omkar Shelke
A Deployment is failing because application configuration is missing. Mount only specific keys from an existing ConfigMap as files inside the Pod at the correct path so the application can start successfully.
Submissions: 8/18