Federate, Scale, and Secure: Practical SPIFFE/SPIRE for Containers...
summary
SPIFFE/SPIRE issues short-lived identities (X.509 and JWT-SVIDs) and scales by using nested spire (intermediate CAs per cluster) and one-way federated spire trusts to extend boundaries. Production guidance calls for multiple SPIRE servers per trust domain, rate-limited OIDC endpoints, allow lists and audience restrictions, hardened agent access via CSI/UDS, strong crypto with key rotation (recommend half-TTL), post-quantum testing, and backing the datastore with a cloud-native Postgres operator for HA and DR.
AI-written summary · about
chapters (11)
- 0:00SPIFFE/SPIRE introduction
- 1:27Workload identity in cloud-native
- 3:36SPIFFE/SPIRE architecture
- 6:54Secure SPIRE control plane
- 10:48Hardening agent configurations
- 12:54Post-quantum cryptography
- 13:37Scaling with federated SPIRE
- 15:48High availability strategies
- 16:33Performance tuning SPIRE
- 17:36Production readiness checklist
- 17:56Q&A
related talks
34mSecuring Multi-Cloud Cross-Cluster Communication with SPIFFE and SPIRE
33mSPIFFE and SPIRE: Architecture Deep Dive
30mIntro: SPIFFE
41mSPIFFE Project Intro
36mFederated Identity for Distributed Systems: Understanding SPIFFE
49mReal World SPIFFE Scenarios and Outcomes
34mScaling SPIRE for Performance and Availability
29mBridging the Great Divide: SPIFFE/SPIRE for Cross-Cluster Authentication
