Sealane v1.12.0¶
install.yaml installs keep their sessions¶
Highlights¶
- Generated session key. When no
SESSION_SECRETis set (theinstall.yamland GitOps shapes, where Helm'slookupis unavailable), Sealane now generates a signing key on first start and stores it in thesealane-secretSecret (keySESSION_SECRET), the way Argo CD fillsargocd-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'ssessionSecret.create=truedefault is unchanged;sessionSecret.existingSecretstill lets you bring your own key. - Air-gapped install without Helm is spelled out in the FAQ: download
install.yaml, pointimage:at your mirror, apply.
Upgrade notes¶
- No breaking changes and no manual step. The Role gains
get/patchon thesealane-secretSecret (by name) so the pod can store the key; the chart andinstall.yamlapply it. If the pod cannot read or create that Secret it falls back to the old per-boot key and logssession 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
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