Helm Values Helper

Generated a Helm chart scaffold for "web" with 11 values.yaml key(s).

How it works

• Wrote the Chart.yaml required keys with the apiVersion v2 schema.
• Wrote a values.yaml with replicaCount, image, service and resources.
• Added the optional ingress block.

• Create templates/ yourself; this scaffold only produces the chart metadata and defaults.
• Run `helm lint ./chart` to check the scaffold before packaging.

Methodology

1. Validate the chart name, versions, repository and port.
2. Emit Chart.yaml with the required keys in the documented order.
3. Emit values.yaml with nested image, service, resources and optional ingress keys.

Usage

1. Enter the chart name, description and versions.
2. Set the image repository/tag, replica count and service settings.
3. Copy Chart.yaml and values.yaml, then add your templates.

Examples

These are examples, not current values: they use fixed inputs, while the interactive tool computes live results in your browser.

Application chart

{
  "name": "web",
  "description": "A sample web application chart.",
  "type": "application",
  "version": "0.1.0",
  "appVersion": "1.4.0",
  "repository": "ghcr.io/example/web",
  "imageTag": "1.4.0",
  "replicaCount": 2,
  "serviceType": "ClusterIP",
  "servicePort": 80,
  "ingress": true
}

Limitations

What goes where

Chart.yaml describes the chart; values.yaml holds the defaults a user overrides. Keeping both explicit makes the chart reviewable before it is deployed.