Is Kubernetes a modern way of vendor lock-in?

[thingrex@fosstodon.org]

Is Kubernetes a modern way of vendor lock-in?

Companies execute multi-cloud strategies to avoid vendor lock-in. The "default" implementation leverages Kubernetes, as containerized applications/workloads are easy to distribute.
Deploying software using Kubernetes is not cost-free; applications have to be designed in a specific way, and Kubernetes itself requires significant resources to operate.
I am not against Kubernetes or containerization in general.

#software #kubernetes #architecture

[jan@toot.io]

@thingrex K8s removes the vendor-lock-in from cloud providers. Instead of implementing proprietary cloud APIs you can use K8s API everywhere, even on localhost.

[thingrex@fosstodon.org]

@jan That is why K8s is the "default" way of implementing multi-cloud solutions. But does it mean that there are no shortcomings in that approach?

[jan@toot.io]

@thingrex It depends on the use-case. Deploying one container on K8s is quite useless, but for hundreds or thousands containers it helps a lot. I prefer open source APIs instead of proprietary APIs.