A CLI tool for linting and testing Helm charts, designed for CI/CD pipelines and pull request validation.
Chart Testing is a CLI tool designed to lint and test Helm charts, primarily for use in CI/CD pipelines and pull request validation. It automatically detects which charts have changed and runs linting and installation tests to ensure they are valid and deployable. This helps maintain high-quality chart repositories and prevents broken charts from being merged.
Helm chart developers, DevOps engineers, and platform teams who manage Helm chart repositories and need automated validation in their CI/CD workflows.
Developers choose Chart Testing for its deep integration with Helm workflows, automatic change detection, and comprehensive testing capabilities that catch issues before charts are merged. Its support for Docker, flexible configuration, and private repositories makes it a robust tool for enterprise-grade chart management.
CLI tool for linting and testing Helm charts
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Identifies which Helm charts have been modified against a target branch, enabling targeted testing only on changed charts, as highlighted in the README for pull request validation.
Integrates with Yamllint and Yamale to validate chart structure, syntax, and schema compliance, providing thorough checks beyond basic Helm linting.
Supports configuration via CLI flags, environment variables, and multiple config file formats (YAML, JSON, TOML), with clear precedence rules, as detailed in the README's configuration section.
Handles authentication for private chart repositories and OCI registries through extra Helm arguments, making it suitable for enterprise environments with secure chart sources.
Requires multiple prerequisites like Helm, Git, Yamllint, Yamale, and Kubectl, and configuration files for linting, which can be cumbersome for quick adoption or simple setups.
Relies on tools like Yamllint and Yamale for linting, adding maintenance overhead and potential version compatibility issues, as noted in the prerequisites.
Specifically designed for Helm chart testing, so it lacks features for broader Kubernetes resource validation or non-Helm deployment methods, limiting its scope.
Upgrading from major versions (e.g., v1 to v2) required syntax changes in scripts, as mentioned in the README, which can disrupt existing workflows and require manual updates.