How is Helm template storage best organized for infrastructure management?

It is best to store Helm templates in a version control system (e.g., Git). It is recommended to organize the repository so that each Helm chart is a separate directory with its own Chart.yaml, values.yaml, and templates in the templates/ folder.

You can use a monorepo structure if you have many charts, or separate repositories for each major component. It is important to keep templates up to date, use branches and pull requests for changes.

It is also useful to store configurations for different environments (dev, staging, prod) in separate files values-<env>.yaml or in separate directories to facilitate parameter management during deployment.

Example structure:

my-helm-charts/
  ├── my-app/
  │    ├── Chart.yaml
  │    ├── values.yaml
  │    └── templates/
  │         ├── deployment.yaml
  │         └── service.yaml
  └── another-app/
       ├── Chart.yaml
       ├── values.yaml
       └── templates/

This approach ensures ease of versioning, collaboration, and automation of CI/CD processes.