helm-chart-developer

You can build production-grade Helm charts by following a mandatory 6-step workflow that enforces updates to values.schema.json, writes unit tests, and validates templates through helm-unittest before release.

The best way to add schema validation is updating values.schema.json within a structured development workflow that enforces strict input validation before template rendering and subsequent unit testing.

Yes, this workflow explicitly supports helm-unittest for creating CI-ready validation and real-world testing strategies. Unit tests are a mandatory step in the 6-step process before any chart release.

To secure Helm charts for production, apply security hardening practices including PodSecurityContext configuration, OCI signing, and RBAC integration. This ensures compliance and external secret integrations across complex charts.

Yes, you can use this workflow to migrate complex Helm charts to OCI registries and Helm 4. It provides specific best practices and transition patterns for migrating existing charts.

You need to update values.schema.json before writing unit tests because the 6-step workflow mandates schema validation first. This ensures all template inputs are strictly defined and validated before testing rendering logic.