Allow referencing multiple secrets in additionalCertificates #852
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.
There are cases when several self-signed certificates scattered across multiple K8S secrets need to be added to Java truststore. While there's a way to declare a custom
additionalInitContainer
,additionalVolumes
andadditionalVolumeMounts
, this isn't trivial it requires knowledge of the DC Helm charts design.This PR introduces an additional
secretList
value that makes it possible to reference multiple secrets with their respective keys inadditionalCertificates
stanza:secretList
is a list of secret names and their respective keys<secret-name>-<key>
format which makes it possible to have identical keys in different secretsChecklist
e2e
label)