Helm Chart Review Prompt

You are a senior platform engineer who has shipped Helm charts to production for hundreds of services across multiple companies. You know where charts fail in real environments.

Review the Helm chart I share. Apply this checklist:

1. **values.yaml hygiene.** Are defaults sane for *production*, not just local dev? Are sensitive defaults (credentials, hosts) clearly marked as REQUIRED? Are types consistent (no surprise mix of strings/booleans)?
2. **Templating correctness.** Look for: missing `quote`/`toYaml` calls, unsafe `printf` patterns, missing `with`/`if` scoping, off-by-one indent issues, missing `nindent`.
3. **Resource sanity.** Every Deployment has resource requests AND limits. Probes are tuned (initialDelaySeconds, periodSeconds, failureThreshold), not just copy-pasted. PodDisruptionBudget exists for HA workloads.
4. **Security defaults.** Pods run as non-root by default. ReadOnlyRootFilesystem where possible. No `securityContext.privileged: true` unless documented and gated. NetworkPolicy or equivalent considered.
5. **Upgrade safety.** Will `helm upgrade` work without data loss? Are PVCs preserved across upgrades? Are immutable fields (Service spec.selector, StatefulSet spec.serviceName, Job spec.selector) protected?
6. **Dependency management.** Subcharts in Chart.yaml are pinned to exact versions, not floating ranges.
7. **Documentation.** README explains required values, install commands, and known limitations.

For each finding, give a **severity** (critical / warning / nit), the file and line, the problem, the fix.

After the review, propose a **3-bullet ranked list of changes** to make first.

Chart structure (paste `ls -R chart/` or the relevant files):
```
[PASTE]
```

Chart.yaml:
```yaml
[PASTE]
```

values.yaml:
```yaml
[PASTE]
```

Templates (one at a time, or paste the most critical ones):
```yaml
[PASTE]
```