Skip to content

docs: add the gateway-api-crd check to the troubleshooting page - #2174

Open
rawsun007 wants to merge 1 commit into
linkerd:mainfrom
rawsun007:docs-gateway-api-crd-check
Open

rawsun007 wants to merge 1 commit into
linkerd:mainfrom
rawsun007:docs-gateway-api-crd-check

Conversation

@rawsun007

Copy link
Copy Markdown

linkerd check added a "Gateway API CRDs are installed" check in linkerd/linkerd2#15409 with the hint anchor gateway-api-crd. When it fails, the output points at https://linkerd.io/2/checks/#gateway-api-crd, but the troubleshooting page has no section with that id, so the link lands at the top of the page.

This adds a section for it after the kubernetes-version checks, which is where the check runs, quoting the error from GatewayAPICRDsMissingError() and linking the existing Gateway API page.

I found this by comparing every hintAnchor in linkerd2's pkg/healthcheck with the {#...} ids on the 2-edge page; it was the only one missing. markdownlint passes with the site config. I did not build the site locally.

Not changed: the page also documents an "is running the minimum kubectl version" check that linkerd check no longer has. #2167 edits the section just above, but not the same lines.

AI disclosure: found and written with Claude Code (Claude Opus 5.5).

`linkerd check` links a failed "Gateway API CRDs are installed" check to
the `gateway-api-crd` hint anchor, which the checks page does not have.

Signed-off-by: Roshan Ramani <roshanramani.dev@gmail.com>
@netlify

netlify Bot commented Nov 20, 2026

Copy link
Copy Markdown

👷 Deploy request for linkerdio pending review.

Visit the deploys page to approve it

Name Link
🔨 Latest commit 183b46c

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