<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/announcing-the-workload-conformance-working-group-ve5zsyx2h" -->

---
title: Announcing the Workload Conformance Working Group
description: Kubernetes now has a Workload Conformance Working Group writing a shared standard for how workloads behave at runtime. Certified Kubernetes tests the cluster...
canonical: https://daily.dev/posts/announcing-the-workload-conformance-working-group-ve5zsyx2h
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Announcing the Workload Conformance Working Group | daily.dev
og:description: Kubernetes now has a Workload Conformance Working Group writing a shared standard for how workloads behave at runtime. Certified Kubernetes tests the cluster...
og:url: https://daily.dev/posts/announcing-the-workload-conformance-working-group-ve5zsyx2h
og:image: https://api.daily.dev/og/posts/vE5zSyX2H.png
og:image:alt: Announcing the Workload Conformance Working Group
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Announcing the Workload Conformance Working Group

**[K8S Contributors](https://daily.dev/sources/k8s_contrib)** · 4 min read · 0 upvotes · 0 comments

## Summary

Kubernetes now has a Workload Conformance Working Group writing a shared standard for how workloads behave at runtime. Certified Kubernetes tests the cluster and Kubernetes AI Conformance tests whether a cluster can run AI and ML workloads, but nothing checks the workloads themselves, so operators manually assess each app before upgrades. The charter calls for a behavior specification per Kubernetes minor version, a testing method, and upstream conformance tooling. Scope covers security, resilience, resource use, networking, storage, API usage, and observability, with every requirement backed by an objective test. SIG Architecture and SIG Apps sponsor the effort, targeting a stable first specification within two to three release cycles.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://www.kubernetes.dev/blog/2026/10/27/announcing-workload-conformance-wg>

## Questions this post answers

### What is the Kubernetes Workload Conformance Working Group and what will it deliver?

It is a new Kubernetes community working group writing a shared standard for how workloads behave at runtime, sponsored by SIG Architecture and SIG Apps. Its charter calls for a behavior specification per Kubernetes minor version, a testing method for each requirement, and upstream conformance tooling, all built on objective, test-binary-verifiable requirements rather than subjective criteria.

_Track Kubernetes governance changes like this working group on daily.dev as the workload conformance spec takes shape._

### How is Kubernetes workload conformance different from Certified Kubernetes or Kubernetes AI Conformance?

Certified Kubernetes tests the cluster itself, and Kubernetes AI Conformance tests whether a cluster can run AI and ML workloads, but neither checks the workloads running on top of the cluster. The new Workload Conformance effort targets runtime behavior like resilience to disruption, security, resource use, networking, storage, API usage, and observability, not application logic.

_Cluster operators weighing upgrade risk can follow this workload conformance work on daily.dev._

### What kinds of problems does Kubernetes workload conformance aim to catch before they break production?

It targets issues operators currently find by hand, such as applications that cannot tolerate a node drain, workloads that depend on a removed API version after an upgrade, and apps requesting unnecessary privileges or reserving unused resources. The working group wants a common specification with repeatable tests so operators and maintainers share the same baseline instead of repeating manual assessments per environment.

_Teams hardening upgrade and maintenance playbooks can follow this standard's progress on daily.dev._

## Similar posts on daily.dev

- [CNCF Launches Certified Kubernetes AI Conformance Programme To Standardise Workloads](https://daily.dev/posts/cncf-launches-certified-kubernetes-ai-conformance-programme-to-standardise-workloads-ixfhkll6v) · InfoQ · 1 upvotes · 0 comments
- [Infrastructure for AI is finally getting a standard](https://daily.dev/posts/infrastructure-for-ai-is-finally-getting-a-standard-vpa1rswka) · Giant Swarm · 30 upvotes · 0 comments
- [Kubernetes Gets an AI Conformance Program — and VMware Is Already On Board](https://daily.dev/posts/kubernetes-gets-an-ai-conformance-program-and-vmware-is-already-on-board-kpztby2by) · The New Stack · 1 upvotes · 0 comments

---

Tags: [#kubernetes](https://daily.dev/tags/kubernetes), [#cloud-native](https://daily.dev/tags/cloud-native)

[View this post on daily.dev](https://daily.dev/posts/announcing-the-workload-conformance-working-group-ve5zsyx2h)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Announcing the Workload Conformance Working Group","url":"https://daily.dev/posts/announcing-the-workload-conformance-working-group-ve5zsyx2h","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/announcing-the-workload-conformance-working-group-ve5zsyx2h"},"datePublished":"2026-10-27T06:10:44.445Z","dateModified":"2026-10-27T06:11:11.556Z","description":"Kubernetes now has a Workload Conformance Working Group writing a shared standard for how workloads behave at runtime. Certified Kubernetes tests the cluster...","image":"https://media.daily.dev/image/upload/s--qPvKM23u--/f_auto/v1722860399/public/Placeholder%2009","thumbnailUrl":"https://media.daily.dev/image/upload/s--qPvKM23u--/f_auto/v1722860399/public/Placeholder%2009","isAccessibleForFree":true,"articleSection":"K8S Contributors","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"K8S Contributors","logo":"https://media.daily.dev/image/upload/s--QfYbdBSH--/f_auto/v1729364703/logos/k8s_contrib","url":"https://daily.dev/sources/k8s_contrib"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/announcing-the-workload-conformance-working-group-ve5zsyx2h","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"kubernetes,cloud-native","timeRequired":"PT4M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"K8S Contributors","item":"https://daily.dev/sources/k8s_contrib"},{"@type":"ListItem","position":3,"name":"Announcing the Workload Conformance Working Group"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/announcing-the-workload-conformance-working-group-ve5zsyx2h#faq","mainEntity":[{"@type":"Question","name":"What is the Kubernetes Workload Conformance Working Group and what will it deliver?","acceptedAnswer":{"@type":"Answer","text":"It is a new Kubernetes community working group writing a shared standard for how workloads behave at runtime, sponsored by SIG Architecture and SIG Apps. Its charter calls for a behavior specification per Kubernetes minor version, a testing method for each requirement, and upstream conformance tooling, all built on objective, test-binary-verifiable requirements rather than subjective criteria. Track Kubernetes governance changes like this working group on daily.dev as the workload conformance spec takes shape."}},{"@type":"Question","name":"How is Kubernetes workload conformance different from Certified Kubernetes or Kubernetes AI Conformance?","acceptedAnswer":{"@type":"Answer","text":"Certified Kubernetes tests the cluster itself, and Kubernetes AI Conformance tests whether a cluster can run AI and ML workloads, but neither checks the workloads running on top of the cluster. The new Workload Conformance effort targets runtime behavior like resilience to disruption, security, resource use, networking, storage, API usage, and observability, not application logic. Cluster operators weighing upgrade risk can follow this workload conformance work on daily.dev."}},{"@type":"Question","name":"What kinds of problems does Kubernetes workload conformance aim to catch before they break production?","acceptedAnswer":{"@type":"Answer","text":"It targets issues operators currently find by hand, such as applications that cannot tolerate a node drain, workloads that depend on a removed API version after an upgrade, and apps requesting unnecessary privileges or reserving unused resources. The working group wants a common specification with repeatable tests so operators and maintainers share the same baseline instead of repeating manual assessments per environment. Teams hardening upgrade and maintenance playbooks can follow this standard's progress on daily.dev."}}]}
```

