Skip to content

refactor(support): make /support a general support page, not a SUSE one - #39

Merged
kaya-abdullah merged 1 commit into
mainfrom
feat/support-page-general
Aug 7, 2026
Merged

refactor(support): make /support a general support page, not a SUSE one#39
kaya-abdullah merged 1 commit into
mainfrom
feat/support-page-general

Conversation

@kaya-abdullah

Copy link
Copy Markdown
Member

Follow-up to #38, which is already merged.

The problem

The page as shipped read as though it existed for the SUSE Ready for Rancher review:

  • three of six table rows started with "SUSE"
  • the page title was "Commercial Support — LibreDB Studio on Rancher, RKE2, K3s & Kubernetes"
  • the only listing link sat at the top of the vendor block, and it was the SUSE catalog
  • the Deployment bullet opened with the Rancher Apps catalog

No partner programme asks for a page about itself. SUSE requirement #4 asks a vendor to publish the supported versions "in your documentation and web site"; Red Hat and the cloud marketplaces ask for the same thing. A page that looks built for one reviewer is weaker evidence for all of them, and DigitalOcean and Azure both want a support URL we can hand over unchanged.

What changed

Platform table leads with Kubernetes and carries the distributions as rows. The SUSE rows stay, and keep their SUSE-qualified names, because requirement #4 names those products specifically — they are just no longer the whole page. New row: Red Hat OpenShift 4.15 to 4.22.

Runtimes moved to 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 would blur what that split means.

The SUSE link left the vendor block and joined a one-line listing sentence at the foot of the page, next to the Red Hat catalog and Artifact Hub.

Title and description generalised to "Commercial Support — LibreDB Studio".

Where each version comes from

Row Source
Kubernetes 1.26+ charts/libredb-studio/Chart.yamlkubeVersion: >=1.26.0-0
K3s, RKE2, Rancher docs/RANCHER.md supported-versions table (libredb/libredb-studio#303)
OpenShift 4.15 to 4.22 redhat-openshift-ecosystem/community-operators-prod#10581, merged 2026-07-28
Node 20.9+, 24 LTS recommended docs/DISTRIBUTION.md ## npx support tiers
linux/amd64 + linux/arm64 the release workflow's build platforms

Only listings that have actually merged are named. The operatorhub.io submission (k8s-operatorhub/community-operators#8794) is still open, so it is absent.

bun run gate and bun run build pass.

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.
@kaya-abdullah
kaya-abdullah requested a review from cevheri August 6, 2026 23:58
@kaya-abdullah
kaya-abdullah merged commit 6f6c3e7 into main Aug 7, 2026
4 checks passed
@cevheri
cevheri deleted the feat/support-page-general branch August 7, 2026 00:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant