For charts like Istio and Longhorn today, we have multiple release lines that need to be maintained for a given package in a single branch.
Currently, the workaround is to keep the chart name the same and create a brand new package to track the separate release line. e.g.
assets/longhorn-1.1 tracks the 1.1.x release line
assets/longhorn-1.2 tracks the 1.2.x release line
but because both are named longhorn internally, the index.yaml has them as the same chart (since it is indexed by chart name, not package name).
Instead, we should be able to have something like packages/longhorn/1.1/* and packages/longhorn/1.2/* which allows each of those directories to output a chart that is all stored under assets/longhorn instead.
For charts like Istio and Longhorn today, we have multiple release lines that need to be maintained for a given package in a single branch.
Currently, the workaround is to keep the chart name the same and create a brand new package to track the separate release line. e.g.
assets/longhorn-1.1tracks the 1.1.x release lineassets/longhorn-1.2tracks the 1.2.x release linebut because both are named longhorn internally, the index.yaml has them as the same chart (since it is indexed by chart name, not package name).
Instead, we should be able to have something like
packages/longhorn/1.1/*andpackages/longhorn/1.2/*which allows each of those directories to output a chart that is all stored underassets/longhorninstead.Epic Issue: https://github.com/rancher/charts-build-scripts/issues/60