Kubernetes network latency
.svg)
.svg)
Description
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.
What this Scenario does
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.
Expected outcome
When network latency increases significantly within Kubernetes pods, our services continue to respond within acceptable bounds and users experience minimal impact.
