Login Contact Us Book a Demo

HELM CHARTS PACKAGE SUPPORT

Secure and Scalable Management of Helm Charts Across Your Organization

Ensure your Kubernetes applications stay compliant, controlled, and ready for rapid delivery. At Sonatype, we know how critical it is to have full visibility and control over your Helm charts, the package manager for Kubernetes, designed to simplify the installation and upgrade of even the most complex Kubernetes applications. With native support for Helm in Sonatype Nexus Repository, you can confidently manage and secure your Helm charts at enterprise scale.

Header-LR-Gray-(RIGHT)
Header-LR-Gray-(LEFT)

 

Understanding Helm Charts and the Role of Sonatype in Kubernetes Builds

Helm is the de facto package manager for Kubernetes, using “charts” as versioned bundles of Kubernetes resources, such as templates, values, and dependencies. By integrating Helm chart support into Nexus Repository, you gain a unified platform to host, proxy, manage and secure your Helm repositories and charts alongside your other package formats — giving you consistent governance, visibility and automation.

Supported Features

Hosted Repository

Create a dedicated Helm charts repository in Nexus Repository to store your packaged charts, values files, and provenance.

Proxy Repository

Proxy remote Helm or partner charts to speed access, cut duplication, and enforce policies.

Chart Versioning

Manage versioned chart packages and auto-generate the index.yaml, ensuring users retrieve correct, secure versions.

Access Control

Apply role-based access, audit logs, and chart signing to control who can publish or use Helm packages in your ecosystem.

CI/CD Pipeline Integration

Integrate your Helm charts repository with your pipelines for reproducible, version-controlled, and traceable releases.

Ecosystem Consolidation

Manage Helm charts, Docker images, and Maven packages in one Nexus Repository instance, simplifying tooling, governance, and visibility.

What You Can Do with Helm Chart Support

Managing your Helm repositories effectively delivers measurable results across security, speed, and scalability. Strong Helm chart governance drives better Kubernetes outcomes.

  • Reduce Deployment Risk

    Centralizing Helm charts in a controlled repository and enforcing provenance/signing limits unauthorized or vulnerable chart usage, boosting Kubernetes deployment reliability.

  • Improve Developer Productivity

    With a single, trusted Helm charts repo and integrated pipeline tooling, developers spend less time managing charts and more time delivering value.

  • Gain Enterprise-Grade Governance at Scale

    Scaling Kubernetes means more clusters, teams, and services. A standard Helm charts repository with access controls, audit trails, and version management provides the control for smooth scaling.

Take Control of Kubernetes Builds

Book a Demo

Resources

Helm Charts + Nexus Repository

See Documentation

Sonatype Helm Charts on GitHub

Get Started

Explore Helm Chart Repositories Support

See Blog

Frequently Asked Questions

Why manage Helm charts in a private repository instead of using public ones? 

Hosting your own Helm charts repository gives you full control over versioning, security (signing, provenance), access restrictions, and availability even if public repositories change or disappear.

Can the same repository support both Helm v2 and Helm v3 charts? 

Many repository managers (including Nexus Repository) support both Helm v2 and Helm v3 formats, but since Helm v2 is now deprecated, you should prefer Helm v3 and plan migration.

How does this fit into CI/CD workflows? 

After packaging a chart and publishing it to your Helm charts repository, your CI/CD pipeline can pull the chart from the repository, deploy it to Kubernetes (via Helm install or Helm upgrade), and trace back the exact version used — enabling consistent, automated releases.