feat: use Vault Transit as signing service#8
Merged
Conversation
- Add edc-vault-transit runtime dependency to identity-hub launcher - Add do_curl helper to seed job for proper HTTP status inspection, distinguishing 409 (already exists) from other errors - Add IPC_LOCK capability to vault-agent sidecar in siglet Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
wolf4ood
approved these changes
May 26, 2026
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR uses Vault's Transit engine to sign cryptographic material to prevent the private key from ever leaving the secure enclosure.
This PR also separates the
appdeployment into three different sub-deployments:k8s/apps/edck8s/apps/cfmk8s/apps/uithis makes un-deploying and redeploying easier.
Also, this PR adds a local docker image cache for subsequent attempts.