The Power of SecretOps: Automating Secrets Workflows
summary
A concrete framework names four layers: storage, governance, orchestration and rotation, with Doppler positioned as a hub-and-spoke source of truth. Claims include centralized secrets storage with versioned rollbacks and audit logs, role-based and ephemeral access so no developers have access to production, and orchestration via a Kubernetes operator and CLI to sync secrets. Examples show automatic rotation (Twilio integration that can rotate every 30 days), webhook-triggered redeploys, and change-request workflows that let teams propose, approve and apply secrets safely.
AI-written summary · about
chapters (11)
- 0:00Introduction to Secret Ops
- 0:10Understanding Software Components
- 0:40Automation in Code, Compute, and Secrets
- 1:00Challenges in Secret Management
- 1:13Introducing the Secret Ops Framework
- 2:07A Personal Story on Secret Management
- 3:02Centralizing Secret Storage
- 5:21Governance and Access Control
- 9:22Orchestration of Secrets
- 12:54Automation and Rotation of Secrets
- 15:21Conclusion and Call to Action
related talks
26mThe Power of SecretOps Automating Secret Workflows
35mAutomate Secret Rotation in Kubernetes, Then Get Out of the Way!
29m100,000 Different Ways to Manage Secrets in GitOps
44mSecrets at Scale: Managing Cloud Credentials with PowerShell Automation
26mSecret Management in Kubernetes: The GitOps Way - Benjamin Ritter
10mLightning Talk: How to Keep a Secret in GitOps, Without Keeping...
43mA Confidential Story of Well-Kept Secrets
30mLong Live Short Lived Credentials - Auto-rotating Secrets At Scale