A Nomadic Vault: Secrets for Schedulers and Runtimes
summary
Demonstrates a working Nomad-Vault integration that automatically issues ACL tokens and programs Nomad policies on demand, using Vault roles to create short‑lived scheduler tokens and render per‑job secrets. Shows dynamic DB credentials issued at job start (TTL ~1 hour) and rendered into container files, validates accessor/secret IDs and Nomad allocations, and confirms self‑service job submission without human token management. Practical configs and demo run succeed end‑to‑end. dynamic DB credentials ACL tokens programmed on demand
AI-written summary · about
chapters (7)
- 0:00Introduction and challenges
- 4:48Nomad ACLs and policies
- 8:00Managing multi-tenancy
- 10:14Vault and Nomad integration
- 12:21Configuration and setup
- 16:47Demonstration and workflow
- 24:35Conclusion and wrap-up
related talks
39mBuilding Efficient Continuous Integration Pipelines with Nomad, Vault and Jenkins
28mSecret Management with Hashicorp´s Vault
41mChanging Applications for Changing Secrets
42mDynamic credentials for Kubernetes workloads with Vault and VSO
44mSecret Management with Hashicorp's Vault
38mKeeping Secrets - A Practical Approach to Managing Credentials
47mThe Secret to Handling Dynamic Secrets
40mA Better Way To Manage Secrets