NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules, #401 by repository stars
Latest stable
v0.41.2
Last release 15 days ago
30 Oct 2026
Ships on a steady schedule
a new release about every 9 days
Nearly every release is documented
notes for 21 of 22 stable releases
Nothing withdrawn
no release was ever pulled
9 years old
72 releases · first in 2017
Drag across the ruler to compare, or tap a release to open it.
Existing/older "all-in-one" SealedSecrets are declared deprecated, but will continue to be supported by the controller for the foreseeable future. New…
Big change for this release is the switch to per-key encrypted values.
kubeseal tool does not yet have an option to output just a single value, but you can safely mix+match the individual values from kubeseal output with an existing SealedSecret. Improving kubeseal support for this feature is still an open action item.kubeseal tool now produce per-key encrypted output - if you need to produce the older format, just use an older kubeseal. Please raise a github issue if you have a use-case that requires supporting "all-in-one" SealedSecrets going forward.Your coding agent can read these notes before it upgrades. Set up the MCP server →
Support "cluster wide" secrets, that are not restricted to the original namespace
sealedsecrets.bitnami.com/cluster-wide: "true" annotationNote: this version moves TPR/CRD definition into a separate file. To install, you need controller.yaml *and* either sealedsecret-tpr.yaml or sealedsec
Note: this version moves TPR/CRD definition into a separate file. To install, you need controller.yaml and either sealedsecret-tpr.yaml or sealedsecret-crd.yaml
kubeseal --fetch-cert to dump server cert to stdout, for later offline use with kubeseal --certkubeseal(v0.5.1 fixes a travis/github release issue with v0.5.0)
Nothing published for this version
controller: deployment security hardening: non-root uid and read-only rootfs
kubeseal: Include oidc and gcp auth provider pluginskubeseal: Add support for YAML outputAdd controller-norbac.yaml to the release build. This is controller.yaml without RBAC rules and related service account - for environments where RBAC
controller-norbac.yaml to the release build. This is controller.yaml without RBAC rules and related service account - for environments where RBAC is not yet supported, like Azure.Rename everything to better represent project scope. Better to do this early (now) and apologies for the disruption.
Rename everything to better represent project scope. Better to do this early (now) and apologies for the disruption.
bitnami/sealed-secretskubesealSealedSecret apiGroup -> bitnami.comFix invalid field resourceName in v0.2.0 controller.yaml (thanks @Globegitter)
resourceName in v0.2.0 controller.yaml (thanks @Globegitter)Client tool has better defaults, and can fetch the certificate automatically from the controller.
Basic functionality is complete.
Basic functionality is complete.
Switch to quay.io (docker hub doesn't offer robot accounts??)
Nothing published for this version
One column per quarter.