Users hit an Ingress host and receive HTTP 503. kubectl shows the Ingress backend Service name is misspelled relative to the real Service. What should the developer fix first?
Select an answer to reveal the explanation.
Short Explanation
503 from Ingress often means "I cannot find a healthy backend." A typo in the Service name is a classic culprit—fix the backend reference to the real Service and port before chasing replica counts or DNS theater.
Full Explanation
Ingress controllers return 503 when they cannot resolve a usable upstream, including when the referenced Service name or port is wrong. Aligning the Ingress backend with an existing Service and port is the direct fix. Scaling replicas, restarting CoreDNS without evidence, or elevating privileges does not repair a bad backend reference.