added ca injection for secrets and configmaps #31
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 addresses #29 by adding the following feature:
In addition to those objects, it is also possible to inject ca bundles from secrets to secrets and configmaps:
secrets
: the secret must of type:kubernetes.io/tls
. These types of secret must contain thetls.crt
andtls.key
keys, but is this case those keys are going to be presumably empty. So it is recommended to create these secrets as follows:confimaps
: the ca bundle will be injected in this keyca.crt
, here is an example:Projected volumes can be use dto merge the caBundle with other pieces of configuration and or change the key name.