Umbrella charts defined through a HelmChart and built from file trees (i.e. HelmChart objects whose value of .spec.sourceRef points to one of GitRepository or Bucket) are able to indirectly reference HelmRepository objects in the same namespace through dependency URLs. This allows the dependencies to be resolved using configuration specified in the respective HelmRepository objects, useful for example for authentication. Both types are supported: default (HTTP/S Helm repositories) and oci.
As part of our efforts to make OCIRepository the strongest and definitive choice for OCI Helm charts in Flux, we should support OCIRepository for this purpose as well. For example: proxy secret, object-level workload identity and verification are supported for Helm charts consumed via OCIRepository. The same features are not available for dependencies resolved via HelmRepository type oci. This helps us move users from HelmRepository type oci to OCIRepository.
Umbrella charts defined through a
HelmChartand built from file trees (i.e.HelmChartobjects whose value of.spec.sourceRefpoints to one ofGitRepositoryorBucket) are able to indirectly referenceHelmRepositoryobjects in the same namespace through dependency URLs. This allows the dependencies to be resolved using configuration specified in the respectiveHelmRepositoryobjects, useful for example for authentication. Both types are supported:default(HTTP/S Helm repositories) andoci.As part of our efforts to make
OCIRepositorythe strongest and definitive choice for OCI Helm charts in Flux, we should supportOCIRepositoryfor this purpose as well. For example: proxy secret, object-level workload identity and verification are supported for Helm charts consumed viaOCIRepository. The same features are not available for dependencies resolved viaHelmRepositorytypeoci. This helps us move users fromHelmRepositorytypeocitoOCIRepository.