enable ports based on the config value in the kubernates about helm HOT 15 OPEN

The issue is that a dash is included in {{ .Values.image.debug-port }} which is not supported. If you change it to {{ index .Values "image" "debug-port" }}, Helm will no longer produce en error

from helm.

@sabre1041

we have changed the "debug-port" in the values.ymal to "debugport" and updated the daemonset.yaml respectively. But still getting the same error.

{{- if eq (index .Values.configMap.test-config "services-debug") "true" }}

• name: debug-port
  containerPort: {{ .Values.image.debugport }}
  hostPort: {{ .Values.image.debugport }}
  {{- end }}

Error: parse error at (test/templates/daemonset.yaml:59): bad character U+002D '-'

{{- if eq (index .Values.configMap "test-config" "services-debug") "true" }}

• name: debug-port
  containerPort: {{ .Values.image.debugport }}
  hostPort: {{ .Values.image.debugport }}
  {{- end }}

templates/daemonset.yaml:59:20: executing "test/templates/daemonset.yaml" at <index .Values.configMap "test-config" "services-debug">: error calling index: index of untyped nil

from helm.

 {{- if eq (index .Values.configMap "test-config" "services-debug" | toString) "true" }}

Values:

configMap:
  test-config:
    services-debug: false
image:
  debug-port: 81

from helm.

Still getting the same error with {{- if eq (index .Values.configMap "test-config" "services-debug" | toString) "true" }}

test/templates/daemonset.yaml:59:20: executing "test/templates/daemonset.yaml" at <index .Values.configMap "test-config" "services-debug">: error calling index: index of untyped nil

Note: the we dont have the services-debug value in values.yaml instead we have a config map where we define services-debug value.

e.g.

apiVersion: v1
kind: ConfigMap
metadata:
  name: {{ .Chart.Name }}
data:
    services-debug: true

This is deployed a test-config

from helm.

@nchitimilla Can you please share as much information as possible. Your values.yaml and template files

from helm.

Provided all the necessary filles

daemonset.yaml:
apiVersion: v1
kind: ConfigMap
metadata:
name: {{ .Chart.Name }}
annotations:
reloader.stakater.com/match: "true"
data:
services-debug: {{ .Values.servicesdebug | quote }}

values.yaml
servicesdebug: false

daemonset.yaml
apiVersion: apps/v1
kind: DaemonSet
metadata:
name: {{ .Chart.Name }}
annotations:
reloader.stakater.com/auto: "true"
spec:
hostNetwork: yes
containers:
ports:
- name: http-port
containerPort: {{ .Values.image.porthttp }}
hostPort: {{ .Values.image.porthttp }}
- name: debug-port
containerPort: {{ .Values.image.debugport }}
hostPort: {{ .Values.image.debugport }}

values.yaml
image:
porthttp: 8080
debugport: 8081

from helm.

@nchitimilla This structure looks totally different than the original issue.

Are you testing against the servicesdebug property in the values.yaml file and then will enable the debug-port based upon it?

from helm.

@nchitimilla This structure looks totally different than the original issue.

Are you testing against the servicesdebug property in the values.yaml file and then will enable the debug-port based upon it?

Yes. If the servicesdebug is true we would like to enable the debug port

from helm.

@nagraj321 @nchitimilla why are there 2 values.yaml files? A since this is a relatively flat structure, you can just perform a simple check and it should work without issue. You can remove all of the complex index logic

from helm.

First daemons.yaml and values.yaml are deployed as a one service i.e. test-config which will have the common details required by the other services.

Other daemonset.yaml and values.yaml are related to some other service.

We can’t club together as this test-config service is being used by nearly 10 other services.

Now we need to look up if we have a debug enabled in the test-config service then we need to enable the debug port.

from helm.

so we can assume there is a ConfigMap where you want to look up a value already on the cluster?

from helm.

so we can assume there is a ConfigMap where you want to look up a value already on the cluster?

Yes

from helm.

You would want to use the lookup filter

from helm.

You would want to use the lookup filter

If you can give some example or link to documentation will be helpful.

from helm.

You would want to use the lookup filter

If you can give some example or link to documentation will be helpful.

https://helm.sh/docs/chart_template_guide/functions_and_pipelines/#using-the-lookup-function

from helm.