Training Example: Helm – Review the Data, Give Your Score & Compare to the Real AI Evaluation

[H2] What is Helm?
Helm helps you manage Kubernetes applications — Helm Charts help you define, install, and upgrade even the most complex Kubernetes application.Charts are easy to create, version, share, and publish — so start using Helm and stop the copy-and-paste.Helm is a graduated project in the CNCF and is maintained by the Helm community.
[H3] Learn more:
Helm ArchitectureQuick Start GuideVideo: An Introduction to Helm
[H2] Features
[H3] Manage Complexity
Charts describe even the most complex apps, provide repeatable application installation, and serve as a single point of authority.
[H3] Easy Updates
Take the pain out of updates with in-place upgrades and custom hooks.
[H3] Simple Sharing
Charts are easy to version, share, and host on public or private servers.
[H3] Rollbacks
Use helm rollback to roll back to an older version of a release with ease.
[H2] Getting Started
[H3] Get Helm
Install Helm with a package manager, or download a binary.HomebrewChocolateyScoopSnapbrew install helmchoco install kubernetes-helmscoop install helmsudo snap install helm --classicOnce installed, unpack the helm binary and add it to your PATH and you are good to go! Check the docs for further installation and usage instructions.
[H3] Get Charts
Visit Artifact Hub to explore Helm charts from numerous public repositories.
[IMG: Artifact Hub]
[H2] Join the Community
More information about the Helm project, and how to contribute.
[H3] Next Feature Release
v4.2.0May 2026Release Calendar
[H3] Events
Upcoming EventsMar 23 - Mar 26, 2026 - KubeCon Europe 2026Past EventsNov 10 - Nov 13, 2025 - KubeCon North America 2025Apr 1 - Apr 4, 2025 - KubeCon Europe 2025Nov 12 - Nov 15, 2024 - KubeCon North America 2024
[H3] SIG Apps
They meet each week to demo and discuss tools and projects. Community meetings are recorded and shared to YouTube.
[H3] Developer Standups
Thursdays 9:30-10am (PT)These meetings are open to all. Check the community repo for notes and details.
[H3] Slack
Request access here to join the Kubernetes Slack team.Helm UsersDiscussion around using Helm, working with charts and solving common errors.Helm DevelopmentTopics regarding Helm development, ongoing PRs, releases, etc.ChartsDiscussion for users and contributors to Helm Charts.
[H3] Contributing
Helm always welcomes new contributions to the project!
[H3] Where to begin?
Helm is a big project with a lot of users and contributors. It can be a lot to take in!We have a list of good first issues if you want to help but don't know where to start.
[H3] What do I do?
Before you contribute some code, please read our Contribution Guide. It goes over the processes around creating and reviewing pull requests.After you write some code, please sign your commits to ensure Helm adheres to the DCO agreement used by the CNCF.
[H2] Supporters
Helm is supported by and built with a community of over 400 developers.
[IMG: Bitnami logo]
[IMG: codecentric AG logo]
[IMG: Codefresh logo]
[IMG: Google logo]
[IMG: IBM logo]
[IMG: JetBrains logo]
[IMG: Microsoft logo]
[IMG: Montreal logo]
[IMG: Red Hat logo]
[IMG: Replicated logo]
[IMG: Samsung SDS logo]
[IMG: SUSE logo]
[IMG: Ticketmaster logo]
...and many other wonderful helm core maintainers.

Version: 4.2.0
Welcome to the Helm documentation. Helm is the package
manager for Kubernetes, and you can read detailed background information in the
CNCF Helm Project Journey
report.
[H2] ?️ Docs Home
Everything you need to know about how the documentation is organized.
[H2] ?️ Helm 4 Overview
Helm v4 represents a significant evolution from v3, introducing breaking changes, new architectural patterns, and enhanced functionality while maintaining backwards compatibility for charts.
[H2] ?️ Full Changelog
Scope: 443 PRs from (v4.2.0) compared to v3.19.0
[H2] ?️ Introduction
4 items
[H2] ?️ How-to
3 items
[H2] ?️ Topics
15 items
[H2] ?️ Best Practices
8 items
[H2] ?️ Chart Template Guide
16 items
[H2] ?️ Plugins
3 items
[H2] ?️ Helm Commands
59 items
[H2] ?️ Go SDK
2 items
[H2] ?️ Glossary
Terms used to describe components of Helm's architecture.

