$devtoolkit.sh/examples/yaml/helm-values

Format a Helm Values File

Helm values files configure Kubernetes charts and are injected into templates as YAML. Formatting errors in values.yaml cause helm install to fail or silently produce incorrect manifests. This example shows common values for a web application chart with replicas, image configuration, ingress, and resource limits. Validate and format before running helm upgrade.

Example
replicaCount: 2

image:
  repository: myregistry.io/myapp
  tag: "1.5.0"
  pullPolicy: IfNotPresent

service:
  type: ClusterIP
  port: 80

ingress:
  enabled: true
  host: api.example.com
  tls: true

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

autoscaling:
  enabled: false
  minReplicas: 2
  maxReplicas: 10
[ open in YAML Formatter → ]

FAQ

How do Helm values override chart defaults?
Helm merges your values.yaml with the chart default values.yaml. Your values take precedence. You can also pass individual overrides with --set flag on the command line.
Should image tags be quoted in YAML?
Quote tags that are pure numbers or look like numbers (e.g., "1.5.0" or "latest") to prevent YAML from interpreting them as floats or booleans.
What is the difference between ClusterIP and LoadBalancer service types?
ClusterIP exposes the service only within the cluster. LoadBalancer provisions an external load balancer from the cloud provider, making it accessible from outside the cluster.

Related Examples

/examples/yaml/helm-valuesv1.0.0