: By default, helm pull downloads the .tgz archive into your current working directory .

: You can override any default path by setting the HELM_CACHE_HOME or HELM_CONFIG_HOME environment variables in your shell profile.

If you need to download a chart to modify its values.yaml or use it offline, you should use the helm pull (formerly helm fetch ) command.

Whether you are troubleshooting a failed deployment or preparing for an air-gapped installation, knowing your is vital. Helm uses several different directories depending on whether you are simply caching repository metadata or explicitly pulling a chart for local inspection. 1. Default Local Cache Locations

: If you want to see the files immediately without manually unzipping, add the --untar flag. This creates a folder named after the chart in your current directory. 3. Remote Chart Repositories

: If you can't find a chart you just installed, remember that helm install often pulls the chart into a temporary memory buffer or a system temp folder before deploying it to the cluster; it may not leave a permanent file on your disk unless you use helm pull .

Modern Helm versions (3.7+) also support OCI registries (like Docker Hub, GitHub Packages, or Azure Container Registry). When pulling from these, charts are stored as OCI artifacts. You can manage these local OCI references using the Helm Registry commands. Troubleshooting Tips

Major public charts are often indexed on Artifact Hub , which serves as a centralized search engine for finding the original repository URLs of thousands of community charts. 4. Advanced: OCI Registry Storage