| name | ring:creating-helm-charts |
| description | Creating Helm charts to Lerian conventions via ring:helm: standardized chart structure, full env-var coverage from .env.example, security defaults (runAsNonRoot, readOnlyRootFilesystem), ClusterIP-only services, and health probes; validates helm lint and template render. Use when creating, modifying, or reviewing a chart, or migrating docker-compose to Helm. Skip for app-code-only changes or docker-compose-only deployments. |
Helm Chart Creation & Maintenance
When to use
- Creating a new Helm chart for any Lerian service
- Modifying an existing Helm chart (adding components, dependencies, templates)
- Reviewing a Helm chart PR for convention compliance
- Migrating a docker-compose setup to Helm
Skip when
- Modifying only application code (no chart changes)
- Working on non-Helm deployment (docker-compose only) → use backend engineer via ring:implementing-tasks
Sequence
Standalone/on-demand. Not part of the lean backend dev-cycle.
Related
Complementary: ring:implementing-tasks
Standards reference: dev-team/docs/standards/helm/
Executor agent: ring:helm
You orchestrate. ring:helm creates chart files.
Step 1: Validate Input
Required: service_name, chart_type (single|multi-component|umbrella), components (non-empty).
Optional: dependencies (postgresql, mongodb, rabbitmq, valkey, keda), has_worker, namespace.
Step 2: Naming Convention
Default: {service_name}-helm (e.g., reporter-helm, tracer-helm)
Exceptions (no -helm suffix):
- plugin-access-manager
- otel-collector-lerian
