Managing sensitive configuration and Secrets
Sealed Secrets solves the problem of I can manage all my Kubernetes config in Git, except Secrets. Created by Bitnami Labs and open sourced, they help you encrypt your Kubernetes Secrets into Sealed Secrets using asymmetric cryptography that only the Sealed Secrets controller running on the cluster can decrypt. That means you can store the Sealed Secrets in Git and use GitOps to set up everything, including Secrets.
Sealed Secrets comprise two components:
- A client-side utility called
kubeseal
helps us generate Sealed Secrets out of standard Kubernetes Secret YAML. - A cluster-side Kubernetes controller/operator unseals your secrets and provides the key certificate to the client-side utility.
The typical workflow when using Sealed Secrets is illustrated in the following diagram:
Now, let's go ahead and install the Sealed Secret operator in the next...