Generate helm values

Create starter Helm values for images, replicas, services, ingress, autoscaling, and resources.

freeworks offlinenothing uploaded
ToolHelm Values Generator
Input
Output
—
Put this on your own site

The frame below runs the same code as this page, in the reader's own browser. Nothing is sent to us, and nothing is sent to you.

Pick a dark background and the text and panels follow it, so the frame stays readable on a dark page.

Preview

How it works

Selected deployment settings are emitted as a values.yaml mapping for a chart to consume. The file supplies chart inputs; it does not render templates or validate a chart schema.

  • Common values are editable because chart key names differ.
  • Optional ingress and autoscaling blocks avoid unused settings.

Worked example

API service with ingress + autoscaling
Helm values for a 3-replica Nginx API with ingress routing and horizontal pod autoscaling
Input
											App name: my-api
Image: nginx
Tag: 1.25
Replicas: 3
Port: 80
Ingress: true
Autoscaling: true
Persistence: false
Output
												# Default values for my-api

replicaCount: 3

image:
  repository: nginx
  tag: 1.25
  pullPolicy: IfNotPresent

service:
  type: ClusterIP
  port: 80

resources:
  requests:
    cpu: 100m
    memory: 128Mi
  limits:
    cpu: 500m
    memory: 256Mi

ingress:
  enabled: true
  className: nginx
  hosts:
    - host: my-api.example.com
      paths:
        - path: /
          pathType: Prefix
  tls: []

autoscaling:
  enabled: true
  minReplicas: 3
  maxReplicas: 9
  targetCPUUtilizationPercentage: 80

nodeSelector: {}
tolerations: []
affinity: {}

When to use this

Helm overlays, staging and production values, and release pipelines generate settings.

Edge cases

  • A chart can ignore a generated key if templates use another path.
  • Secrets in values.yaml remain plaintext without an external-secret workflow.
  • Autoscaling values require an HPA template and metrics provider.

References