Take Control of Your Data by Integrating HashiCorp Vault
summary
An end-to-end backup pipeline uses HashiCorp Vault + Vault Agent to inject secrets, Restic to create an encrypted repository, and Ansible over SSH to restore; Kubernetes runs a 1 GB hostPath PV and a three‑replica nginx deployment, a CronJob triggers Restic every 5 minutes, and Restic snapshots are listed and restored successfully to recover the deleted deployment content. The demo shows Vault auto‑auth, templated secret files, and a working restore process.
AI-written summary · about
chapters (13)
- 0:00Introduction and speakers
- 1:09Data backup challenges
- 2:14Backup strategy best practices
- 4:20Building blocks overview
- 5:45Demo setup and environment
- 8:11Secure backup with Vault and Restic
- 10:44Vault UI and agent configuration
- 12:10Vault agent benefits
- 15:30Backup verification
- 17:21Data restore process
- 20:50Restore workflow with Ansible
- 21:16Live recovery demonstration
- 22:32Summary and conclusion
related talks
23mUsing Hashicorp Vault in Kubernetes Clusters
23mHashiCorp Vault and Getting Day 2 Operations Right
01h 03mSecuring Legacy Applications and Container Microservices in Kubernetes
29mAutomating Vault deployments: Patterns, pitfalls, and practical lessons
31mSecure Your Multi-Cloud Delivery Pipeline with HashiCorp Vault
38mKeeping Secrets - A Practical Approach to Managing Credentials
49mManaging Secrets in a Kubernetes Cluster with Hashicorp Vault
38mDon’t Break Your Pasta! Good Practices for Securing Your Pipelines