chart contains one simple web application, and one dependent chart - postgresql. I need my application templates to read auth details of postgresql in its chart overrides, at first glance it looks easy to implement, but I need postgresql to be deployed in a separate namespace, which is not easy to perform when chart author didn't implemented "namespaceOverride" feature. and also I dont want to implement "helmfile" as it complicates things, and after that I can't read psql overrides, and cant also integrate with ArgoCD.
The one option which is coming to my mind is to deploy ArgoCD "application" with terraform so I can pass any parameters between charts, but I it will be hard to maintain later.
Finally.. any advice?))
I'll keep you in my thoughts and prayers
Dude break down your own question. Clearly all your options are at odds
You can set a default for name override
good option. but the chart is from outside, cant change anything inside it.
That's a bit dangerous don't you think?
I think you can have a helper that does some preset, those _files.tpl
A bit confused though. Usually orgs would fork an open source charts and maintain their own version of it since there's usually a lot more stuff involved (like Argo, customize, flux etc etc). Why can't you fork it and modify the stuff?
Обсуждают сегодня