Helm · Rate Limits

Helm Rate Limits

1 Limits
ChartsCloud NativeContainer OrchestrationDevOpsKubernetesPackage ManagerOpen SourceRate Limiting

Limits

Helm-Side Limits client
varies
no client-side rate limiting; Helm respects whatever ceilings the upstream chart repository or OCI registry enforces
Limits are imposed by the upstream host (e.g. Docker Hub anonymous pulls, GitHub raw download limits, Artifact Hub front-end caching) not by the Helm CLI itself.

Policies

Upstream Host Responsibility
Any 429 / 503 response observed during 'helm pull', 'helm install', or 'helm repo update' originates from the upstream chart repository or OCI registry; consult that host's documentation.
Local Caching
Helm caches the index.yaml of subscribed repositories locally; running 'helm repo update' only on demand reduces upstream pressure.
OCI Registry Authentication
Authenticated pulls from OCI registries typically receive higher rate limits than anonymous pulls; configure 'helm registry login' to leverage your account-level limits.

Sources