Istio Certificate Management Through Vault
summary
Describes a concrete Istio certificate flow that replaces Citadel’s internal CA by delegating signing to Vault: a per-node node agent exposes the SDS API, pods send CSRs over a UDS to the agent which forwards the Kubernetes service account identity to Citadel, Citadel authenticates/authorizes then forwards the CSR to Vault signing, Vault returns the signed cert, and the agent hot-delivers keys to Envoy. Covers three integration modes: signing-key injection, Citadel→external CA adapter, and direct node-agent→external CA.
AI-written summary · about
chapters (10)
- 0:00Introduction to Istio
- 1:26Control and Data Plane
- 3:16Security Fundamentals
- 7:10Context-Aware Access Control
- 10:40Security Demo
- 16:47Certificate Management
- 20:58External CA Integration
- 23:39Vault Integration Flow
- 27:31Vault Integration Demo
- 29:28Q&A and Future Plans
related talks
30mIstio New Workload Identity Provision Pipeline Based on Envoy SDS
48mSecuring Kubernetes with Istio
34mEnvoy SDS: Fortifying Istio Security
45mSecure Together: Consul + Vault
19mIdentity, Istio, And You
23mVault for Secrets Management and TLS in Consul K8s
32mIstio: Sailing to a Secure Services Mesh
58mConsul + Vault Learn Lab: Consul API Gateway
