Auto-Configure Your Vault and Boundary With CTS
summary
Deploys Postgres and a sample app to Kubernetes while Consul Terraform Sync watches the Consul catalog and writes terraform tfvars that trigger Terraform modules to: create Vault DB mounts and dynamic DB roles, pull Kubernetes secrets for connection strings, and register Boundary targets. Demo shows successful Boundary HTTP and Postgres connections and automated credential rotation; handles race conditions with an ELB DNS wait (netcat) and Vault Agent retry for auth tokens. Code and Terraform modules are published and runnable.
AI-written summary · about
chapters (9)
- 0:00Introduction and motivation
- 7:48Problem with manual configuration
- 10:38Demo setup and overview
- 13:05Database deployment and Vault setup
- 16:59Application deployment and dynamic access
- 20:11How the automation works
- 24:28Terraform module details
- 27:19Security and best practices
- 28:01Summary and Q&A
related talks
18mForget About DB Credentials with Terraform, Vault and Kubernetes
23mSimplifying Kubernetes deployment with Terraform for OpenAI
28mSelf-Service Vault in Kubernetes
42mDynamic credentials for Kubernetes workloads with Vault and VSO
23mVault for Secrets Management and TLS in Consul K8s
32mIntegrating HashiCorp Vault and K8s Apps - No Code Changes Needed
01h 03mSecuring Legacy Applications and Container Microservices in Kubernetes
54mUsing Terraform and Consul to delegate service deployment to service teams