Interview › Istio & Service Mesh
What is fault injection in Istio, and why would you use it?
Istio & Service Mesh · Basic level
Answer
Fault injection intentionally adds delays or aborts to mesh traffic so teams can test timeout behavior, retry safety, fallbacks, and user impact. It is a controlled resilience test, not a production failure by accident.
Technical explanation
Delay faults simulate slow dependencies, network latency, or saturated downstream services.
Abort faults simulate HTTP errors such as 500 or 503 responses.
Fault injection should be scoped carefully to a test namespace, header, or small traffic segment to avoid broad production impact.
Hands-on example
Example test plan:
1. Match only requests with header x-chaos-test: true.
2. Inject a 2 second delay to ratings.
3. Confirm checkout timeout is lower than user SLA and fallback is graceful.
4. Remove the VirtualService fault rule after the test.
Check how well your resume matches the role with our free resume checker— match score, ATS check, and the skills you're missing.
More Istio & Service Mesh interview questions
- What is Istio, and what are the core capabilities it provides?
- What is the difference between the Istio control plane and data plane?
- What is istiod, and what does it do?
- What is Envoy, and what role does it play in Istio?
- What is the sidecar pattern, and how does Istio inject the proxy?
- How does automatic sidecar injection work (namespace label, webhook)?
- What is the Istio ambient (sidecarless) mode, and how does it differ from sidecar mode?
- What is the difference between ztunnel and a waypoint proxy in ambient mode?