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.)
...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.”
...many CTOs embrace Kubernetes...they see as the next big thing (lots of developers for hire) and go for it, then wish they hadn’t.”
Why the regret? Because with Kubernetes comes complexity, complexity that they didn’t have with the vehicle they need most for cloud portability...simple shell scripts. Indeed, as Johnston goes on, Kubernetes ends up “way overcomplicating something that has been done for years in multiple different ways.”
You want cloud portability to minimize lock-in? You can have it. But you probably don’t need Kubernetes to get there.
I’d argue we have less portability with Kubernetes now.
