This article is based on reporting originally published on forbes.com covering VMware’s VMworld 2019 conference.
Kubernetes Takes Center Stage at VMworld 2019
If there was one clear signal coming out of VMware’s annual user conference, VMworld 2019, it was that Kubernetes had moved from an adjacent technology to the front and center of VMware’s entire product strategy. Executives across the company consistently emphasized that engineering teams were fully embracing the open-source container orchestration platform as the foundation for the next generation of vSphere.
This shift is significant. VMware built its business on virtualization and the vSphere platform, which underpins a massive share of enterprise data center infrastructure. Integrating Kubernetes natively into that platform rather than bolting it on as an afterthought represents a meaningful architectural commitment — and one with long-term implications for both infrastructure operators and application developers.
Project Pacific: Kubernetes Embedded into the Core of vSphere
Project Pacific is VMware’s initiative to embed Kubernetes directly into the vSphere hypervisor layer — not alongside it, but within it. The goal is to bridge the operational gap between traditional VM-based infrastructure and modern container-based workloads running on Kubernetes.
The key design principle of Project Pacific is that it serves two audiences simultaneously without forcing either to change their existing workflows:
- Developers interact with the stack through the Kubernetes API, using familiar kubectl commands, YAML manifests, and Kubernetes-native tooling. From their perspective, they are deploying to a Kubernetes cluster.
- IT Operations teams continue to manage the environment through vCenter and the vSphere interface they already know. From their perspective, workloads remain manageable as vSphere constructs.
This dual-interface approach is architecturally clever. It avoids the common enterprise dilemma of forcing a wholesale platform migration in order to adopt containers. Instead, existing vSphere investments remain valid while the platform gains Kubernetes-native capabilities.
Beyond the immediate operational benefits, embedding Kubernetes into vSphere’s core extends the platform’s strategic relevance significantly. It gives VMware’s ISV ecosystem and technology partners a well-defined integration point for container-aware products and services.
VMware Tanzu: A Brand for the Container Product Portfolio
Alongside Project Pacific, VMware announced Tanzu as an umbrella brand for its growing portfolio of container and Kubernetes-related products. Rather than a single product, Tanzu is a product family — a way of organizing and marketing VMware’s cloud-native offerings under a coherent identity.
Tanzu Mission Control
The first product shipped under the Tanzu brand is Tanzu Mission Control, a centralized management plane designed to provide visibility and governance across multiple Kubernetes clusters regardless of where they run — on-premises data centers or public cloud environments.
The long-term ambition for Tanzu Mission Control is to manage clusters across a broad range of environments, including:
- Clusters running inside Project Pacific on-premises
- Amazon Elastic Kubernetes Service (EKS)
- Google Kubernetes Engine (GKE)
- Azure Kubernetes Service (AKS)
- IBM Kubernetes Service
This positions Tanzu Mission Control as VMware’s answer to the multi-cluster, multi-cloud Kubernetes management problem — a challenge that becomes increasingly acute as enterprises run Kubernetes across multiple providers and environments.
The Pivotal Acquisition and PKS Consolidation
The Tanzu umbrella also brings potential clarity to the naming confusion that existed around Pivotal Kubernetes Service (PKS). With Pivotal becoming part of VMware, rebranding PKS offerings under the Tanzu name — as Tanzu Kubernetes Service — would consolidate the Essential PKS and Enterprise PKS product lines under a single, more coherent brand. This kind of rationalization typically reduces confusion for enterprise buyers evaluating VMware’s Kubernetes offerings.
How Project Pacific and Tanzu Fit Together
The two announcements serve distinct but complementary strategic purposes:
- Project Pacific addresses VMware’s cloud-native strategy by modernizing the core vSphere platform, making it Kubernetes-aware from the ground up.
- Tanzu addresses VMware’s multi-cloud ambitions by providing a management layer that spans Kubernetes deployments across on-premises infrastructure and multiple public clouds.
Both rely on Kubernetes as the common operational fabric — specifically its extensibility model, which allows the Kubernetes API to be extended with custom resource definitions (CRDs) and operators. This extensibility is what makes it practical for VMware to embed Kubernetes into vSphere and simultaneously build a centralized control plane on top of it.
VMware’s History of Platform Integration Strategies
This is not the first time VMware has responded to a major infrastructure trend by integrating the new technology directly into its existing platform rather than building a separate product line. There is a recognizable pattern:
- OpenStack: As OpenStack gained momentum in enterprise data centers, VMware released vSphere Integrated OpenStack, enabling side-by-side deployment and management of vCenter alongside an OpenStack control plane.
- Containers (early wave): When Docker containers began gaining traction, VMware announced vSphere Integrated Containers, allowing containers to run inside VMs on vSphere, alongside Photon OS — a lightweight, open-source Linux distribution optimized for running containers.
- Kubernetes (current wave): Project Pacific and Tanzu represent the same integration instinct applied to Kubernetes orchestration — embed it deeply, manage it centrally, and extend the platform’s life cycle in the process.
Whether this Kubernetes-first approach proves more durable than the OpenStack integration strategy remains to be seen. However, the depth of the Project Pacific integration — Kubernetes embedded into the hypervisor kernel rather than layered above it — suggests a more foundational commitment than previous efforts.
What This Means for DevOps and Infrastructure Teams
For DevOps practitioners and platform engineers working in VMware-heavy environments, these announcements have practical implications:
- Kubernetes skills become directly applicable to vSphere environments. Teams no longer need to maintain entirely separate skill sets for VM management and container orchestration when running on Project Pacific.
- Multi-cluster governance becomes a first-class problem VMware is solving. Tanzu Mission Control is worth evaluating for organizations running Kubernetes clusters across multiple environments without a unified management story.
- The vSphere platform is not going away. For enterprises with significant vSphere investments, Project Pacific represents a path to adopting cloud-native patterns without a forklift migration off the existing hypervisor infrastructure.
- The Kubernetes API becomes the integration surface. Partners and tooling vendors building on top of VMware infrastructure will increasingly target the Kubernetes API rather than proprietary VMware APIs.
VMware’s move to make Kubernetes the architectural backbone of vSphere is one of the more consequential platform decisions in enterprise infrastructure in recent years. The success of this strategy will depend on execution — particularly on how well the dual-interface model (Kubernetes for developers, vSphere for ops) holds up under the real-world complexity of enterprise environments.