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.
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
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: 12/13