<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>akdor1154</author><text>Yeah k8s is great. It gives you an infinite rope generator to let you hang yourself with ever increasing complexity, but with a bit of restraint you can orchestrate pretty much anything in a simple or at least standard way.&lt;p&gt;I&amp;#x27;d take a stack of yaml over a stack of bespoke aws managed service scripts any day.</text><parent_chain><item><author>erulabs</author><text>Well I think it&amp;#x27;s neat. The bit I find most provoking is the &amp;quot;if you already have Kubernetes...&amp;quot; premise. I find myself having a hard time not wanting to shove everything into the Kubernetes framework simply to avoid having to document what solutions I&amp;#x27;ve chosen. `kubectl get all` gives me an overview of a project in a way that is impossible if every single project uses a different or bespoke management system.&lt;p&gt;&amp;quot;simple&amp;#x2F;complex&amp;quot; is not the right paradigm. The real SRE controversy is &amp;quot;unique&amp;#x2F;standard&amp;quot;. Yes, the standard approach is more complex. But it is better _in practice_ to have a single approach, rather than many individually-simpler, but in-aggregate-more-complex approaches.&lt;p&gt;Kubernetes is never the perfect solution to an engineering problem, but it is almost always the most pragmatic solution to a business problem for a business with many such problems.</text></item></parent_chain></comment><story><title>My IRC client runs on Kubernetes</title><url>https://xeiaso.net/blog/2024/k8s-irc-client/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>Spivak</author><text>Is the mountain of k8s code on top of your cloud of choice not strictly more complex than the cloud services it&amp;#x27;s orchestrating? Like I think k8s is good software but to hear that you&amp;#x27;re not choosing it because it&amp;#x27;s good engineering is surprising. To me that&amp;#x27;s the only reason you choose it, because you want or need the control-loop based infrastructure management that you can&amp;#x27;t get on say AWS alone.</text><parent_chain><item><author>erulabs</author><text>Well I think it&amp;#x27;s neat. The bit I find most provoking is the &amp;quot;if you already have Kubernetes...&amp;quot; premise. I find myself having a hard time not wanting to shove everything into the Kubernetes framework simply to avoid having to document what solutions I&amp;#x27;ve chosen. `kubectl get all` gives me an overview of a project in a way that is impossible if every single project uses a different or bespoke management system.&lt;p&gt;&amp;quot;simple&amp;#x2F;complex&amp;quot; is not the right paradigm. The real SRE controversy is &amp;quot;unique&amp;#x2F;standard&amp;quot;. Yes, the standard approach is more complex. But it is better _in practice_ to have a single approach, rather than many individually-simpler, but in-aggregate-more-complex approaches.&lt;p&gt;Kubernetes is never the perfect solution to an engineering problem, but it is almost always the most pragmatic solution to a business problem for a business with many such problems.</text></item></parent_chain></comment><story><title>My IRC client runs on Kubernetes</title><url>https://xeiaso.net/blog/2024/k8s-irc-client/</url></story>