Cloud

Do you really need Kubernetes?


Oh, sure, Kubernetes is all the rage and of course you need one. Maybe three! But if you ever stop to think, “Why Kubernetes?”, as Paul Johnston did, well, expect lots (and lots) of opinions.

One of the primary reasons IT professionals cite for embracing Kubernetes is to reduce lock-in by ensuring portability between clouds. This turns out to be better in theory than in practice. And, as Johnston says, the same people who tell him they’re embracing Kubernetes for cloud portability also tell him they have no plans to move.

So, why Kubernetes?

Containerize away lock-in!

Plenty of people find themselves boarding the Kubernetes bandwagon simply because it’s popular. (“Devs and architects want to use it because tech is a fashion industry and Kubernetes is trendy,” says Orion Edwards.) This despite the likelihood, argues James Thomason, that while developers may look at Kubernetes as a way to “run like Google… in reality it’s overkill for all but 0.001% of use cases.”

While this might be overstating the case a bit, Thomason has a point. As an industry we do have a tendency to apply shiny new things well beyond their intended use.

According to Johnston, many CTOs embrace Kubernetes “usually because they have to. Either inherited or because it is what they see as the next big thing (lots of developers for hire) and go for it, then wish they hadn’t.” 





READ SOURCE

This website uses cookies. By continuing to use this site, you accept our use of cookies.