Skip to content

Sealane v1.12.0

install.yaml installs keep their sessions

Highlights

  • Generated session key. When no SESSION_SECRET is set (the install.yaml and GitOps shapes, where Helm's lookup is unavailable), Sealane now generates a signing key on first start and stores it in the sealane-secret Secret (key SESSION_SECRET), the way Argo CD fills argocd-secret. Every pod reads that Secret, so a restart no longer signs everyone out and several replicas share one key, which SSO needs. The Helm chart's sessionSecret.create=true default is unchanged; sessionSecret.existingSecret still lets you bring your own key.
  • Air-gapped install without Helm is spelled out in the FAQ: download install.yaml, point image: at your mirror, apply.

Upgrade notes

  • No breaking changes and no manual step. The Role gains get/patch on the sealane-secret Secret (by name) so the pod can store the key; the chart and install.yaml apply it. If the pod cannot read or create that Secret it falls back to the old per-boot key and logs session secret: using a per-boot key.
  • Upgrading from 1.10 or earlier with Helm still needs the accounts ConfigMap adoption described in the 1.11.0 notes.
  • helm upgrade sealane oci://ghcr.io/wonjune95/charts/sealane --version 1.12.0 -n <namespace> --reset-then-reuse-values

Install

helm install sealane oci://ghcr.io/wonjune95/charts/sealane --version 1.12.0 -n sealane --create-namespace
# or
kubectl apply -f https://github.com/wonjune95/sealane/releases/download/v1.12.0/install.yaml
Image ghcr.io/wonjune95/sealane:1.12.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.11.0...v1.12.0