Skip to content

[Backport release-0.5] Correct what the telemetry guide says about egress and credentials - #508

Merged
negz merged 1 commit into
release-0.5from
backport-504-to-release-0.5
Oct 7, 2026
Merged

negz merged 1 commit into
release-0.5from
backport-504-to-release-0.5

Conversation

@github-actions

@github-actions github-actions Bot commented Oct 6, 2026

Copy link
Copy Markdown

Description

Backport of #504 to release-0.5.

Three claims in one paragraph of the shipped guide are wrong, and the third
is about where a user's credential is held.

"Your clusters reach the control plane, and only the control plane reaches
your backend." Modelplane composes a collector onto each inference cluster
and no collector onto the control plane. Each cluster exports to the sinks
itself.

"A cluster with no route to your observability stack still reports." It does
not. Without a route to the backend it exports nothing.

"The backend's credential lives in one place instead of on every GPU
cluster." The opposite is true, and deliberately so: compose-serving-stack
resolves the Secret a sink names and composes a copy onto every cluster that
runs a collector, because the collector mounts it there. A reader deciding
whether to give Modelplane a vendor token would have read this and been
wrong about where the token ends up.

The guide elsewhere describes the copy correctly, so this paragraph is the
one place that contradicts both the code and the rest of the page.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Signed-off-by: Dennis Ramdass <dennis@upbound.io>
(cherry picked from commit b64bf8d)
@negz
negz merged commit 3bd9c82 into release-0.5 Oct 7, 2026
4 of 5 checks passed
@negz
negz deleted the backport-504-to-release-0.5 branch October 7, 2026 21:34
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