Set Up Remote Helm OCI Repositories

JFrog Artifactory Documentation

ft:sourceType
Paligo

Artifactory supports proxying remote Helm OCI registries through remote repositories. A Remote Repository in Artifactory serves as a caching proxy for a registry managed at a remote URL such as Helm Registry.

Resources that are requested from a remote repository are cached on demand. You can remove downloaded resources from the remote repository cache, however, you can not manually push resources to a remote repository.

To create a remote repository to proxy a remote OCI registry, follow these steps:

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

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

  3. In the Basic tab, set the Repository Key value, and specify the URL to the remote registry in the URL field.

  4. To allow Artifactory to download foreign layers to the Helm OCI remote repository, click the Advanced tab and select the Enable Foreign Layers Caching checkbox.

  5. (Optional) To match external URL when downloading from foreign layers, set include/exclude patterns. These are Ant-style expressions that allow you to specify where foreign layers may be downloaded from: supported expressions include *, **, ?.

    For example, setting the pattern **/github.com/** will allow the downloading of foreign layers only from the github.com host.

    The default setting for this field is ** ,which allows the download of foreign layers from any source.

  6. Configure the network settings. For more information, see Network Settings.

  7. Click Save and Finish.

Smart Remote Repository Path and Domain

When accessing a Smart Remote OCI repository through Artifactory, the repository URL must be prefixed with api/oci in the path:

Tip

Make sure to replace the placeholder with your JFrog domain information.

<YOUR_JFROG_DOMAIN>/artifactory/api/oci/<REPOSITORY>/v2

For example:

https://my-awesome-jfrog.io:8081/artifactory/api/oci/jfrog-oci-remote/v2