Helm 3.3: OCI-Powered Charts and Safer Releases
K8s Guru
2 min read

Table of Contents
Introduction
Helm 3.3, released on August 13, 2020, keeps the momentum after Helm 3 GA. OCI registry support, atomic install flags, and repo deprecation guidance reshape how teams package and ship Kubernetes applications.
OCI Registry Support (Experimental)
helm registry loginandhelm chart pushlet teams publish charts to Docker-compatible registries like Harbor, ECR, and GCR.- OCI artifacts include provenance metadata, making supply chain verification simpler.
- Chart pulling respects registry authentication and caching, aligning charts with container workflows.
Safer Deployments
--atomicflag now applies tohelm installandhelm upgrade, rolling back automatically on failure.--timeoutdefaults improved accuracy, preventing hung releases during slow hooks.- Release histories gain revision digests, helping auditors verify which chart rendered a given release.
Repository Modernization
- The project officially deprecates the
stable/andincubator/repos, encouraging teams to host curated charts elsewhere. helm repo addemits warnings with links to the Artifact Hub directory for discovery.- New
helm search hubcommand surfaces both official and community charts with metadata.
Getting Started
helm registry login ghcr.io -u USERNAME
helm chart save ./charts/api ghcr.io/org/api-chart:1.2.0
helm chart push ghcr.io/org/api-chart:1.2.0
Install with atomic safety:
helm upgrade --install api ghcr.io/org/api-chart:1.2.0 --atomic --wait
Summary
| Aspect | Details |
|---|---|
| Release Date | August 13, 2020 |
| Headline Features | OCI registry support, atomic installs, repo modernization |
| Why it Matters | Aligns Helm with modern artifact workflows while hardening release reliability |
Helm 3.3 helps platform teams standardize chart distribution, reducing friction between app developers and release engineers.