On Wednesday November 12th, during the Helm 4 presentation at KubeCon + CloudNativeCon, Helm v4.0.0 was released. This is the first new major version of Helm in 6 years.The Helm team is headed to KubeCon + CloudNativeCon NA '25 in Atlanta, Georgia next week and it's truly a special one for us! This time around, as we celebrate our 10th birthday (fun fact, Helm was launched at the first KubeCon in 2015), we will also be releasing the highly anticipated Helm 4! Join us for a series of exciting activities throughout the week -- read on for more details!Ten years ago, in a hackathon shortly after the release of Kubernetes 1.1.0, Helm was born.
commit ecad6e2ef9523a0218864ec552bbfc724f0b9d3dAuthor: Matt Butcher <mbutcher@engineyard.com>Date: Mon Oct 19 17:43:26 2015 -0600 initial addThe first Alpha for Helm v4 has been released. Now that Helm v4 development is in the home stretch, we wanted to share the details on what's happening and how the broader community can get involved.If you are installing helm with Apt, be aware that the Debian/Ubuntu Helm Apt repository is moving.It's that time of the year again – the Helm team is headed to KubeCon + CloudNativeCon EU '25 in London, UK this week from April 1 - 4! Helm 4 is in the works for later this year so be sure to join the conversation with our maintainers during our talk sessions and at our Helm booth in the Project Pavilion! See below for more details on all Helm-related activities throughout the week.Have you ever wondered what it takes to perform a software release of one of the most popular tools in the Kubernetes community? While you may envision a series of complex steps or maybe even some black magic (some of which may be true), the release process is much more organized and streamlined than you may have envisioned. However, until you see it for yourself firsthand, these types of questions will continue to go unfulfilled. Seeing it really is believing it!
[IMG: KubeCon / CloudNativeCon Logo]
Helm is going to be at KubeCon / CloudNativeCon North America in Salt Lake City. There will be something happening each day of the main conference, including:Over four years ago, we introduced Helm 3, a major evolution in Helm's development. And we announced at that time that Helm 2 would receive patches and security updates for a year. We also provided a migration path to Helm 3 from Helm 2 and a tool helm-2to3 to automate migration.We have been saying it for a while now – Helm is "stable software". That should not come as a surprise to anyone familiar with Kubernetes and the surrounding ecosystem as many within the Kubernetes community consider Helm to be the de-facto package manager. The use of Helm is far reaching: from open source community projects, to startups, to Fortune 500 organizations. Helm has become an essential component of build and deployment workflows that handle mission critical workloads.

