Kubernetes Workload Conformance Closes the Portability Gap
14m
Workload conformance is the next frontier for Kubernetes portability. Clusters can already prove they are conformant. The applications running on them often cannot move as easily.
Broadcom Senior Director of Engineering Dilpreet Bindra examines that challenge with Alan Shimel at KubeCon + CloudNativeCon in Salt Lake City.
From Conformant Clusters to Portable Workloads
Kubernetes conformance programs, backed by tools like Sonobuoy, give distributions a shared baseline. AI conformance followed last year. Yet ISVs still struggle to run the same workload across every environment.
Broadcom is co-chairing the new Workload Conformance Working Group in the Kubernetes community. The goal is simple: Kubernetes should be Kubernetes wherever it runs. Shared, verifiable expectations would let vendors validate once instead of certifying platform by platform.
Bindra notes that much of the community's heavy lifting happens in working groups like this one. Competitors sit at the same table to solve problems no single company can fix alone.
Bringing Virtual Machines Into the Kubernetes Model
The second announcement extends the same thinking to virtual machines. Broadcom built VM Operator to describe VMs through the Kubernetes desired state model. That work now ships as KubeVM Service.
A developer can define a virtual machine in a simple YAML document. Teams can then manage VMs with the same GitOps workflows they use for containers. Rather than keep it proprietary, Broadcom contributed the VM API project to the CNCF Sandbox.
Bindra also points to Broadcom's longer record upstream. That includes Cluster API work, an etcd debugging tool and the Velero contribution.
AI Raises the Stakes for Platform Teams
Kubernetes has become the de facto platform for AI inferencing and agents. Bindra sees AI compressing projects that once took months into weeks or days.
Enterprises want that speed with strong security guarantees. Broadcom tracks AI usage across its own developers, tying costs to individual features for future budgeting.
For platform teams, workload conformance and a native VM API point toward a more predictable Kubernetes stack. It is one that is ready for whatever AI brings next.