Repository navigation
v2.14.0
2.14.0 closes the backlog: tracing, feature flags, shareable saved views,
table keyboard navigation, CSV exports, a password policy, shell limits,
per-cluster metrics, arm64 and signed images, an accessibility pass and a
much larger test suite. Only the two on-hold security items (encryption
key outside the DB, CORS allow-list) remain open.
Observability
- OpenTelemetry tracing, opt-in: set OTEL_EXPORTER_OTLP_ENDPOINT (OTLP/HTTP)
and every API request becomes a span named after its route
(GET /api/namespaces/{namespace}/pods) with the user, cluster and
request id, and the Kubernetes API calls it made become child spans.
Incoming traceparent headers are honoured. Probes, /metrics and
background informer traffic are not traced. Request log lines carry
trace_id. Standard OTEL_* variables (sampler, headers, service name)
apply. - New metrics: openconsole_cluster_requests_total{cluster},
openconsole_cluster_connected{cluster}, openconsole_pod_exec_active.
Operator controls
- Feature flags: FEATURE_POD_EXEC, FEATURE_YAML_EDIT,
FEATURE_WORKLOAD_ACTIONS, FEATURE_SECRETS, FEATURE_SECRET_REVEAL,
FEATURE_SECRET_EDIT = false switch a capability off for everyone,
admins included. The buttons disappear and the endpoints answer 403
with a denied audit entry. GET /api/features shows the state. - Password policy: PASSWORD_MIN_LENGTH (default 8) now applies to user
creation and self-service change, not only to admin reset. Passwords
are capped at 72 bytes (bcrypt), must not be blank, and a change must
actually change the password. - Pod shell: at most MAX_EXEC_SESSIONS_PER_USER (default 3) open shells
per user, the next is refused and audited as pod.exec.rate_limited.
EXEC_IDLE_TIMEOUT (default 5m) sets the idle timeout, and the shell
banner shows the configured value. pod.exec.end records exit code,
bytes in / out and duration; a shell ending with a non-zero status is
a normal end, -1 means the session was cut. - AZURE_AD_AUTHORITY for the US Government and China clouds.
UI
- Saved views live on the server (with their cluster), follow you to any
browser and can be shared with everyone. Opening a view saved on
another cluster switches to it. Views stored in the browser by older
versions move to the server the first time the menu opens. - Admin tables (Users, Groups, Roles, Sessions, Recordings): j / k to move,
Enter to open, d to delete (asks first), n / p to page, Esc to clear. - Users and Groups: Export CSV (audited as admin.export).
- Accessibility: a real-browser axe scan of every screen in light and dark
theme now reports 0 issues. Muted text meets WCAG AA contrast in both
themes, scrolling dialogs are keyboard-focusable, and the role matrix
toggles report their state.
Fixes
- Audit log CSV export failed: the download sent no auth header.
- Azure AD: an expired ID token was not rejected.
- Restoring a saved view that changed tab or namespace lost its search.
- When the shell limit was reached, the browser only showed "connection
error"; it now says why. - Untranslated strings in the dashboard (namespace panel, search, view
toggles) and the role list.
Images and supply chain
- Images are multi-arch: linux/amd64 and linux/arm64.
- Every published image is signed with cosign (keyless, GitHub OIDC) and
carries an SPDX SBOM and SLSA provenance. README "Verifying an image"
shows the cosign verify command.
Tests
- Store / migration tests (pre-2.x schema upgrade, idempotent migrations,
encryption at rest), LDAP end to end against an in-process LDAP server,
Azure AD end to end against a fake Entra endpoint, tracing, feature
flags, views, exports, shell limits. - Frontend suite (npm test, run in CI): Vitest + Testing Library + axe,
EN / TR key parity and a check that every t('…') key exists.
Upgrade notes
- The saved_views table is created automatically.
- The default limit of 3 open shells per user is new; set
MAX_EXEC_SESSIONS_PER_USER=0 for the old unlimited behaviour. - Existing passwords keep working; the length rule applies to new ones.
- Nothing to change in deploy/; new env vars are listed, commented out, in
deploy/deployment.yaml.
Image: ghcr.io/vurulkan/kubernetes-openconsole:2.14.0 (published by CI from this tag), linux/amd64 + linux/arm64, cosign-signed with SBOM and provenance.
Known issue: the counters openconsole_pod_exec_sessions_total, openconsole_pod_log_streams_total and openconsole_deployment_actions_total have stayed at 0 since 2.0.0. Fixed in 2.14.1.
🤖 Generated with Claude Code