At the moment, children templates can inherit values in the parent Values.yml file if that file includes the value, prefixed by the chart name. For example,
mysql:
mysqlRootPassword: herapderpa # This overrides the mysqlRootPassword on the top level of its Values.yml
There is no such inheritance allowed for files. It appears that values are being explicitly passed down the stack in the following snippet:
https://github.com/kubernetes/helm/blob/c8af660b181daf4000aca87e19e583fd1abec0b3/pkg/engine/engine.go#L217-L222
It would be good for files to be passed down the stack also, though there is no convention for doing as such. One suggestion might be to create a folder with the name of the child chart, and inherit the files supplied in that folder. For example,
In the case above, the mysql.conf file would override the mysql.conf file in the root of the mysql chart, stored in charts/ (note: don't go looking, I made that up)
Thaanks!
At the moment, children templates can inherit values in the parent
Values.ymlfile if that file includes the value, prefixed by the chart name. For example,There is no such inheritance allowed for files. It appears that values are being explicitly passed down the stack in the following snippet:
https://github.com/kubernetes/helm/blob/c8af660b181daf4000aca87e19e583fd1abec0b3/pkg/engine/engine.go#L217-L222
It would be good for files to be passed down the stack also, though there is no convention for doing as such. One suggestion might be to create a folder with the name of the child chart, and inherit the files supplied in that folder. For example,
In the case above, the mysql.conf file would override the mysql.conf file in the root of the mysql chart, stored in charts/ (note: don't go looking, I made that up)
Thaanks!