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.
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.
Challenges contributed by the community members sharing their knowledge and expertise.
Managing HTTP routing with Kubernetes Ingress resources the imperative way - host-based routing across namespaces, path-based routing, and a catch-all rule.
Create an Ingress resource for a shop application with path-based routing to multiple backend services and configure /etc/hosts for local DNS resolution.
Combine multi-stage builds, build-time arguments, non-root users, and Pod security context into a single production-grade image pipeline.
Use an ambassador container to intercept and forward outbound requests from the main app container via localhost.