A public-health Ingress returns HTTP 503 while the backing Service…

Question

A public-health Ingress returns HTTP 503 while the backing Service exists. What readiness condition commonly explains the 503?

Accepted Answer

Backend Pods are not Ready (no ready endpoints), so the Ingress controller has no healthy upstream. — Ingress is a front desk that only sends guests to staff who signed in Ready—if no Pod is Ready, visitors get a polite 503. Fix readiness before blaming cipher suites.

Answer

The Ingress TLS secret uses RSA instead of ECDSA, which always yields 503.

Answer

The API server read-only port is disabled, which Ingress translates into 503.

Answer

The Service type is ClusterIP; Ingress requires ExternalName for every backend.

A public-health Ingress returns HTTP 503 while the backing Service exists. What readiness condition commonly explains the 503?

Short Explanation

Full Explanation