Integrating SPIRE and Istio
summary
Modified Istio replaces its internal CA so Istio agents fetch identities from SPIRE instead of using the CSR API, implemented via Istio’s SecretManager interface and a glue layer to a SPIFFE Workload API implementation. Demo runs on an EKS two-node cluster hosting Bookinfo with sidecars (three reviews replicas) and visible in Kiali and Torniak. Planned features include hardware/cloud attestation, federation options, keeping root keys outside the cluster, and upstreaming the change into mainline Istio.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:47Istio Background
- 1:32Things we tried first
- 3:49What is this project about?
- 4:23What will this get us?
- 6:07Solution overview
- 7:02Istio (currently)
- 8:46Looking at the fetch SVID flow
- 10:00What comes next?
- 11:22Bookinfo Demo
related talks
16mUsing SPIRE in Production at Uber
36mFederated Identity for Distributed Systems: Understanding SPIFFE
38mStop Reinventing the Wheel with Istio
53mStop reinventing the wheel with Istio
30mIstio New Workload Identity Provision Pipeline Based on Envoy SDS
26m10 Lessons From Migrating to SPIFFE After 10 Years Of Service Identity at Square
46mStop reinventing the wheel with Istio
40mIstio, your K8S cluster best friend
