Repository navigation
v2.23.1
What's new
2.23.1 is a patch release of fixes, not features: security hardening, supply chain, data safety, cluster correctness, frontend reliability and code health. The product is now called OpenConsole for Kubernetes; the image, repository, namespace and manifests keep their names.
Security
- The client address comes from
X-Forwarded-Foronly when the request arrives fromTRUSTED_PROXIES. - Kubeconfigs that run a program or read a file are refused.
- A local account never falls back to LDAP.
- StartTLS verifies the directory's certificate, with a CA field in Admin → LDAP.
- Inactive accounts, and accounts that must change their password, can't open shells.
- Request bodies are size-limited, and CSV exports are formula-safe.
- CORS only for
ALLOWED_ORIGINS; cross-site WebSockets are logged (WS_ORIGIN_CHECK=warn, orenforceto refuse them).
Image and supply chain
- Distroless image with a read-only root filesystem.
- Monaco editor bundled; the page no longer loads anything from a CDN.
- govulncheck,
npm auditand Trivy run in CI. - Signed provenance and SBOM are made with
actions/attest.
Data
- Database copies: daily, before an upgrade, and on demand (Admin → Backups).
- The encryption key of the stored credentials can live in a Secret (
ENCRYPTION_KEY_FILE, with rotation). - SQLite runs in WAL mode with foreign keys and migrations in one transaction.
- Graceful shutdown audits open shells.
deploy/usesstrategy: Recreate.
Clusters and streams
- Each browser tab keeps its own cluster (
X-OpenConsole-Cluster). - Informer caches are used only while synced; cluster errors keep their meaning (
cluster_forbidden,cluster_timeout, …). - Log sockets have limits and resume.
- Followed logs no longer stop after 30 s.
- The session timeout is now an inactivity timeout (12 h at most).
Frontend
- Errors are shown as sentences in English and Turkish, never raw JSON.
- Focus is trapped in dialogs and returns to the opener; the shell is keyboard-reachable (
Ctrl+]). - Smaller bundle.
- The sign-in panel is readable in the light theme.
API and audit
- Every error is RFC 9457 problem details (
application/problem+json) with a reason code inerrorand the English message indetail. - Unknown
/apipaths answer404JSON. - Every admin change is audited for every answer (success, denied, failed).
- YAML views are audited reads, and invalid cluster-write requests are audited as
failed/invalid. - A Kubernetes refusal of OpenConsole's own account on the REST log is
403 cluster_forbidden.
Upgrading
Read Upgrading to 2.23.1 before you install. In short:
- Kubeconfig clusters: clusters added with a kubeconfig that uses
exec(kubelogin),auth-provideror file paths no longer connect. Replace those kubeconfigs first. - Your own manifest: add
TRUSTED_PROXIES,strategy: Recreate,terminationGracePeriodSeconds: 30, and a/tmpemptyDir if you turn onreadOnlyRootFilesystem. - No shell in the image:
kubectl execinto the pod no longer works; usekubectl debug. - API errors: scripts that compare the API's
errortext must switch to the codes. The/api/admin/cluster*endpoints are removed; use/api/admin/clusters. - Database: the first start copies the database to
/data/backups/…-pre-upgrade.db. Backups need about 7 × the database size on the volume. - Settings to review: the session minutes are now an inactivity timeout, and
LOG_RETENTION_DAYS=0now means "keep forever". In Admin → LDAP, put one base DN per line.
Tested on dev, on a k3d cluster and on a real AKS cluster upgraded from 2.23.0 (:dev-173 … :dev-179, then this image). The upgrade kept all data, sessions and API keys. LDAP and Azure AD worked, and so did role-scoped users, scale, restart, YAML, shell, logs, the encryption key moved into a Secret, and WS_ORIGIN_CHECK=enforce. The image passed a Docker smoke test.
Image
ghcr.io/vurulkan/kubernetes-openconsole:2.23.1 (= :latest, same digest sha256:66321e1c…; amd64 + arm64), with signed provenance and SBOM:
gh attestation verify oci://ghcr.io/vurulkan/kubernetes-openconsole:2.23.1 --repo vurulkan/kubernetes-openconsole
🤖 Generated with Claude Code