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 for sharpening your DevOps and server-side skills. Some teach specific concepts while others mirror real-world scenarios. Every challenge includes hints, feedback, and automated solution checks.
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.
An app in the web namespace is served over HTTPS by an ingress-nginx Ingress. Create a Gateway and HTTPRoute on a staging hostname, verify traffic, move the production hostname to the Gateway, and remove the Ingress without downtime.