You’re thinking about Kubernetes all wrong | #linux | #linuxsecurity

Kubernetes is cool, but not for the reasons you think. For a time people glommed onto Kubernetes because it promised to be a great new cloud technology—something like OpenStack (without all its problems). But Kubernetes wasn’t. Nor was it a magical cure for lock-in that offered unbridled portability. Not even close.

Instead, Kubernetes has become the new Linux, as I’ve written. Or, perhaps more accurately, it’s a new app server, as Weaveworks CEO Alexis Richardson suggested in an interview. Rather than enterprises trying to build their own clouds, he argues, “Let your development teams run short-lived Kubernetes clusters that are like app servers.”

What does this mean, exactly?

Technobabble and gobbledygook

Richardson and I were supposed to talk about multicluster Kubernetes on bare metal with microVMs powered by Firecracker. Five seconds in, my eyes were glazing over, which was a problem since I was driving. “Besides being fit for the edge scenario, mixed mode enables significantly greater efficiency in managing bare metal Kubernetes clusters by moving control plane nodes from dedicated bare metal servers into microVMs, thus significantly reducing the overall number of nodes required in a bare metal pool!” he intoned, citing the company’s blog post on the topic.

I was trying desperately to care, given that my employer released Firecracker as an open source project. But I couldn’t. I couldn’t get excited about telco operators rolling out “5G applications where ‘network function’ (5G workload) can be run alongside signaling functions, management functions, web and customer applications in the same hardware with strong isolation and resource control.”

Someone cares about this. I didn’t.

Copyright © 2021 IDG Communications, Inc.

Original Source link

Leave a Reply

Your email address will not be published.

three + five =