-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Possibility to repackage a chart or specify additional values/images in helm_install rules #11
Comments
Thanks! and thanks for trying out the Bazel rules! Your workaround is what I would have done though I'm also not sure if that's the best way. How would this work without Bazel? Is there an existing workflow you have that you're just trying to port over? Also, there's helm_import_repository which you could use to import charts from a registry. The docs there are a bit lacking but I have an example of using it here: https://github.com/abrisco/rules_helm/blob/0.0.3/tests/test_deps.bzl |
I'd push dependent image to the registry first and then install a chart with additional values like this helm repo add bitnami https://charts.bitnami.com/bitnami
helm install kafka bitnami/kafka -f values.yaml From my perspective, providing additional values(and images) to
Yes, currently I use another library, but it's very limited in the process of resolving images(I could pass only 1 image there), so I decided to try something else.
Yes, that's exactly what I want to use to install a chart later with additional values/images. P.S. I think there should be also a way to provide a namespace(with the possibility to create it) via helm install. Usually, we don't hardcode it in a chart. |
Sorry for the delay!
You can pass arguments to helm install using a command like the folling
Sounds reasonable to me. Could definitely see a |
First of all, thank you for the great library!
I want to use it in my project, but i'm not sure how to handle a case when I need to import a chart from repository and install it with additional values file and docker image dependency.
More specifically, I want to import a bitnami kafka chart and provide additional initContainers and change heap opts.
First possible workaround, which comes to my head, is to import a chart by
http_archive
rule and then package it withhelm_package
rule. Is there any way to do it better?The text was updated successfully, but these errors were encountered: