general helm best practice question.. should helm subcharts share the same namespace as the parent chart?
Yes. Probably. I think. Maybe? It depends.
IMO, 100% yes for public charts. That’s why helm has a namespace argument.
For in-house charts you can do what you want, but for the aforementioned reason I would say it’s not recommended
@Erik Osterman (Cloud Posse) this is where helmfile comes in i guess! In the process of seperating out my “cluster chart” into multiple smaller charts, and deployed via helmfile
@Erik Osterman (Cloud Posse) makes a great point. Don’t specify namespace, let the user do that
Do you have any recommended way to automatically bump appVersion in Chart.yaml? I’d like to integrate it with my Jenkins CI/CD Pipeline. (bump appVersion and commit to Chart repo)
Most implementations I’ve seen modify the chart to allow for passing in the container tag which is then used as the ‘version’ of the app instead (usually semver+git commit hash or similar). Then when cutting a new release you manually update that chart appVersion. I know of no other way other than tokenizing the chart appVersion and using something like gomplate to automate that particular task. Perhaps there is a better way I’m not aware of though.
Just wondering if anyone knows an official Jenkins chart? Or which one most use?
We are currently using the cloudbees Jenkins operator chart
So far so good