Artem
Artem
This one is quite tricky to fix. Used YAML encoder `sigs.k8s.io/yaml v1.2.0` creates line breaks for all lines longer than 80 symbols. Which is fine, because such quotes in the...
@Duologic looks really nice! Can you please add statefulset sample to `test_data/sample-app.yaml` And regenerate examples in /examples directory by running: ```shell cat test_data/sample-app.yaml | go run ./cmd/helmify examples/app ```
Hi @KaiReichart. The issue was fixed in #42 PR. Please upgrade to [v0.3.13 release](https://github.com/arttor/helmify/releases/tag/v0.3.13) containing the fix.
@chenrui333 Cool, thank you! But let's keep `arttor/tap/helmify` in the Readme because it allows installing the latest version right after a new release.
Thank you for the feedback! Totally agree that `Appversion` should be a default value for the image tag of the main container. But it is difficult to identify the main...
Thanks, good idea! Seems like I was unlucky to not find Chartify when I googled solutions for charts generation. I actually don't know how helmify is different from Chartify but...
HI, @KaiReichart , can you please try to upgrade to [the latest version](https://github.com/arttor/helmify/releases/tag/v0.3.18)? The issue might be fixed in #42
Very good suggestion @alanmeadows ! I was thinking to add something like this: ```shell helmify --only=rbac,crd helmify --skip=deployment,configmap ``` What do you think?
Change in `values.yaml` v0.0.30 to v0.0.31 - removes ability to define end user params via ConfigMap
Hi, thank you for raising the issue. Just want to confirm that old version was handling yaml data in configMap incorrectly because k8s expects string key-value pairs in data. I...
Change in `values.yaml` v0.0.30 to v0.0.31 - removes ability to define end user params via ConfigMap
I absolutely agree that separate values for yaml were more user-friendly but resulted ConfigMap was incorrect because k8s expects string value according to spec.