I think the article oversells the guarantees infrastructure can give you, especially around this: > We can make sure that we always have X instances of a given

I think the article oversells the guarantees infrastructure can give you, especially around this: > We can make sure that we always have X instances of a given service or process running in our infrastructure. Kubernetes will make sure to try to start new instances if existing ones fail. It cannot make sure that you always have those X instances running by any means! This may sound nitpicky - and of course, any code-level solution to redundancy or failure issues won't work if you don't have anywhere available to run on - but it's important to understand both your requirements and what specific guarantees your infrastructure can make. There are cases where "let it fail fast, Kubernetes will restart it" may not be your best choice.