It allows teams to version and manage environment configuration and infrastructure through declarative code. While Kubernetes allows teams to manage their container workloads using resource manifests, storing Kubernetes Secrets in a Git repository has always been a challenge.
Once you generate a SealedSecret using kubeseal for a particular namespace, you can’t use the SealedSecret in another namespace.
There are three scopes you can create your SealedSecrets with: Apart from the name and namespace, you can rename the secret keys without losing any decryption capabilities.
Now let’s use the Secret in a busybox pod and see if we can retrieve it in the cluster.