VMware's in court again. Customer relationships rarely go this wrong

The bigger issue is, if you're refusing to honour a contract as a vendor, not only do you risk a lawsuit like this one. But more importantly, who is ever going to sign up for another contract with you? You just proved it isn't worth the paper it's written on.

Unwritten terms like "valid until I decide to tear it up haha lol" are not generally appreciated by companies that depend on your stuff for their business. Of course you can extort your existing customers until they manage to move away but basically in the longer term you're suiciding your entire business.

So switch to openstack or kubernetes (with kubevirt if you want VMs). Open source. Way more beautiful design.

With Kubernetes, actually fast storage if you need it. Can scale up to AI demands if you need it.

Or proxmox or the like if you're small enough.

My beef with K8s (and to be clear, it’s the leanest cut of beef from the deli - so not much substance to it) is that unless you pay someone else to manage the Control Plane for you, you’re not only going to need to upskill your workers on K8s itself but also administering the components of the Control Plane, like HA, etcd, storage, network plane, etc.

Compared to standing up literally any Linux distro and KVM, K8s remains an overly complex PITA to get off the ground and integrated into an org on the cheap/free. In that area, it handily loses to even Microsoft Hyper-V in the “just get us going” category of business adoption/velocity.

I’d really, really like to see K8s more streamlined for initial deployment than it is. It’s getting better, but I generally still have to grudgingly recommend a premium, managed control plane for any serious deployment.

Word for word my experience with operating k8s.

To be clear: I like K8s! It’s fun to be able to write some YAML, apply it, and be done!

But the sheer work of getting to that point, safely and securely? It ruins the experience for me, personally.

What would you like setup to look like?

Would there be real interest in a kubernetes distro that takes IPs and a (set of) domain names, and boots up on N nodes, installing letsencrypt, so that you can do a deployment and have ingress actually working?

For homelabs and SMBs, that is definitely an opportunity. Other areas I’d like to see more growth in:

* “No-Code Kubernetes”, that lets staff design basic (or even not-so-basic) deployments using a web-based GUI. We’re seeing more of this from a “understand how things work while they run” perspective, but I haven’t personally come across any “here’s your building blocks and explainers of the environment variables, go build” solutions.

* An “ESXi-ified” K8s. Talos comes so, so close to this, but I’d love something that was as easy to deploy into production as ESXi was on SD cards. Deploy as an appliance on bare metal or as a VM, and voila, Control Plane with an IP schema, network layer, AD CA/ACME support (including Let’s Encrypt), and a basic load balancer/ingress. Changing the setup is as simple as adding a basic text file with the control plane IP and join string (worker nodes), with a simple flag to add it as another control plane node for HA.

* Renewed focus on etcd management ease. A lot of the cert track focuses extensively on etcd management through kubectl, which is an unnecessary abstraction layer for things like backups, failovers, and redundancies in smaller IT departments.

* Automated migrations. The K8s evangelists hype it as being able to manage VMs, which would be great if kube-virt was standard (it’s an add-on). I’d like to see K8s either formally integrate it into the baseline or more distros make it a checkbox option at cluster creation. Part of that should also be support for automatic deployment creations for existing VMs in a hypervisor, by analyzing current settings and suggesting the YAML or JSON to replicate that VM in K8s with appropriate IP address, current storage, and ACLs

From a tech standpoint, the foundations for K8s success have long been polished into a mirror shine. At this point it’s usability and accessibility that remain broadly unaddressed, especially if we want more people and companies using iterative, composable infrastructure.