docs(rancher): declare commercial support and name the supported SUSE versions - #303
Merged
Conversation
… versions (#166) SUSE Ready for Rancher requirement #3 asks the partner to provide commercial support on the declared Rancher and RKE2/K3s versions, and #4 asks that those versions be published. docs/RANCHER.md carried neither: it said "Rancher 2.9 or later" with no vendor, no support statement and no way to tell a supported version from a validated one. Split the version table into Supported and Validated columns so the RKE2 and arm64 rows can say "supported, not yet exercised" honestly, name Rancher Prime alongside the community build the 2.14.3 run actually used, and add a Commercial support section naming Sekoya as the entity behind the commitment. SECURITY.md pointed at a personal Gmail and still listed 0.5.x/0.4.x as the supported line while the app is at 0.9.66 — both now read as a maintained product, which is what requirement #5 is asking about. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
cevheri
approved these changes
Aug 6, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
Documents commercial support and updates supported Rancher and security-policy versions.
Changes:
- Adds supported and validated Rancher/K3s/RKE2 combinations.
- Documents Sekoya’s commercial support scope and channels.
- Updates supported releases and security contacts.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
SECURITY.md |
Updates supported versions and security contact details. |
docs/RANCHER.md |
Adds validation details and commercial support documentation. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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
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.
Closes the last of our own gaps in the SUSE Ready for Rancher track (#166).
SUSE listed LibreDB Studio in the Partner Certification & Solutions Catalog on 2026-08-04, accepting our existing community-distribution testing. Of the two things Troy Topnik asked for, the catalog content is done; this PR does the other one: "document support on Rancher Kubernetes distributions".
What changed
docs/RANCHER.mdRancher | 2.9 or laterrow, and gains a Validated column. That split lets RKE2 and arm64 say "supported, not yet exercised" instead of implying a test run that never happened. The Rancher row reads2.14.3 (community build)— same release, but our evidence is from the community distribution, not Prime, and SUSE will read this page.—in the Validated column is still supported.SECURITY.mdinfo@sekoya.tech.0.9.x/< 0.9.0.Certification requirements this closes
Requirement #4 also says "documentation and web site" — the matching libredb.org update is libredb/libredb.github.io#38.
Docs-only; no executable lines, so coverage is unaffected.