Default Values in Helm Chart cause problems

[fm4991]

When we Install the otel-collector with this values.yaml in our k3s clusters we get the following error message:

kubectl logs splunk-otel-collector-agent-xl89v
2022/08/23 15:53:28 main.go:225: Set config to [/conf/relay.yaml]
2022/08/23 15:53:28 main.go:291: Set ballast to 165 MiB
2022/08/23 15:53:28 main.go:305: Set memory limit to 450 MiB
Error: failed to get config: cannot unmarshal the configuration: error reading receivers configuration for "filelog": 2 error(s) decoding:

* 'force_flush_period' expected a map, got 'string'
* 'poll_interval' expected a map, got 'string'
2022/08/23 15:53:29 main.go:143: application run finished with error: failed to get config: cannot unmarshal the configuration: error reading receivers configuration for "filelog": 2 error(s) decoding:

* 'force_flush_period' expected a map, got 'string'
* 'poll_interval' expected a map, got 'string'

We tried to fix it in serveral playing around with the YAML structure, but in our opinion it is already a map.
In the End we fixed it with commenting the two mentioned values in the agent configmap.

splunk-otel-collector-chart/helm-charts/splunk-otel-collector/templates/config/_otel-agent.tpl

Lines 250 to 257 in fbf3579

	poll_interval: 200ms
	max_concurrent_files: 1024
	encoding: utf-8
	fingerprint_size: 1kb
	max_log_size: 1MiB
	# Disable force flush until this issue is fixed:
	# https://github.com/open-telemetry/opentelemetry-log-collection/issues/292
	force_flush_period: "0"

[aryznar-splunk]

This issue is fixed and delivered.