News for hackers. Stuff that matters.
Re:Failure Injection on Kubernetes with SMI and Linkerd by samstave on Monday July 22, 2019 @08:40PM (#20503528)
You know what would be an interesting service:

Chaos monkey/failure injection-as-a-service: in that you define the parameters by which you wanted to be assessed...

King of like pen test contractors...

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.

Re:Failure Injection on Kubernetes with SMI and Linkerd by 0vermorrow on Monday July 22, 2019 @08:47PM (#20503564)
You mean like https://www.gremlin.com/ ?

One of the founders of Gremlin is an Engineer that worked in Netflix and probably worked on Chaos Monkey as well :)

Re:Failure Injection on Kubernetes with SMI and Linkerd by adlleong on Tuesday July 23, 2019 @02:43PM (#20509119)
If I understand correctly, one of the limitations of doing application level failure injection with Gremlin is that you need to integrate it into your code: https://www.gremlin.com/docs/application-layer/installation/

It might be interesting to combine these approaches and use a traffic split to send a percentage of traffic to Gremlin instead of integrating into the code directly.

Re:Failure Injection on Kubernetes with SMI and Linkerd by barbecue_sauce on Monday July 22, 2019 @10:47PM (#20504046)
Shh, you're going to wake up the TinkerPop Gremlin guy.
Re:Failure Injection on Kubernetes with SMI and Linkerd by jrockway on Wednesday July 24, 2019 @02:54PM (#20518416)
These kinds of errors are going to happen in production, whether you inject them or let them occur naturally. Any release process that doesn't go perfectly with a drain / rebalance / start new version / rebalance per (backend, proxy) combo is going to have a timeout or broken connection between the proxy and the backend as it restarts. Should you return 502 to your users when that happens? Nope, just retry on a different backend. This lets you test that.