Values files not taken into account ? #279

qlemaire-dvt · 2025-04-04T07:12:01Z

qlemaire-dvt
Apr 4, 2025

Hi there,

I just started using the tool, and I've been playing around a bit.
Wanted to test on a real-life use case, but it seems like my values are not getting taken into account ?

Before opening an issue, I wanted to check if it was a "user-issue" or not.

This is how I proceeded :

Create Chart.yaml

apiVersion: v2
name: mychart
version: 1.0.0
dependencies:
- name: vault
  version: 0.29.0
  repository: https://helm.releases.hashicorp.com

Create Chart.lock

nelm chart dependency download

Re-used my existing values.yaml

global:
  openshift: true

injector:
  enabled: false
ui:
  enabled: true
  
server:
  image:
    repository: "redacted.com/ocp-platform-mirror/hashicorp/vault"
    tag: "1.18.1-ubi"
  readinessProbe:
    path: "/v1/sys/health?uninitcode=204"
  resources:
    requests:
      memory: 512Mi
      cpu: 250m
    limits:
      memory: 1Gi
      cpu: 500m
  logLevel: debug

dev:
  enabled: true

Plan release (I love this !)

nelm release plan install --values values.yaml -r vault -n vault-dvp

Also tried with the --no-default-values=false and without the --values parameter.

This isn't showing any of the values I defined in values.yaml, and I can't figure out what I did wrong.

Answered by ilya-lesikov

Apr 4, 2025

Your vault chart is a subchart of mychart. Thus you should wrap your values for vault chart in a vault key in values.yaml file:

global:
  openshift: true

vault:
  injector:
    enabled: false
  ui:
    enabled: true
    
  server:
    image:
      repository: "redacted.com/ocp-platform-mirror/hashicorp/vault"
      tag: "1.18.1-ubi"
    readinessProbe:
      path: "/v1/sys/health?uninitcode=204"
    resources:
      requests:
        memory: 512Mi
        cpu: 250m
      limits:
        memory: 1Gi
        cpu: 500m
    logLevel: debug

  dev:
    enabled: true

Btw, --values values.yaml not needed. It is a default, since values.yaml is a values-file of the root chart.

View full answer

ilya-lesikov · 2025-04-04T12:16:43Z

ilya-lesikov
Apr 4, 2025
Maintainer

Your vault chart is a subchart of mychart. Thus you should wrap your values for vault chart in a vault key in values.yaml file:

global:
  openshift: true

vault:
  injector:
    enabled: false
  ui:
    enabled: true
    
  server:
    image:
      repository: "redacted.com/ocp-platform-mirror/hashicorp/vault"
      tag: "1.18.1-ubi"
    readinessProbe:
      path: "/v1/sys/health?uninitcode=204"
    resources:
      requests:
        memory: 512Mi
        cpu: 250m
      limits:
        memory: 1Gi
        cpu: 500m
    logLevel: debug

  dev:
    enabled: true

Btw, --values values.yaml not needed. It is a default, since values.yaml is a values-file of the root chart.

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Values files not taken into account ? #279

Uh oh!

{{title}}

Uh oh!

Replies: 1 comment

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Values files not taken into account ? #279

Uh oh!

qlemaire-dvt Apr 4, 2025

Replies: 1 comment

Uh oh!

ilya-lesikov Apr 4, 2025 Maintainer

qlemaire-dvt
Apr 4, 2025

ilya-lesikov
Apr 4, 2025
Maintainer