Skip to content
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

helm install with multiple --set parameters (maybe missing documentation) #3351

Closed
chucky2305 opened this issue Jan 17, 2018 · 4 comments
Closed
Labels

Comments

@chucky2305
Copy link

chucky2305 commented Jan 17, 2018

#values.yml
namespace: defaultnamespace
secrets:
   database: defaultdatabase
   password: defaultpassword

helm install mychart --set secrets.database=mydatabase --set secrets.password=mypassword
This will only change the value for password. database will still remain with "defaultdatabase"

This is the correct way to pass two values that lie under the same node in values.yaml
helm install chartsendis --set secrets.database=mydatabase,secrets.password=mypassword

What i found out later. Calling
helm install chartsendis --set secrets.database=mydatabase,secrets.password=mypassword --set namespace=anothernamespace

doesn't work either. In this case only "namespace" is set to "anothernamespace". both values from "secrets" remain in their default values.

If this happends by design, i maybe just did not find the documentation for this. If it is missing i could help you to make it more clear in the documentation.

Greetings,
Chucky

@chucky2305 chucky2305 changed the title helm install with multiple --set parameters helm install with multiple --set parameters (maybe missing documentation) Jan 17, 2018
@jascott1
Copy link
Contributor

Hi @chucky2305

Im not sure why your first example isn't working. What version of Helm are you using?

@chucky2305
Copy link
Author

I learned that i need to write it like this:
helm install mychart --set secrets.database=mydatabase,secrets.password=mypassword

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants