I was chatting with Sakthi about automating some testing of hbck2 commands. Nothing too fancy, I just want some assurance that they ought to work.
This got us talking about how we might purposefully break a cluster to meet a set of symptoms that hbck2 knows how to correct. We need something different from the chaos monkeys. in this case we're not trying to peturb the cluster in ways we think it should handle; we're setting up a state we already know requires an outside tool. Where should this kind of tooling live? Main repo next to the monkeys? Alongside hbck2 in operator tools? Somewhere else entirely?
