Skip to content

What it is

The /dashboard/<svc>/proxy routes the staff dashboard on kbve.com calls: workflows (Windmill), edge, firecracker, firecracker-net, argo, grafana, clickhouse, forgejo, cube, vm and chuckrpg. Each one checks the caller’s Supabase session, sent only as Authorization: Bearer, against GoTrue’s JWKS and the staff bits: DASHBOARD_VIEW to read, DASHBOARD_MANAGE to change anything.

What it holds

Only what it forwards: the anon key, ArgoCD’s read-and-sync kbve-dashboard token, the forgejo and Cube API tokens, the ClickHouse login and the ROWS customer GUID. Windmill and edge get the caller’s own session, so it holds no Windmill token. It holds no JWT signing secret, no service_role key and no database URL. The route table and the reasoning are in docs/plans/dashboard-proxy/README.md.

Where it came from

Moved out of axum-kbve (GitLab #34), whose image can no longer be rebuilt. Paths and JSON stay the same; the rules got stricter. Writes need DASHBOARD_MANAGE everywhere, the session cookie and ?access_token= are no longer accepted, and responses can neither set a kbve.com cookie nor run as a kbve.com page.

Releasing

Bump version: above. The dashboard-proxy job publishes the image and dashboard-proxy-deploy opens the merge request that repoints dashboard-proxy-deployment.yaml.

Discuss on the forum

Questions, fixes and notes on this page live in the KBVE forum.