Skip to content

Support OCI artifact for the helm charts #1817

@cthtrifork

Description

@cthtrifork

Is your feature request related to a problem? Please describe.
I prefer installing helmcharts through
https://fluxcd.io/flux/components/source/ocirepositories/

There is a trend of storing helm charts as OCI artifacts.

Storing Helm charts in OCI registries alongside container images offers several advantages:

  • Signed charts — All charts are signed with cosign for verification
  • Simpler setup — No repository configuration needed
  • Digest pinning — Reference exact chart versions by SHA for reproducibility
  • Unified tooling — Use the same registry infrastructure for images and charts

Describe the solution you'd like
So we would need something like:

helm registry login ghcr.io -u ${{ github.actor }} -p ${{ secrets.GITHUB_TOKEN }}
echo "PACKAGE_PATH=$(helm package . | awk '{print $NF}')" >> $GITHUB_ENV
helm push ${{ env.PACKAGE_PATH }} oci://ghcr.io/$GITHUB_REPOSITORY_OWNER

to ensure its on ghcr.io.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
What’s important to note is that the an OCIRepository can be reused across multiple HelmRelease resources, which is useful when deploying multiple microservices using the generic Helm chart.

I dont mind implementing this, if there is support

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementAdding additional functionality or improvementspinnedPrevents stalebot from removingpriority: couldFuture work depending on bandwidth and availability

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions