{"slug": "announcing-the-workload-conformance-working-group", "title": "Announcing the Workload Conformance Working Group", "summary": "The Kubernetes community has formed a Workload Conformance Working Group to write a shared standard for how workloads behave at runtime on Kubernetes, with a stable first specification and working tests targeted within two to three Kubernetes release cycles. The group's charter sets three deliverables covering security, resilience during disruptions, resource use, networking, storage, API usage and observability, and requires every requirement to have an objective test a test binary can run. The effort fills a gap left by Certified Kubernetes, which tests clusters, and Kubernetes AI Conformance, which tests whether a cluster can run AI and ML workloads, since nothing comparable exists for the workloads themselves.", "body_md": "We are excited to announce that the Kubernetes community now has a [Workload Conformance Working Group](https://www.kubernetes.dev/community/community-groups/wg/workload-conformance/).\nThe working group is writing a shared standard for how [workloads](https://kubernetes.io/docs/concepts/workloads/) behave at runtime on Kubernetes.\nTo get it right, we need input from the people who build those workloads and from the people who run the clusters they're deployed on.\n\n[Certified Kubernetes](https://www.cncf.io/training/certification/software-conformance/) tests the cluster, and [Kubernetes AI Conformance](https://github.com/cncf/k8s-ai-conformance) tests whether a cluster can run AI and ML workloads.\nNothing comparable exists for the workloads themselves, so cluster operators still check each application by hand before routine maintenance or a Kubernetes upgrade.\n\nThe problems they find are familiar. A routine [node drain](https://kubernetes.io/docs/tasks/administer-cluster/safely-drain-node/) is often how you discover that an application can't tolerate disruption.\nAn upgrade can break an application that still depends on a [removed API version](https://kubernetes.io/docs/reference/using-api/deprecation-guide/).\nOthers show up in day-to-day operation: workloads that ask for privileges they don't need, or reserve resources they never use.\n\nKubernetes already documents much of this, including [security](https://kubernetes.io/docs/concepts/security/) and [handling disruptions](https://kubernetes.io/docs/concepts/workloads/pods/disruptions/).\nEven so, every cluster operator ends up repeating the same assessment, and application maintainers get the same questions from each environment they support.\nA common specification with repeatable tests would give both groups the same baseline to start from.\n\nThe [charter](https://github.com/kubernetes/community/blob/main/wg-workload-conformance/charter.md) sets out three deliverables:\n\nThe first step is deciding which workloads and behaviors the specification covers. 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. However, one rule is already set: every requirement needs an objective test that a test binary can run, so nothing subjective goes into the specification.\n\nThe specification covers how a workload runs, and importantly not what it does. Consequently, application logic is out of scope of workload conformance.\nThe binary won't retest anything [Certified Kubernetes](https://www.cncf.io/training/certification/software-conformance/) already covers, and it won't require a particular workload packaging format, or vendor tool like policy engine, security scanner, etc.\n\nTwo Special Interest Groups (SIGs) are sponsors for the working group.\n\nWhenever a requirement touches another Kubernetes SIG's area, such as node behavior or networking, the working group will initiate conversations with those SIGs as well.\n\nThe working group is a forum where SIGs can get involved and shape the direction of Workload Conformance while the specification is being written. We're aiming for a stable first specification and working tests within two to three Kubernetes release cycles.\n\nThe specification will and needs to be built from real examples, so we want to hear your experiences. If you run clusters, tell us how you assess workloads today and what broke during your last upgrade or maintenance window. If you maintain an application, tell us what it needs from the cluster and where the existing guidance left you guessing.\n\nYou can find us in [`#wg-workload-conformance`](https://kubernetes.slack.com/messages/wg-workload-conformance) on Kubernetes Slack (visit [slack.k8s.io](https://slack.k8s.io/) for an invitation) and on the [mailing list](https://groups.google.com/a/kubernetes.io/g/wg-workload-conformance).\nThe working group meets every other Wednesday at 15:00 UTC.\nThe Zoom link and the agenda are in the [meeting notes](https://docs.google.com/document/d/16GPnmukPqbTkauWb3CtXzA3aEDUXoVKY34gA41YQmPk/edit).\nIf you want to raise a topic, add it to the agenda.\nJoining the mailing list usually adds the meeting invite to your calendar.\n\nThanks to everyone who reviewed and supported the [working group proposal](https://github.com/kubernetes/community/pull/9139).", "url": "https://wpnews.pro/news/announcing-the-workload-conformance-working-group", "canonical_source": "https://kubernetes.io/blog/2026/10/27/announcing-workload-conformance-wg/", "published_at": "2026-10-27 04:30:00+00:00", "updated_at": "2026-11-14 00:53:09.976286+00:00", "lang": "en", "topics": ["ai-infrastructure", "developer-tools", "mlops"], "entities": ["Kubernetes", "Workload Conformance Working Group", "Certified Kubernetes", "Kubernetes AI Conformance", "Cloud Native Computing Foundation", "Kubernetes Slack"], "also_reported_by": [], "takeaway": "The working group's charter requires every workload conformance requirement to have an objective test runnable by a test binary, with a stable first specification and working tests targeted within two to three Kubernetes release cycles.", "recommendation": null, "alternates": {"html": "https://wpnews.pro/news/announcing-the-workload-conformance-working-group", "markdown": "https://wpnews.pro/news/announcing-the-workload-conformance-working-group.md", "text": "https://wpnews.pro/news/announcing-the-workload-conformance-working-group.txt", "jsonld": "https://wpnews.pro/news/announcing-the-workload-conformance-working-group.jsonld"}}