<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>colllectorof</author><text>The tech churn cycle is getting more and more insane. It&amp;#x27;s the same process repeating endlessly.&lt;p&gt;1. Identify one problem you want to fix and ignore everything else.&lt;p&gt;2. Make a tool to manage the problem while still ignoring everything else.&lt;p&gt;3. Hype the tool up and shove it in every niche and domain possible.&lt;p&gt;4. Observer how &amp;quot;everything else&amp;quot; bites you in the ass.&lt;p&gt;5. Identify the worst problem from #4, use it to start the whole process again.&lt;p&gt;Microservices will save us! Oh no, they make things complicated. Well, I will solve that with containers! On no, managing containers is a pain. Container orchestration! Oh no, our clusters fail.&lt;p&gt;Meanwhile, the complexity of our technology goes up and its reliability &lt;i&gt;in practice&lt;/i&gt; goes down. Plus, the concepts we operate with are less and less tethered to reality, which makes even talking about certain issues really hard.</text><parent_chain><item><author>tutfbhuf</author><text>The current trend goes to multi-cluster environments, because it&amp;#x27;s way too easy to destroy a single k8s cluster due to bugs, updates or human mistake. Just like it&amp;#x27;s not an very unlikely event to kill a single host in the network e.g. due to updates&amp;#x2F;maintenance.&lt;p&gt;For instance, we had several outages when upgrading the kubernetes version in our clusters. If you have many small cluster it&amp;#x27;s much easier and more save to apply cluster wide updates, one cluster at a time.</text></item></parent_chain></comment><story><title>Kubernetes Failure Stories</title><url>https://k8s.af</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>superbcarrot</author><text>Sounds like madness. Should we expect a new tool that orchestrates all of your Kubernetes clusters?</text><parent_chain><item><author>tutfbhuf</author><text>The current trend goes to multi-cluster environments, because it&amp;#x27;s way too easy to destroy a single k8s cluster due to bugs, updates or human mistake. Just like it&amp;#x27;s not an very unlikely event to kill a single host in the network e.g. due to updates&amp;#x2F;maintenance.&lt;p&gt;For instance, we had several outages when upgrading the kubernetes version in our clusters. If you have many small cluster it&amp;#x27;s much easier and more save to apply cluster wide updates, one cluster at a time.</text></item></parent_chain></comment><story><title>Kubernetes Failure Stories</title><url>https://k8s.af</url></story>