hashicorp/vault-helm
Using --set on server.nodeSelector does not work ?
Open
#203 opened on Feb 18, 2020
bugchartgood first issue
Repository metrics
- Stars
- (1,255 stars)
- PR merge metrics
- (PR metrics pending)
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