chore(doc,versions): Update README and Versions for 26.09

[mc-nv]

What does the PR do?

Advances main to the 26.09 release train. Cherry-picked from r26.09
(#171): bumps container tags/examples 26.08 -> 26.09 across 22 tutorial
files.

Checklist

• PR title reflects the change and is of format <commit_type>: <Title>
• Changes are described in the pull request.
• Related issues are referenced.
• Populated github labels field
• Added test plan and verified test passes.
• Verified that the PR passes existing CI.
• Verified copyright is correct on all changed files.
• Added succinct git squash message before merging.
• All template sections are filled out.

Commit Type:

• docs

Related PRs:

• post: advance main to 26.09 upstreams client#933

Where should the reviewer start?

README.md / container-tag references across the tutorial examples.

Test plan:

• pre-commit run on changed files passed.

Caveats:

None.

Background

Part of the post-26.09-release "advance default branches" step
(triton-release-post-advance-default-branches skill).

Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)

• Resolves: TRI-1872

[greptile-apps]

Confidence Score: 4/5

[Low risk] Updates documentation and version references to 26.09.

The PR appears safe to merge, though the Python API instructions and EKS image defaults should be aligned with the release update.

Findings

1.  Launch instructions name wrong image ▶
2.  EKS image tags remain outdated ▶

Summary

This PR advances Triton server, SDK, vLLM, and TensorRT-LLM image references to 26.09 across tutorial documentation and build assets.

• Stable Diffusion and Python API build defaults move to 26.09.
• The Python API launch instructions and EKS chart defaults still need alignment with the images they describe.

_{Reviews (1) · Last reviewed commit: "chore(doc,versions): Update README and V..."}

[greptile-apps]

Launch instructions name wrong image The guide says ./run.sh starts the newly built r26.09 image, but the script still defaults to triton-python-api:r24.08. Someone following the build-and-run steps will launch an older image, or get an error if that tag is absent. Align the default or show how to pass --image.

Knowledge Base Used: Triton Python API workflows

[greptile-apps]

EKS image tags remain outdated This containerfile now uses the 26.09 base, but the chart’s default serving image and the build instructions still use triton_trtllm_multinode:24.07. A deployment using the supplied chart values will not select the newly built release image unless users override or deliberately retag it. Align the build instructions and chart values with the intended release.

Knowledge Base Used: Kubernetes TensorRT-LLM deployments