bitnami /sealed-secrets

A Kubernetes controller and tool for one-way encrypted Secrets

★ 9,346⑂ 788👁 72⑃ 1,415● 610▤ 209
GoApache-2.0Created 2017-05-29
下载:sealed-secrets-v0.41.2sealed-secrets-v0.41.2 ↓0.41.22026-10-26
+2
日增长
9,346
stars
788
forks
72
watchers
1,415
prs
610
issues
209
releases

README

"Sealed Secrets" for Kubernetes








!Downloads


Problem: "I can manage all my K8s config in git, except Secrets."

Solution: Encrypt your Secret into a SealedSecret, which is safe
to store - even inside a public repository. The SealedSecret can be
decrypted only by the controller running in the target cluster and
nobody else (not even the original author) is able to obtain the
original Secret from the SealedSecret.





- Overview
  - SealedSecrets as templates for secrets
  - Public key / Certificate
  - Scopes
- Installation
  - Installation in Restricted Environments (No RBAC)
  - Controller
    - Kustomize
    - Helm Chart
      - Helm Chart on a restricted environment
  - Kubeseal
    - Homebrew
    - MacPorts
    - Nixpkgs
    - Linux
    - Installation from source
- Upgrade
  - Supported Versions
  - Compatibility with Kubernetes versions
- Usage
  - Managing existing secrets
  - Patching existing secrets
  - Seal secret which can skip set owner references
  - Update existing secrets
  - Raw mode (experimental)
  - Validate a Sealed Secret
- Secret Rotation
  - Sealing key renewal
  - Key registry init priority order
  - User secret rotation
  - Early key renewal
  - Common misconceptions about key renewal
  - Manual key management (advanced)
  - Re-encryption (advanced)
- Details (advanced)
  - Crypto
- Developing
- FAQ
  - Can I encrypt multiple secrets at once, in one YAML / JSON file?
  - Will you still be able to decrypt if you no longer have access to your cluster?
  - How can I do a backup of my SealedSecrets?
  - Can I decrypt my secrets offline with a backup key?
  - What flags are available for kubeseal?
  - How do I update parts of JSON/YAML/TOML/.. file encrypted with sealed secrets?
  - Can I bring my own (pre-generated) certificates?
  - How to use kubeseal if the controller is not running within the kube-system namespace?
  - How to verify the images?
  - How to use one controller for a subset of namespaces
  - Can I configure the Controller unseal retries?
  - How to manage SealedSecrets across the cluster or specific namespaces?
- Community
  - Related projects



 Overview

Sealed Secrets is composed of two parts:

- A cluster-side controller / operator
- A client-side utility: kubeseal

The kubeseal utility uses asymmetric crypto to encrypt secrets that only the controller can decrypt.

These encrypted secrets are encoded in a SealedSecret resource, which you can see as a recipe for creating
a secret. Here is how it looks:

yaml
apiVersion: bitnami.com/v1alpha1
kind: SealedSecret
metadata:
  name: mysecret
  namespace: mynamespace
spec:
  encryptedData:
    foo: AgBy3i4OJSWK+PiTySYZZA9rO43cGDEq.....


Once unsealed this will produce a secret equivalent to this:

yaml
apiVersion: v1
kind: Secret
metadata:
  name: mysecret
  namespace: mynamespace
data:
  foo: YmFy   mycert.pem,
and use it offline with kubeseal --cert mycert.pem.
The certificate is also printed to the controller log on startup.

Since v0.9.x certifica

Top issues

Discussions

Latest release

sealed-secrets-v0.41.2 v0.41.2 2026-10-26
v0.41.2 (2026-10-26T12:43:03Z)

New v0.41.2 release!

 Changelog
 51799eb6dd970239e356c1ccffd354fe74408700 Release notes 0.41.2 (2082)

 Installation Instructions

 Cluster-side

Install the SealedSecret CRD and server-side controller into the kube-system namespace:

sh
kubectl apply -f https://github.com/bitnami/sealed-secrets/releases/download/v0.41.2/controller.yaml


 Client-side

Install the client-side tool into /usr/local/bin/:

Linux x86_64:
sh
curl -OL "https://github.com/bitnami/sealed-secrets/releases/download/v0.41.2/kubeseal-0.41.2-linux-amd64.tar.gz"
tar -

Snapshot: 2026-11-16T09:23:14Z · Data license Apache-2.0 · JSON