Skip to content

v2.5.0 — Cluster switcher shortcut + Role Permissions redesign

Choose a tag to compare

@vurulkan vurulkan released this 02 Oct 11:58
· 45 commits to main since this release

v2.5.0 — Cluster switcher shortcut + Role Permissions redesign

Two usability wins, both frontend-only, both behind a safety net.

Cluster switcher

  • Global c opens the header cluster dropdown (admins only; non-admin
    switcher stays read-only).
  • Inside the menu: 1..9 pick a cluster by index, ↑/↓ navigate, Enter
    activates the focused row, Esc closes. Each row shows its 1..9 prefix
    as a kbd so the shortcut is self-explanatory.

Keyboard cheat sheet (?) lists the new keys under a new Cluster switcher
section.

Role Permissions redesign (new default · classic reachable)

The old form (one role → one cluster/ns → checkbox grid → flat pill list) was
noisy and tedious for anything beyond a single grant. The new layout:

  • Role sidebar with search and a N perms · M ns · K clusters summary per
    role (parallel-loaded on mount).
  • Grouped grant cards — one card per (cluster, namespace) pair, one row
    per resource. Action chips are tinted by family: read = slate, write =
    amber, destructive (exec) = rose. One glance tells you the risk shape of
    a grant.
  • Chip X / shift-click removes a single (resource, action) grant.
  • Row ⋯ menu: Duplicate to another namespace… (seeds the Add modal with
    the current grants pre-selected) and Clear row.
  • Add permissions modal — cluster + multi-namespace picker + four
    templates (Viewer / Developer / SRE / Admin). Chips are struck-through
    when every selected namespace already has that (resource, action), and a
    live counter at the bottom says Will create N new permissions · M will be skipped.
  • Copy from another role modal — pick a source role, bulk-copy grants.
    Overlaps are skipped automatically.

Rollback

If the new UI isn't for you, click "Switch to classic view" in the Role
Permissions header. localStorage.rolePermissionsLayout persists the choice.
The classic UI stays fully intact and offers a reverse link. Nothing changes
on the backend; a future release can delete the classic code once we've lived
with the new one for a while.

Upgrade

docker pull ghcr.io/vurulkan/kubernetes-openconsole:2.5.0
docker rm -f openconsole && \
  docker run -d --name openconsole -p 8080:8080 -e DATA_PATH=/tmp/app.db \
    ghcr.io/vurulkan/kubernetes-openconsole:2.5.0

No schema change, no backend-contract change.

Rollback (if the whole release goes sideways)

docker pull ghcr.io/vurulkan/kubernetes-openconsole:2.4.0
docker rm -f openconsole && docker run -d --name openconsole -p 8080:8080 \
  -e DATA_PATH=/tmp/app.db ghcr.io/vurulkan/kubernetes-openconsole:2.4.0