To use all features of Artifactory Helm chart repositories, including resolution of Helm charts, you must use version 2.9.0 or above of the Helm client that supports basic authenticated access to Artifactory.
Before you can use your Helm client to resolve Helm charts from Artifactory, you need to configure it for authenticated access with your Artifactory user and password by adding the virtual Helm chart repository to be used for resolution as shown below:
helm repo add <REPO_KEY> http://<ARTIFACTORY_HOST>:<ARTIFACTORY_PORT>/artifactory/<REPO_KEY> --username <USERNAME> --password <PASSWORD> helm repo update
helm repo add helm-virtual http://10.1.16.114:32775/artifactory/helm-virtual --username admin --password password helm repo update
We recommend using an encrypted password instead of clear-text. For details, please refer to Centrally Secure Passwords.
The JFrog Helm Client was necessary for authenticated access to Artifactory 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 Artifactory user and password by adding the virtual Helm chart repository to be used for resolution as shown below:
helm repo add <REPO_KEY> http://<ARTIFACTORY_HOST>:<ARTIFACTORY_PORT>/artifactory/<REPO_KEY> <USERNAME> <PASSWORD> helm repo update
helm repo add helm-virtual http://10.1.16.114:32775/artifactory/helm-virtual admin password helm repo update
To enable calculation of Helm chart metadata, set Helm to be the Package Type when you create your local repository.
Artifactory only supports resolution of Helm charts from virtual repositories.
You can create Helm remote repository to proxy and cache remote repositories or other Artifactory instances.
In order for Artifactory to properly cache Helm charts, resolve the charts only through a virtual repository.
A Virtual Repository defined in Artifactory 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 repository, 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.
Artifactory 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 Artifactory, use the following command:
helm install <REPO_KEY>/<CHART_NAME>
helm install helm-virtual/artifactory
Deploying Helm charts is done using cURL, Wget, JFrog CLI or any of the ways described in Deploying Artifacts.
To deploy Helm charts to a virtual Helm repository, make sure you have set the Default Deployment 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.
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.
<iframe width="560" height="315" src="https://www.youtube.com/embed/QbTOQsQA_LE" frameborder="0" allowfullscreen></iframe>