#helm (2020-04)
Archive: https://archive.sweetops.com/helm/
2020-04-06
![btai avatar](https://avatars.slack-edge.com/2019-09-04/736463433650_34701761239ea7ba8207_72.jpg)
general helm best practice question.. should helm subcharts share the same namespace as the parent chart?
![roth.andy avatar](https://avatars.slack-edge.com/2019-09-18/753707271651_6f58c1cbab3c77754f58_72.jpg)
Yes. Probably. I think. Maybe? It depends.
![Erik Osterman (Cloud Posse) avatar](https://secure.gravatar.com/avatar/88c480d4f73b813904e00a5695a454cb.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0023-72.png)
IMO, 100% yes for public charts. That’s why helm has a namespace argument.
![Erik Osterman (Cloud Posse) avatar](https://secure.gravatar.com/avatar/88c480d4f73b813904e00a5695a454cb.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0023-72.png)
For in-house charts you can do what you want, but for the aforementioned reason I would say it’s not recommended
![btai avatar](https://avatars.slack-edge.com/2019-09-04/736463433650_34701761239ea7ba8207_72.jpg)
@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
![roth.andy avatar](https://avatars.slack-edge.com/2019-09-18/753707271651_6f58c1cbab3c77754f58_72.jpg)
@Erik Osterman (Cloud Posse) makes a great point. Don’t specify namespace, let the user do that
2020-04-07
2020-04-22
![Szymon avatar](https://secure.gravatar.com/avatar/1a988919d30403e12ad15c20c38b058d.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0006-72.png)
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)
![Zachary Loeber avatar](https://avatars.slack-edge.com/2020-05-13/1115475485942_e68ae4d6556df390de70_72.jpg)
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.
2020-04-25
![s_slack avatar](https://avatars.slack-edge.com/2020-09-20/1375444277730_12639a283934dec29897_72.png)
Just wondering if anyone knows an official Jenkins chart? Or which one most use?
![Erik Osterman (Cloud Posse) avatar](https://secure.gravatar.com/avatar/88c480d4f73b813904e00a5695a454cb.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0023-72.png)
We are currently using the cloudbees Jenkins operator chart
![Erik Osterman (Cloud Posse) avatar](https://secure.gravatar.com/avatar/88c480d4f73b813904e00a5695a454cb.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0023-72.png)
So far so good
![Erik Osterman (Cloud Posse) avatar](https://secure.gravatar.com/avatar/88c480d4f73b813904e00a5695a454cb.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0023-72.png)
Kubernetes native Jenkins Operator. Contribute to jenkinsci/kubernetes-operator development by creating an account on GitHub.