Is this Feature/Enhancement related to an Existing Problem? If so, please describe:
-
Yes, when adding helm-charts to the store two issues are present. 1. there is no customization allowed for the default namespace hauler. and 2. there is no customization allowed for chart names.
-
This causes issues with charts simply named crd or tenant this will cause clashes in the store locally on disk but also in the target registry. It will also not allow me to customize where i push the charts but always have the /hauler/some-chart:some-version in the path.
Describe Proposed Solution(s):
- Allow override of chart-name and namespace/project when storing the helm chart to the local helm-chart store
Describe Possible Alternatives:
Additional Context:
- I can't push where I want. I can't de-conflict charts named the same thing ie
crd what chart crd?
Is this Feature/Enhancement related to an Existing Problem? If so, please describe:
Yes, when adding helm-charts to the store two issues are present. 1. there is no customization allowed for the default namespace
hauler. and 2. there is no customization allowed for chart names.This causes issues with charts simply named
crdortenantthis will cause clashes in the store locally on disk but also in the target registry. It will also not allow me to customize where i push the charts but always have the/hauler/some-chart:some-versionin the path.Describe Proposed Solution(s):
Describe Possible Alternatives:
Additional Context:
crdwhat chart crd?