VMware Launches Initiative to Standardize Hybrid Kubernetes Workload Portability
New working group aims to eliminate manual application testing across diverse cloud environments.
1Standardizing Hybrid Cloud Workloads
VMware has initiated the Workload Conformance Working Group within the Kubernetes community to address portability issues. While cloud-native software promises seamless movement, hybrid environments often cause application failures. This group seeks to establish a shared standard, ensuring workloads run predictably across both on-premises infrastructure and various public cloud deployments.
2The Problem of Manual Assessment
Currently, no standardized testing exists for application behavior within Kubernetes clusters. Cluster operators must manually inspect every application before routine maintenance or upgrades occur. This repetitive process creates significant operational overhead, as application maintainers face identical inquiries from different environments, highlighting the urgent need for a common, repeatable testing baseline.
3Defining the Technical Scope
The proposed specification aims to cover critical operational areas including security, resilience during disruptions, resource utilization, networking, storage, and API usage. Although the project is in its early stages, the group has mandated that every requirement must include an objective, automated test binary, strictly excluding any subjective or qualitative performance metrics.
4Vendor and Developer Alignment
Prashanth Shenoy of Broadcom’s VMware Cloud Foundation division notes that applications packaged for public clouds often struggle in hybrid setups. By creating a unified standard, VMware hopes to attract support from other hybrid cloud vendors like Red Hat and Nutanix, ultimately simplifying the deployment process for developers who want write-once, run-anywhere capabilities.
5VM API Joins CNCF Sandbox
In a separate move, VMware has contributed its VM API to the Cloud Native Computing Foundation Sandbox. This tool enables Kubernetes users to create and manage virtual machines running under various hypervisors, including ESXi. This integration supports the ongoing trend of managing legacy VMs alongside modern containerized applications within automated infrastructure.
6Coexistence of VMs and Containers
While developers increasingly favor containerized architectures, operations teams frequently prefer running these abstractions within lightweight virtual machines. The VM API serves as a bridge, acknowledging that both technologies will coexist for years. By making VMs first-class citizens in Kubernetes, VMware aims to reduce complexity for teams managing diverse, hybrid infrastructure stacks.
7Evolution of VMware Strategy
VMware’s latest efforts represent a shift from past attempts to package container technology following its acquisition of Pivotal Software. By moving the VM API to the CNCF, the company demonstrates a commitment to open-source collaboration. This approach aligns with the industry-wide shift toward infrastructure-as-code, where automated deployments are now the standard expectation.
8Future Implications for Operations
The success of these initiatives depends on industry-wide adoption of the proposed conformance tests. If standardized, these tools could significantly reduce the time spent on manual cluster verification. For organizations balancing legacy systems with new cloud-native apps, these developments offer a path toward more predictable, efficient, and scalable hybrid cloud operations.