Support Helm using the -config.file but hosted in the values.yaml

[mbrancato]

Is your feature request related to a problem? Please describe.

It is extremely confusing what config is relevant in the Helm chart today.

The config in the Helm chart today is for a dependency "Phlare", and can seem like it is part of the Pyroscope configuration.

pyroscope/operations/pyroscope/helm/pyroscope/values.yaml

Lines 155 to 169 in bbe05cc

	structuredConfig: {}
	# -- Contains Phlare's configuration as a string.
	# @default -- The config depends on other values been set, details can be found in [`values.yaml`](./values.yaml)
	config: |
	{{- if .Values.minio.enabled }}
	storage:
	backend: s3
	s3:
	endpoint: "{{ include "pyroscope.fullname" . }}-minio:9000"
	bucket_name: {{(index .Values.minio.buckets 0).name | quote }}
	access_key_id: {{ .Values.minio.rootUser | quote }}
	secret_access_key: {{ .Values.minio.rootPassword | quote }}
	insecure: true
	{{- end }}

But when you look closer, this is not the Pyroscope configuration file. The example uses:

storage:
  backend: s3
  s3:
    endpoint: "minio:9000"

But Pyroscope uses:

s3_storage_backend:
  endpoint: "minio:9000"

This means that most of the available configuration parameters are left to be specified in the extraArgs section as CLI params.

Describe the solution you'd like

There should be a structured Pyroscope configuration that aligns with the Pyroscope documentation in the Helm chart values.