Version: 4.2.0On this page
Helm v4 represents a significant evolution from v3, introducing breaking changes, new architectural patterns, and enhanced functionality while maintaining backwards compatibility for charts.
For more information about the planned Helm 4 release phases, see Path to Helm v4.
[H2] What's New​
This section provides an overview of what's new in Helm 4, including breaking changes, major new features, and other improvements. For complete technical details, see the Full Changelog.
[H3] Summary​
New features: Wasm-based plugins, kstatus watcher, OCI digest support, multi-doc values, JSON arguments
Architecture changes: Plugin system completely redesigned, package restructuring, CLI flag renaming, move to versioned packages, chart v3 support, content-based caching
Modernization: slog migration, Go 1.24 update, dependency cleanup
Security: Enhanced OCI/registry support, TLS improvements
[H3] Breaking Changes​
[H4] Post-renderers implemented as plugins​
Post-renderers are implemented as plugins. With this change, it is no longer possible to pass an executable directly to helm render --post-renderer, but a plugin name must be passed. This might require updates to any existing post-renderer workflows.
[H4] Registry login does not accept full URLs​
The helm registry login command must be done with the domain name only in v4.
This is so login can be scoped at different levels on a registry in the future.
[H3] New Features​
[H4] Plugin System Overhaul​
Helm 4 introduces an optional WebAssembly-based runtime for enhanced security and expanded capabilities. Existing plugins continue to work, but the new runtime opens up more of Helm's core behavior for plugin customization. Helm 4 launches with three plugin types: CLI plugins, getter plugins, and post-renderer plugins, plus a system that enables new plugin types for customizing additional core functionality. See HIP-0026 plugin system and Helm 4 example plugins.
tipExisting plugins work as before. The new WebAssembly runtime is optional but recommended for enhanced security.
[H4] Better resource monitoring​
New kstatus integration shows detailed status of your deployments. Test with complex applications to see if it catches issues better.
[H4] Enhanced OCI Support​
Install charts by digest for better supply chain security. For example, helm install myapp oci://registry.example.com/charts/app@sha256:abc123.... Charts with non-matching digests are not installed.
[H4] Multi-Document Values​
Split complex values across multiple YAML files. Perfect for testing different environment configs.
[H4] Server-Side Apply​
Better conflict resolution when multiple tools manage the same resources. Test in environments with operators or other controllers.
Helm 4 will default to server-side apply when installing a new Chart release.
When upgrading (or rolling back), Helm will by default follow the previous apply method of the release.
This latching behavior is done to ensure continuity of operation for existing releases that used client-side apply.
The behavior can be overridden by setting the --server-side flag explicitly.
As such, all releases created by Helm 3 will default to using client-side apply after upgrading to Helm 4.
[H4] Custom Template Functions​
Extend Helm's templating with your own functions through plugins. Great for organization-specific templating needs.
[H4] Post-Renderers as Plugins​
Post-renderers are implemented as plugins, providing better integration and more capabilities.
[H4] Stable SDK API​
API breaking changes are now complete. Test it, break it, give us feedback! The API also enables additional chart versions, opening possibilities for new features in the upcoming Charts v3.
[H4] Charts v3​
Coming soon. v2 charts continue to work unchanged.
[H3] Improvements​
[H4] Performance​
Faster dependency resolution and new content-based chart caching.
[H4] Error Messages​
Clearer, more helpful error output.
[H4] Registry Authentication​
Better OAuth and token support for private registries.
[H4] CLI Flags renamed​
Some common CLI flags are renamed to better clarify their operation.
The existing flags remain, but emit a deprecated warning:
--atomic → --rollback-on-failure
--force → --force-replace
Update any automation that uses these renamed CLI flags.
[H4] CLI Flags deprecated​
The following flags for helm template are deprecated and will be removed in Helm 5:
--hide-notes
--render-subchart-notes
These flags have no effect because template output never includes notes. They remain in Helm 4 for backwards compatibility but are hidden from help output.
[H2] Upgrading to Helm 4​
While we work hard to make Helm 4 rock-solid for everyone, Helm 4 is brand new. To that end, before upgrading, we've added some tips below for specific things to look out for when testing Helm 4 with your existing workflows. As always, we welcome all feedback about what works, what breaks, and what could be better.
[H3] High Priority​
Test your existing charts and releases to verify that they still work with v4.
Test all 3 plugin types (CLI, getter, post-renderer).
Try building WebAssembly plugins with the new runtime (see example plugins)
SDK users: test the now-stable API. Try to break it and share your feedback.
Test your CI/CD pipelines and fix any script errors from the renamed CLI flags.
Test your post-renderer integrations.
Test registry authentication and chart installation in your OCI workflows.
[H3] Other​
Test other new features, including multi-document values, digest-based installs, and custom template functions.
Test the performance of Helm 4 with large, complex charts to see if it is noticeably faster for your workloads.
Try breaking things intentionally to see if the updated error messages are helpful.
[H3] Feedback​
What other plugin types would you like to see added to customize Helm core functionality?
With the API supporting additional chart versions, what new features would you want in Charts v3?
[H2] How to Give Feedback​
Find issues? Have suggestions? We want to hear from you before the November release:
[H3] GitHub Issues​
Review the list of open issues and feature requests in the Helm repo. Add comments on the existing items, or create new issues and requests.
[H3] Community Slack​
Join Kubernetes Slack channels:
#helm-dev for development discussions
#helm-users for user support and testing feedback
[H3] Weekly Dev Meetings​
Join live discussion with maintainers every Thursday 9:30am PT on Zoom.
For more options, see the Helm community communication details.What's NewSummaryBreaking ChangesNew FeaturesImprovementsUpgrading to Helm 4High PriorityOtherFeedbackHow to Give FeedbackGitHub IssuesCommunity SlackWeekly Dev Meetings