We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug We tried to configure opensearch extraOutputs for the aws-for-fluent-bit chart but the specified values are never retrieved.
It seems that there is a typo in the configmap.yaml file (stable/aws-for-fluent-bit/templates/configmap.yaml) at line 451.
configmap.yaml
stable/aws-for-fluent-bit/templates/configmap.yaml
The line is:
{{ .Values.opensearch.extraOutputsIndent_8 }}
it should be:
{{ .Values.opensearch.extraOutputs | Indent 8 }}
Steps to reproduce In the helm values file for the opensearch output of the aws-for-fluent-bit chart, we have the following configuration:
opensearch: enabled: true match: "*" host: <HOSTNAME> port: "443" tls: "on" ... extraOutputs: | tls.verify off tls.debug 4
Expected outcome In the generated fluent-bit.yaml configuration file, we should see something like this:
[OUTPUT] Name opensearch Match * Host <HOSTNAME> Port 443 tls on ... tls.verify off tls.debug 4
Environment
aws-for-fluent-bit
2.28.4
1.24
eks.6
Additional Context:
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Describe the bug
We tried to configure opensearch extraOutputs for the aws-for-fluent-bit chart but the specified values are never retrieved.
It seems that there is a typo in the
configmap.yaml
file (stable/aws-for-fluent-bit/templates/configmap.yaml
) at line 451.The line is:
it should be:
Steps to reproduce
In the helm values file for the opensearch output of the aws-for-fluent-bit chart, we have the following configuration:
Expected outcome
In the generated fluent-bit.yaml configuration file, we should see something like this:
Environment
aws-for-fluent-bit
2.28.4
1.24
eks.6
Additional Context:
The text was updated successfully, but these errors were encountered: