If we defined secretEnv section in values.yaml for master or tserver, we observe the helm chart deployment fails and so does 'helm template' command.
Following section is added:
`master:
affinity:
podAntiAffinity: {}
extraEnv: []
extraVolumeMounts: []
extraVolumes: []
podAnnotations: {}
podLabels: {}
secretEnv:
If we defined secretEnv section in values.yaml for master or tserver, we observe the helm chart deployment fails and so does 'helm template' command. Following section is added: `master: affinity: podAntiAffinity: {} extraEnv: [] extraVolumeMounts: [] extraVolumes: [] podAnnotations: {} podLabels: {} secretEnv:
name: YSQL_PASSWORD valueFrom: secretKeyRef: name: test-secret key: password`
Helm template command execution fails with reason:
Error: template: yugabyte/templates/service.yaml:385:12: executing "yugabyte/templates/service.yaml" at <include "yugabyte.addenvsecrets" $data>: error calling include: template: yugabyte/templates/_helpers.tpl:119:15: executing "yugabyte.addenvsecrets" at <$v.valueFrom.secretKeyRef.namespace>: nil pointer evaluating interface {}.secretKeyRefThanks Rohan Roy Sharma