Using the latest version?
JFrog Container Registry Guide
Configuring the Helm Client
Download Helm client version 2.9.0 or above for authenticated access
To use all features of the JFrog Container Registry Helm Registry, including resolution of Helm charts, you must use version 2.9.0 or above of the Helm client that supports basic authenticated access to JFrog Container Registry.
Before you can use your Helm client to resolve Helm charts from JFrog Container Registry, you need to configure it for authenticated access with your JFrog Container Registry user and password by adding the virtual Helm chart repository to be used for resolution as shown below:
Use an encrypted password
We recommend using an encrypted password instead of clear-text. For details, please refer to Centrally Secure Passwords.
Using the JFrog Helm Client
JFrog Helm Client
The JFrog Helm Client was necessary for authenticated access to JFrog Container Registry before the Helm client supported basic authentication (before version 2.9.0).
If you are using the JFrog Helm Client, you need to configure it for authenticated access with your JFrog Container Registry user and password by adding the virtual Helm chart repository to be used for resolution as shown below:
Configuring Helm Repositories
To enable calculation of Helm chart metadata, set Helm to be the Package Type when you create your local repository.
Resolving Helm charts
JFrog Container Registry only supports resolution of Helm charts from virtual repositories.
You can create Helm remote repository to proxy and cache remote repositories or other JFrog Container Registry instances.
In order for JFrog Container Registry to properly cache Helm charts, resolve the charts only through a virtual repository.
A Virtual Repository defined in JFrog Container Registry aggregates packages from both local and remote repositories.
This allows you to access both locally hosted Helm charts and remote proxied Helm charts repositories from a single URL defined for the virtual repository.
To define a virtual Helm chart repository, create a Virtual Repositories, set the Package Type to be Helm, and select the underlying local and remote Helm repositories to include in the Basic settings tab.
This repository will be configured in the Helm client.
Resolving Helm Charts
Virtual Repositories Only
JFrog Container Registry only supports resolution of Helm charts from virtual Helm chart repositories. To resolve Helm charts from other local or remote Helm chart repositories, you need to aggregate them in a virtual Helm chart repository.
To resolve a Helm chart through JFrog Container Registry, use the following command:
Deploying Helm Charts
Deploying Helm charts is done using cURL, Wget, JFrog CLI or any of the ways described in Deploying Artifacts.
Setting the Default Deployment Repository
To deploy Helm charts to a virtual Helm repository, make sure you have set the Default Deployment Repository.
Reindexing a Helm Chart repository
You can trigger an asynchronous reindexing of a local Helm chart repository either through the UI or using the REST API.
Through the UI, select your Helm chart repository in the Tree Browser and select Recalculate Index from the right-click menu as shown below (requires Admin privileges).
To reindex a Helm chart repository through the REST API, please refer to Calculate Helm Chart Index
Viewing Individual Helm Chart Information
In the Tree Browser, select your virtual Helm chart repository and drill down to find and select the package you want to inspect. The metadata is displayed in the Chart Info tab.