Gremlin Scenario: Container zone redundancy

How it works

How this Scenario works

This Scenario drops network traffic between your containers in one availability zone and the rest of your infrastructure, simulating a complete zone outage. This forces your load balancers and service discovery mechanisms to redirect traffic to containers running in the remaining zones.

Use cases

Why run this Scenario?

Demonstrate that your containerized services are truly zone-redundant, with replicas distributed across availability zones.
Verify that service discovery and load balancing detect the zone outage and redirect traffic to healthy containers.
Test whether your secondary zones have enough container capacity to handle the traffic surge from the failed zone.
Ensure that container orchestration returns traffic to normal distribution when the zone comes back online.

Result

What to expect when you run it

When a zone fails, containers in secondary zones automatically absorb the traffic with no interruption in service.

Keep going

More Scenarios to try

Kubernetes packet loss

Ensure your Kubernetes systems can detect and route around resources that fail health checks. This Scenario gradually increases packet loss to validate liveness/readiness probe and load balancer behavior.

Container packet loss

Ensure your containerized systems can detect and route around resources that fail health checks. This Scenario gradually increases packet loss to validate health check and load balancer behavior.

Windows packet loss

Ensure your Windows systems can detect and route around resources that fail health checks. This Scenario gradually increases packet loss to validate health check and load balancer behavior.

Container zone redundancy