-
Notifications
You must be signed in to change notification settings - Fork 7k
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
Support Extras #7077
Labels
Comments
@michelleN Here is the other scenario I brought up at the KubeCon table last week. Mind pulling in the right folks to noodle on this one as well? |
potentially related: #5276 |
Hi, @zendril - I'm closing this issue because we now have a recommended path forward for proposals: if you'd like to formally propose this idea, please file a Helm Improvement Proposal to discuss it with the community. Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature Request: Ability to provide a template to add extra functionality to a chart.
Scenario: I pull a vendor chart and a feature isn't supported. For example, we might run additional deployments or a different ingress.
These are usually things that are extra and bespoke to our running of this chart.
Similar to #7076 except that usually means a small modification to the templates of the vendor chart, mostly until those changes get merged upstream. In this case, it is adding completely new functionality, but is driven by the same values.yaml in most cases (otherwise we would just create another chart for these).
Currently I have a folder called /manifest/extras that is in the same structure as the chart, I run a helm fetch, copy the extras on top and then run helm template.
The goal of this issue is to have the discussion about options for accomplishing this in a supported or well known paradigm.
The text was updated successfully, but these errors were encountered: