Course contentsShow
← Security
Lesson 1972 of 3,05239. Cloud Security - Compute and ServerlessFree lesson

Secrets Management in Kubernetes

Learn Kubernetes Secrets limitations, encryption at rest, external secret stores, and secure secret injection patterns.

Secrets Management in Kubernetes

You'll learn why Kubernetes Secrets aren't truly "secret" by default and how to manage sensitive data securely.

Kubernetes provides a native Secret object for storing sensitive information like passwords, API keys, and certificates. However, understanding its limitations is critical for production security.

The Reality of Kubernetes Secrets

By default, Secrets are merely base64-encoded — not encrypted. Anyone with access to etcd (Kubernetes' backing store) or sufficient RBAC permissions can decode them instantly. Think of it like hiding a key under a doormat: you've obscured it, but not secured it.

Encryption at Rest

Kubernetes supports encryption at rest for Secret objects stored in etcd. You configure an EncryptionConfiguration that defines encryption providers (like AES-CBC or KMS integrations). This ensures Secrets are encrypted on disk, protecting against etcd database compromise.

# Conceptual: enabling encryption requires cluster-level config
# Secrets in etcd become encrypted using specified provider

External Secret Stores

Production environments often use external secret management systems like HashiCorp Vault, AWS Secrets Manager, or Azure Key Vault. These provide:

  • Centralized secret lifecycle management
  • Audit logging of secret access
  • Dynamic secret generation
  • Fine-grained access policies

Secure Injection Patterns

Instead of mounting Secrets as files or environment variables (which can leak via logs or process listings), consider:

  • Volume mounts with restrictive permissions (read-only, specific paths)
  • Init containers that fetch secrets at pod startup
  • Sidecar patterns that inject secrets into shared volumes
  • External Secrets Operator that syncs from external stores into native Secret objects

Avoid exposing secrets in environment variables visible through /proc or pod inspection.

Key Takeaway:
Kubernetes Secrets require encryption at rest and external secret stores with secure injection patterns to protect sensitive data — base64 encoding alone provides no real security.