Set Up Virtual Helm OCI Repositories

JFrog Artifactory Documentation

ft:sourceType
Paligo

Artifactory supports virtual Helm OCI Repositories. A Virtual Repository aggregates images from both local and remote repositories that are included in the virtual repositories. This allows you to access images that are hosted locally on local Helm OCI repositories, as well as remote images that are proxied by remote Helm OCI repositories, and access all of them from a single URL defined for the virtual repository.

Virtual repositories can be very useful since users will continue to work with the virtual repository while the admin can manage the included repositories, and replace the default deployment target, while the changes will be transparent to the users.

To create a virtual Helm OCI repository:

  1. From the Administration module, select Repositories | Repositories | Virtual.

  2. Click New Virtual Repository and select Helm from the Select Package Type dialog.

  3. Set the Repository Key value.

  4. Select the underlying local and remote Helm OCI repositories to include under the Repositories section.

  5. (Optional) Configure your Default Deployment Repository, where the images you upload to this virtual repository will be routed. Once you configure this repository, your Helm OCI repository will be fully fledged.

    Use Virtual Repositories to Represent Your Pipeline

    You can also set up your virtual repository to wrap a series of repositories representing the stages of your development pipeline, and then use them to promote resources from the default deployment repository through the pipeline to production.

    All of the repositories representing pipeline stages can also be configured with different access permissions, to tailor the pipeline to your needs.