[proposal] Reuse charts between releases with OCIRepository
#789
Labels
area/api
API related issues and pull requests
area/ux
In pursuit of a delightful user experience
enhancement
New feature or request
I propose we offer an alternative solution to the current
HelmRepository
/HelmChart
APIs for users which deploy the same chart version across clusters with various values. And for users that want to use immutable charts by pinning a chart to its OCI digest.Using an
OCIRepository
would allow users to create thousands of release in an efficient manner with close to zero CPU & memory usage for source-controller. Compared to the current approach where for eachHelmRelease
, source-controller needs to parse the infamousindex.yaml
and generate a chart per release, reusing anOCIRepository
will enable running Flux at massive scale with no overhead. Even for when Helm charts and Helm repos are not reused,OCIRepository
is still more efficient, instead of having to create two objects for eachHelmRelease
, aHelmRepository
(OCI or HTTP) and aHelmChart
, users would create oneOCIRepository
, less pressure on etcd, easier to debug for users. Using anOCIRepository
means Flux no longer depends on Helm SDK for pulling charts, it would allow pinning on digests and have immutable charts.The only downside when using an
OCIRepository
is that users can no longer swap thevalues.yaml
from within a chart with a diffrent file e.g.values-production.yaml
.HelmRelease.spec.chartRef
We'll introduce an optional field for referencing a Helm chart artifact produced by an OCIRepository. Any number of
HelmReleases
could refer to the sameOCIRepository
. When theOCIRepository
detects a new chart version in the container registry, all Helm releases will be upgraded by helm-controller.Example HelmReleases that use the same chart version fetched from a container registry:
Example OCIRepository that scans the container registry for new versions and pulls the latest stable version of a chart:
Example OCIRepository that pins a chart to its immutable digest (something that Helm doesn't support):
The text was updated successfully, but these errors were encountered: