Title: Arguable the goals of DevOps align partly with the goals of system administrators in former days: Provide reliable compute infrastructure for<p><pre><code>  1) internal users: mainly developers by providing CI&#x2F;CD
  2) external users: end users
</code></pre>
Nowadays we call people that do 1) DevOps and people that do 2) SREs (so one could argue that the role of sys admins just got more specialized).<p>The platform of choice is mostly Kubernetes these days, which promises among other things stuff like<p><pre><code>  - load balancing
  - self-healing
  - rollbacks&#x2F;rollouts
  - config management
</code></pre>
Before the cloud days, this stuff has been implemented using a conglomerate of different software and shell scripts, issued at dedicated &quot;pet&quot; servers.<p>In particular, a main critic is &quot;state&quot; and the possibility to change that state by e.g. messing with config files via SSH, which makes running and maintaining these servers more error-prone.<p>However, my main question is:<p>&quot;If this old way of doing things is so error-prone, and it&#x27;s easier to use declarative solutions like Kubernetes, why does the solution seem to need sooo much work that the role of DevOps seems to dominate IT related job boards? Shouldn&#x27;t Kubernetes <i>reduce</i> the workload and need <i>less</i> men power?&quot;<p>Don&#x27;t get me wrong, the old way does indeed look messy, I am just wondering why there is a need for so much dev ops nowadays ...<p>Thanks for your answers.
Upvote: