> Ansible does not watch and maintain the infrastructure and services state Yeah, but what I've done is that i've deployed a tiny go binary on each cloud insta

> Ansible does not watch and maintain the infrastructure and services state Yeah, but what I've done is that i've deployed a tiny go binary on each cloud instance that is run every few minutes. Instances take turns checking on each other using a round robin sort of approach (no complicated leader election algorithms etc...) The script knows how to check the health of the other instances/services and to restart them or alarm if they get stuck. For fifty hosts, it works fairly well. I didn't say in the original post, but we are not a product group, so our stuff is 'semi production'. We don't have customers to worry about. >Somebody posted here that it takes just several hours to learn it. Sure I can probably learn it quickly, but what I don't want is to now have complicated and mysterious kubernetes problems to solve on a deadline. I understand linux pretty well, been using it for 20+years, so I'm not intimidated by OS level troubleshooting. Sure without containers, you have to be more careful to keep your dependencies from overlapping, but it hasn't been a problem we couldn't handle till now. I don't particularly want to trade problems I'm familiar with solving for a whole new set of unfamiliar problems unless there is a clear benefit.