Helmgen

Auto-generate Helm charts from Docker Compose files.

HelmGen is a Python CLI tool that converts your docker-compose.yml into a structured Helm chart — including Deployments, StatefulSets, Services, PVCs, Ingress, and Secrets (native or ExternalSecrets).

Features

• Convert Docker Compose files directly into Helm charts
• Auto-detect databases (postgres, mysql, mariadb, mongodb, redis) → StatefulSet + PVC with real volume mount paths
• Auto-generate Kubernetes Secrets or ExternalSecrets (External Secrets Operator)
• Generate SecretStore or ClusterSecretStore, or reuse an existing one
• Auto-detect Ingress from exposed web ports (80/443/8080) and Traefik-style Host(...) labels
• Replace hardcoded secrets with safe placeholders in values.yaml
• Sensible storage size defaults per database type
• Maps compose replicas, command/args, deploy.resources, and healthcheck (→ liveness/readiness probes) into the chart
• Default CPU/memory resources on all containers, overridable per service in values.yaml
• Optional HTTP liveness/readiness probes via probePath/probePort in values.yaml
• Standard app.kubernetes.io/* labels on every resource (via _helpers.tpl)

Installation

pip install helmgen

From source (recommended for development):

git clone https://github.com/marcelodevops/helmgen.git
cd helmgen
pip install -e .

Usage

helmgen docker-compose.yml [options]

Example

docker-compose.yml:

version: "3.8"
services:
  web:
    image: nginx:alpine
    ports:
      - "8080:80"
    environment:
      APP_ENV: production
      SECRET_KEY: supersecret

  db:
    image: postgres:14
    environment:
      POSTGRES_USER: user
      POSTGRES_PASSWORD: pass123
    volumes:
      - db-data:/var/lib/postgresql/data
    ports:
      - "5432:5432"

volumes:
  db-data:

Hardcoded secrets in compose files are bad practice — HelmGen detects them and replaces their values in values.yaml with <secret-from-values> placeholders.

Generate a chart using ExternalSecrets backed by a shared ClusterSecretStore:

helmgen docker-compose.yml \
  --output ./charts/myapp \
  --secret-provider externalsecret \
  --store-scope cluster \
  --reuse-store global-vault-store

Output:

charts/myapp/
├── Chart.yaml
├── values.yaml
└── templates/
    ├── _helpers.tpl          # standard label helpers
    ├── deployment.yaml       # non-database services
    ├── statefulset.yaml      # database services (storage: true)
    ├── service.yaml
    ├── pvc.yaml
    ├── ingress.yaml
    ├── secrets.yaml          # rendered only when secretProvider=internal
    ├── externalsecret.yaml   # rendered only when secretProvider=externalsecret
    └── secretstore.yaml      # skipped when --reuse-store is set

A ready-to-try input lives in examples/docker-compose.yml.

Tuning the generated chart

values.yaml is meant to be edited after generation:

services:
  web:
    probePath: /healthz   # adds liveness + readiness httpGet probes
    probePort: 8080
    replicas: 3
    resources:            # overrides the global default per service
      requests: {cpu: 50m, memory: 256Mi}
resources:                # global default for all containers
  requests: {cpu: 10m, memory: 128Mi}
  limits: {cpu: "1", memory: 512Mi}

Deploy:

helm install myapp ./charts/myapp

Development

pip install -e .[dev]
ruff check .
pytest --cov=helmgen

The templates in helmgen/helm_templates/ are plain Helm templates (copied verbatim into the generated chart); all chart logic driven by values.yaml lives in helmgen/generator.py.

Dependencies

License

MIT