Skip to content

feat: Link the CRD reference on the Stackable Hub#888

Open
lfrancke wants to merge 1 commit into
mainfrom
feat/crd-links-to-hub
Open

feat: Link the CRD reference on the Stackable Hub#888
lfrancke wants to merge 1 commit into
mainfrom
feat/crd-links-to-hub

Conversation

@lfrancke

@lfrancke lfrancke commented Jul 16, 2026

Copy link
Copy Markdown
Member

Description

Our Hub now uses a similar URL style to the old CRD browser which means we can switch the docs to use the Hub instead of the old one.

To help with that there are new attributes in antora.yml:

  • crd-ref - the listing (https://hub.stackable.tech/crds)
  • {crd-ref}/<group>/<apiVersion>/<kind>{crd-ref-release} - a deep link
  • crd-ref-release - ?release=dev on main, the release number on release branches (same mechanism as crd-docs-version today)

Converted: the reference nav entry, the landing page link, and the five deep links (AuthenticationClass ×3, S3Bucket, S3Connection).

Deliberately unchanged

  • The old crd-docs-* attributes stay: the operator repos still build their deep links from them (~40 links). We need to update those separately :( (I'll do it...)
  • page-crd-docs is removed - nothing in the UI templates reads it.

@netlify

netlify Bot commented Jul 16, 2026

Copy link
Copy Markdown

Deploy Preview for stackable-docs ready!

Name Link
🔨 Latest commit b9dc3c4
🔍 Latest deploy log https://app.netlify.com/projects/stackable-docs/deploys/6a58895c95227200083a3261
😎 Deploy Preview https://deploy-preview-888--stackable-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

The docs' own pages now link https://hub.stackable.tech/crds instead of
the old CRD browser on crds.stackable.tech, using the new attributes:

  crd-ref: the listing
  {crd-ref}/<group>/<apiVersion>/<kind>{crd-ref-release}: a deep link

crd-ref-release is ?release=dev on this branch and gets the release
number on release branches (like crd-docs-version today).

The old crd-docs attributes stay until the operator repos migrate their
deep links to crd-ref (they do so in the planned operator sweep, one PR
per repo). page-crd-docs is removed: nothing in the UI templates reads
it.

The OIDC provider deep link loses its per-property anchor: the Hub has
section-level anchors only, so it points at #provider now.
@lfrancke lfrancke force-pushed the feat/crd-links-to-hub branch from 3e4086e to b9dc3c4 Compare July 16, 2026 07:33
@lfrancke lfrancke self-assigned this Jul 16, 2026
@lfrancke lfrancke moved this to Development: Waiting for Review in Stackable Engineering Jul 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Development: Waiting for Review

Development

Successfully merging this pull request may close these issues.

1 participant