Kubernetes network latency
Simulate unreliable network conditions in Kubernetes by adding latency to API calls. Test whether your users are affected when network response times degrade to hundreds or thousands of milliseconds.
Latency
Kubernetes
6 minutes
How this Scenario works
This Scenario adds increasing levels of network latency to your Kubernetes pods, simulating unreliable network conditions that are common in microservice architectures—where services make frequent API calls across a growing number of pods and nodes.
Why run this Scenario?
- Validate that Kubernetes services handle degraded network conditions without cascading failures across the cluster.
- Test timeout, retry, and circuit breaker configurations in your Kubernetes service mesh or networking layer.
- Identify pods and services that are overly sensitive to latency increases in the Kubernetes network.
- Verify that Kubernetes network policies and service mesh configurations handle latency gracefully.
What to expect when you run it
When network latency increases significantly within Kubernetes pods, our services continue to respond within acceptable bounds and users experience minimal impact.
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)