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

Reproducible chart dependency archives #8850

Closed
MOZGIII opened this issue Oct 5, 2020 · 4 comments
Closed

Reproducible chart dependency archives #8850

MOZGIII opened this issue Oct 5, 2020 · 4 comments
Labels
bug Categorizes issue or PR as related to a bug.

Comments

@MOZGIII
Copy link

MOZGIII commented Oct 5, 2020

Currently (as of 3.3.4), helm dependency build doesn't produce reproducible .tgz archives at charts/ dir.

We're using file:// only dependencies, and expect two runs of the helm dependency build to generate the same charts/*.tgz files, however the sha256 sums are different.

This prevents us from using git lfs to store the charts/*.tgz dir.

@bacongobbler
Copy link
Member

This may be a symptom of #3612 as helm dependency build calls the same APIs as helm package to package the file::// dependencies.

@bacongobbler bacongobbler added the bug Categorizes issue or PR as related to a bug. label Oct 5, 2020
@MOZGIII
Copy link
Author

MOZGIII commented Oct 5, 2020

Sounds very much like it.

I'm thinking about a workaround - if we copy-over/symlink the contents of the file:// dependencies to charts/, unarchived - this should allow us to both omit the lfs and work around this issue.

Does this sound like a good idea? Any hidden issues with this approach?

@mattfarina
Copy link
Collaborator

If someone wants to fix this issue... we would be happy to look at it.

@bacongobbler
Copy link
Member

I'm thinking about a workaround - if we copy-over/symlink the contents of the file:// dependencies to charts/, unarchived - this should allow us to both omit the lfs and work around this issue.

Does this sound like a good idea? Any hidden issues with this approach?

I don't see any issues with that approach. The charts do not have to be in archived form to be used. Let us know what you find out.

Closing this issue as a duplicate of #3612, as the symptoms and the solution is identical.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

3 participants