Friday, August 3, 201833 likes1 comment

Introducing Kubernetes, Microservices, and DevOps

Versioning deep dive in August

If you’re at all involved with DevOps, or even just DevOps-curious, you’ve probably heard about Kubernetes. Or, you’ll have read about it, and never really understood how to pronounce it. (Seriously, when I told devs in the office or elsewhere that I was covering this subject, many of them sighed in relief upon realizing how to say that word.)

To clear that up:


So kubernetes is pronounced /koo-ber-nay'-tace/ and means "sailing master"

Ok, that's a cool name!

July 11, 2014
So containers have definitively become the defacto standard for managing infrastructure, but until recently there wasn’t a decent way to manage them.

Now, we have Kubernetes, an open source platform (formerly a Google project) for managing containerized workloads and services. It’s now the industry standard for deploying containers in production. It’s flexible and can run anything, it’s well-loved by developers. The Google pedigree doesn’t hurt, either.

Kubernetes removes a lot of the complexity of managing containers, making it easier to orchestrate when apps should run, where to find them, how to ensure they’re running, as well as things like autoscaling. You can also extend Kubernetes with custom resource definitions. People are building their own packages to make sharing applications easier, and it’s a vibrant ecosystem. It’s a new world!

But it can make your head spin (I have had to sit down and gather myself a few times after reading many, many articles about cluster interaction, for example). But one thing was pretty easy to grasp:

If you’re at all interested in infrastructure management or DevOps as a passion or a career, right now Kubernetes is the thing you need to master!

This month I’ll take a look around this world and show you the best of what I’ve found to help you get there, and we’ll learn more about this platform, this emerging field, together.

I hope you’ll join me, it’ll be very 'nete!