Improve Cluster Dashboard Timeline #1

2026-04-19T13:07:30Z

tu commented

2026-04-19 13:07:30 +00:00

No description provided.

tu added 6 commits 2026-04-19 13:07:31 +00:00

v2.0.13 — oumta-dashboard via PHP proxy; quiet support poll efd3f9d5ae

Dashboard now reachable across the internet: browser calls /api/dashboard/*
same-origin, PHP forwards to OUMTA_DASHBOARD_URL (configurable via env,
with docker-compose defaults pointing at host.docker.internal:8085).
Keeps the bearer token server-side and lets the dashboard live on a
private network.

Plumbing bits: polling indicator now green (no reason to look anxious
about a healthy poll loop), and the support plugin returns 200 pulled=0
when its relay isn't configured instead of flooding the network tab
with 502s on every background tick.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

v2.0.14 — oumta-dashboard: self-healing poll loop cdfb6d4ecd

Initial-bootstrap failure stopped the poll interval from ever starting,
and even once running, refresh() never reset the indicator back to
'polling' on success — so a single upstream blip pinned the plugin
in an error state until the user reloaded the page.

refresh() now loads namespaces on demand (absorbs bootstrap), the
interval is started unconditionally on show(), and every successful
poll flips the indicator back to green.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Merge branch 'master' of https://git.uesome.de/tanztee/hyprcrd into feature/check-whether-works-as-pwa 0bf7137428

v2.0.15 — oumta-dashboard: dot color follows cluster outcome bd5a462a1e

The per-cluster dot now reflects how the workload ended up after the
cluster's events, not the worst thing that happened inside it: if the
most recent state transition in the cluster was "-> healthy", the dot
turns green even when the cluster contains earlier degraded/warning
events. Falls back to the existing dominantSev logic for clusters
without any state transition (e.g. rollout-only clusters).

Matches the reality that a rollout which briefly degrades and then
recovers is a normal, healthy outcome — not a "warning" forever.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

v2.0.16 — oumta-dashboard: green dot for rollout-only clusters 985cd39b2a

Clusters with no state-transition events (e.g. a clean rollout that
didn't cause a degradation) now show a green dot instead of blue.
Rationale: absence of a transition means the workload stayed in its
existing state — the rollout went through unscathed, which is the
healthy outcome a reader is scanning for.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Merge branch 'master' of https://git.uesome.de/tanztee/hyprcrd into feature/check-whether-works-as-pwa 14d3cc5434

tu commented

2026-04-19 13:08:37 +00:00