docs(compliance): add Kubernetes conformance results page - #658
Merged
Conversation
Records conformance runs across five Kubernetes releases on self-hosted Cozystack alongside the existing CNCF listings for Hikube, so both the distribution and the hosted shapes of the platform are covered. Documents the two cluster properties a conformance run depends on — a dedicated tenant etcd and an explicit compaction interval — since neither is discoverable from a failing run. Co-Authored-By: Claude <noreply@anthropic.com> Signed-off-by: tym83 <6355522@gmail.com>
✅ Deploy Preview for cozystack ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Timur Tukaev (tym83)
marked this pull request as ready for review
August 19, 2026 13:04
Timur Tukaev (tym83)
requested review from
Andrei Kvapil (kvaps),
Timofei Larkin (lllamnyp) and
myasnikovdaniil
as code owners
August 19, 2026 13:04
Timur Tukaev (tym83)
added a commit
that referenced
this pull request
Aug 19, 2026
…sions (#660) ## Summary Follow-up to #658: adds the fifth conformance run and corrects which versions were actually submitted to the CNCF. Both landed on the branch after #658 was merged, so they missed it. ## What - Adds the v1.31.14 row to the results table: **404 passed, 0 failed** of 6607 specs. That completes the set — all five Kubernetes releases the platform offers now have a published run, none with a failure. - Corrects the submission scope. The page said results for v1.35, v1.34 and v1.33 were submitted. With v1.36 the current Kubernetes release, the programme accepts v1.35 and v1.34 only, and the v1.33 submission was withdrawn on that basis. Fixed in the results section, the FAQ and the notes. - Updates the surrounding prose that referred to four releases and used v1.32 as the oldest example. ## Why The correction matters more than the extra row: as merged, the page claims a submission that does not exist. The v1.33 entry was closed after the CNCF conformance bot pointed out it was outside the window. ## Verification `hugo` builds clean, `hack/check-i18n.sh` passes.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a Kubernetes conformance page under the Compliance section, covering both shapes the platform is used in.
What
content/en/compliance/kubernetes-conformance.mdhugo.yamlunder the existing Compliance parentcontent/en/compliance/_index.mdupdated to list itThe page records conformance runs on self-hosted Cozystack across five Kubernetes releases, alongside the existing CNCF listings for Hikube, the hosted platform built on Cozystack. It also documents the two cluster properties a conformance run depends on — a dedicated tenant etcd, and an explicit
--etcd-compaction-interval— and the Talos-specific reason for running only thee2eplugin.Why
Conformance is the first question in most platform evaluations, and until now the answer lived only in a third party's submission. Publishing both the distribution results and the hosted ones is more useful to an evaluator and more accurate about what each result covers.
The older releases are deliberately included. Conformance holding on v1.32 tells someone migrating from an existing platform that they can move at the Kubernetes version they run today and upgrade afterwards, rather than doing both at once. The page states plainly that those releases no longer receive upstream patches, so they read as a migration path rather than a destination.
Wording follows the trademark constraint throughout: these are conformance runs, and the page does not claim the Certified Kubernetes mark.
Preview
Netlify deploy preview,
/compliance/kubernetes-conformance/.