How Helm caching works
A classic Helm repository is an index.yaml plus a set of .tgz chart packages. You register the upstream repository in your workspace under a short name, and Cacheport serves it at /helm/<name>/.
Charts stored in OCI registries are container artifacts. They go through Container Mirror with the same token.
- index.yaml
- Refreshed every 15 minutes, stale copy on failure.
- Chart packages
- Cached forever per version.
- Provenance files
- .prov files cached alongside charts for helm verify.
Set it up
Add a mirrored repository
helm repo add prometheus-community https://acme.cacheport.cc/helm/prometheus-community/ \
--username ci --password "$CACHEPORT_TOKEN"
helm repo update
helm install monitoring prometheus-community/kube-prometheus-stackKeep the repository name the same as the upstream one, so existing chart references like prometheus-community/kube-prometheus-stack keep working.
Use it in CI
Store the token as a secret named CACHEPORT_TOKEN, then pick your provider.
GitHub Actions
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: azure/setup-helm@v4
- run: |
helm repo add prometheus-community https://acme.cacheport.cc/helm/prometheus-community/ \
--username ci --password "${{ secrets.CACHEPORT_TOKEN }}"
helm dependency build charts/appMore for GitHub Actions: GitHub Actions setup guide.
GitLab CI
deploy:
image: alpine/helm:3
script:
- helm repo add prometheus-community https://acme.cacheport.cc/helm/prometheus-community/ --username ci --password "$CACHEPORT_TOKEN"
- helm dependency build charts/appMore for GitLab CI: GitLab CI setup guide.
GitOps controllers
Argo CD and Flux re-fetch chart indexes on their reconcile interval. Pointing them at Cacheport takes that recurring load off the upstream chart host and keeps deploys working if it goes away.