Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
helm module feedback #29661
I tried out the helm module from the 2.4 prerelease. Here's my feedback.
Frankly, that's a bit of a PITA, the kubernetes module should support specifying a kubeconfig file or remote location, and so should this module.
An easier option would be just to add to the documentation what I did as an example:
@flaper87 I might be doing something wrong but I tried the following and didnt work:
What distro are you using? You may need to install
Check what package contains
Thanks for helping out :)
@flaper87 i gave another try to it, but unfortunately some other dependency is failing and i couldnt uninstall from the master branch. :/
Not sure if this is familar to python devs and i didnt had enough time to proceed with digging on it.
referenced this issue
Aug 30, 2018
@flaper87 I tried to get the helm module to work but failed miserably.
As of right now, it only supports installing your own helm charts from a directory but this is actually all I need. No matter which helm chart we install, we always add the upstream chart as a dependency and then customise
The big difference you'll notice immediately is I'm not integrating with Helm/Tiller APIs, just going straight for the
My usage as of right now, looks like this:
in my roles taks file I then have a bunch of tasks to install stuff like this:
The current implementation behaves like this:
There are a number of todos e.g. verify etc but this works reliably with the only dependency being helm installed on the deployment machine(which I think is acceptable, I fought with libgit2 because of various version issues to no avail).
This should work for upstream charts by simply specificing
I'll clean up the repo later and Apache V2 on it with readme/instructions but it took less time to write this than I spent trying to get the current module to work. Feedback welcome.
@zcourts thanks a lot for the feedback and sharing your work. I honestly don't have the time to maintain and move this module forward. My focus changed after the module was accepted. I'd be more than happy to have this module deprecated in favor of yours or have any of you given access as maintainers :)
Let me know what you'd prefer. Like you could do a major refactor to the existing module and have it use your code.