I am just wondering if this is Vitess related. I am moving tens of PBs into Vitess and it would be really bad if these incidents are vitess related...

I mean, you can rest assured that you will have problems with Vitess at some point. All software is buggy, and there is no guarantee one of those bugs won't be catastrophic. You should plan for a method to completely replace your entire production cluster in the event of failure. This can be quite difficult with horizontally-scaled databases. It's also not uncommon to hit a scaling limit for which there's no simple solution, or not be able to build out a replacement production cluster due to unplanned-for limitations.

I know a lot of GitHubbers and they say the irony is that this is one of the only clusters that is not on Vitess.

It's common to promote someone to just get rid of that person :) Sometimes promoting is just easier that firing.

Failing upwards, as someone here said

1 container per VM? What's the point? If you can bypass container sandbox it's very likely that you can do the same with VM.

> If you can bypass container sandbox it's very likely that you can do the same with VM.

Hypervisors are much, much harder to break out of than a Linux container.

What is the point in writing blog posts like this?