Home / Blog / Kubernetes announces Workload Conformance Working Group
Engineering

Kubernetes announces Workload Conformance Working Group

On October 27, 2026, Nabarun Pal announced the Kubernetes Workload Conformance Working Group, writing a shared standard for how workloads behave at runtime.

By Dillip Chowdary • Oct 27, 2026 • Source: Kubernetes Blog

Kubernetes announces Workload Conformance Working Group
Illustration · Pexels

At a glance

Announced
October 27, 2026
Announced by
Nabarun Pal (Broadcom)
Deliverables
Spec, test method, conformance tooling
Scope areas
7, including security and networking
Meetings
Every other Wednesday, 15:00 UTC
Target
Stable first spec in 2-3 release cycles

On Tuesday, October 27, 2026, Nabarun Pal of Broadcom announced on behalf of WG Workload Conformance that the Kubernetes community now has a Workload Conformance Working Group. Kubernetes Blog's report says the group is writing a shared standard for how workloads behave at runtime on Kubernetes. "To 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," Pal wrote. It was last modified October 26, 2026 at 9:08 AM PST.

This piece covers the missing standard for workloads, the three deliverables in the charter, the SIG sponsors, and how operators, maintainers, reviewers, and test authors can take part. It is for cluster operators who check each application by hand before routine maintenance or a Kubernetes upgrade, and for application maintainers who get the same questions from each environment they support.

01The announcement

A routine node drain is often how an operator discovers that an application cannot tolerate disruption. An upgrade can break an application that still depends on a removed API version. Others show up in day-to-day operation: workloads that ask for privileges they do not need, or reserve resources they never use.

A routine node drain is often how an operator discovers that an application cannot tolerate disruption. An upgrade can break an application that still depends on a removed API version. Others show up in day-to-day operation: workloads that ask for privileges they do not need, or reserve resources they never use.

A common specification with repeatable tests would give both groups the same baseline to start from. Pal announced the working group on behalf of WG Workload Conformance and thanked everyone who reviewed and supported the working group proposal. The blog revision cited on the page is 67216389b4.

A common specification with repeatable tests would give both groups the same baseline to start from. Pal announced the working group on behalf of WG Workload Conformance and thanked everyone who reviewed and supported the working group proposal. The blog revision cited on the page is 67216389b4.

02What actually changed

The Workload Conformance Working Group charter sets out three deliverables: a specification of workload behavior for each Kubernetes minor version, a method for testing each requirement against a running workload, and upstream conformance tooling that implements those tests. The 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. The group has not yet agreed on specific requirements or on how to test them.

One rule is already set: every requirement needs an objective test that a test binary can run, so nothing subjective goes into the specification. "The specification covers how a workload runs, and importantly not what it does," the announcement states.

Application logic is out of scope of workload conformance. The binary will not retest anything Certified Kubernetes already covers, and it will not require a particular workload packaging format, or a vendor tool such as a policy engine or a security scanner.

Advertisement

Tech Pulse Daily

Get tomorrow's pulse first

Join engineers who read Tech Pulse before stand-up. Free, weekday mornings.

03Who should care

SIG Apps will bring the application perspective. When a requirement touches another SIG's area, such as node behavior or networking, the working group will initiate conversations with those SIGs. The working group is a forum where SIGs shape the direction of Workload Conformance while the specification is being written.

SIG Apps will bring the application perspective. When a requirement touches another SIG's area, such as node behavior or networking, the working group will initiate conversations with those SIGs. The working group is a forum where SIGs shape the direction of Workload Conformance while the specification is being written.

Cluster operators should care because they still assess each application by hand before routine maintenance or a Kubernetes upgrade, and a node drain is often the moment an application shows it cannot tolerate disruption. Application maintainers should care because each environment they support asks the same questions, including about a removed API version, extra privileges, and reserved resources the workload never uses. The subproject will outlive the working group, so the organizers are also looking for people who want to maintain it for the long term.

04How to try it

Application maintainers can describe what an application needs from the cluster and where the existing guidance left them guessing. Beyond examples, the work needs reviewers for proposed requirements and contributors to write the tests and tooling. The group wants early testers when early versions of the tests are ready.

Application maintainers can describe what an application needs from the cluster and where the existing guidance left them guessing. Beyond examples, the work needs reviewers for proposed requirements and contributors to write the tests and tooling. The group wants early testers when early versions of the tests are ready.

Early testers are asked to run the binary against their own workloads and say where the results differ between runs or environments. If a requirement touches a SIG's area, that SIG helps check its scope and the test behind it.

Meetings are every other Wednesday at 15:00 UTC, with the Zoom link and the agenda in the meeting notes. A topic is raised by adding it to the agenda. Joining the mailing list usually adds the meeting invite to the calendar.

Meetings are every other Wednesday at 15:00 UTC, with the Zoom link and the agenda in the meeting notes. A topic is raised by adding it to the agenda. Joining the mailing list usually adds the meeting invite to the calendar.

05What to watch next

Every requirement that is accepted needs an objective test that a test binary can run, so nothing subjective goes into the specification. The aim is a stable first specification and working tests within two to three Kubernetes release cycles. Nabarun Pal stated that aim in the announcement.

Every requirement that is accepted needs an objective test that a test binary can run, so nothing subjective goes into the specification. The aim is a stable first specification and working tests within two to three Kubernetes release cycles. Nabarun Pal stated that aim in the announcement.

The deliverable to watch is a specification of workload behavior for each Kubernetes minor version, a test method that runs each requirement against a running workload, and upstream conformance tooling. SIG Architecture creates the subproject that will own the specification and tooling once the Working Group proposes the first artifacts.

That subproject will outlive the working group. When early versions of the tests are ready, testers run the binary on their own workloads and report where results differ between runs or environments.

Frequently asked questions

What is the Kubernetes Workload Conformance Working Group?

It is a Kubernetes community group announced on Tuesday, October 27, 2026, by Nabarun Pal of Broadcom on behalf of WG Workload Conformance. The group is writing a shared standard for how workloads behave at runtime on Kubernetes.

How does Workload Conformance relate to Certified Kubernetes and Kubernetes AI Conformance?

Certified Kubernetes tests the cluster. Kubernetes AI Conformance tests whether a cluster can run AI and ML workloads. Nothing comparable exists for the workloads themselves, which is the gap this working group is writing a specification and tests to fill.

What are the three charter deliverables?

A specification of workload behavior for each Kubernetes minor version, a method for testing each requirement against a running workload, and upstream conformance tooling that implements those tests. The aim is a stable first specification and working tests within two to three Kubernetes release cycles.

What is out of scope for Kubernetes workload conformance?

Application logic is out of scope. The announcement states that the specification covers how a workload runs, and importantly not what it does. The test binary will not retest anything Certified Kubernetes already covers, and it will not require a particular workload packaging format or a vendor tool such as a policy engine or a security scanner.

How can someone take part in the Workload Conformance Working Group?

The group is in #wg-workload-conformance on Kubernetes Slack, with invitations at slack.k8s.io, and on the mailing list. It meets every other Wednesday at 15:00 UTC. The Zoom link and the agenda are in the meeting notes, and joining the mailing list usually adds the meeting invite to the calendar.

Sources

Dillip Chowdary

Author

Dillip Chowdary

Writes Tech Bytes coverage of AI, engineering, and the tools that actually ship. Editor of Tech Pulse Daily.

Related on Tech Bytes

Advertisement

5-min tech signal

Weekday briefing for engineers who skip the noise.

No spam · Unsubscribe anytime

Advertisement

✈️ CareerPilot

Your AI job-search copilot

Match your resume against live Ashby, Greenhouse & Lever openings — fit scores, job-specific resume optimization and email alerts.

Find matching jobs →

Free Tools

Browse all tools →