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.
Packet Loss
Containers
5 minutes
How this Scenario works
This Scenario gradually increases packet loss on a targeted container, simulating degraded network conditions. This tests whether your container health checks detect the degradation and whether your load balancer or service mesh removes the unhealthy container from rotation.
Why run this Scenario?
- Validate that container health check thresholds are configured to detect packet loss before users are impacted.
- Verify that load balancers or service meshes remove unhealthy containers from rotation and redistribute traffic.
- Test that container orchestration detects the unhealthy container and replaces it with a new one.
- Ensure that containers are returned to service correctly once packet loss resolves.
What to expect when you run it
As packet loss degrades network communications to a container, health checks mark it as unhealthy and traffic is redistributed to healthy container replicas.
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)