How to get config activated in an app-in-apps scenario with Chart/values?

[svenakela]

I would like to deploy kured with ArgoCD and we have an app-in-apps setup. Kured is deployed with following Chart.yaml:

apiVersion: v2
name: kured
description: A Helm chart for Kured
type: application
version: 0.0.1
appVersion: 5.2.0

dependencies:
- name: kured
  repository: https://kubereboot.github.io/charts
  version: 5.2.0

This part works fine, ArgoCD picks it up and deploy Kured as expected. I would like to set some configuration points (endTime, startTime etc) and whatever structure I set in the values.yaml file the config is not applied.

We do have other external apps deployed in the same way, like ingress-nginx, where the values.yaml file adds/overrides values for the dependency. It would be great to get an example of a working values.yaml that sets one or two run parameters correctly.

Thanks in advance.

[ckotzbauer]

I never tested such a structure before, but charts like the kube-prometheus-stack from the prometheus-community are also using dependency-charts and those values are below a key named the same as the dependency-name in chart.yaml.

So instead of

configuration:
  metricsHost: ""

you may write:

kured:
  configuration:
    metricsHost: ""

Did you test this?