VMware floats new standard to make sure apps don’t break in hybrid K8s environments
That’s challenging for VMware, and other vendors of hybrid clouds like Nutanix and Red Hat, because they all sell tools to create and run a stack that users can deploy to both on-prem infrastructure and public clouds.
- The two abstractions are therefore going to coexist for years to come, both for new apps and as organizations run new containerized apps alongside legacy VMs, and do so in an infrastructure-as-code world in which automated deployments are assumed.
- But VMware argues that’s not happening across hybrid clouds, and has taken the lead in an effort to improve matters.
- VM API to CNCF Sandbox VMware this week announced another contribution to Kubernetes by moving its VM API to the Cloud Native Computing Foundation (CNCF) Sandbox.
VMware therefore thinks it will find support for an effort to ensure that cloud-native apps run predictably and efficiently in any Kubernetes environment.
- Advocates for cloud-native software have long argued that their approach to development makes applications portable across different Kubernetes environments.
- That effort, the new Workload Conformance Working Group in the Kubernetes community, aims to establish a shared standard for how workloads run on Kubernetes.
- VM API will therefore likely be a welcome addition to Kubernetes, representing another option to make life a little easier for ops and dev teams.
- Suffice to say past efforts didn’t catch on, and VMware is now trying a different approach to making VMs a first class citizen of Kubernetes.
- “The scope includes security, resilience during disruptions, resource use, networking, storage, API usage, and observability, but the group hasn’t yet agreed on specific requirements or on how to test them.
How this summary was made: extractive summary — built from the sources' own reporting. It is drawn only from the reporting of the sources listed below — read the originals for full detail. How we summarize →