After creating these repositories, let’s set up the Helm client to interact with the virtual repository. You can use the handy “Set Me Up” instructions in the UI:
After the repository has been added, run a “helm repo update” for the virtual repository that was just added:
helm repo update helm-legacy-virtual
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "helm-legacy-virtual" chart repository
Update Complete. ⎈Happy Helming!⎈
After performing this update, you should see the upstream local repository’s artifacts in the UI:
If we look at the index.yaml for “helm-legacy-virtual”, we will see the URL of this Artifactory as opposed to the URL of the upstream Artifactory. This is due to selecting “Enable Dependency Rewrite” in Step 1. If the URL in the index.yaml still matches the upstream artifactory’s URL, try performing “Zap Caches” on the virtual repository, followed by a “helm repo update”. You can read more about zapping caches here.
At this point, you can try pulling a helm chart from the virtual repository. In this example, the upstream has only one chart, postgresql, which I’ll pull here:
helm pull helm-legacy-virtual/postgresql
After pulling this chart, you should also notice that this chart appears in the smart remote’s cache:
If you’d like to set up a smart remote repository that points to an upstream remote repository, the steps are identical to these. Remember to point the smart-remote repository directly to the upstream remote repository and not an upstream virtual repository.
Happy Helming!
After the repository has been added, run a “helm repo update” for the virtual repository that was just added:
helm repo update helm-legacy-virtual
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "helm-legacy-virtual" chart repository
Update Complete. ⎈Happy Helming!⎈
After performing this update, you should see the upstream local repository’s artifacts in the UI:
If we look at the index.yaml for “helm-legacy-virtual”, we will see the URL of this Artifactory as opposed to the URL of the upstream Artifactory. This is due to selecting “Enable Dependency Rewrite” in Step 1. If the URL in the index.yaml still matches the upstream artifactory’s URL, try performing “Zap Caches” on the virtual repository, followed by a “helm repo update”. You can read more about zapping caches here.
At this point, you can try pulling a helm chart from the virtual repository. In this example, the upstream has only one chart, postgresql, which I’ll pull here:
helm pull helm-legacy-virtual/postgresql
After pulling this chart, you should also notice that this chart appears in the smart remote’s cache:
If you’d like to set up a smart remote repository that points to an upstream remote repository, the steps are identical to these. Remember to point the smart-remote repository directly to the upstream remote repository and not an upstream virtual repository.
Happy Helming!