[opentelemetry-kube-stack] scrape_configs_file is basically useless

[kristeey]

Hi,
Trying out different features in the opentelemetry-kube-stack helm chart, and came over the scrape_configs_file attribute in the collectors.collectorName section. This is basically useless unless the user wants to use the default scrape config that comes with the helm chart deamon_scrape_configs.yaml or the user clones the chart and installes the helm chart locally. When installing the helm chart using the remote repository it is not possible to include "external" scrape config files into the helm structure (because of helm...). This is also the case when the chart is used as a subchart, and the scrape config files exists in the parent chart. Quoting the helm docs:

"Files outside of a Helm application subchart, including those of the parent, cannot be accessed"

this is a limitation with the .Files object in Helm.

[jaronoff97]

Yes, this is a very annoying limitation of helm, this is useful if and only if you are forking the chart with a local copy. I'm not sure there's a way around this unfortunately. FWIW, I run the chart as a fork and periodically update my local copy for this reason.

[jaronoff97]

either way we should document this.