-
Notifications
You must be signed in to change notification settings - Fork 164
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
Use existing HelmChart resource in a HelmRelease #204
Comments
Is your wish to share a chart within the same namespace, or across namespaces? |
probably both, but at first within the same namespace |
@hiddeco If this is being taken, would like to pick this one up |
Before you start working on this, I would really like to see an outline of the planned and/or proposed changes to the |
Any update for this issue? I would like to enhance this issue~~ |
Hello ! |
This is in the pipeline to be addressed in combination with #789. You can expect it to become available in next-next minor, or if you are really lucky, next minor scheduled for December. |
Each HelmRelease automatically creates a corresponding HelmChart object and it looks like a separate tarball gets downloaded for each HelmChart object. This seems like an inefficient use of storage if multiple HelmReleases use the same chart & version because multiple identical tarballs are being downloaded.
Is there a way to manually create a shared HelmChart object and reference it from multiple HelmReleases?
The text was updated successfully, but these errors were encountered: