Repository navigation
v2.13.0 — Per-user cluster selection, local password reset, usage guide
Per-user cluster
- Every user picks their own cluster in the header switcher (or with
c); other users are unaffected. The choice is stored per user and
survives sessions and devices. - Users who never picked one work on the default cluster. Admins set it
with Admin → Clusters → "Set as default" (formerly "Activate";
"Unset default" no longer disconnects anyone). - The switcher lists only clusters the user's permissions cover (admins:
all). A selection that is deleted or no longer allowed falls back to
the default. - One connection + informer cache per cluster, opened on first use.
- Audit entries record the cluster: new column in Admin → Audit Logs,
the CSV export and the console mirror. - /readyz checks the DB only, so one unreachable cluster no longer takes
the console (and the admin screens to fix it) out of service.
Users and passwords
- Admin → Users shows each account's source: Local, LDAP or Azure AD.
- "Reset password" for local users: minimum 8 characters, forces a change
at next login by default, signs the user out everywhere, and is audited
as user.password_reset.{success,denied,failed}. LDAP and Azure AD users
are refused, because a local password would bypass the directory. - Local users get a "Change password" key icon in the header.
Fixes
- Cluster credentials are really validated before saving (a namespace
list call). Before, only a client object was built, so a wrong
server, token or CA was accepted. - LDAP login: with a wildcard user filter such as (sAMAccountName=%s*),
the login lookup could resolve a username to another user's DN (for
example "jo" → john). Login now also requires an exact match on the
username attribute. Exact filters are unchanged.
Docs
- README "Using OpenConsole": first login, admin checklist, users,
LDAP / Active Directory (every field, test, search + import, sign-in),
Azure AD (app registration, auto-created accounts, username claim),
groups / roles / permissions, choosing your cluster, daily Dashboard
use, admin tools.
Upgrade notes
- DB migrations run automatically: users.active_cluster_id,
users.auth_source, audit_logs.cluster. - Existing LDAP / Azure AD accounts show as "Local" until their next
sign-in, which tags them. LDAP users imported from now on are tagged
at import. - The previously "active" cluster becomes the default, so nothing changes
for users until they pick another cluster. - The legacy single-cluster write endpoint (POST/PUT /api/admin/cluster)
now returns 410; use /api/admin/clusters.
Image: ghcr.io/vurulkan/kubernetes-openconsole:2.13.0 (published by CI from this tag), linux/amd64.
🤖 Generated with Claude Code