Stop the (Password) Insanity! - Managing Credentials with HashiCorp Vault
summary
Microservices app using Postgres and NATS has 22 credentials to manage; Vault is used to store secrets, create a policy and a Kubernetes-auth role bound to service account GOTemp user service. The Vault agent injector creates an init container that writes environment-variable files and a configurable sidecar that refreshes them so services don’t need restarts. Demo applies a patch that adds init container and annotations, writes secrets for Postgres and NATS, and proves rotation works end to end with a successful login after updating Vault.
AI-written summary · about
chapters (7)
- 0:00The credential challenge
- 1:36Centralized secret solution
- 4:19Configuring HashiCorp Vault
- 9:41Kubernetes integration setup
- 17:11Applying and testing secrets
- 21:29Validating dynamic updates
- 25:40Conclusion and Q&A
related talks
38mHow To Secure Your MicroServices
28mSecret Management with Hashicorp´s Vault
01h 03mSecuring Legacy Applications and Container Microservices in Kubernetes
31mModern Security with Microservices and the Cloud
27mWho's managing the credential for your data infrastructure?
38mKeeping Secrets - A Practical Approach to Managing Credentials
42mDynamic credentials for Kubernetes workloads with Vault and VSO
32mIntegrating HashiCorp Vault and K8s Apps - No Code Changes Needed