Kubernetes Cluster API v1.0, Production Ready
Some of the arguments against Kubernetes and for simpler systems&#x2F;approaches, like Docker Compose, systemd or others actually gave me the push i needed to collect some of my thoughts and past experiences in a blog post &quot;My journey from ad hoc chaos to order (a tale of legacy code, services and containers)&quot;: <a href="https:&#x2F;&#x2F;blog.kronis.dev&#x2F;articles&#x2F;my-journey-from-ad-hoc-chaos-to-order-a-tale-of-legacy-code-services-and-containers" rel="nofollow">https:&#x2F;&#x2F;blog.kronis.dev&#x2F;articles&#x2F;my-journey-from-ad-hoc-chao...</a><p>(i&#x27;m linking it as a top level comment here, since responding to multiple comments would feel spammy, but the discussion is interesting)<p>In short:<p><pre><code>  - Docker Compose is lovely for local development, but isn&#x27;t necessarily the only option to do containers easily
  - Docker Swarm is what i chose and has been working wonderfully with software like Portainer
  - K3s is a good Kubernetes distro that cuts down on the resource usage and allows you to work slightly more easily with it
  - that said, Kubernetes isn&#x27;t always the right tool for the job, with which i agree, especially for smaller teams
  - systemd services can also be perfectly passable, but only as long as you control everything around the service itself (e.g. the environment with the updates etc.)
  - regardless of whether you use containers or not, there are benefits to configuration management systems like Ansible, which i suggest you look into if you haven&#x27;t already</code></pre>