Skip to content

Add CI Workflow for Helm Chart Linting & Testing #20

@MAVRICK-1

Description

@MAVRICK-1

Description

The repository currently has only one GitHub Actions workflow (release.yaml), which is manually triggered and only handles chart packaging and publishing to GitHub Pages. There is no automated CI pipeline that validates chart changes on pull requests.

Any PR that modifies values.yaml, templates, or subcharts is merged without any automated validation, which means broken charts could be released undetected.

What's Missing

  • No helm lint on pull requests
  • No helm template rendering validation
  • No chart-testing (ct lint) to catch schema or values issues
  • No CI triggered on push or pull_request events
  • No test coverage for custom values overrides

Why This Is Needed

Without a CI workflow:

  • Broken templates can be merged and released silently
  • Contributors have no automated feedback on their PRs
  • Chart correctness relies entirely on manual review
  • Regressions in values.yaml or templates go unnoticed until release

Proposed Solution

Add a CI workflow at .github/workflows/ci.yaml triggered on pull requests and pushes to main, that runs the following steps:

  1. helm lint — validates chart structure and values schema
  2. helm template — verifies all templates render without errors
  3. ct lint (via helm/chart-testing-action) catches values/schema inconsistencies
  4. (Optional) ct install with a kind cluster end-to-end install validation

References

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions