Kubernetes region evacuation
Test your Kubernetes service's availability when an entire cloud region becomes unavailable. Verify that traffic automatically fails over to clusters in backup regions without impacting the user experience.
Blackhole
Kubernetes
5 minutes
How this Scenario works
This Scenario drops all network traffic to your Kubernetes cluster in a specified cloud region, simulating a catastrophic regional outage. This forces your global load balancers, multi-cluster service mesh, or federation layer to redirect all traffic to Kubernetes clusters in your backup region(s).
Why run this Scenario?
Large-scale infrastructure outages are an unfortunate reality. Power outages happen, storms flood data centers, and curious sharks will snack on data cables. This Scenario tests your systems to see how they handle an entire cloud region suddenly becoming unavailable.
- Verify that your backup Kubernetes clusters have sufficient node and pod capacity to absorb the full production workload.
- Validate that multi-cluster service mesh or federation correctly detects the regional outage and routes traffic.
- Test Kubernetes Horizontal Pod Autoscaler behavior in backup clusters under sudden traffic increases.
- Ensure that Kubernetes-native storage and stateful workloads handle cross-region failover correctly.
What to expect when you run it
When a region becomes unavailable, traffic automatically fails over to Kubernetes clusters in backup regions, and those clusters handle the increased load without impacting the user experience.
More Scenarios to try
Avoid downtime. Use Gremlin to turn failure into resilience.
Gremlin empowers you to proactively root out failure before it causes downtime. See how you can harness chaos to build resilient systems by requesting a demo of Gremlin.
.svg)