Route or Ingress has no healthy backend
External traffic gets 503 from the router.
ImpactUsers see the outage
Can it be seen coming?Partly
RupturaNot covered yet
How to detect it
Backend Service without ready endpoint.
Metrics and signals to watch:
Route or Ingress backend Servicekube_endpoint_address
Can you see it coming?
Partly Precursor: The failures of the pods behind the Service.
What it hits next
users.
What to do
Fix the backend pods or the Route target.
Sources
- OpenShift Route
- Kubernetes Ingress
Where Ruptura stands
Ruptura does not cover this failure yet. The card is here so you know it exists and how to detect it.
Related failures
- Service with no ready endpoint
- Calls to a dependency fail
- DNS resolution fails
- Network retransmits rise
- NetworkPolicy blocks a needed call
See it coming instead of reading about it
Ruptura is an open-source operator for Kubernetes and OpenShift that predicts the failures in this catalog that can be predicted, detects the others, and sends them to Alertmanager. Watch an OOM crash predicted 21 minutes early · ★ GitHub
Ruptura is an open-source operator for Kubernetes and OpenShift that predicts the failures in this catalog that can be predicted, detects the others, and sends them to Alertmanager. Watch an OOM crash predicted 21 minutes early · ★ GitHub