Context
Part of epic #1 — Build production-ready REST microservice with k8s deployment on top of casehub-engine. Helm chart simplifies deployment, configuration management, and upgrades across different environments (dev, staging, production).
What
Create Helm chart for casehub-flow deployment:
- Chart structure with templates for Deployment, Service, ConfigMap, Secret, Ingress
- Values files for different environments (dev, prod)
- Parameterized configuration (replicas, resources, database settings, image tag)
- PostgreSQL dependency (bitnami/postgresql subchart)
- Installation and upgrade documentation
Acceptance Criteria
Notes
- Use Helm 3 (no Tiller dependency)
- PostgreSQL dependency using bitnami/postgresql chart (required, not optional)
- Database credentials auto-generated by PostgreSQL subchart or overridable in values
- Consider adding NOTES.txt with post-installation instructions
- Ingress template should be optional (enabled: false by default)
- Chart version should track application version
- File paths:
helm/casehub-flow/Chart.yaml, helm/casehub-flow/values.yaml, helm/casehub-flow/templates/*
Context
Part of epic #1 — Build production-ready REST microservice with k8s deployment on top of casehub-engine. Helm chart simplifies deployment, configuration management, and upgrades across different environments (dev, staging, production).
What
Create Helm chart for casehub-flow deployment:
Acceptance Criteria
helm/casehub-flow/directoryvalues.yamlwith sensible defaults (replicas: 2, resource limits, health check settings)values-dev.yamlandvalues-prod.yamlfor environment-specific overridesChart.yaml(bitnami/postgresql)/q/health/live,/q/health/ready)helm install casehub-flow ./helm/casehub-flowNotes
helm/casehub-flow/Chart.yaml,helm/casehub-flow/values.yaml,helm/casehub-flow/templates/*