Sealane v1.19.0¶
Not published
The v1.19.0 tag exists, but its release stopped at the new vulnerability scan (go-jose, CVE-2026-116587) before anything was pushed, so it has no image, chart or GitHub release. Use 1.19.1, which carries these changes and the fix.
Ready to hand out¶
A security release, from an outside review of what it takes to run Sealane as published open source. Everyone signs in again once after the upgrade; read the upgrade notes.
Highlights¶
- No default password. A fresh install creates
adminwith a random password in Secretsealane-initial-admin(<release>-initial-adminwith Helm). An upgradedadminstill onadmin/adminmust change it before the server answers anything else; this is now enforced by the server, not only the UI. - Sessions end when the account changes. Sealane reads the accounts ConfigMap through the API, so a deleted account, a changed role or a changed password ends its sessions within seconds on every replica (within about a minute if that read keeps failing, through the mounted copy). Changing your password signs out your other sessions. A cluster that refuses Sealane's own credentials now shows as an error (502), not as a sign-out.
- Cross-site request protection for every
POST,PUTandDELETE(TRUSTED_ORIGINSfor proxies that rewriteHost), and Secure cookies whenever the request came over TLS or withX-Forwarded-Proto: https(secureCookies: truefor proxies that send neither), plus HSTS on those responses. - Pasted kubeconfigs cannot reach Sealane's files. Registering a cluster refuses kubeconfigs that point to certificate, key or token files, and servers that are not
https://. Before, such a kubeconfig could make Sealane send its own ServiceAccount token to the named server. - Deleting a cluster can remove Sealane's account there. For clusters registered with the dedicated account, the delete dialog removes its roles, namespace and token on the cluster (on by default). A failed first registration no longer leaves half an account behind.
- Read-only ServiceAccount in impersonation mode. Writes already ran as
sealane:admin/sealane:editor; now the ServiceAccount itself can no longer change the managed kinds, locally and on remote clusters registered in that mode. - Narrower RBAC. The managed Istio and Gateway API kinds are listed by name instead of
*. The Istio version comes from the istiod pods, so nothing is created inistio-systemany more andinstall.yamlapplies cleanly on clusters without Istio. - Change history. Objects before and after each change are kept in Secret
<release>-history-objects, and only editors and admins can open them; the objects 1.15–1.18 kept in a ConfigMap are moved there at startup. A client that disconnects right after a change no longer loses its record, and two replicas can no longer give two changes the same ID. - Fixes. Two replicas starting together share one session key and one initial password; a pod that cannot store the session key stops instead of running with its own, and a failed first-admin setup is retried. ServiceEntries of the same name in different namespaces are told apart in the traffic graph and the analysis. Settings show load errors with a retry instead of an empty list. The editor hides Apply on the History tab, its tabs follow the WAI-ARIA pattern, and the guided forms are translated.
- Operations. New metrics
sealane_build_info,sealane_history_write_failures_total,sealane_login_failures_totalandsealane_account_read_errors_totalwith alert examples; complete backup and restore, a cumulative upgrade path and a rollback section in the docs. - Release pipeline. A tag is released only if its commit passed e2e on
main; tests, lint and a Trivy scan of both platforms (HIGH and CRITICAL with a fix) run before anything is pushed, base images are pinned by digest, andlatestmoves only after the Release exists. CI also upgrades from 1.18.3 and rolls back. Each release attachesTHIRD_PARTY_NOTICES(also in the image under/licenses),image-digest.txtand a cosign-signedSHA256SUMSover every asset. The chart carries the project license.
Upgrade notes¶
- Everyone signs in again once: sessions now carry a fingerprint of the account's password.
- An
adminstill onadmin/adminis asked to change it, and the API refuses other calls until then. Other accounts and passwords are untouched. - If saving anything fails with HTTP 403 behind a proxy that rewrites the
Hostheader, setTRUSTED_ORIGINSto Sealane's public URL. - Revisions recorded by 1.15–1.18 move from the ConfigMap
<release>-history-objectsinto the Secret of that name at startup. install.yamlusers can delete the oldsealane-istiod-readerRole and RoleBinding inistio-system; Helm removes them.install.yamlwith impersonation mode: applyimpersonation.yamlafterinstall.yaml; it now carries Sealane's read-only ClusterRole.- Clusters registered before 1.19 keep working. Register them again to add the cleanup role used by Also remove Sealane's account, to list the managed kinds by name, and, in impersonation mode, to drop the remote account's write rights.
- A hand-maintained Role must allow
get,updateandcreateon Secretsealane-secret: without them the pod now stops at startup instead of running with a per-pod session key. - Full list and rollback: Upgrading.
- To upgrade, use 1.19.1 or later; 1.19.0 itself was never published.
Install¶
Not published: install 1.19.1 or later.
Full Changelog: https://github.com/wonjune95/sealane/compare/v1.18.3...v1.19.0