aws / aws/eks-charts

Opensearch extraOutputs values for the aws-for-fluent-bit chart are never retrieved

Open
#955 0 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Mustache
Stars
1.3k
Forks
1.1k
Avg merge
22m
Merged PRs (30d)
5

Description

**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:

```
{{ .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:
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
Port 443
tls on
...
tls.verify off
tls.debug 4
```

**Environment**

* Chart name: `aws-for-fluent-bit`
* Chart version: `2.28.4`
* Kubernetes version: `1.24`
* Using EKS (yes/no), if so version? `eks.6`

**Additional Context**:

Contributor guide

Open the contributing guide

Research direction

Inspect stable/aws-for-fluent-bit/templates/configmap.yaml around line 451, starting with how the opensearch extraOutputs value is rendered. Render the chart with the issue's opensearch values and confirm that the generated fluent-bit.yaml contains the configured tls.verify and tls.debug lines with the expected indentation.

Written by the indexing model from the issue text.

Assessment

Tech stack
helm, kubernetes
Domain
devops
Issue type
Bug
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.