Futureweb

Open Source

Workload conformance is a charter

Kubernetes announced a Workload Conformance group on October 27. The charter wants a testable standard. Certification waits on SIG Architecture.

The short version

No. The October 27 announcement and the charter describe a working group. SIG Architecture has not approved a standard, and the charter says a certification program is out of scope for the group.

The announcement

On October 27, 2026, the Kubernetes project announced a Workload Conformance working group. Nabarun Pal wrote the post on the group's behalf. The post says Certified Kubernetes checks the cluster, and that no shared community standard checks how a workload behaves at runtime on top of that cluster. The deliverables named are a specification for each Kubernetes minor version, a way to test each requirement against a running workload, and upstream tooling. The post says the first step, deciding which behaviors are in the specification, is not done. One rule is already stated: a requirement needs an objective test, so a subjective rule does not enter the spec.

The charter

The charter is the longer document. It says the specification covers security posture, behavior under disruption, resource footprint, networking, storage, API usage, and observability, and that each of those still has to be made into an objective test before it counts. It says the group does not own code. SIG Architecture creates a subproject when the first artifacts exist, reviews them, and can withhold approval. If approval never comes, Steering decides whether the group continues. The charter also says the Kubernetes project will not endorse a certification program until SIG Architecture approves a standard, and that running such a program is CNCF's concern, not the group's.A name is not a location.

The proposal issue

The community tracker shows a proposal, kubernetes/community issue 9139, opened in September 2026. The October 27 post is the announcement that the group now exists. A proposal issue is how the project records the ask. The announcement is how the project tells users the ask was accepted as a working group. Neither document contains a test binary. Origin Range was a cache rule with a date. This charter has a meeting time and no conformance badge.Origin Range.

What a workload author has today

A person shipping software onto Kubernetes does not have a new badge to pass. The announcement invites cluster operators and application maintainers to bring examples of what broke on an upgrade or a node drain. That invitation is a call for stories, not a checklist. The group expects two to three release cycles to reach a stable first specification. If the work finishes sooner, the charter says the group can wind down sooner. systemd's Rust limit was a boundary on which programs the project would rewrite. This charter is a boundary on what the future spec is allowed to demand: only what a test can check.systemd's leaf programs.

Application logic stays out

The announcement says the binary will not retest what Certified Kubernetes already covers, and will not require a packaging format or a vendor policy engine. The workload's own business logic is out of scope. A reader who hears conformance and pictures a security scanner has gone past the document. SpaceDB's pin was a house choice of a datastore, not a Kubernetes test. It is linked so a product name on another desk is not borrowed as this working group's output.The SpaceDB pin.

The Node patch is a release

The Node October release was a patch a user can install. Workload conformance, on October 27, is a charter a user cannot install. Both are software-community documents. Only one of them changes a runtime today. The JetBrains terminal post is a third kind of document, a vendor swapping a library. The working group has not swapped anything. Asked directly, What has the group already agreed? The announcement says every requirement needs an objective test a program can run. It also says specific requirements are not agreed yet.The Node October patch.

Who is in scope

The people the announcement addresses are cluster operators, application maintainers, and SIG members whose area a future requirement might touch. Nobody is required to do anything this week. Slack channel and mailing-list details are in the post for people who want to attend. Attendance is not conformance. Asked directly, Who announced the working group? Nabarun Pal, writing on October 27, 2026, on behalf of the group. Asked directly, When does the charter expect a stable spec? In two to three Kubernetes release cycles. The group meets every other Wednesday at 15:00 UTC.

What this page will not predict

This page will not guess which rules will survive the two-to-three-cycle window, and it will not treat the charter's topic list as requirements already written. Security, networking, and storage are areas the charter says the spec may cover once a test exists. An area is not a rule. A reader who needs a rule today still has whatever their own cluster already enforces. Asked directly, Who sponsors the group? SIG Architecture is to own the specification and tooling through a subproject created when the first artifacts exist. SIG Apps participates.

The record

The record is the October 27 announcement, the working-group charter, and the community proposal issue. The group exists. The specification does not. The certification program, the charter says, is not this group's job, and it is not approved. AI Conformance's later move under SIG Architecture is a separate governance filing. The short answer this page will stand on is this: No. The October 27 announcement and the charter describe a working group. SIG Architecture has not approved a standard, and the charter says a certification program is out of scope for the group.AI Conformance.

Sources

The reports this brief is filing. Futureweb did not republish them.

  1. Kubernetes
  2. Charter
  3. Proposal

Questions

Who announced the working group?

Nabarun Pal, writing on October 27, 2026, on behalf of the group.

What has the group already agreed?

The announcement says every requirement needs an objective test a program can run. It also says specific requirements are not agreed yet.

Who sponsors the group?

SIG Architecture is to own the specification and tooling through a subproject created when the first artifacts exist. SIG Apps participates.

When does the charter expect a stable spec?

In two to three Kubernetes release cycles. The group meets every other Wednesday at 15:00 UTC.

Does the charter cover application logic?

The charter says the specification covers how a workload runs, and that the workload's own application logic is out of scope.