Conversation
![github-code-quality[bot]](https://avatars.githubusercontent.com/u/9919?s=60&v=4){kind=small}
mxsrc
force-pushed
the
kms
branch
12 times, most recently
from
b89eaff to
b0c1bc8
Compare
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
1 participant
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 introduces an integration to an external KMS (Hashicorp Vault/openbao) for storing decryption keys.
The configuration is cluster-specific, an attribute
hashicorpVaultSettingsis introduced that at the moment only stores thebase_urlthe KMS is reachable with. The communication is done viaTLS, and authentication is done using client certificates. For this reason, mTLS needs to be used when using the external KMS.On the vault, a cert logins need to be enabled, a policy for the API container placed, and linked to the certificates the API presents.
To keep the implementation clean, the access to keys is managed through a common interface, that, depending on the presence of the KMS configuration either stores the secrets in the FDB, as is the status-quo, or offloads them to the KMS.