Skip to content

docs: fix dead Triton guide links in kubeflow pipeline example - #1448

Merged
dholt merged 1 commit into
NVIDIA:masterfrom
farisbasha:docs-fix-triton-guide-links
Nov 20, 2026
Merged

dholt merged 1 commit into
NVIDIA:masterfrom
farisbasha:docs-fix-triton-guide-links

Conversation

@farisbasha

Copy link
Copy Markdown
Contributor

The kubeflow pipeline deploy example (workloads/examples/k8s/kubeflow-pipeline-deploy/README.md) links to two pages of the old triton-inference-server-master-branch-guide, which now return 404:

  • .../docs/run.html#example-model-repository -> Triton quickstart, Create A Model Repository
  • .../docs/client_example.html#section-getting-the-client-examples -> Triton quickstart, Send an Inference Request (it runs the same image_client -m densenet_onnx ... mug.jpg command as step 7)

Docs-only change, no deployment impact. The new URL returns 200 and both anchors exist on the page. Commit is signed off (DCO).

The triton-inference-server-master-branch-guide pages are gone. Point
both links to the matching sections of the Triton quickstart.

Signed-off-by: farisbasha <farisbashatm@gmail.com>

@dholt dholt left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed f9f4152. Both replacement links return HTTP 200, their anchors exist, and the sections cover the example model repository and the matching image_client invocation. The diff changes only these two documentation links; no execution paths or workflow files change.

Local validation: role lint passed (347 files), all 12 playbook syntax checks passed, and the public-content scan passed. The README retains its existing CRLF endings; the CRLF-aware whitespace check passed. No findings.

@dholt
dholt merged commit beda9b9 into NVIDIA:master Nov 20, 2026
30 checks passed
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.

2 participants