Is K8s Too Complicated? ￼
I suppose we have to assume that we should use the right tool for the right job, and all that. And I&#x27;m sure that the Kubernetes folk know what they&#x27;re doing. But I definitely think that it&#x27;s too complicated without a cutting-edge Kubernetes expert in place to manage it. And even then, it&#x27;s just a <i>building block</i> for a larger system.<p>I&#x27;ve tried maybe half a dozen times to get started for relatively small workloads – let&#x27;s say between 5 to 50 servers. There seems to be a lack of any good documentation on how to get started – sure, I can spin up a couple of pods on a cluster or whatever, but then actually taking that to an easy-to-deploy, load-balanced, publicly-accessible infrastructure seems to be much harder.<p>It&#x27;s maybe a lack of some kind of official, blessed version of a &quot;this is how you should build a modern infrastructure from container to deployment&quot; guide. There are so many different moving parts that it&#x27;s hard to figure out what the optimal strategy is, and I&#x27;ve not found much to make it easier.<p>Maybe there&#x27;s actually a niche for a nice and simple &quot;infrastructure  in a box&quot; kind of product. I&#x27;d love something like Heroku that I could run on my own bare metal, or on AWS – the various solutions I&#x27;ve tried were all lacking.<p>In the end I&#x27;ve fallen back to using the Hashicorp stack of Nomad and Consul. This seems to work in a much simpler way that I can actually wrap my brain around – I get a nice cluster running balanced across machines, deploying and scaling my applications as required, and it was super easy to set up with good documentation.<p>I&#x27;ve been nervous about this approach because of how Kubernetes-mad the industry seems to have gone – so maybe it&#x27;ll be worth another look when there are some more comprehensive solutions in place that make it easier to get started!