This repository was archived by the owner on Jul 10, 2026. It is now read-only.
feat(spiffe): socket credential handler for Workload API (RFC UAA-SPIFFE-001)#136
Draft
rkoster wants to merge 1 commit into
Draft
feat(spiffe): socket credential handler for Workload API (RFC UAA-SPIFFE-001)#136rkoster wants to merge 1 commit into
rkoster wants to merge 1 commit into
Conversation
Deliver the SPIFFE workload socket into app containers. SpiffeSocketHandler bind-mounts the host socket directory read-only at /run/spiffe and exports SPIFFE_ENDPOINT_SOCKET so go-spiffe / spiffe-helper workloads discover it automatically. Wired into the cred-manager fan-out alongside instance identity; dormant until SpiffeSocketDir is configured.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a SPIFFE socket credential handler to the Diego executor so app
containers can reach the per-cell SPIFFE Agent's Workload API.
When
executor.spiffe_socket_diris configured, the executor bind-mounts thathost directory read-only into every app container at
/run/spiffeandinjects
SPIFFE_ENDPOINT_SOCKET=unix:///run/spiffe/workload.sock. Workloads thenuse the standard SPIFFE Workload API (
FetchJWTSVID) to obtain a JWT-SVID mintedby UAA.
Key changes
depot/containerstore/spiffe_socket_handler.go(+ tests) — new credential handlerinitializer/initializer_garden.go— register the handler, gated onconfig.SpiffeSocketDirdepot/depot.go— wire the handler into the container lifecycleContext
Part of RFC UAA-SPIFFE-001 — UAA as a SPIFFE Identity Server for Cloud
Foundry — a POC in which UAA issues offline-OIDC JWT-SVIDs to CF apps.
Cross-repo dependencies
spiffe-agentbranch), which shipsthe SPIFFE Agent sidecar (Plan B1) and creates the shared socket directory.
spiffe-signer).Status
Draft / POC. End-to-end verified on a live bosh-lite CF deployment: a test app
fetched a valid RS256 JWT-SVID
(
spiffe://<trust-domain>/cf/org/.../space/.../app/.../process/web) over theinjected socket.