Skip to content

feat(kromgo): add flux reconciliation badges and fix uptime/age display - #4951

Open
dapperdivers wants to merge 1 commit into
mainfrom
kromgo-flux-badges
Open

dapperdivers wants to merge 1 commit into
mainfrom
kromgo-flux-badges

Conversation

@dapperdivers

Copy link
Copy Markdown
Owner

Adds GitOps health badges for the portfolio site's telemetry band and fixes two display issues.

New badges (all from the Flux Operator's flux_resource_info):

  • flux_kustomization_count, flux_helmrelease_count
  • flux_waiting_count: not Ready only because of DependencyNotReady / Progressing*. That's normal for a while after a rolling Talos upgrade: it was 67, then 49 and falling, right after feat(talos): roll v1.14.6 to the remaining nodes #4949.
  • flux_failing_count: every other not-Ready source, Kustomization or HelmRelease. Suspended objects are excluded.

Fixes

  • cluster_uptime_days read 0d after every node roll. It now shows 52m / 2h under a day, and days after that.
  • cluster_age_days went red past a year. It's now always blue.

Every expression was tested in a local kromgo 0.16.4 (same image digest as the cluster) against the cluster's Prometheus before committing.

- flux_kustomization_count / flux_helmrelease_count: object counts from flux_resource_info
- flux_waiting_count: not Ready only because a dependency or rollout is in progress
- flux_failing_count: everything else not Ready (suspended objects excluded)
- cluster_uptime_days: show minutes/hours under a day instead of "0d" after node rolls
- cluster_age_days: always blue; an old cluster is not a warning
@dunce-bot

dunce-bot Bot commented Nov 22, 2026

Copy link
Copy Markdown
Contributor

Note

2 resources changed across 2 apps

konflate 0.6.6 · rendered d157523 · full diff →

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant