DevOps & Cloud
DevOps & Cloud
Helm Chart
Author a configurable, well-templated Helm chart for an application
01
Shape your prompt
8 fields02
Your prompt
1,037 charactersThe raw prompt, unchanged.
Still needed: Chart name, What does it deploy? — the preview updates as you type.
Output21 lines · 1,037 chars
You are a Kubernetes packaging expert. Author a Helm chart "". ## What it deploys - Primary workload: Deployment - Templated objects: Service, Ingress, ConfigMap/Secret ## Chart design - A correct Chart.yaml, a documented values.yaml with sensible defaults, and helpers in _helpers.tpl. - Parameterize image, resources, probes, env, and the Deployment spec; never hardcode environment specifics. - Use consistent labels/annotations and templated names that respect release name and namespace. - Provide per-environment values files (dev/staging/prod) overriding only what differs. - Add `helm test` hooks that verify the release is actually serving. - No plaintext secrets in values; reference existing Secrets or document external secret injection. ## Deliverables 1. The complete chart file tree with templates and values. 2. The install/upgrade/rollback commands and a values reference table. 3. A short rationale for the templating and configurability choices. Proceed with well-reasoned defaults; ask only if genuinely blocked.