Kubernetes Auto Analyzer

Securing Kubernetes

Special Thanks: This article was made possible by support from Linux Professional Institute

Few software applications have changed the way modern infrastructure works – not Infrastructure as a Service provisioning, such as Amazon Web Services, but applications. Outside of desktop-style applications (e.g., Software as a Service), which of course can’t really be counted as infrastructure, I cannot pick many examples out of the air without careful consideration, although I suppose virtualization software, which needs hardware innovations to some extent, might fit. You certainly, however, can fly the flag for Docker as one of the recent game-changers, providing software developers fully portable, boxed-up units of code that will work exactly the same way in a test environment as in a production environment. To be fair to its predecessors, some of the container concepts on which Docker is built have existed longer than the Docker project .

Thanks to neat and tidy containers of code, Docker was surfing the crest of a wave for a number of years (and arguably still is), releasing ship-loads of exciting new features, with a momentum that was hard to match. As the adoption of containers grew, suddenly a need arose for an automated way of steering the ships holding the containers, because developers and infrastructure operators realized that when you hit an n th number of containers, it’s akin to herding cats.

From such scenarios, the exceptionally popular Kubernetes (which in Greek means “pilot” or “helm”) began to gain traction. Kubernetes is now used by multinational enterprises that embraced containers sooner rather than later and trusted it with high-value production workloads.

...

Use Express-Checkout link below to read the full article (PDF).