chart-tests

To write pytest tests for Helm charts, use the repository's render_chart() utility to validate template rendering and check values against Kubernetes OpenAPI schemas. This approach replaces the unsupported helm unittest plugin with standardized, reusable test patterns.

To override sub-chart values correctly in a Helm chart test, nest your values under the correct sub-chart keys. Following clear nesting rules for both top-level and nested sub-charts prevents common override errors during template rendering.

The best way to validate Helm chart security contexts is to write cross-cutting invariant tests. These tests validate requirements across all rendered cluster objects to prevent admission controller rejections from missing security or probe configurations.

The helm unittest plugin is unsupported for testing Astronomer Private Cloud deployments. Instead, use standardized pytest patterns with the repository's render_chart() utility to reliably author and run Helm chart tests.

To parametrize Helm chart tests for multiple Kubernetes versions, write parametrized tests that validate rendering across all supported versions. This ensures your new component renders correctly and meets required security and probe constraints consistently.

Helm chart deployments fail admission controller checks when rendered objects lack mandatory security contexts or probe configurations. Write cross-cutting invariant tests to validate these requirements across all cluster objects before deployment.