A city exposes permits.example.gov and inspections.example.gov with different URL paths and does not want a separate LoadBalancer Service for each hostname. Which Kubernetes object declares host and path HTTP routing typically in front of ClusterIP Services?
Select an answer to reveal the explanation.
Short Explanation
Ingress is the HTTP map: hosts and paths share front-door capacity instead of one LoadBalancer Service each. Controllers implement those rules, usually toward ClusterIP Services. That is L7 routing inside Kubernetes—not API Gateway’s Domain 3 story.
Full Explanation
Ingress resources express HTTP host and path routing. An ingress controller implements those rules, commonly fronting ClusterIP Services so many hostnames share entry capacity. That is distinct from L4 Service types. API Gateway is a separate OCI serverless/front-door topic (Domain 3) and is not the answer for this in-cluster Ingress concept. Queues and per-Pod NodePorts are the wrong tools here.