4 ms·
single tank point of failure should be single YAML point of failure mobile autocorrect is super "helpful"
by AtlasBarfed 2y ago
single tank point of failure should be
single YAML point of failure
mobile autocorrect is super "helpful"
- withinboredom 2y agoI have completely tanked a kubernetes cluster before. Everything kept working. The only problem was that we couldn’t spin up new containers and if any of the running ones stopped, dns/networking wouldn’t get updated. So for a few hours while we figured out how to fix what I broke, not many issues happened. So sure, I can kinda see your point, but it feels rather moot. In the cluster, there isnt much that is a single point of failure that also wouldn’t be a point of failure in multiple clusters.