Sealed Secrets Tutorial: Encryption Scope and Controller Decryption
Sealed Secrets supports an encrypted declaration workflow with a controller that produces relevant Kubernetes Secrets. This tutorial separates public encrypted content from decrypted runtime resources and examines scope binding and key handling. You will identify what can be stored in source history and what still needs protection inside the cluster. Encryption aids configuration sharing, but restoring the controller's key context and managing actual credentials remain distinct operational responsibilities.
Here's a popular Sealed Secrets video — watch it, then summarize it with one click. Or paste any other YouTube link below.
— or paste your own YouTube link —
Want to keep the key points from a YouTube video? Paste the link below to turn it into structured notes.
Why Use Sealed Secrets Tutorial: Encryption Scope and Controller Decryption
- Distinguish encrypted and decrypted resource forms
- Understand the configured sealing scope
- Connect controller keys to decryption
- Review access to the generated Secret
- Plan recovery and credential rotation separately
Frequently Asked Questions
Does a SealedSecret stay encrypted inside every application?
The controller produces the relevant Secret for workload use, and applications receive sensitive data through their configured mechanism. That runtime data needs its own protection. Encrypted source storage does not eliminate all plaintext access in the execution environment.
Why does sealing scope matter?
Scope can bind encrypted content to relevant identity conditions such as resource name or namespace under its mode. Changing those relationships can prevent intended decryption. Inspect the actual sealing model before moving a declaration mechanically.
Can any new controller decrypt old encrypted files automatically?
Decryption depends on the appropriate private-key context and supported setup. A fresh controller instance does not automatically possess the previous keys. Define restoration requirements before relying on encrypted source as the only preserved configuration input.
Does changing encryption keys rotate the application's credential?
Encryption-key handling and the underlying credential's validity are separate matters. Re-encrypting a value does not necessarily replace the secret accepted by an external service. Evaluate both when the goal is actual credential rotation.
What should a recovery test establish?
Establish that the intended key and controller arrangement can recreate relevant Secrets from preserved encrypted declarations. Then verify required application use. Possessing ciphertext alone is not proof that the environment can decrypt and consume it after restoration.