Helm Kubernetes compatibility — check your chart before release

Lint Chart.yaml before helm package: SemVer 2 version, apiVersion v2 fields, unquoted appVersion, kubeVersion ranges stuck on EOL Kubernetes, and CI files still pinned to Helm 3 (security fixes end 2026-11-11). Runs entirely in your browser — nothing is uploaded.

Same engine as the VS Code extension, byte for byte.

Get the full version $29

Team key: a dated Helm 4 readiness report (Markdown + JSON) covering every chart in the repo, plus a CI gate that fails the build on any finding.

One payment, one licence key for this tool. The key is shown right after payment.

Buy the full version — $29

Questions people ask

What does helm chart lint Chart.yaml - Helm 4 Release Gate actually do?

It reads Chart.yaml and CI YAML files and flags lines Helm will reject or misread, each with its replacement line. On the bundled sample chart it reports 6 findings from 16 rules: apiVersion v1, version v2.4 coerced to 2.4.0, unquoted appVersion 1.10 read as 1.1, kubeVersion capped below 1.35, an owner field outside the spec, and dependencies on a v1 chart.

Who is the Chart.yaml release gate for?

Platform, DevOps and SRE engineers who publish Helm charts, run an internal chart repository, or call helm package in CI. It is aimed at teams moving pipelines from Helm 3 to Helm 4, because Helm 3 bug fixes ended on 2026-07-08 and Helm 3 security fixes end on 2026-11-11, according to the Helm project.

Why not just run helm lint on the chart?

helm lint validates chart structure, but it carries no Kubernetes end-of-life calendar and no Helm 3 cut-off date, and it never reads your CI workflow files. This checker flags a kubeVersion range that only matches Kubernetes 1.34, which reaches end of life on 2026-10-27, and a setup-helm step still pinned to v3.x before 2026-11-11.

What is free and what needs the team key?

Free, with no key: all 16 rules on every Chart.yaml and CI YAML file, in VS Code and on the web page, with the replacement line for each finding. The team key, $29 once, adds a dated Helm 4 readiness report in Markdown and JSON covering every chart in the repository, plus a CI gate that fails the build on findings.

What does the alternative cost?

The alternative is an engineer reading the Helm chart documentation, the Helm 4 release notes and the Kubernetes release calendar, then walking each Chart.yaml and pipeline file by hand. The free checker does the reading in one pass and prints the replacement line for each finding. The team report is $29 once, one licence key per person or team seat.

Ask about this tool

One question, answered by the person who built it. Your email only if you want the answer sent.

Want the full version?
Enter your email and we send the download link.
ENDEJAESPT

Find a tool