Question

You deployed an NGINX Ingress controller and created an Ingress resource that maps host 'shop.example.com' with path '/api' (pathType: Prefix) to service 'api-svc:8080' and path '/' to service 'web-svc:80'. Requests to 'shop.example.com/' work correctly, but requests to 'shop.example.com/api/orders' return a 503 Service Temporarily Unavailable from NGINX. The web-svc endpoints are healthy. What is the MOST likely cause of the 503?

Accepted Answer

The 'api-svc' service has no ready endpoints (its selector matches no running/ready pods)

Answer

The Ingress resource is missing the correct ingressClassName, so the controller ignores the '/api' rule

Answer

pathType Prefix is invalid for multi-segment paths like '/api/orders' and must be changed to Exact

Answer

CoreDNS cannot resolve 'api-svc', so the Ingress controller returns 503