NetworkPolicy blocks a needed call
A new or changed policy drops traffic between two workloads.
ImpactThe caller times out
Can it be seen coming?No
RupturaNot covered yet
How to detect it
Drops between workloads that called each other before.
Metrics and signals to watch:
NetworkPolicy changesflow logs
Can you see it coming?
No Precursor: None, a policy change is the cause. This failure arrives without a reliable warning sign, so the goal is to detect it fast and explain it.
What it hits next
callers of the blocked workload.
What to do
Allow the call in the policy or revert the change.
Sources
- Kubernetes NetworkPolicy
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
- 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