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

Dependencies not handled in local helm charts #702

Open
Tracked by #2823
frank-bee opened this issue Aug 12, 2019 · 2 comments
Open
Tracked by #2823

Dependencies not handled in local helm charts #702

frank-bee opened this issue Aug 12, 2019 · 2 comments
Labels
area/helm customer/feedback Feedback from customers kind/bug Some behavior is incorrect or out of spec mro2 Monica's list of 2st tier overlay related issues

Comments

@frank-bee
Copy link

For local helm charts dependency update should be called before rendering them with helm template to resolve dependencies in requirements.yaml

@frank-bee frank-bee changed the title Dependencies not handled fully in local helm charts Dependencies not handled in local helm charts Aug 12, 2019
@lblackstone lblackstone self-assigned this Aug 12, 2019
@lblackstone lblackstone added area/helm customer/feedback Feedback from customers kind/bug Some behavior is incorrect or out of spec labels Aug 12, 2019
@jessebye
Copy link

We are seeing this problem as well, using the latest k8s.helm.v3.Release. We set dependencyUpdate: true but it doesn't appear to run a helm dep up prior to the templating, so it fails.

@mnlumi mnlumi added the mro2 Monica's list of 2st tier overlay related issues label Mar 28, 2023
@lblackstone lblackstone removed their assignment Jul 14, 2023
@EronWright
Copy link
Contributor

EronWright commented May 14, 2024

I haven't been able to repro the issue, if anyone has some repro steps, I'd appreciate it.

Let me share a detail that might bear on this. The helm dependency update command negotiates new versions for the dependencies (upgrading them based on the version constraints). Meanwhile, helm install --dependency-update updates the dependencies if they are missing. Pulumi's Release resource likewise updates conditionally. Maybe the update logic isn't being triggered for whatever reason. Do people expect that dependencyUpdate: true will always update the dependencies?

Also, it seems to me that helm dependency build is the ideal command to run, at least if a lockfile exists.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/helm customer/feedback Feedback from customers kind/bug Some behavior is incorrect or out of spec mro2 Monica's list of 2st tier overlay related issues
Projects
None yet
Development

No branches or pull requests

5 participants