Service with no ready endpoint
A Service selects no ready pod.
ImpactEvery caller of the Service fails
Can it be seen coming?Partly
RupturaNot covered yet
How to detect it
Zero ready addresses for a Service that has callers.
Metrics and signals to watch:
kube_endpoint_addressService selector
Can you see it coming?
Partly Precursor: The failures of the pods behind it.
What it hits next
callers of the Service.
What to do
Fix the selector or the pods behind it.
Sources
- Kubernetes Endpoints
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
- Calls to a dependency fail
- DNS resolution fails
- Network retransmits rise
- NetworkPolicy blocks a needed call
- Route or Ingress has no healthy backend
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