As organizations modernize their application portfolios, Kubernetes has become the de facto platform for deploying and operating cloud-native applications. The challenge for many enterprises is not whether to adopt Kubernetes, but how to do so without creating additional infrastructure silos, operational complexity, and security risks.
With VMware Cloud Foundation (VCF) 9.x, VMware has significantly simplified this journey through VMware Kubernetes Service (VKS), a CNCF-certified Kubernetes runtime built directly into the VCF platform. VKS enables organizations to run virtual machines and Kubernetes workloads on a single infrastructure platform while leveraging integrated lifecycle management, security, networking, and storage services.
Why VKS Matters
Historically, deploying enterprise Kubernetes often required stitching together multiple products and operational models. Platform teams needed to manage Kubernetes separately from their virtualization infrastructure, creating additional overhead and skill requirements.
VKS addresses this challenge by providing Kubernetes as a native service within VCF. Through vSphere Supervisor, platform engineers can provision, manage, scale, and upgrade Kubernetes clusters using the same infrastructure platform that already supports traditional virtual machine workloads.
The result is a unified operating model that supports both legacy and modern applications.
High-Level Architecture
At a high level, VKS sits on top of the core VMware Cloud Foundation infrastructure stack.
VCF Management Domain
│
├── SDDC Manager
├── vCenter
├── NSX
│
VCF Workload Domain
│
└── vSphere Supervisor
│
├── VMware Kubernetes Service (VKS)
│
└── Namespaces
│
├── Development Clusters
├── Test Clusters
└── Production Clusters
The vSphere Supervisor acts as the Kubernetes management layer and exposes Kubernetes services to platform engineers and developers. VKS is delivered as a Supervisor Service and can be managed independently from the core VCF platform lifecycle.
Step 1: Establish the VCF Foundation
Before Kubernetes can be deployed, the underlying VMware Cloud Foundation infrastructure must be in place.
This includes:
- VCF Management Domain
- One or more Workload Domains
- vCenter
- NSX
- Enterprise storage platforms such as vSAN, Fibre Channel, or NFS
VCF provides the compute, networking, storage, security, and lifecycle management services that Kubernetes clusters consume. One of the key advantages of VKS is that Kubernetes is built directly into this platform rather than requiring a separate infrastructure stack.
Step 2: Enable vSphere Supervisor
The next step is enabling vSphere Supervisor within the workload domain.
Supervisor provides:
- Kubernetes control plane integration
- Self-service infrastructure consumption
- Namespace management
- Cloud services integration
In VCF 9.x, Supervisor becomes the foundation for Kubernetes operations and serves as the interface for deploying and managing VKS clusters.
Think of Supervisor as the bridge between traditional infrastructure operations and modern Kubernetes platform services.
Step 3: Design the Networking Architecture
Networking is often the most important architectural decision in any Kubernetes implementation.
A production-ready VKS deployment should include:
- NSX integration
- IP address management
- Load balancing strategy
- Network segmentation
- Ingress and egress policies
VMware’s reference architectures leverage NSX networking capabilities to provide connectivity and isolation for Kubernetes workloads while maintaining consistent operational controls across the environment.
For large enterprises, networking design should be completed before cluster deployment to avoid operational challenges later.
Step 4: Create Namespaces
Namespaces provide multi-tenancy and resource isolation within the Supervisor environment.
Typical namespace controls include:
- CPU allocation
- Memory allocation
- Storage policies
- Access controls
- Resource quotas
Namespaces enable platform teams to safely provide Kubernetes resources to development, testing, and production teams while maintaining governance and operational standards. VMware documentation identifies namespaces as a required component before deploying VKS workloads.
Step 5: Deploy Kubernetes Clusters
Once namespaces are available, platform engineers can deploy Kubernetes clusters using VKS.
Clusters can be provisioned through:
- vCenter
- APIs
- CLI tools
- VCF Automation
One of the major benefits of VKS is its ability to automate cluster provisioning, scaling, health management, and lifecycle operations. This significantly reduces the operational burden traditionally associated with Kubernetes deployments.
For organizations supporting multiple development teams, standardized cluster templates can accelerate deployment while ensuring consistency across environments.
Step 6: Integrate Enterprise Services
Deploying Kubernetes is only the beginning.
Production environments require integration with enterprise services such as:
- Active Directory and identity providers
- Monitoring platforms
- Logging solutions
- Backup and recovery systems
- Container registries
- Vulnerability scanning tools
These integrations ensure that Kubernetes workloads operate within the same governance, security, and compliance framework as traditional enterprise applications.
Step 7: Establish Lifecycle Management
One of the most compelling enhancements in VCF 9.x is the decoupling of VKS from the core vSphere release cycle.
Because VKS is delivered as a Supervisor Service, organizations can manage Kubernetes versions independently from broader infrastructure upgrades. This allows platform teams to adopt new Kubernetes releases more quickly while reducing operational disruption.
This model provides greater flexibility and aligns more closely with the rapid innovation cycles common in modern application development.
Recommended Enterprise Design
For a large regulated enterprise, I would recommend the following architecture approach:
Infrastructure Layer
- VMware Cloud Foundation 9.x
- NSX networking
- Enterprise storage platform (vSAN, PowerStore, or equivalent)
Kubernetes Layer
- VMware Kubernetes Service (VKS)
- Dedicated Development, Test, and Production namespaces
- Standardized cluster templates
Security Layer
- Role-based access control (RBAC)
- Identity federation
- Image scanning
- Network segmentation
Operations Layer
- Centralized monitoring
- Backup and recovery
- Capacity planning
- Lifecycle automation
This approach delivers a scalable and secure Kubernetes platform while leveraging the operational maturity already present within the VMware ecosystem.
Final Thoughts
VMware Kubernetes Service represents a significant evolution in VMware’s Kubernetes strategy. Rather than forcing organizations to build and manage separate Kubernetes platforms, VKS enables enterprises to consume Kubernetes as an integrated service within VMware Cloud Foundation.
For infrastructure and platform teams, the real value is not simply deploying Kubernetes. It is delivering a consistent operating model where virtual machines, containers, networking, storage, security, and lifecycle management are all managed through a single platform.
