Connecting Kubernetes services with linkerd
I appreciate the sentiment behind linkerd et al but I think we are <i>really</i> over-complicating things and tying ourselves into knots by going head-first into this world. I can&#x27;t help but think we&#x27;re going to regret it in a few years.<p>The complexity introduced not only by Docker, but also k8s and all of the other things competing for a spot in the middle of your cluster, is immense and <i>widely</i> underestimated.<p>Your applications need to be aware and adapted to the k8s model of automatic pod termination, no hard storage, etc. Google has had over 10 years with the best computer scientists money can buy to perfect their stack. Most companies don&#x27;t.<p>For most companies, k8s&#x2F;linkerd&#x2F;Docker deployments are a case of overengineering run <i>frighteningly</i> amok.<p>There are many-a-snafu lying down this path. I&#x27;m very worried about how casually everyone is willing to jump aboard.<p>One particular worry: most Dockerfiles are built on opaque images registered with an image registry, and many of the publishers are not well-known. If you want Ruby, the habit is to go find someone&#x27;s &quot;pre-configured&quot; alpine-ruby image (for instance). These are frequently distributed by complete strangers. Building &quot;from scratch&quot; off the base image distributed by the distro itself is considered &quot;the old way&quot;, at least among those I&#x27;ve worked with.<p>My understanding is that most public image repositories are unmoderated. The moment a widely-used image gets pwned, there is going to be panic.<p>Source: been converting entire company to Docker&#x2F;k8s