Vault for Secrets Management and TLS in Consul K8s
summary
Consul on Kubernetes uses Vault as the secrets backend, replacing Kubernetes secrets with Vault paths and keys and modifying Helm values to point at Vault. The integration uses Vault Agent Injector, Vault PKI and KV-v2 engines and mounts secrets via annotations; deployments inject three sidecars (init, Vault agent, credential rotation sidecar) that sync and apply rotations. Demo shows a full end‑to‑end rotation of a gossip encryption key: Vault update triggers pod file update, rotation logic promotes the new key and deletes the old, and the cluster verifies the change.
AI-written summary · about
chapters (5)
related talks
45mSecure Together: Consul + Vault
58mConsul + Vault Learn Lab: Consul API Gateway
31mVault and Secret Management in Kubernetes
20mEvolving Kubernetes security with Vault and OpenShift
23mUsing Hashicorp Vault in Kubernetes Clusters
01h 03mSecuring Legacy Applications and Container Microservices in Kubernetes
39mManaging and securing Kubernetes secrets - Simon Pearce
42mDynamic credentials for Kubernetes workloads with Vault and VSO