helm-validator
Scannednpx machina-cli add skill pantheon-org/tekhne/validator --openclawHelm Chart Validator & Analysis Toolkit
Overview
This skill provides a comprehensive validation and analysis workflow for Helm charts, combining Helm-native linting, template rendering, YAML validation, schema validation, CRD documentation lookup, and security best practices checking.
IMPORTANT: This is a READ-ONLY validator. It analyzes charts and proposes improvements but does NOT modify any files. All proposed changes are listed in the final summary for the user to review and apply manually or via the helm-generator skill.
Validation & Testing Workflow
Follow this sequential workflow. Each stage catches different types of issues.
Stage 1: Tool Check
bash scripts/setup_tools.sh
Required: helm (v3+), yamllint, kubeconform, kubectl (optional). If tools are missing, provide installation instructions and ask the user before proceeding.
Stage 2: Chart Structure Validation
bash scripts/validate_chart_structure.sh <chart-directory>
Validates required files (Chart.yaml, values.yaml, templates/) and recommended files (_helpers.tpl, NOTES.txt, .helmignore).
Stage 3: Helm Lint
helm lint <chart-directory> --strict
# Optional: --values <file>, --set key=value, --debug
Stage 4: Template Rendering
helm template <release-name> <chart-directory> \
--values <values-file> \
--debug \
--output-dir ./rendered
Useful flags: --validate, --include-crds, --is-upgrade, --kube-version 1.28.0, --show-only templates/<file>.yaml.
Stage 5: YAML Syntax Validation
yamllint -c assets/.yamllint ./rendered/*.yaml
Fix template-generated YAML issues in the source template — not the rendered output.
Stage 6: CRD Detection and Documentation Lookup
bash scripts/detect_crd_wrapper.sh <chart-directory>/crds/*.yaml
bash scripts/detect_crd_wrapper.sh ./rendered/*.yaml
Output:
[{"kind": "Certificate", "apiVersion": "cert-manager.io/v1", "group": "cert-manager.io", "version": "v1", "isCRD": true}]
For each detected CRD:
-
Try context7 MCP first (preferred):
mcp__context7__resolve-library-idwith the CRD project name (e.g."cert-manager")mcp__context7__get-library-docswith the resolved ID, topic (e.g."Certificate spec"), tokens: 5000
-
Fallback to WebSearch:
"<Kind>" "<group>" kubernetes CRD "<version>" documentation spec
Extract required fields, types, validation rules, and version-specific deprecations.
Stage 7: Schema Validation
kubeconform \
-schema-location default \
-schema-location 'https://raw.githubusercontent.com/datreeio/CRDs-catalog/main/{{.Group}}/{{.ResourceKind}}_{{.ResourceAPIVersion}}.json' \
-summary -verbose \
./rendered/*.yaml
Add -strict for production, -ignore-missing-schemas for internal CRDs, -kubernetes-version 1.28.0 for version pinning. "No schema found" for CRDs is expected — validate those manually using Stage 6 docs.
Stage 8: Cluster Dry-Run (if available)
helm install <release-name> <chart-directory> --dry-run --debug --values <values-file>
helm upgrade <release-name> <chart-directory> --dry-run --debug --values <values-file>
# With helm-diff plugin:
helm diff upgrade <release-name> <chart-directory>
Catches admission controller rejections, policy violations, quota issues, and webhook errors. Skip and document if no cluster access.
Stage 9: Security Best Practices Check (MANDATORY)
Analyze rendered Deployment/Pod templates:
grep -l "securityContext" ./rendered/*.yaml
grep -l "resources:" ./rendered/*.yaml
grep "image:.*:latest" ./rendered/*.yaml
Required checks:
- Pod securityContext:
runAsNonRoot,runAsUser,fsGroup - Container securityContext:
allowPrivilegeEscalation: false,readOnlyRootFilesystem,capabilities.drop: [ALL] - Resource limits/requests for cpu and memory
- No
:latestimage tags - Liveness and readiness probes present
Stage 10: Final Report (MANDATORY)
This stage is MANDATORY even if all validations pass.
Step 1: Load References (when issues found)
Read references/helm_best_practices.md
Read references/k8s_best_practices.md
Step 2: Validation Summary Table
| Stage | Status | Issues |
|-------|--------|--------|
| 1. Tool Check | ✅ Passed | All tools available |
| 2. Structure | ⚠️ Warning | Missing: .helmignore |
| 3. Helm Lint | ✅ Passed | 0 errors |
| 4. Template Render | ✅ Passed | 5 templates rendered |
| 5. YAML Syntax | ✅ Passed | No errors |
| 6. CRD Detection | ✅ Passed | 1 CRD documented |
| 7. Schema Validation | ✅ Passed | All resources valid |
| 8. Dry-Run | ✅ Passed | No cluster errors |
| 9. Security Check | ⚠️ Warning | Missing securityContext |
Step 3: Categorize Issues
- ❌ Errors (must fix): Template syntax errors, missing required fields, schema failures, dry-run failures
- ⚠️ Warnings (should fix): Deprecated APIs, missing securityContext, missing resource limits,
:latesttag, missing recommended files - ℹ️ Info: Missing values.schema.json, missing README.md, optimization opportunities
Step 4: Proposed Changes (DO NOT APPLY)
For each issue:
- File path and line number
- Before/after code blocks
- Explanation of why the change is recommended
Step 5: Automation Opportunities
Common fixes:
- Missing
_helpers.tpl:bash scripts/generate_helpers.sh <chart> - Missing
.helmignore: Copy fromassets/.helmignore - Missing
values.schema.json: Copy/customize fromassets/values.schema.json - Use
includeinstead oftemplatefor pipeline support - Add
nindentfor proper YAML indentation - Add
defaultfunction for optional values - Add
requiredfor critical values
Step 6: Final Summary
## Validation Summary
**Chart:** <chart-name>
**Status:** ⚠️ Warnings Found (or ✅ Ready for Deployment)
**Issues:** Errors: X Warnings: Y Info: Z
**Proposed Changes:** N changes recommended
**Next Steps:**
1. Review proposed changes above
2. Apply manually or use helm-generator skill
3. Re-run validation to confirm fixes
Helm Templating Reference
For complex templating tasks, load the dedicated reference:
Read references/template_functions.md
Standard helper patterns (templates/_helpers.tpl) — including fullname, labels, and selectorLabels definitions — are documented in references/template_functions.md.
Key template functions: required, default, quote, include, tpl, toYaml, merge, lookup — see references/template_functions.md for full reference with examples.
macOS Extended Attributes Issue
Symptom: Helm reports "Chart.yaml file is missing" even though the file exists.
Diagnosis & Fix:
xattr /path/to/chart/Chart.yaml # check for attributes
xattr -cr /path/to/chart/ # remove all recursively
Prevention: Use helm create as a base, or create files with shell heredocs (cat > file << 'EOF').
Error Handling
- Tool not available: Run
scripts/setup_tools.sh, skip optional stages, document what was skipped. - Template errors: Show file and line number, check values.yaml definitions, use
--debug. - Cluster access issues: Fall back to
kubectl apply --dry-run=server -f ./rendered/, document limitations. - CRD schema not found: Use kubeconform CRD catalog; fall back to
kubectl explain <kind>. - Stage failures: Continue to next stage, collect all errors, present together in Stage 10.
Version Awareness
- Ensure
apiVersion: v2in Chart.yaml (Helm 3+) - Check for deprecated Kubernetes APIs
- Use
kubectl api-versionsto list available API versions - Set
kubeVersionconstraint in Chart.yaml when needed - Target specific K8s version with
--kube-versionin helm template / kubeconform
Resources
scripts/
setup_tools.sh: Check/install required toolsvalidate_chart_structure.sh: Validate chart directory structuredetect_crd_wrapper.sh: Detect CRDs in YAML files (manages Python venv)detect_crd.py: Parse YAML to identify CRDs, output JSONgenerate_helpers.sh: Generate standard_helpers.tpl
references/
helm_best_practices.md: Chart structure, template conventions, values organizationk8s_best_practices.md: Metadata, labels, resource limits, security contexttemplate_functions.md: All built-in Helm/Sprig functions with examples, standard helper patterns
assets/
.helmignore: Standard ignore patterns for chart packaging.yamllint: Pre-configured yamllint rules for Kubernetes YAMLvalues.schema.json: Example JSON Schema template for values validation
Source
git clone https://github.com/pantheon-org/tekhne/blob/main/skills/ci-cd/helm/validator/SKILL.mdView on GitHub Overview
helm-validator provides a comprehensive, read-only workflow for validating Helm charts and their rendered Kubernetes resources. It combines Helm linting, template rendering, YAML and schema validation, CRD documentation lookup, and security best-practices checks to surface issues without modifying source charts.
How This Skill Works
It guides users through a nine-stage validation flow: tool check, chart structure validation, Helm lint, template rendering, YAML syntax validation, CRD documentation lookup, schema validation, cluster dry-run, and security best-practices checks. The tool analyzes outputs, flags issues, and surfaces concrete improvements as a final summary for manual review and remediation.
When to Use It
- Pre-release validation of Helm charts in CI to catch issues early
- Debugging template rendering or CRD documentation gaps
- Validating CRDs and applying schema checks against rendered output
- Assessing security context, resource requests, and other hardening checks
- Generating actionable change suggestions for manual review or helm-generator flow
Quick Start
- Step 1: Ensure helm (v3+), yamllint, kubeconform, and kubectl (optional) are installed
- Step 2: Run the helm-validator workflow on your chart directory (Stages 1-9)
- Step 3: Review the final summary and apply changes manually or via the helm-generator skill
Best Practices
- Run in a clean environment with all required tools installed
- Use helm lint --strict to catch stricter issues early
- Review the final summary of proposed changes before applying
- Validate both source templates and rendered YAML when possible
- Treat this as a read-only analysis feed into manual remediation
Example Use Cases
- CI pipeline stage that runs helm lint --strict and template rendering to surface issues
- Chart maintenance workflow: analyze CRD docs lookup results for deprecated fields
- Security review by inspecting rendered manifests for securityContext and limits
- Generate a final summary report of recommended changes for team review
- Integrate with helm-generator to apply approved changes automatically