-
Notifications
You must be signed in to change notification settings - Fork 265
Description
Today I discovered two minor bugs related to the use of self-created secrets:
-
When you use a self-created Secret to store your token (secret.create = false) the global option for an caFile is not working.
This (correctly) leads to an error with untrusted HEC endpoint certificates, since the caFile is not added to the (self-created) Secret
The documentation should be changed so that the CAFile must also be included in the secret -
when adding the CAFile to the Secret, the CA is not used, because the ENV variable "SSL_CERT_FILE" is only used when the CAFile is imported via values.yaml
There should be an additional variable to allow the creation of the ENV variable
However, as a workaround you can add a dummy entry to your values.yaml

Line 86 in 64a4405
| {{- if or .Values.splunk.hec.caFile .Values.global.splunk.hec.caFile }} |