[bitnami/fluentd] Remove template fragments from example ConfigMap in README

[stv0g]

Description of the change

This PR closes #2389

Benefits

Users dont get errors when using the example ConfigMap for their setups.

Possible drawbacks

None.

Checklist

• Chart version bumped in Chart.yaml according to semver.
• Title of the PR starts with chart name (e.g. [bitnami/chart])

[stv0g]

Please merge #2404 first. Afterwards I will rebase and bump the chart version

[andresbono]

Hi @stv0g, thanks for opening this PR.

In the meantime the PR gets merged, we both agree that the {{- end }} line should be removed. However I don't see why the other changes are required. This is how I am testing it:

1. Create the configmap.yaml file in bitnami/fluentd/templates/configmap.yaml
2. Execute helm template bitnami/fluentd
3. Look for the configmap k8s manifest:

  fluentd.conf: |
    # Prometheus Exporter Plugin
    # input plugin that exports metrics
    <source>
      @type prometheus
      port 24231
    </source>

    # TCP input to receive logs from the forwarders
    <source>
      @type forward
      bind 0.0.0.0
      port 24224
    </source>

Both templates ({{ .Values.metrics.service.port }} and {{ .Values.aggregator.port }}) are correctly substituted. Is it different for you?

[stv0g]

Hi @andresbono,

Ah okay I see.. I usually dont checkout the Helm charts locally.
I just copied the example ConfigMap and applied it alongside Helm with kubectl.
I think its the more common scenario, or isn't it?

[andresbono]

That's true, @stv0g. Let's hard-code the ports as this is an example.

[andresbono]

LGTM

[andresbono]

@stv0g, I merged the PR before we bumped the chart version, sorry for that. This is the commit 92a2215 that increases the chart version of bitnami/fluentd to 1.0.4.