Skip to content

feature request: Support for multiple values files, and values files outside of "root" #190

@cNorspang

Description

@cNorspang

It would be great, for a multi-environment setup, if we could somehow give a list of values files to take into consideration, potentially with a heirachy akin to how ArgoCD does it

eg.

apps/
├── app1/
│   ├── Chart.yaml
│   ├── templates/
│   │   └── deployment.yaml
│   └── values/
│       ├── dev.yaml
│       ├── staging.yaml
│       └── prod.yaml
└── app2/
    ├── Chart.yaml
    ├── templates/
    │   └── deployment.yaml
    └── values/
        ├── dev.yaml
        ├── staging.yaml
        └── prod.yaml
configuration/
└── values/
    ├── dev.yaml
    ├── staging.yaml
    └── prod.yaml
    └── generated/
        ├── dev.yaml
        ├── staging.yaml
        └── prod.yaml

If I, for any given chart, could tell it to consider dev.yaml within a set of predefined paths ["../../configuration/values", "../../configration/generated/values", "./values"]

And i would do that as a heirachy, applying first -> last, so the "resulting" value, in case of conflict in all files would be the one in "./values/dev.yaml"

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions