Affects Version/s: None
Fix Version/s: None
Configure a helm-remote repository pointing to https://helm.datadoghq.com and add this to a helm-virtual repository . Now, configure the helm client to point to Artifactory.
helm repo add helm https://myart.jfrog.io/myart/helm --username amithkm --password password
Get the API key from the datadog by registering at https://app.datadoghq.com/
helm install helm/datadog --version 2.4.20 --set datadog.apiKey=4f0440ba2bf59d199287232e92ebda0c --debug
[debug] Created tunnel using local port: '51521'
[debug] SERVER: "127.0.0.1:51521"
[debug] Original chart version: "2.4.20"
[debug] Fetched helm/datadog to /Users/amithkm/.helm/cache/archive/datadog-2.4.20.tgz
[debug] CHART PATH: /Users/amithkm/.helm/cache/archive/datadog-2.4.20.tgz
Datadog agents are spinning up on each node in your cluster. After a few
minutes, you should see your agents starting in your event stream:
**truncated the output for simplicity. (gives the status of pods).
Impact or Issue:- Artifactory is not caching the actual chart in helm-remote-cache repository. The only cached item is index.yaml which contains the location of the chart in github page (
The issue same across all the versions in Artifactory 6 and 7.