The funny thing about the massive crater created by the explosion of container management systems emerging lately is that it’s forcing people working in the systems administration field to come to terms with the container paradigm… or perhaps it’s more like sysadmins have been pushing business towards automating infrastructure which is part of the package in most PaaS (Platform as a Service) … quick note here, I’m going to mention Apcera here as part of at Apcera it was Policy as a Service, a much more effective approach to securing jobs and services for a broad range of uses…
Kubernetes brings ‘Google style’ cluster management capabilities to the world of virtual machines, or ‘on the metal’ scenarios.
Kubernetes is a declarative system…
Stop, what’s that?
In Kubernetes you can define a deployment with a yaml config. Effectively employing infrastructure as code, it manages your deployments and maintains the structure declared.
When you consider what Kubernetes does for an organization, it’s probably worth more thinking on what Kubernetes does for an engineering organization.
Since Kubernetes came onto the stage there’s been a change to how that abstraction layer deploys an application. When you deploy an application operators no longer need to install software on the OS. Kubernetes enacts the needed packages, essentially filling dependency for successful operation of that application.
This is going to manifest in some interesting ways, especially in a datacenter where Kubernetes could be used to manage available resources for a whole farm of machines sitting in a rest state being active only on demand.
We are in so much trouble!