It's worth noting that Istio has built-in support for failure injection (i.e. without needing to run a separate service to return 500s): <a href="https://istio.io/docs/tasks/traffic-management/fault-injection/#injecting-an-http-abort-fault" rel="nofollow">https://istio.io/docs/tasks/traffic-management/fault-injecti...</a><p>As far as I know Linkerd does not (yet) have such a feature though, so this post seems like a reasonable alternative.
So... if I were going to inject failures into my service mesh, it would be my service mesh that I'd be counting on to do the retry after the failure. Does it even make sense to do it in that case?
You know what would be an interesting service:<p>Chaos monkey/failure injection-as-a-service: in that you define the parameters by which you wanted to be assessed...<p>King of like pen test contractors...<p>So OK let me spin up an environ and attack the fuck out of it. Show me where im weak. So that in prod... im good.