4 ms·
Kubernetes absolutely does not mean no lock-in. The lock-in is just quieter (people will eventually realize this). Use higher-level services (or even long-tail
by solidasparagus 7y ago
Kubernetes absolutely does not mean no lock-in. The lock-in is just quieter (people will eventually realize this).
Use higher-level services (or even long-tail features of low-level services) that are differentiated between cloud providers from k8s, you are locked in.
Make k8s auth work cleanly with cloud auth, you're locked in.
Rely on a cloud provider service to manage master and/or worker nodes, you're locked in.
You can avoid lock-in by manually running a k8s cluster while using only the lowest-level services that every cloud providers offers (VM, block store, NFS, load balancer, maybe one or two others), but most people don't actually want to do this.
- bryanlarsen 7y agoThe point is that Google is currently actively working towards reducing lock-in. Storage is one area where I've seen some good movement. Microsoft is also contributing a lot of good stuff to make Kubernetes migration easier. We'll never get to zero, and I'm sure that Google & Microsoft will eventually put more emphasis on complementary products that increase lock-in. But right now it's trending in the right direction.
- solidasparagus 7y agoI don't agree at all. The current trend is for cloud providers to create k8s operators as a way to lock you in by using cloud services in the background. The Spark Operator for Kubernetes is one example of this that was created by Google. It seems like all the major clouds are doing it (I don't actually have an Azure example, but I imagine you could find some).