JSONToTable

Loading Helm Chart Validator...

How to Validate Helm Charts - Step by Step Guide

Step 1

Prepare Your Chart.yaml File

Locate your Chart.yaml file in your Helm chart directory. This file contains metadata about your chart including name, version, and dependencies. Copy the contents of the file to validate it.

•
Required fields: apiVersion, name, and version must be present in Chart.yaml
•
Helm 3: Use apiVersion: v2 for Helm 3 charts
•
Try the sample: Click "Sample" to see a properly formatted Chart.yaml

Example: Helm Chart.yaml File

Here's what a typical Chart.yaml file looks like:

apiVersion: v2
name: myapp
description: A Helm chart for Kubernetes
type: application
version: 1.0.0
appVersion: "1.0"
maintainers:
  - name: John Doe
    email: [email protected]
Step 2

Automatic Validation

Paste your Chart.yaml content into the editor. The validator automatically checks for YAML syntax errors, missing required fields, invalid values, and compliance with Helm best practices. Validation happens in real-time as you type.

•
Schema validation: Ensures all required fields are present and correctly formatted
•
Version check: Validates semantic versioning format (MAJOR.MINOR.PATCH)
•
Dependencies: Checks that all dependencies have required fields

Example: Common Validation Issues

The validator catches typical errors:

Missing required field: apiVersion

Chart.yaml must specify an apiVersion (v1 or v2).

Invalid version format

Version must follow semantic versioning (e.g., 1.0.0, not 1.0).

Missing description field

Adding a description helps users understand your chart's purpose.

Step 3

Review Errors, Warnings & Suggestions

The validator categorizes feedback to help you fix issues efficiently. Review the results panel to understand what needs attention before packaging your chart.

•
Errors (red): Critical issues that must be fixed before deploying
•
Warnings (yellow): Best practice violations that should be addressed
•
Suggestions (gray): Optional improvements for chart quality and discoverability

Example: Validation Results

The validator provides clear feedback:

✓ Chart.yaml is Valid!
All required fields present. Your chart is ready to package.
⚠ Warning
No maintainers specified. Add maintainer contact information.
Suggestions
Add keywords to improve chart discoverability on Artifact Hub.
Step 4

Download and Package Chart

Once validation passes, download your corrected Chart.yaml file. Save it back to your chart directory, then package and deploy using helm package and helm install commands.

•
Test packaging: Run helm lint . to verify your entire chart
•
Version control: Commit your validated Chart.yaml to git
•
Ready to publish: Your chart is now ready for Artifact Hub or private registries

Example: Package and Deploy Your Chart

After validation, package and deploy your Helm chart:

# Lint the entire chart
$ helm lint ./myapp
==> Linting myapp
1 chart(s) linted, 0 chart(s) failed

# Package the chart
$ helm package ./myapp
Successfully packaged chart and saved it to: myapp-1.0.0.tgz

# Install the chart
$ helm install myapp-release ./myapp-1.0.0.tgz
NAME: myapp-release
STATUS: deployed

Frequently Asked Questions

What fields are required in a Chart.yaml file?

Every Chart.yaml must include apiVersion (v1 or v2), name, and version. For Helm 3 charts, use apiVersion v2. Additional recommended fields include description, type (application or library), maintainers, and keywords for better discoverability.

What's the difference between Helm 2 and Helm 3 Chart.yaml?

Helm 2 charts use apiVersion: v1, while Helm 3 charts use apiVersion: v2. Helm 3 introduces the type field (application or library) and the dependencies field (replacing requirements.yaml). Helm 3 also has stricter validation rules.

How do I fix semantic versioning errors?

Chart versions must follow semantic versioning (SemVer) format: MAJOR.MINOR.PATCH (e.g., 1.0.0, 2.3.1). Versions like "1.0" or "v1.0.0" are invalid. The validator will flag these and you should update to proper format like "1.0.0". Each number represents major changes, minor features, and patches respectively.

Can I validate Chart.yaml without the full Helm chart?

Yes! This validator specifically checks only the Chart.yaml file, so you don't need templates, values.yaml, or other chart files. It's perfect for quick validation during development or when creating a new chart. For full chart validation including templates, use helm lint locally or check out the official Helm lint documentation.

What are chart dependencies and how do I validate them?

In Helm 3 charts (apiVersion: v2), dependencies are listed directly in Chart.yaml under the dependencies field. Each dependency must have name, version, and repository fields. The validator checks that all dependency entries are properly formatted and have required fields. Learn more about chart dependencies. You can also use our Helm to Kubernetes converter to see the rendered output.

Is this validator the same as helm lint?

No, this validator focuses specifically on Chart.yaml file validation, while helm lint validates your entire chart including templates, values, and dependencies. Use this validator for quick Chart.yaml checks during development, then run helm lint to validate your complete chart before packaging.

Is the Helm Chart validator free to use?

Yes, completely free with no limitations! Validate unlimited Chart.yaml files, no registration required. Perfect for developers, DevOps teams, and anyone working with Helm charts.

Related Tools

Docker Compose to Kubernetes

Convert Docker Compose files to Kubernetes manifests with Deployments, Services, and PVCs

Kubernetes to Docker Compose

Convert Kubernetes manifests to Docker Compose format for local development

Docker Compose to Helm

Generate complete Helm charts from Docker Compose files with templates and values

Kubernetes to Helm Chart

Generate Helm charts from Kubernetes manifests with Chart.yaml, values.yaml, and templates

Helm to Kubernetes

Convert Helm charts to plain Kubernetes manifests by rendering templates with values

Kustomize to Helm

Convert Kustomize configurations to Helm charts with templates and values