add-helm-chart

Add Helm Chart

Scaffold a new Helm chart following project conventions.

Arguments

• {chart-name} — Name of the chart (required, e.g., my-service, api-gateway)

Configuration

Read cloudstack.json from the project root at the start of execution. Extract:

• CHARTS_PATH = infrastructure.chartsPath (default: deploy/charts)
• K8S_NAMESPACE = infrastructure.namespace (default: detect from existing charts or use project name)

If cloudstack.json does not exist, auto-detect by scanning the project structure.

Process

1. Create the chart directory structure under {CHARTS_PATH}/{chart-name}/:

{CHARTS_PATH}/{chart-name}/
├── Chart.yaml
├── values.yaml
├── templates/
│   ├── _helpers.tpl
│   ├── deployment.yaml
│   ├── service.yaml
│   ├── configmap.yaml
│   ├── ingress.yaml
│   └── hpa.yaml

1. Read the helm-charts rule file (if present) for project conventions. Also scan existing charts in {CHARTS_PATH}/ to follow established patterns.

2. Generate files following these conventions:

   • Namespace: Use {{ .Release.Namespace }} in templates (do not hardcode)
   • Standard Kubernetes labels: app.kubernetes.io/name, app.kubernetes.io/instance, app.kubernetes.io/version
   • Health check paths: /health/live (liveness), /health/ready (readiness)
   • Resource limits and requests with sensible defaults
   • HPA with min 1, max 3 replicas

3. Chart.yaml template:

apiVersion: v2
name: {chart-name}
description: {description}
type: application
version: 0.1.0
appVersion: "0.1.0"

1. values.yaml — Include configurable values for:

   • image.repository, image.tag, image.pullPolicy
   • replicaCount
   • resources.requests and resources.limits
   • service.type, service.port
   • ingress.enabled, ingress.hosts
   • env (environment variables as key-value map)

2. Validate the chart:

helm lint {CHARTS_PATH}/{chart-name}
helm template test {CHARTS_PATH}/{chart-name} > /dev/null