feat: add shard liveness API and UI indicator#6166
Open
krancour wants to merge 1 commit intoakuity:mainfrom
Open
feat: add shard liveness API and UI indicator#6166krancour wants to merge 1 commit intoakuity:mainfrom
krancour wants to merge 1 commit intoakuity:mainfrom
Conversation
Surface per-shard liveness in the API and UI, derived from heartbeat ConfigMaps in the Kargo namespace. A shard is considered alive when its heartbeat ConfigMap carries an observedAt timestamp within AGENT_STATUS_DEADLINE (default 10m), and dead otherwise. - Add REST endpoint GET /v1beta1/system/shards returning each known shard's alive/dead status and last-heartbeat timestamp. - Add api.defaultShardName chart value plus DEFAULT_SHARD_NAME on the API server, used to resolve Stages with no explicit spec.shard. - Render a small shard-status indicator (broadcast tower icon, green for alive, red for dead, hidden when no shard data is available) on each Stage card in the project DAG view. - Default the Tilt dev environment to a single shard named 'tilt-shard' so the indicator has something to render. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Signed-off-by: Kent Rancourt <kent.rancourt@gmail.com>
krancour
added
area/ui
✅ Deploy Preview for docs-kargo-io ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #6166 +/- ##
==========================================
+ Coverage 57.72% 57.74% +0.02%
==========================================
Files 475 476 +1
Lines 40541 40584 +43
==========================================
+ Hits 23402 23435 +33
- Misses 15746 15754 +8
- Partials 1393 1395 +2 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
thomastaylor312
approved these changes
Apr 25, 2026
Contributor
thomastaylor312
left a comment
thomastaylor312
left a comment
There was a problem hiding this comment.
Good to go from the backend perspective. Someone with more frontend experiences needs to look at that side of things
| DefaultShardName string | ||
| // AgentStatusDeadline is the maximum age of a shard heartbeat before the | ||
| // shard is considered dead. | ||
| AgentStatusDeadline time.Duration |
Contributor
There was a problem hiding this comment.
Nit: Suggest renaming to ShardStatusDeadline
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
2 participants
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.
Surface per-shard liveness in the API and UI, derived from heartbeat ConfigMaps in the Kargo namespace. A shard is considered alive when its heartbeat ConfigMap carries an observedAt timestamp within AGENT_STATUS_DEADLINE (default 10m), and dead otherwise.
cc @rpelczar, I let Claude try the UI parts. I don't feel git to evaluate front end stuff. I can at least tell you it doesn't look spectacular. Would you mind having a look and amending the PR directly if you would like to change anything?