From e822cce6e0a79b33b287abf2a9cdaa740a9f9b03 Mon Sep 17 00:00:00 2001 From: Abdullah Kaya Date: Fri, 7 Aug 2026 02:00:02 +0300 Subject: [PATCH] feat(support): publish the commercial support commitment at /support MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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) --- src/components/sections/SupportSection.astro | 189 +++++++++++++++++++ src/data/deploy-targets.test.ts | 10 + src/data/deploy-targets.ts | 15 ++ src/data/section-seo.ts | 19 ++ src/data/sections.test.ts | 11 ++ src/data/sections.ts | 20 ++ src/lib/github-stars.ts | 1 + src/pages/[section].astro | 2 + 8 files changed, 267 insertions(+) create mode 100644 src/components/sections/SupportSection.astro diff --git a/src/components/sections/SupportSection.astro b/src/components/sections/SupportSection.astro new file mode 100644 index 0000000..ced8b3f --- /dev/null +++ b/src/components/sections/SupportSection.astro @@ -0,0 +1,189 @@ +--- +// The page a certification reviewer or a procurement team gets sent to. +// +// SUSE Ready for Rancher asks the vendor to (a) provide commercial support on +// named Rancher and RKE2/K3s versions and (b) publish those versions in its +// documentation *and on its web site*. This is the web-site half; the +// repository half is docs/RANCHER.md. The two tables must stay in step — if one +// gains a row or a validated version, so does the other, in the same change. +import SectionHeader from './SectionHeader.astro'; +import { VENDOR, VENDOR_ADDRESS_FULL } from '../../data/company'; + +const RANCHER_DOCS = 'https://github.com/libredb/libredb-studio/blob/main/docs/RANCHER.md'; +const SECURITY_MD = 'https://github.com/libredb/libredb-studio/blob/main/SECURITY.md'; +const ISSUES = 'https://github.com/libredb/libredb-studio/issues'; +const SUSE_CATALOG = 'https://www.suse.com/pcsc/viewVersionPage?versionID=26969'; + +// "Supported" is what the commitment above covers. "Validated" is what we have +// actually exercised end to end and published a result for — an em dash means +// supported on the same terms but not yet in a published test run. Never turn a +// dash into a version without a run behind it: this table is read as evidence. +const platforms = [ + { + component: 'SUSE Rancher Prime and Rancher (community)', + supported: '2.9 or later', + validated: '2.14.3 (community build)', + }, + { component: 'SUSE K3s', supported: '1.26 or later', validated: 'v1.31.14+k3s1, v1.35.5+k3s1' }, + { component: 'SUSE RKE2', supported: '1.26 or later', validated: '—' }, + { component: 'Kubernetes', supported: '1.26 or later', validated: 'v1.31.14, v1.35.5' }, + { component: 'Any CNCF-conformant distribution', supported: '1.26 or later', validated: '—' }, + { component: 'Architectures', supported: 'linux/amd64, linux/arm64', validated: 'linux/amd64' }, +]; + +const scope = [ + { + area: 'Deployment', + detail: + 'Helm chart installation, upgrades and rollback on the versions above — including the Rancher Apps catalog path via a ClusterRepo, and air-gapped installs from your own registry.', + }, + { + area: 'Configuration', + detail: + 'OIDC single sign-on, role mapping, storage backends, seed connections, ingress and TLS, and the hardened chart defaults (non-root, read-only root filesystem, NetworkPolicy, PDB, HPA).', + }, + { + area: 'Defects', + detail: + 'Triage and fixes for reproducible defects, shipped in tagged releases. Serious bugs are disclosed in the release notes rather than fixed quietly.', + }, + { + area: 'Security', + detail: + 'Coordinated disclosure, timely patching of critical vulnerabilities, and advisories published in the repository security tab.', + }, +]; + +const channels = [ + { need: 'Commercial support enquiries', href: `mailto:${VENDOR.email}`, label: VENDOR.email, external: false }, + { need: 'Security vulnerabilities', href: SECURITY_MD, label: 'SECURITY.md', external: true }, + { need: 'Community questions and bug reports', href: ISSUES, label: 'GitHub issues', external: true }, +]; +--- + +
+ + + +
+

The vendor of record

+

+ LibreDB Studio is developed, published and commercially supported by{' '} + {VENDOR.legalName} ({VENDOR.tradeName}), a company registered in + Türkiye. LibreDB is the product brand; {VENDOR.tradeName} is the legal entity behind the commitment on this page. +

+

{VENDOR_ADDRESS_FULL}

+
+ + Company information + + + SUSE Partner Certification & Solutions Catalog + +
+
+ + +

+ {VENDOR.tradeName} provides commercial support for LibreDB Studio on every Rancher, K3s, RKE2 and Kubernetes version + listed below. + Support is available in English and Turkish. LibreDB Studio itself stays MIT-licensed and free — support is a service + on top of it, never a paywall in front of it. +

+ +

Supported platform versions

+ +
+ + + + + + + + + + { + platforms.map((p) => ( + + + + + + )) + } + +
ComponentSupportedValidated
{p.component}{p.supported}{p.validated}
+
+ +

+ Supported is what the commitment above covers. + Validated is what we have exercised end to end and published a result for; + an em dash means the same support terms apply, but no test run is published yet. The chart uses only core Kubernetes APIs + and carries no distribution-specific dependencies, so the version floor comes from the chart's{' '} + kubeVersion constraint rather than from distribution features. +

+ + + Rancher deployment & validation record + + +

What support covers

+ +
+ { + scope.map((s) => ( +
+

{s.area}

+

{s.detail}

+
+ )) + } +
+ +

How to reach us

+ +
+ { + channels.map((c) => ( + + )) + } +
+ +

+ -- supported is a promise; validated is a receipt. This page keeps them apart. +

+
+