Kubernetes example config is using the old TLS config

[jpkrohling]

The Kubernetes example config is currently using the old squashed TLS configuration, which causes pods to fail with:

2021-10-22T11:44:16.540Z	info	service/collector.go:303	Starting otelcol...	{"Version": "v0.33.0-50-g0594aa1a", "NumCPU": 6}
2021-10-22T11:44:16.540Z	warn	service/collector.go:312	`mem-ballast-size-mib` command line option has been deprecated. Please use `ballast extension` instead!
2021-10-22T11:44:16.540Z	info	service/collector.go:242	Loading configuration...
Error: cannot load configuration: error reading exporters configuration for otlp: 1 error(s) decoding:

* '' has invalid keys: tls
2021/10/22 11:44:16 collector server run finished with error: cannot load configuration: error reading exporters configuration for otlp: 1 error(s) decoding:

* '' has invalid keys: tls

Steps to reproduce:

• minikube start --vm-driver kvm2 --cpus 6 --memory 20480 --container-runtime=crio --addons=ingress --addons=metrics-server
• kubectl apply -f https://raw.githubusercontent.com/open-telemetry/opentelemetry-collector/main/examples/k8s/otel-config.yaml
• kubectl logs deployments/otel-collector

[jpkrohling]

References:

• Inconsistency in config for TLS vs Auth #4028
• Remove squash on configtls.TLSClientSetting in confighttp & cnofiggrpc #4063

[shree007]

May i proceed to work on it?

[jpkrohling]

It's yours!

[jpkrohling]

Sorry, my diagnosis was really wrong. I should have paid more attention to the error message. The actual problem is that the image being used by that example seem to be using an older code base, which still didn't have the TLS changes I mentioned earlier. The example has been updated to use the new TLS option.

So, the solution really is to use another more recent image, like otel/opentelemetry-collector:0.37.1 (or perhaps even latest) instead of otel/opentelemetry-collector-dev:latest.

You'll notice that it will fail due to a command line parameter that has been removed. Just change the command to remove it.

[shree007]

Hey Juraci
No problem. Let me check once.

[shree007]

Hi Juraci
So I have replaced the image from otel/opentelemetry-collector-dev:latest to otel/opentelemetry-collector:0.37.1
and removed the "--mem-ballast-size-mib=165" and "--mem-ballast-size-mib=683" based on following error msg
"mem-ballast-size-mib command line option has been deprecated." that i got while running.

Please review #4278