Scaling SPIRE for Performance and Availability
Talkat KubeCon + CloudNativeCon North America 2019 · on Wednesday, 2019-11-20· at 11:50· Pacific Ballroom, Salon 25-26 - Marriott Marquis San Diego Marina Hotel·
summary
SPIRE is the SPIFFE runtime that bootstraps workload identity using short-lived X.509 certs served by local agents and signed by a control-plane server; agents do optimistic fetching to cache credentials so workloads get sub-second responses while server-side signing scales horizontally. The talk covers the Kubernetes registrar, tradeoffs between per-host vs per-cluster registrations, and operational knobs like certificate lifetimes (default TTL one hour, community ranges from weeks down to 10–15s in tests) and caching for availability.
AI-written summary · about
chapters (9)
- 0:00Understanding zero trust
- 3:48SPIFFE and SPIRE overview
- 5:56Architecture of SPIRE
- 7:55Short-lived credentials
- 10:44Workload API and caching
- 13:21Node attestation and server
- 15:32Registration and policy
- 18:39TTL trade-offs and summary
- 21:21Audience Q&A session
related talks
33mSPIFFE and SPIRE: Architecture Deep Dive
26mSPIFFE at GitHub
30mIntro: SPIFFE
34mSecuring Multi-Cloud Cross-Cluster Communication with SPIFFE and SPIRE
49mReal World SPIFFE Scenarios and Outcomes
19mFederate, Scale, and Secure: Practical SPIFFE/SPIRE for Containers...
32mProduction Workload Identity with SPIRE
04mSecurely Bridging Cloud-Native and Traditional Workloads...
