[bitnami/kafka] Flexible tls config for metrics exporter #5520
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.
Description of the change
Flexible JKS configuration for the metrics-exporter.
In my company we are using cert-manager to automate certificate management. The cert-manager creates a secret, which is completely different, than the one forced by the kafka-helm-chart.
We need to be able to change the default JKS secret and key mappings.
Benefits
This is helpful for anyone who is using already some kind of cert-management or even using a different scheme for creating the certs.
Possible drawbacks
Applicable issues
Additional information
Checklist
Chart.yaml
according to semver.[bitnami/chart]
)