Ingress for host and path routing
WHAT IT TESTS: Knowing when to use Ingress. OUTLINE: Use an Ingress with an Ingress controller for layer-7 host/path routing behind one external IP, instead of one cloud LoadBalancer per service.
WHAT IT TESTS: Whether you choose the right layer-7 routing object and understand the cost trade-off. ANSWER OUTLINE: Use an Ingress resource, backed by an Ingress controller (such as NGINX). It defines host-based and path-based rules that route HTTP/S traffic to multiple backend Services behind a single external IP and load balancer. Versus multiple LoadBalancer Services, Ingress avoids provisioning (and paying for) a separate cloud load balancer per service and centralizes TLS termination and routing.
Read the original → interview
- #kubernetes
- #ingress
- #routing
- #layer-7
- #loadbalancer
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.