Production Helm chart where the image tag safely defaults to AppVersion and migrations run as a hook

Production Helm chart for a Node API. Below is the chart skeleton plus the two files that matter most — a templated deployment and a documented `values.yaml`. ``` checkout/ ├── Chart.yaml ├── values.yaml ├── values-prod.yaml └── templates/ ├── _helpers.tpl ├── deployment.yaml ├── service.yaml ├── ingress.yaml ├── hpa.yaml └── NOTES.txt ``` ```yaml # values.yaml — every option commented replicaCount: 3 image: repository: registry.acme.io/checkout tag: "" # defaults to .Chart.AppVersion if empty pullPolicy: IfNotPresent resources: requests: { cpu: 250m, memory: 256Mi } limits: { cpu: 500m, memory: 512Mi } autoscaling: enabled: true minReplicas: 3 maxReplicas: 12 targetCPUUtilizationPercentage: 70 ingress: enabled: true host: checkout.acme.io tls: true ``` ```yaml # templates/deployment.yaml — note the safe tag default and helper labels apiVersion: apps/v1 kind: Deployment metadata: name: REPLACE-fullname labels: REPLACE-labels spec: replicas: REPLACE-replicaCount template: spec: containers: - name: checkout image: "REPLACE-repository:REPLACE-tag-or-appVersion" resources: REPLACE-resources readinessProbe: httpGet: { path: /api/ready, port: 3000 } ``` (The `REPLACE-...` markers stand in for Helm's templating expressions — in the real file they use the standard `.Values` / `.Chart` template syntax and the `_helpers.tpl` named templates for consistent labels.) **Best practices baked in:** image tag falls back to `.Chart.AppVersion` so deploys are versioned even if a caller forgets to set it; `_helpers.tpl` centralizes naming and labels; a `pre-upgrade` Helm hook runs DB migrations. **Validate before shipping:** `helm lint ./checkout && helm template ./checkout -f values-prod.yaml` renders cleanly and passes lint.