Workload Identity for Humans: A Twelve-Factor Approach#
KubeCon + CloudNativeCon Europe 2025 (London) digest Program Core pick London · 1–4 April 2025
Vish Abrams, Heroku — Core
- Why: A useful counterpoint to the platform-level SPIFFE/SPIRE talks above: an argument that workload identity primitives are powerful but leave application developers reinventing bespoke integration per platform, and a proposal for a more opinionated developer-facing layer.
- What: A developer-focused workload identity approach layered on top of existing CNCF primitives (Kubernetes Service Accounts, SPIFFE/SPIRE), applying Twelve-Factor App principles to make identity integration feel natural rather than bespoke. (from abstract only)
- How: Not detailed mechanically in the abstract; framed as an opinionated abstraction layer over existing identity primitives rather than a new protocol. (from abstract only — thin on mechanism)
- Where applicable: General; relevant to anyone whose application teams treat workload identity as ops-only plumbing rather than a first-class app concern.
