Wrong test scope
A disruptive test can start without a shared decision about risk and permissions.
QA and release evidence
Make Kubernetes conformance tests repeatable and easy to review.
ClusterPilot links each Sonobuoy test to the exact cluster, release, settings, permissions, result and cleanup status. QA and platform teams see the same record.
Operational challenge
A passing result is only part of the check.
A reliable test also needs the right tool version, clear permissions, saved results and proof that temporary resources were removed.
Results on one computer
Results may stay on a workstation and lose their link to the exact cluster and release.
Cleanup not confirmed
Temporary namespaces, workloads or credentials may remain after the test.
Enterprise value
A repeatable test and approval process.
The value comes from shared state, explicit ownership and reviewable execution.
Explicit admission
Cluster state, selected mode, permissions, tool identity, storage and disruption boundary are checked before execution.
Immutable result snapshot
Result, logs, archives, checksums, cluster/release identity and timestamps remain tied to the run.
Visible cleanup
Cleanup is a first-class state with evidence, timeout and a safe operator next action.
Controlled workflow
From test request to accepted evidence
The validation path stays inspectable before, during and after Sonobuoy execution.
Select and admit
Choose the approved mode, cluster and release; validate health, permissions, capacity, storage and tool digest.
Execute visibly
Create an OperationRun, follow ordered preparation and Sonobuoy steps, and retain correlated events and logs.
Collect immutably
Capture status, result archive, checksums, summaries, cluster identity, inputs and exact tool version.
Clean and accept
Remove temporary resources, prove cleanup and record the release/environment acceptance decision.
Evidence
Evidence for QA, release and platform teams.
The validation record answers what ran, where it ran, what it produced and whether the environment returned to a known state.
Scope
Cluster identity, Kubernetes version, release, Sonobuoy mode, plugin selection and admission decision.
Result
Terminal status, summary, archives, checksums, logs, durations and stable failure context.
Acceptance
Cleanup outcome, retained artifacts, reviewer decision, expiry and link to the evaluated release.
Honest product boundary
Conformance is evidence—not a blanket certification claim
- A Sonobuoy result applies to the tested cluster, mode, release and point in time.
- ClusterPilot does not claim Kubernetes certification merely because a conformance workflow exists or passes.
- v0.0.1 exposes conformance as a gated candidate workflow that requires environment-specific approval.
Frequently asked questions
Questions about Kubernetes Conformance Testing
Clear answers about fit, boundaries and the evaluation path.
Which conformance tool is documented?+
The v0.0.1 documentation defines a pinned Sonobuoy workflow and records the exact tool identity with each validation run.
Does a passing result certify the entire platform?+
No. The result is evidence for the tested cluster, release, scope and time. Certification and regulatory conclusions require their own process.
What happens when cleanup fails?+
Cleanup remains visible as an operation state with diagnostics and a safe next action; the workflow should not be accepted while residual resources are unexplained.
Capability scope: v0.0.1 release candidate. Review the current release boundary →
Start with a measurable workflow
Translate the requirements into a bounded technical evaluation.
We will review the environment, operational bottleneck, control boundaries and evidence needed for a decision.
hello@clusterpilot.de