CtrlK
BlogDocsLog inGet started
Tessl Logo

pantheon-ai/helm-toolkit

Complete helm toolkit with generation and validation capabilities

94

Quality

94%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

task.mdvalidator/evals/scenario-5/

Task: Generate Stage 10 Final Validation Report

You have completed stages 1-9 of the helm-validator workflow on a chart called monitoring-stack. The results from each stage are summarised below:

  • Stage 1 (Tool Check): helm v3.14.0, yamllint 1.35.1, kubeconform 0.6.4 all present. kubectl not available.
  • Stage 2 (Structure): Chart.yaml present (apiVersion: v2). values.yaml present. templates/ present. Missing: .helmignore, NOTES.txt.
  • Stage 3 (Helm Lint): 0 errors. 1 warning: icon field missing from Chart.yaml.
  • Stage 4 (Template Render): 6 templates rendered successfully to ./rendered/.
  • Stage 5 (YAML Syntax): 1 issue: trailing whitespace on line 14 of rendered/deployment.yaml.
  • Stage 6 (CRD Detection): 1 CRD detected: monitoring.coreos.com/v1 ServiceMonitor. Documentation lookup performed — required fields: selector, endpoints.
  • Stage 7 (Schema Validation): Deployment, Service, ConfigMap: valid. ServiceMonitor: "No schema found" (expected for CRD). Manual check using Stage 6 docs: selector present, endpoints present — passes.
  • Stage 8 (Dry-Run): Skipped — no cluster access. Documented as limitation.
  • Stage 9 (Security): Deployment has no pod securityContext. Container has no allowPrivilegeEscalation: false. Image tag is v2.1.0 (pinned — good). No livenessProbe or readinessProbe. Resource limits missing for memory.

Your Task

Produce the complete Stage 10 Final Report exactly as specified by the helm-validator skill, including:

  1. A validation summary table covering all 9 stages with status icons and issue counts.
  2. Categorised issue list (Errors, Warnings, Info) with file references.
  3. Proposed changes section with at least two before/after code blocks.
  4. An automation opportunities section listing any applicable helper commands.
  5. A final summary block with chart name, overall status, issue counts, and next steps.

tile.json