Skip to content

Sealane v1.16.0

Change history you can restore from, and writes that cluster RBAC decides

Highlights

  • Change history kept in the cluster. Every create, update and delete made through Sealane is stored with the object before and after it, in two ConfigMaps next to Sealane: sealane-history lists the last 200 changes and sealane-history-objects keeps their objects up to about 768 KiB, dropping the oldest first. Replicas share the history and restarts keep it; until now it lived in each pod's memory. Sealane creates both ConfigMaps on the first change.
  • Compare and restore. The editor has a History tab listing the changes to that resource. Compare with current shows a diff between the live object and a stored version, and Load into editor puts that version in the editor with the current resourceVersion, so restoring is an ordinary Apply with dry-run, diff preview and conflict check. A deletion on the home page's change history offers Restore, which opens the new-resource editor with the deleted object. Viewers can compare but not load. See Change history and restore.
  • Impersonation mode (opt-in). With impersonation.enabled=true, resource writes, their dry-runs and the editor's permission check run as sealane:admin or sealane:editor through Kubernetes impersonation, carrying the person's name as a user extra. Cluster RBAC then decides what each role may change (for example editors only in their namespaces) and the API server's audit log names the person. The ServiceAccount may impersonate only those two identities. impersonation.bindDefaults (default true) grants both edit rights on the managed kinds, which matches the mode off. See Impersonation mode.

Upgrade notes

  • No breaking changes. The chart adds the HISTORY_CONFIGMAP variable and a Role rule (get, update on the two history ConfigMaps); kubectl apply -f install.yaml and helm upgrade both bring them. A Sealane without that rule (an edited Role) keeps working and logs change history not saved.
  • The in-memory history of the running pods is not carried over; the stored history starts with the first change after the upgrade.
  • Impersonation mode is off unless you turn it on. Without Helm, apply the impersonation.yaml attached to this release and set IMPERSONATION=true on the Deployment (see Impersonation mode).
  • helm upgrade sealane oci://ghcr.io/wonjune95/charts/sealane --version 1.16.0 -n <namespace> --reset-then-reuse-values

Install

helm install sealane oci://ghcr.io/wonjune95/charts/sealane --version 1.16.0 -n sealane --create-namespace
# or
kubectl apply -f https://github.com/wonjune95/sealane/releases/download/v1.16.0/install.yaml
Image ghcr.io/wonjune95/sealane:1.16.0 (linux/amd64, linux/arm64) and the chart are signed with cosign (keyless); the SBOM is attached below.

Full Changelog: https://github.com/wonjune95/sealane/compare/v1.15.0...v1.16.0