Repository navigation
feat(vermeer): expose independent cluster readiness and process telemetry - #369
Merged
Merged
Conversation
added 2 commits
October 29, 2026 12:07
Report administrator-scoped Master and Worker readiness, collect process CPU and RSS independently, and cover stream lifecycle and availability checks.
3 of 9 tasks
MrJs133
approved these changes
Oct 29, 2026
4 of 8 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Before → After
Before: Hubble cannot distinguish registered Vermeer Workers from workers ready to receive compute work, and resource telemetry is not exposed as a deployment snapshot.
After: Add an administrator-scoped, read-only
/api/v1/admin/clustersnapshot with separate readiness checks and CPU/RSS availability. Preserve worker identities and counts when bounded telemetry collection times out or is cancelled; extend Worker statistics compatibly.Dependencies and validation boundary
Pair with 🔗 Toolchain #868 and 🔗 Server #3434. The author reports Go unit/race checks and local Master/Worker integration; these are not independent validation here. Container images remain unpublished and no Helm rollout or RC acceptance is established.
Source: 🔗 org Computer #22.
Visual overview
The administrator cluster snapshot separates registration/readiness evidence from process CPU/RSS telemetry. Worker metadata is retained when bounded resource sampling is unavailable, cancelled or warming up. The illustrated 800 ms budget applies to Worker RPC telemetry collection, not an independently measured end-to-end response guarantee. Existing authentication mode and admin authorization rules are unchanged; paired images and separate deployment/RC acceptance are required.