Skip to content

Add diego.executor.inject_workload_identity BOSH property - #1204

Merged
ameowlia merged 2 commits into
cloudfoundry:developfrom
klapkov:CFAR-1430-workload-identity-opt-in
Sep 15, 2026
Merged

ameowlia merged 2 commits into
cloudfoundry:developfrom
klapkov:CFAR-1430-workload-identity-opt-in

Conversation

@klapkov

@klapkov klapkov commented Sep 11, 2026

Copy link
Copy Markdown
Contributor

Exposes the InjectWorkloadIdentity ExecutorConfig flag as a rep job property (default false). Operators set this to true on cells where all volume drivers accept the _workload_guid/_workload_type keys. This way the nfs-volume isn't obligated to support the new workload_identidy keys.

Fixes: #1203

Summary

Backward Compatibility

Breaking Change? Yes/No

@klapkov
klapkov requested a review from a team as a code owner September 11, 2026 10:49
Exposes the InjectWorkloadIdentity ExecutorConfig flag as a rep job
property (default false). Operators set this to true on cells where all
volume drivers accept the _workload_guid/_workload_type keys.
@iaftab-alam

Copy link
Copy Markdown

hey @klapkov Thanks for the PR. Can this PR be merged? We need a new Diego release with the fix as our validation pipeline is blocked and unable to cut new cf release. Thanks

@ameowlia ameowlia left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

AI reported a missing test.

[MINOR] — src/code.cloudfoundry.org/executor/depot/containerstore/containerstore_test.go / Missing false-path test for Workload Identity Injection — Testing The test suite verifies the injection behavior when injectWorkloadIdentity is true, but lacks an explicit test ensuring the keys are not injected when the flag is false (the default configuration). Fix: Add a test context in containerstore_test.go asserting that when injectWorkloadIdentity is false, the volume manager mount config does not contain the _workload_guid or _workload_type keys.

Comment thread jobs/rep_windows/spec
description: "Experimental: arbitrary command to run after setup action"
diego.executor.post_setup_user:
description: "Experimental: user to run post setup hook command"
diego.executor.inject_workload_identity:

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you update this description to include a bit of info about why someone might want to do this?

config[:volman_driver_paths] = value
end

config[:inject_workload_identity] = p("diego.executor.inject_workload_identity")

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you update the rspec tests for this new property?

@github-project-automation github-project-automation Bot moved this from Inbox to Pending Merge | Prioritized in Application Runtime Platform Working Group Sep 15, 2026
@ameowlia
ameowlia merged commit b5e57f6 into cloudfoundry:develop Sep 15, 2026
10 checks passed
@github-project-automation github-project-automation Bot moved this from Pending Merge | Prioritized to Done in Application Runtime Platform Working Group Sep 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Development

Successfully merging this pull request may close these issues.

Forward workload identity to volume drivers via mount config breaks backward compatibility with strict option validations in NFS volume drivers

3 participants