Repository navigation
v2.12.0 — Secrets, authorization test suite, cluster connection guide
Secrets
- New Secrets tab with four permissions you can grant to any role, per
namespace and cluster (admins have all four):- secrets:list: name, type, key count.
- secrets:get: Keys modal with type, labels, annotations, key names and
sizes. Values are never sent on list or get, and kubectl's
last-applied-configuration annotation is stripped. - secrets:reveal: "Show" returns one key's value per request (POST,
no-store), with copy / hide. Binary values come back base64-encoded
and labelled. Audited as secret.reveal.{success,denied,failed}. - secrets:edit: the same YAML editor as other resources (view → Edit →
dry-run → diff → Apply). Text values appear as plain-text stringData,
binary values stay base64 in data, and removing a key deletes it.
Opening the YAML is audited as secret.yaml.view., applying as
secrets.apply..
- Secrets are read from the API server on demand; they are never put in
the informer cache.
Recordings
- Download now asks for confirmation first: the file can contain
secrets, leaves OpenConsole's access control once downloaded, and must
not be shared in tickets, chat or email.
Tests
- An RBAC engine test and an API authorization suite, run on the real
router and SQLite store against a fake clientset. They cover tokens
(missing / forged / revoked / deactivated), login lockout, every admin
endpoint, namespace / resource / cluster-scoped grants, write denials
with their audit entries, exec, and secrets (no value leaks; reveal and
edit enforced and audited).
Deploy and docs
- deploy/rbac.yaml: ServiceAccount, long-lived token Secret, ClusterRole
(now with secrets get / list / update) and binding. - deploy/rbac-readonly.yaml: a view-only ClusterRole as a drop-in
replacement. Writes, shell and secrets are refused by Kubernetes. - deploy/kustomization.yaml: the whole install is
kubectl apply -k deploy/. - deployment.yaml:
- The image is pinned instead of :latest.
- The pod mounts no ServiceAccount token (serviceAccountName is
commented out, automountServiceAccountToken: false). OpenConsole only
uses the credentials added in Admin → Clusters.
- Dockerfile: DATA_PATH=/data/app.db by default, with /data writable by
the app user. Before,docker runwithout DATA_PATH crashed. - README:
- New "Connecting clusters" guide: token method field by field,
kubeconfig method, rotation, troubleshooting. - New sections: "Read-only mode", "Application permissions",
"Secrets", "Tests". - Removed the wrong claim that a cluster is detected automatically
when running in-cluster.
- New "Connecting clusters" guide: token method field by field,
Fixes
- Restart and scale returned a generic 502 when Kubernetes refused them.
They now return the real status (for example 403 under the read-only
ClusterRole) together with the API server's message. - Confirm dialogs showed English "Cancel" / "Confirm" in the Turkish UI.
Upgrade notes
- To use the Secrets tab, re-apply deploy/rbac.yaml (or add secrets
get / list, plus update for edit, to your own ClusterRole). Without it
the tab shows a clear 403 hint, and everything else keeps working. - No other changes are required. If your deployment still sets
serviceAccountName, it is harmless; you can drop it.
Image: ghcr.io/vurulkan/kubernetes-openconsole:2.12.0 (published by CI from this tag), linux/amd64.
🤖 Generated with Claude Code