Helm Chart Generator

Scaffold a Helm chart: Chart.yaml, values.yaml and templates

Chart metadata

Image & workload

Service & Ingress

Generated chart files

apiVersion: v2
name: my-app
description: A Helm chart for my-app
type: application
version: 0.1.0
appVersion: 1.0.0

Examples

A standard chart scaffold

Input
my-app · image nginx:1.27 · 2 replicas · ClusterIP · no ingress
Output
Chart.yaml + values.yaml + templates/{deployment,service,_helpers}.yaml

Each tab is one file in the chart; copy them into matching paths and adapt the helpers to your app.

Add an Ingress

Input
Toggle 'Include Ingress template', host my-app.example.com
Output
An extra templates/ingress.yaml wired to the service port.

Enable ingress to generate a templated Ingress that routes your host to the chart's service.

About this tool

A Helm chart is a small bundle of templated Kubernetes manifests plus a values file. Scaffolding one from scratch means remembering the Chart.yaml fields, the conventional Go-template helpers, and how to wire values into a Deployment and Service.

This generator produces a complete chart scaffold: Chart.yaml, values.yaml, and Go-templated Deployment, Service, Ingress, and _helpers.tpl. Configure the chart metadata, image, replicas, container port, and service type, toggle an Ingress, and copy each file into your chart directory.

How to use

  1. Set chart metadata

    Enter the chart name, version, appVersion and description for Chart.yaml.

  2. Configure the workload

    Set the image repository and tag, replica count and container port.

  3. Choose service & ingress

    Pick the service type and optionally include an Ingress template.

  4. Copy the files

    Copy each generated file into the matching path in your chart folder.

Common mistakes

Mistake:Editing templates instead of values.

Fix:Put environment-specific settings in values.yaml; templates should read them via .Values.

Mistake:Repeating helper logic.

Fix:Use the generated _helpers.tpl (fullname, labels, selectorLabels) so names stay consistent across templates.

Frequently asked questions

References & standards