HelmRelease with subcharts/dependencies

[kgorskowski]

Sorry if this has been solved somewhere before, I couldn't find it. I was trying to "migrate" a monitoring stack from a vanilla helm install to a flux workflow. Its based on this loki-stack grafana helm chart . The HelmRelease is picked up but it seems like the provided values are not processed correctly. When setting eg grafana and/or prometheus on "enabled" the values are picked up but its only ever the loki pod that is starting. So maybe its because they depend on subcharts definded in the requirements.yaml? Or am I missing something obvious? Where would be the best place to debug things like that?
Thanks for any input!
output from helm get values

grafana:
  enabled: true
prometheus:
  enabled: true

and my HelmRelease yaml:

apiVersion: helm.toolkit.fluxcd.io/v2beta1
kind: HelmRelease
metadata:
  name: loki
  namespace: monitoring
spec:
  chart:
    spec:
      version: "2.0.x"
  values:
    prometheus:
      enabled: true
    grafana:
      enabled: true

• edit - I just tried a manual debug like stated here in the docs - when filtering out the existing spec.values a manual helm upgrade would spin up the missing deployments, volumes, service accounts and so on. So I guess the syntax is correct and the values are in the right place but somehow the whole subchart rollout is just not picking up

[kgorskowski]

Ok. Feeling pretty stupid right now and wasted a couple of hours by not double checking the naming of the charts.
I was rolling out simply the loki chart from the repo, what I needed was the loki-stack chart of wich the components with grafana, prometheus and loki are a part of. So of course now it works as intended... damn