# VMware Proposes New Standard for Hybrid Kubernetes Workload Portability The new working group aims to standardize application behavior across diverse cloud environments. - **Source:** [www.theregister.com - Articles](https://www.theregister.com) - **Published:** 2026-11-10 - **Topic:** [technology](https://brifing.si/c/technology) - **Original article:** - **On Brifing:** https://brifing.si/s/f75d3727-fde8-48ff-9431-ed1279fd2cb8 ## Addressing Hybrid Cloud Inconsistencies VMware has initiated the Workload Conformance Working Group within the Kubernetes community to address portability issues. While cloud-native software promises seamless movement, applications often fail when transitioning between public and hybrid clouds. This new effort seeks to establish shared standards, ensuring workloads run predictably regardless of the underlying infrastructure environment. ## Manual Assessment Bottlenecks Currently, cluster operators must manually verify every application before routine maintenance or Kubernetes upgrades. This repetitive process creates significant operational overhead for maintainers who face identical questions across different environments. The proposed common specification aims to provide a reliable baseline, allowing teams to automate assessments rather than relying on manual checks. ## Defining the Technical Scope The working group is in its early stages, currently defining which behaviors the specification will cover. The proposed scope includes critical areas such as security, resource utilization, networking, storage, and API usage. A core requirement is that every standard must have an objective, testable binary, explicitly excluding any subjective or qualitative criteria. ## Broad Industry Support Expected Prashanth Shenoy, VP of product marketing at Broadcom's VMware Cloud Foundation, suggests that application vendors will likely support this initiative. By packaging their software once to meet these standards, vendors can ensure their products run efficiently anywhere. This move benefits providers like Nutanix and Red Hat, who also sell hybrid cloud infrastructure. ## VM API Joins CNCF Alongside the new working group, VMware has moved its VM API to the Cloud Native Computing Foundation (CNCF) Sandbox. This contribution allows Kubernetes users to create and manage virtual machines running under various hypervisors, including VMware’s ESXi. The move signals a strategic shift in how VMware integrates its legacy virtualization technology into containers. ## Coexistence of VMs and Containers The CNCF's acceptance of the VM API highlights the reality that containers and virtual machines will coexist for years. While developers prioritize container-native code, operations teams frequently prefer running these abstractions within lightweight VMs for stability. This integration supports organizations managing modern containerized applications alongside legacy virtualized workloads in automated environments. ## Evolution of Infrastructure Management VMware’s approach reflects the broader industry trend toward infrastructure-as-code, where automated deployments are the standard. Previous attempts to bridge the gap between Pivotal-acquired container technology and VMware’s core offerings faced challenges. This new strategy treats VMs as first-class citizens within Kubernetes, aiming to simplify life for both development and operations teams. ## Future Implications for Operators If successful, these standards will reduce the friction associated with hybrid cloud deployments. By shifting from manual validation to repeatable, objective tests, organizations can accelerate their upgrade cycles. The ultimate success of this initiative depends on the group's ability to finalize specific requirements and gain broad adoption across the Kubernetes ecosystem. ## Sources covering this story - https://www.theregister.com/virtualization/2026/11/10/vmware-floats-new-standard-to-make-sure-apps-dont-break-in-hybrid-k8s-environments/5308956 — --- _Summary written by Brifing from the original reporting. Copyright in the original article belongs to its publisher; read the full piece at the link above._