Have you considered the use of maven profiles for different deployment environments?
I came across this issue helm/helm#2620 that suggests storing common values in values.yaml and then overriding them with environment-specific values that are stored in an environment-specific file, e.g. prod-values.yml.
Would you consider an optionextraFiles that accepts a list of files with the overriding values?
Or, if possible, a generic, more flexible parameter extraOptions that passes a string to helm, e.g. -f prod-values.yml.
The process would look something like this:
- In Maven
pom.xml one would define profiles, e.g. dev, prod.
- A chart folder would contain
values.yaml, values-dev.yaml and values-prod.yaml for common, dev- and prod-specific values respectively.
- Maven Helm plugin would be configured to pass the following string to helm:
<extraOptions>-f values-${project.ActiveProfiles[0]}.yaml</extraOptions>
Have you considered the use of maven profiles for different deployment environments?
I came across this issue helm/helm#2620 that suggests storing common values in
values.yamland then overriding them with environment-specific values that are stored in an environment-specific file, e.g.prod-values.yml.Would you consider an option
extraFilesthat accepts a list of files with the overriding values?Or, if possible, a generic, more flexible parameter
extraOptionsthat passes a string to helm, e.g.-f prod-values.yml.The process would look something like this:
pom.xmlone would define profiles, e.g.dev,prod.values.yaml,values-dev.yamlandvalues-prod.yamlfor common, dev- and prod-specific values respectively.<extraOptions>-f values-${project.ActiveProfiles[0]}.yaml</extraOptions>