feat(support): publish the commercial support commitment at /support - #38
Merged
Conversation
SUSE Ready for Rancher asks the vendor to provide commercial support on named
Rancher and RKE2/K3s versions, and to publish those versions in its
documentation *and on its web site*. libredb-studio#303 did the documentation
half; the site had nothing — no support statement and no mention of Rancher,
RKE2 or K3s anywhere in src/.
company.ts already carried the vendor identity for exactly this reason ("partner
programmes and certification reviews verify the vendor from the product
website"), so the new section derives the legal entity and address from it
rather than restating them, and the Service node in section-seo points at the
same @id as the vendor Organization.
The platform table mirrors the one in the studio repo's docs/RANCHER.md and
keeps its Supported/Validated split, so a dash reads as "same terms, no
published run yet" instead of implying a test that never happened. The two
tables have to move together.
Also adds the Rancher deploy card — the logo was already sitting unused in
public/logos/deploy/. It stays 'available' rather than 'official' until
rancher/partner-charts#1158 merges and the chart ships in Rancher's own
Partners repository.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
cevheri
approved these changes
Aug 6, 2026
kaya-abdullah
added a commit
that referenced
this pull request
Aug 7, 2026
The page shipped in #38 read as though it existed for the SUSE Ready for Rancher review: three of six table rows started with "SUSE", the page title led with Rancher, and the only listing link in the vendor block was the SUSE catalog. No partner programme asks for a page about itself. They ask a vendor to publish who provides commercial support and on which versions, and a page that looks built for one reviewer is weaker evidence for all of them. It also has to serve the cloud marketplaces, which want the same URL. So the table now leads with Kubernetes and carries the distributions as rows, including Red Hat OpenShift 4.15 to 4.22 from the merged community-operators-prod catalog PR. Runtimes move into their own block: a container runtime and a Node floor have no validated version in the Supported/Validated sense, and mixing them into the platform table blurred what that split means. The Node tiers come from docs/DISTRIBUTION.md rather than being asserted here. The SUSE link leaves the vendor block and joins a one-line listing sentence at the foot of the page alongside the Red Hat catalog and Artifact Hub. Only listings that have actually merged are named, so the still-open operatorhub.io submission is absent.
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
2 participants
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.
The web-site half of SUSE Ready for Rancher requirements #3 and #4. The repository half is libredb/libredb-studio#303; SUSE's step 4 says "your documentation and web site", so both are needed.
What the site was missing
grep -ri "commercial support\|rancher\|rke2\|k3s\|suse" src/returned nothing. No support statement, no platform versions, no Rancher anywhere — while we are already listed in the SUSE Partner Certification & Solutions Catalog.New
/supportsectioncompany.ts. That file's own header says "partner programmes and certification reviews verify the vendor from the product website", which is exactly this page; nothing is restated, so the page cannot drift from the footer, the privacy policy or the JSON-LD.docs/RANCHER.md, including its Supported/Validated split. A—means "same support terms, no published test run yet" rather than implying a run that never happened. If one table gains a row or a validated version, so does the other, in the same change.info@sekoya.tech,SECURITY.md, GitHub issues.Servicenode whoseprovideris the same@idas the vendorOrganization, so a crawler resolves support to a legally identified company.Rancher deploy card
public/logos/deploy/rancher.svgwas already in the repo, unused. Added under Kubernetes & orchestration, linking todocs/RANCHER.md, withrancher/rancherstars.Status is
available, notofficial— it flips once rancher/partner-charts#1158 merges and the chart ships in Rancher's own Partners repository. A test pins that so it is a deliberate change, not a drive-by edit.Checks
bun run gate(typecheck · prettier · oxlint · knip · 68 tests) andbun run buildboth pass. Two new tests cover the section wiring and the Rancher card;rancher/ranchergot a baked star fallback, whichgithub-stars.test.tsrequires.