Thanks for the eloquent reply! During my PoC I did see that a lot of things that I traditionally do on the machine are now done external. But for me that makes

Thanks for the eloquent reply! During my PoC I did see that a lot of things that I traditionally do on the machine are now done external. But for me that makes it harder. A practical example was: How do I get all my "fail2ban"-rules ported to "whatever this cluster-management uses"? Simple things like "if someone requests admin.php on this Rust-only API: ban it for 2 hours". I did see this is possible, but the amount of tools and their complexity was off-putting to me. I really appreciate how you suggest good alternatives and solutions to problems I stated: I hope they'll help me or someone else moving to k8s in future. And about: > Traditionally management has been the job of the application itself. Yes. Been there; hell, I even wrote rate-limiters for Drupal, and WordPress for our large customers on the Drupal, and later WordPress webhoster that I ran. But I also understand how microservices is the solution to this. However: Microservices does not require containerization, IMO. I'm running between 8 and 14 VMs on Linode and DigitalOcean exactly because of this: because stuff is "microserviced". I have a flock of Elasticsearch servers. A server that ingest, processes and then stores the OSM database weekly into that elasticsearch. Several postgres database servers. A statistics-server. Had an "avatar server", there's a dedicated url-shortener somewhere, A mailserver. Moving an authentication server onto my flock next week. I don't need k8s for that. Microservices are a good solution to specific problems but the underlying tech can easily be $6.99 VPSs managed with ansible.