hashicorp / hashicorp/vault-helm

Using --set on server.nodeSelector does not work ?

Open
#203 1 comment 4 reactions 0 assignees View on GitHub
bug chart good first issue
Dominant language
Shell
Stars
1.3k
Forks
898
Avg merge
3d 1h
Merged PRs (30d)
1

Description

Hello guys !

So I'm using helm Version:"v3.1.0" and I'm trying to deploy vault & consul via helm.
Pretty much all values that I want to override with --set seems to work but nodeSelector won't.

In my kubernetes I have different AutoScalingGroups, one is reserved for consul & vault.

So here's the error to my command, any hint ?

```
helm install --generate-name --debug --set server.nodeSelector.nodegroup="eks-asg-consul-vault" vault-helm
```

```
install.go:158: [debug] Original chart version: ""
install.go:175: [debug] CHART PATH: /vault-helm

client.go:98: [debug] creating 0 resource(s)
Error: no objects visited
helm.go:75: [debug] no objects visited
helm.sh/helm/v3/pkg/kube.init
/home/circleci/helm.sh/helm/pkg/kube/client.go:51
runtime.doInit
/usr/local/go/src/runtime/proc.go:5222
runtime.doInit
/usr/local/go/src/runtime/proc.go:5217
runtime.doInit
/usr/local/go/src/runtime/proc.go:5217
runtime.main
/usr/local/go/src/runtime/proc.go:190
runtime.goexit
/usr/local/go/src/runtime/asm_amd64.s:1357
```

I tried to format the argument in many different ways but never succeed.
I'm not very familiar with helm, been hitting my head on this one for a while now.
Could it be a bug or something ?

Thanks for helping out!
--jm

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the shown helm install command with the server.nodeSelector.nodegroup override and inspect the rendered chart output. Trace the server.nodeSelector values path through the chart templates; done means the override is accepted and the expected server resources are generated with the requested node selector.

Written by the indexing model from the issue text.

Assessment

Tech stack
helm, kubernetes
Domain
devops, infrastructure
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.