K8s requires a flat plane addressability model across all containers, meaning anyone can see and call anyone else?
I can see security teams getting uppity about that.
Also budgetary and org boundaries, cloud providers, disaster recovery/hot spares/redundancy/AB hotswap, avoid single tank point of failure.
Addressability is not accessibility . It's easy to control how services talk to each other through NetworkPolicy.
This… sounds remarkably like the problems kubernetes solves.
single tank point of failure should be
single YAML point of failure
mobile autocorrect is super "helpful"
I 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.