Skip to content

Value files precedence behaviour changes when custom values file is used #9940

Description

@ankitabhopatkar13

Edit: The issue can be reproduced and outputs can be seen here - https://github.com/ankitabhopatkar13/helm-values-issue

Output of helm version: version.BuildInfo{Version:"v3.6.1", GitCommit:"61d8e8c4a6f95540c15c6a65f36a6dd0a45e7a2f", GitTreeState:"dirty", GoVersion:"go1.16.5"}

I have 3 kind of charts -

  • Library Chart
  • App Chart (Uses Library Chart as dependecy)
  • Umbrella Chart (Has all the app charts as dependencies)

Library chart has value structure like -
----- templates/
----- values.yaml

- exports:
     service:
       type: ClusterIP
       port: 9090

App Chart has value structure like -
----- templates/
----- values.yaml

service:
  type: ClusterIP
  port: 1234

Umbrella Chart has value structure like -
----- values/
------- aws/
--------- test.yaml
--------- accp.yaml

helm upgrade --install release release --values aws/test.yaml, the service port is still used as 9090 and not 1234.

But if I don't pass the custom values file and just use values.yaml in the umbrella chart, the port is getting set to 1234 which is what should be the case even when custom values file(test.yaml) is used.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugCategorizes issue or PR as related to a bug.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions