Consul + Vault Learn Lab: Consul API Gateway
summary
Deploys HCP Vault and Vault Agent Injector into an EKS cluster, enables KV and PKI secret engine to generate a root CA and on‑the‑fly certificates, and stores the gossip encryption key and license in Vault. Kubernetes auth maps service accounts to Vault roles and policies; Helm installs Consul which pulls secrets at startup — Vault shows eight clients connected. Consul API Gateway creates a cloud load balancer and routes /echo between echo1 and echo2 with a 50% traffic split, and the demo proves end‑to‑end traffic and cert provisioning work.
AI-written summary · about
chapters (6)
- 0:00Introduction and setup
- 13:09Deploying Vault and injector
- 22:30Configuring Vault policies and roles
- 33:18Deploying Consul with Vault integration
- 42:31Consul API Gateway overview
- 52:45Q&A and closing remarks
related talks
23mVault for Secrets Management and TLS in Consul K8s
26mCombining DevOps with PKI Compliance Using HashiCorp Vault & Consul
38mModern Service Networking With Consul Connect, Envoy and Kubernetes
23mUsing Hashicorp Vault in Kubernetes Clusters
29mDesigning High Availability for HashiCorp Vault in AWS
49mUsing HashiCorp Vault with Kubernetes
29mAdopting HashiCorp Vault: Deployment, Adoption, and Beyond
51mRun modern PKI workflows with HCP Vault on AWS