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

Add --dependency-update flag to the helm upgrade command #7162

Closed
damodhar22 opened this issue Dec 5, 2019 · 14 comments · Fixed by #9659 · May be fixed by #9335
Closed

Add --dependency-update flag to the helm upgrade command #7162

damodhar22 opened this issue Dec 5, 2019 · 14 comments · Fixed by #9659 · May be fixed by #9335
Labels

Comments

@damodhar22
Copy link

Output of helm version:v3.0.0

Output of kubectl version:v1.15.0

Cloud Provider/Platform (AKS, GKE, Minikube etc.): EKS

@hickeyma
Copy link
Contributor

hickeyma commented Dec 6, 2019

@damodhar22 Can you provide more context and details on the feature you are requesting/

@damodhar22
Copy link
Author

damodhar22 commented Dec 9, 2019

@hickeyma helm install has an option --dependency-update, which can download all the dependencies
provided in Charts.yaml without explicitly running helm dep update command.

I am using the below command to both install and update helm charts
helm upgrade --install myrelease mychart
Here I had to run helm dep update command as the helm upgrade command do not have
--dependency-update option.

@hickeyma hickeyma changed the title helm upgrade command should have --dependency-update option Add --dependency-update flag to the helm upgrade command Dec 9, 2019
@DocX
Copy link

DocX commented May 18, 2020

@hickeyma I've just run to the same thing, we use helmfile which internally uses helm upgrade which causes the error on dependencies when I do not have them installed locally. It took me some time to understand it. It would be great if upgrade can accept the option to just do it internally. WDYT?

@hickeyma
Copy link
Contributor

@DocX It is an open feature if you would like to work on it.

@github-actions
Copy link

This issue has been marked as stale because it has been open for 90 days with no activity. This thread will be automatically closed in 30 days if no further activity occurs.

@janario
Copy link
Contributor

janario commented Sep 27, 2020

PR #8810

@github-actions github-actions bot removed the Stale label Sep 30, 2020
@jaksky
Copy link

jaksky commented Sep 30, 2020

Guys how do you updadate dependecies when chart is from remote repository? e.g. stable/xxx

@janario
Copy link
Contributor

janario commented Sep 30, 2020

@jaksky
When you try to package a chart to update to the remote and it has requirements that were not resolved it will complain

helm package .
Error: found in Chart.yaml, but missing in charts/ directory: mysql

helm package provides a flag to help with that

helm package --dependency-update .
Successfully packaged chart and saved it to: /home/janario/Projects/my-chart-0.0.1.tgz

so I suppose all the remote charts will always have its dependencies

@jaksky
Copy link

jaksky commented Sep 30, 2020

@janario I am new to helm but wondering as I am installing/upgrading stuff via helm upgrade --install prometheus. stable/prometheus ...
Locally I see manifests rendered correctly but latter on getting an error.

Can helm package even remote charts? I am struggling with stable/prometheus with dependant kube-state-metrics which is dependency from that chart.

@janario
Copy link
Contributor

janario commented Sep 30, 2020

@jaksky not sure but I guess it goes a bit out of the scope of this issue

Try to ask some help at slack or some other community channel

https://github.com/helm/community/blob/master/communication.md#slack

@github-actions
Copy link

This issue has been marked as stale because it has been open for 90 days with no activity. This thread will be automatically closed in 30 days if no further activity occurs.

@github-actions github-actions bot added the Stale label Dec 30, 2020
@woodcockjosh
Copy link

/re-activate

@github-actions
Copy link

github-actions bot commented Apr 1, 2021

This issue has been marked as stale because it has been open for 90 days with no activity. This thread will be automatically closed in 30 days if no further activity occurs.

@github-actions github-actions bot added the Stale label Apr 1, 2021
@janario
Copy link
Contributor

janario commented Apr 2, 2021

/remove-stale

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