Passwords, API keys, TLS private keys, and database credentials must never live in git or a plaintext env file in a repo. This section covers how secrets are stored, injected, and rotated safely. Part of the DevOps curriculum.
[reference] — covered from roadmap.sh and primary docs.
Reading order
- Secret Management — [Advanced] — why secrets can’t live in git, the tools (HashiCorp Vault in depth, plus SOPS, Sealed Secrets, External Secrets Operator, and cloud KMS/Secrets Manager), dynamic secrets, and rotation
Related
- Infrastructure as Code — IaC references secrets, never hardcodes them
- Kubernetes — k8s Secrets and why they need help (Sealed Secrets, ESO)
- Networking & Protocols — TLS certificates are managed secrets
- DevOps curriculum map
Jump to a subject
Software engineering
Infrastructure & security
Computer science
Hardware & engineering