Artem
Artem
Change in `values.yaml` v0.0.30 to v0.0.31 - removes ability to define end user params via ConfigMap
please describe how it should look in a helm chart keeping in mind that it should be represented as a string in resulted k8s manifest.
Change in `values.yaml` v0.0.30 to v0.0.31 - removes ability to define end user params via ConfigMap
Understood. Can you please elaborate on the first option? What change do we need to introduce or you are speaking about your project? About the second option: having an extra...
@smitthakkar96 great idea! Such config will enable users to easily adjust helmify to other use-cases. Let's discuss specs first. Maybe we can reuse the config to implement [57](https://github.com/arttor/helmify/issues/57) and [54](https://github.com/arttor/helmify/issues/54)....
Hi @vbehar! Thank you for your contribution. The proposal looks very interesting but i see several potential problems: - the change is quite big and it is better to hide...
Fixed in [0.3.22 release](https://github.com/arttor/helmify/releases/tag/v0.3.22).
true, multi-ns charts are not supported right now. Unfortunately, I don't have capacity to implement it right now, but i can help with review if someone volunteers implementing it.
changes are available in [v0.4.13 release](https://github.com/arttor/helmify/releases/tag/v0.4.13)
Sorry, I think I created a duplicate issue #1128. I have similar behavior with: - NooBaa Operator Version: 5.11.0 - Platform: K8s v1.22.3 on minikube 1.24.0 5CPU 8GB Default StorageClass...
> @arttor you worked on it did you try using this PR or have any review comments for it? @ideepika all config parameters from our use-case are covered. LGTM
> > @arttor you worked on it did you try using this PR or have any review comments for it? > > @ideepika all config parameters from our use-case are...