Hacker News new | ask | show | jobs
by iwontberude 803 days ago
I don't agree exactly. The standardization in Kubernetes has brought calm to the chaos. Having controllers which act as the public interfaces for additional capability in ways that can integrate with other controllers cleanly is transformational. I have vendors supporting the interfaces that Kubernetes has defined which commoditizes the vendor, which is exactly what I want in a platform. I am not locked into a vendor because they are using these generic, interchangeable interfaces.
1 comments
politelemon 803 days ago
> I am not locked into a vendor because

I see this often mentioned in the context of k8s and find it baffling that it gets repeated. K8s is simply swapping a form of lock in, to the abstract layer.

link
nijave 803 days ago
K8s does have a lot of open interfaces like CRI, CNI, CSI that can & are used in other solutions like Hashicorp Nomad.

The core/control plane components aren't interchangeable but a lot of the "userland" can be swapped around (I have cri-o, Calico, and a homemade CSI on libvirt VMs at home and it runs workloads the same as containerd, AWS VPC CNI, EBS CSI at work)

However, it's not open in the way there's a drop in replacement

link