A Kubernetes Secret stores external information intended for use by Pods when that information is sensitive. Unlike ConfigMaps, Secret values use Base64 encoding, which supports binary data but does not provide meaningful confidentiality: anyone able to view a Secret can trivially decode it. section 3.2.6
Treat Secret protection as a layered operational concern:
- Use an external secret manager such as Vault or Google Secret Manager when stronger protection is required. section 3.2.6
- Enable encryption for Secrets stored in etcd, while recognizing that this protects the database value rather than the Secret throughout Kubernetes. section 3.2.6
- Combine external protection with etcd encryption to cover both cluster handling and database storage. section 3.2.6





