<story><title>The full-time job of keeping up with Kubernetes</title><url>https://gravitational.com/blog/kubernetes-release-cycle/#</url></story><parent_chain></parent_chain><comment><author>tw1010</author><text>There aught to be a name to the tendency that as tools get better and better, the more your time goes from having your mind in technical-space to social and news-space. It&amp;#x27;s like the authority to create goes from the individual first-principles (by necessity) maker, to the control over development being in the hands of an external group, and then all your time is spent keeping up with what they&amp;#x27;re doing. A similar thing happened with a lot of javascript frameworks. It also happened with the transition from building servers from the ground up, to it all being managed by AWS.</text></comment>
<story><title>The full-time job of keeping up with Kubernetes</title><url>https://gravitational.com/blog/kubernetes-release-cycle/#</url></story><parent_chain></parent_chain><comment><author>hueving</author><text>This reads like a giant ad for GKE. It emphasizes several times to just use GKE for pretty lame reasons (Google has good SREs and Google started the project).&lt;p&gt;The people that work on upstream k8s in Google (Tim et al) have a pretty limited overlap with the Google Cloud people that run GKE. Upstream k8s is a full time job so they are most certainly not spending their time also writing internal GKE code.&lt;p&gt;I don&amp;#x27;t have an issue with GKE, but this article uses little evidence to recommend it when it seems the conclusion should have been &amp;quot;maintaining a k8s cluster requires a full time sysadmin.  If your company has a culture of pretending sysadmins are pointless, then you should pay another company offering k8s sysadmin-as-a-service hosted on their hardware.&amp;quot;</text></comment>