Skip to content

Sealane v1.19.2

Fixes from the final review

An independent review of 1.19.1 found two ways to keep access that should have ended, and a few rough edges. All are fixed here.

Highlights

  • Account changes cannot be undone by a racing password change. A password change and an admin's change to the same account used to be blind writes: a password change that read the account just before an admin deleted or demoted it could bring the account or its old role back. Account changes are now read-modify-writes on the ConfigMap's version; the losing write is re-checked against the new data, so a deleted account stays deleted and a demotion stands.
  • Deleted clusters stop working on every replica. Each replica cached a registered cluster's kubeconfig until it restarted, so a cluster deleted or replaced through one replica kept working through the others. Replicas now check the clusters Secret again every few seconds.
  • Remote accounts are not left behind. If storing a registration fails after Sealane created its account on the cluster, the account is removed again. A proxy-url in the pasted kubeconfig is kept in the stored one. Registering again with impersonation mode off removes the impersonation roles an earlier registration added. A cleanup that the cluster refuses with 401 no longer counts as done; the error says how to check.
  • Newly installed CRDs show up without a restart. The list of installed kinds is discovered again every minute.
  • The service page's create buttons wait for the service. They carry its port; clicked before it loaded, the editor fell back to port 80.
  • Hardening. The server limits how long reading a request may take and how long idle connections stay open. Releases now also require the tagged commit's ci and CodeQL runs to have passed, run one at a time, and move latest only for the newest version.
  • Docs and UI. kubectl delete -f install.yaml deletes the namespace and every account and history entry with it; the uninstall docs said otherwise and are corrected. /readyz documents the initial-admin condition. With secureCookies: true the chart's notes no longer suggest a plain-http port-forward. The remaining form labels and the delete buttons in forms have translated, accessible names.

Upgrade notes

  • No breaking changes and no new values. The Role adds update on the accounts ConfigMap; the chart and install.yaml bring it. With a hand-maintained Role, add it, or account changes fail with 403.
  • With impersonation mode, apply impersonation.yaml after install.yaml as before.
  • From 1.18 or earlier, read From 1.11–1.18 to 1.19: everyone signs in again once.
  • helm upgrade sealane oci://ghcr.io/wonjune95/charts/sealane --version 1.19.2 -n <namespace> --reset-then-reuse-values

Install

helm install sealane oci://ghcr.io/wonjune95/charts/sealane --version 1.19.2 -n sealane --create-namespace
# or
kubectl apply -f https://github.com/wonjune95/sealane/releases/download/v1.19.2/install.yaml
# first sign-in: user admin, password from
kubectl -n sealane get secret sealane-initial-admin -o jsonpath='{.data.password}' | base64 -d; echo
Image ghcr.io/wonjune95/sealane:1.19.2 (linux/amd64, linux/arm64) and the chart are signed with cosign (keyless). SHA256SUMS covers every asset below and is signed too (SHA256SUMS.sigstore.json); see Air-gapped install for verifying it.

Full Changelog: https://github.com/wonjune95/sealane/compare/v1.19.1...v1.19.2