feat(status): warn when the workspace lost its bundle components#74
Merged
Conversation
`grounds cluster status` rendered an emptied workspace as a perfectly healthy `active` / `0 ready` — the exact output a working, freshly created workspace produces. When a vCluster loses its state (idle-pause stranded its RWO volume), nothing in the CLI said anything was wrong. forge now returns `bundleHealth` on GET /v1/cluster (the components it installed vs. what is actually running). Surface it: a `bundle` row in the table, plus an error block naming the missing components and pointing at `grounds cluster reset`.
This was referenced Jul 11, 2026
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
1 participant
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.
grounds cluster statusrendered an emptied workspace as a perfectly healthy one:which is byte-for-byte what a working, freshly-created workspace looks like. When a vCluster loses its state (idle-pause stranded its RWO Cinder volume, taking etcd with it), nothing in the CLI said anything was wrong — it took a manual
kubectl get podsto discover the bundle base was gone.forge now returns
bundleHealthonGET /v1/cluster(groundsgg/grounds-forge#450) — the components it installed vs. what is actually running in the vCluster. This surfaces it:Quiet when healthy. Tests cover both (degraded renders the components + the remedy;
okwarns about nothing).