-
Notifications
You must be signed in to change notification settings - Fork 23
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 of SubChart packaging for the helm input type #1007
Comments
These dependencies are usually evaluated by $ cd openstack/content-repo
$ ls charts
ls: cannot access 'charts': No such file or directory
$ helm lint . --values ci/test-values.yaml
==> Linting .
[INFO] Chart.yaml: icon is recommended
[WARNING] /x/src/github.com/sapcc/helm-charts/openstack/content-repo: chart directory is missing these dependencies: linkerd-support,owner-info
1 chart(s) linted, 0 chart(s) failed
$ helm dep build
Saving 2 charts
Downloading linkerd-support from repo oci://keppel.eu-de-1.cloud.sap/ccloud-helm
Pulled: keppel.eu-de-1.cloud.sap/ccloud-helm/linkerd-support:1.0.0
Digest: sha256:2f9ecf9ab62c1f73c15bdbd0dc0316860dd6d0c551d6b6d5d94568f2e2bd57a8
Downloading owner-info from repo oci://keppel.eu-de-1.cloud.sap/ccloud-helm
Pulled: keppel.eu-de-1.cloud.sap/ccloud-helm/owner-info:1.0.0
Digest: sha256:343ea4e433a0482cffd334f5a85d2ca9abc7ece8fd94169c4a42e7b3365ee91a
Deleting outdated charts
$ ls charts
linkerd-support-1.0.0.tgz owner-info-1.0.0.tgz
$ helm lint . --values ci/test-values.yaml
==> Linting .
[INFO] Chart.yaml: icon is recommended
1 chart(s) linted, 0 chart(s) failed So there is an option for a "cheap" solution wherein |
I double-checked what I only assumed in the previous comment: Running
The last nine files (everything below |
What would you like to be added:
So far, the helm input type allows to package a helm chart from the filesystem or any other source
as local blob resource.
To use sub charts, those sub chards must already charts described a s local sub charts be the main helm chart.
Required is the possibility to additionally describe charts, which should be packaged together with the main chart
as local sub charts.
This could be described in several ways:
the dependency information in the
Chart.yaml
contains the location f the sub charts. They are just internalized by the input.To be able to keep references, this would require an optional flag in the input spec to enable the internalization behaviour.
For the internalized charts the dependency entry has to be adapted to refer to the local representation.
The input spec makes it possible to describe a dependency list for the charts, which should be internalized.
The dependency field of the
Chart.yaml
has be extended by the specified sub chart names.In both cases the effective chart has to be prepared on a temporary filesystem by copying the main one, adding
the additional sub charts to the filesystem content and modifying the
Chart.yaml
.Why is this needed:
Requested by @majewsky
The text was updated successfully, but these errors were encountered: