Kubernetes Without the VMware Tax
A demo of native Rancher and Kubernetes integration on VergeOS. The session shows the CSI driver, Cloud Controller Manager, Cluster Autoscaler, and Rancher node driver in action, and walks through how to retire vSphere licensing, distribution licensing, and overlay storage in a single platform decision.
VMware Shops Running Kubernetes Pay Three Taxes at Once
They pay vSphere licensing to host cluster nodes. They pay a Kubernetes distribution tax, Tanzu, OpenShift, or Rancher Prime. Many pay a third tax for overlay storage like Longhorn or Portworx because vSphere storage policies do not extend cleanly into Kubernetes without commercial Tanzu add-ons.
VergeOS now collapses all three layers into a single integrated platform. Rancher remains the management plane customers already use. Workloads move on the customer’s timeline. The session walks through how it works, with a demo of Rancher continuity on VergeOS plus a discussion of what migration looks like for Tanzu shops and what comes next on the roadmap.
What’s Covered
The Three-Tax Problem
Five-minute framing on what makes Kubernetes on vSphere expensive and what the integration actually replaces.
VMware Exit with Rancher Continuity
Walk-through of provisioning a Kubernetes cluster on VergeOS through the Rancher control plane. Same workflow customers already use for vSphere clusters. Node driver, CSI, CCM, all in action.
What Migration Looks Like for Tanzu Shops
How parallel operation works in practice. Old TKG clusters keep running while new clusters land on VergeOS. Workloads move on the customer’s timeline. Stateless first, stateful after the new platform validates under real load.
What Ships Next
The next phase of integration work, including bare-metal Kubernetes operational uplift.
Questions From the Audience
Audience questions answered by David, George, and Aaron. The full Q&A is included in the recording.
Built for Platform Engineers Running Kubernetes on vSphere
If your team manages Kubernetes clusters inside VMware, runs Tanzu Kubernetes Grid, or operates Kubernetes directly on bare metal, this session is built for you. Cloud-native architects, infrastructure platform leads, SREs, and IT decision-makers evaluating Kubernetes platform consolidation will get the most value.
The Private Cloud Operating System
VergeOS unifies compute, storage, networking, and data protection into a single integrated software stack running on commodity hardware. The native Kubernetes integration extends VergeOS as the substrate underneath any Kubernetes distribution: RKE2, K3s, vanilla upstream, or vendor distributions managed through Rancher.
The integration ships as Helm charts from the verge-io repository on GitHub. VergeIO is not introducing a Kubernetes distribution. The integration assumes customers already run a distribution they trust and provides the platform layer underneath.
Built and Validated with Production Customers
The integration was developed with a European sports gaming platform as the MVP design partner during integration development. Their engineering team validated the CSI driver, Cloud Controller Manager, and Rancher node driver against real production workloads. The demo in the recording is not a slideware walkthrough. It is the same workflow design partner customers used to validate the integration in production.
Watch the Recording
Submit your business email to get instant access to the full 30-minute session, including the demo, the migration discussion, the roadmap, and the audience Q&A.