Deep Dive: SPIFFE
summary
SPIRE is deployed on Kubernetes with the server usually as a statefulset + PVC and agents as a daemonset that expose the workload API via a UNIX domain socket directory mount; production requires a shared database (Postgres/MySQL) because the certificate bundle is eventually consistent. Kubernetes-specific attesters include a service account token tester and a projected service account token tester (K8s 1.12+). A new bundle notifier plugin stores the trust bundle in a ConfigMap. Demo on minikube succeeds and the project is released as 0.8.
AI-written summary · about
chapters (6)
- 0:00Start
- 1:29K8 work
- 7:51SPIRE Server • Typically deployed as a StatefulSet
- 9:26SPIRE Agent
- 11:01Node Attestation
- 14:14Registration Entries
related talks
33mSPIFFE and SPIRE: Architecture Deep Dive
37mSPIFFE Deep Dive
29mBridging the Great Divide: SPIFFE/SPIRE for Cross-Cluster Authentication
34mScaling SPIRE for Performance and Availability
26mSPIFFE at GitHub
36mFederated Identity for Distributed Systems: Understanding SPIFFE
33mUniform Workload Identity Everywhere: SPIRE Integrations and Extensibility
49mReal World SPIFFE Scenarios and Outcomes
