ARTIFACTORY: How to Proxy Helm Chart New Relic repository using Helm Remote Repository

This article will cover the steps for creating a Remote Helm repository on your Artifactory instance to proxy the Helm Chart New Relic repository.

Step 1
Create a Remote Helm Repository, by creating a remote Helm repository using the following URL to ensure proxying from New-Relic: “https://helm-charts.newrelic.com/“.
 
Step 2
Set the “Charts Base URL” option to: “https://github.com/newrelic/helm-charts/releases/download/”.

At this point, you should have configured your remote repository similar to the screenshot below:

 
 
** When creating the remote repository using Repositories Configurations in Artifactory YAML, add the following to the YAML:

remoteRepositories:
  test-remote-helm-new-relic: #name of the repository 
    type: helm
    url: https://helm-charts.newrelic.com/
     helm:
      chartsBaseUrl: https://github.com/newrelic/helm-charts/releases/download/

Step 3
Include the Remote Repository in a Virtual Repository.

Ensure that the newly created Remote Helm repository is included in a Virtual repository.

Note: 
To ensure Artifactory properly caches Helm charts, resolve the charts only through a Virtual repository.


Step 4
Configure Helm Client with the Virtual Repository you created:

1. Add the repository to the Helm Client:
   “helm repo add <Virtual-Repository-Name> https://<ARTI_URL>/artifactory/api/helm/<Virtual-Repository-Name>”
    
2. Update the repository: “helm repo update”.
    
3. You can now search or pull from the repository, for example:

Important Note:
If the Remote or Virtual repository was used before, perform Zap Cache on Helm Remote and Virtual Repositories.


After adding the Remote repository to the Virtual repository, it's crucial to perform a Zap cache on both the Helm Remote cache and the Helm Virtual repository. This process helps eliminate any potential caching issues and ensures smooth retrieval of Helm charts during deployment.