search

cetic / helm-fadi

Helm Chart for FADI
https://github.com/cetic/fadi
Apache License 2.0
13 stars 4 forks source link

[cetic/fadi] specific and hard-coded release name #41

Open fzalila opened 3 years ago

fzalila commented 3 years ago

Describe the bug The current values.yaml requires that the release must be named fadi. This install does not work with my-release release name.

Version of Helm and Kubernetes:

How to reproduce it (as minimally and precisely as possible): Install fadi as explained here and try to access to a any service. The access (admin/password1) will not work because the server is not found. t=2021-06-28T13:21:50+0000 lvl=eror msg="Error while trying to authenticate user" logger=context userId=0 orgId=0 uname= error="LDAP Result Code 200 \"Network Error\": dial tcp: lookup fadi-openldap on 10.96.0.10:53: no such host" remote_addr=172.17.0.1 t=2021-06-28T13:21:50+0000 lvl=eror msg="Request Completed" logger=context userId=0 orgId=0 uname= method=POST path=/login status=500 remote_addr=172.17.0.1 time_ms=124 size=53 referer=http://192.168.99.254:32676/login

A suggestion to resolve issue: Multiple services start withfadi- must be updated like {{ .Release.Name }}-

AyadiAmen commented 2 years ago

I tried to change fadi- to {{ .Release.Name }}- in the values.yaml file but it doesn't work, some services ( jupyterHub, zabbix, airflow ) don't accept {{ .Release.Name }} in the values and postgresql gives the error 

 LOG:  authentication option not in name=value format: .Release.Name
2021-09-28 07:52:16.119 UTC [1] CONTEXT:  line 1 of configuration file "/var/lib/postgresql/conf/pg_hba.conf"
2021-09-28 07:52:16.119 UTC [1] LOG:  authentication option not in name=value format: .Release.Name
2021-09-28 07:52:16.119 UTC [1] CONTEXT:  line 2 of configuration file "/var/lib/postgresql/conf/pg_hba.conf"
2021-09-28 07:52:16.119 UTC [1] FATAL:  could not load pg_hba.conf
2021-09-28 07:52:16.119 UTC [1] LOG:  database system is shut down

so i suggest we keep the default release-name fadi.

banzo commented 2 years ago

Do you know why?

AyadiAmen commented 2 years ago

I think it works on the resources files ( Deployment, configmap ... ) but not in the values file. there are others who faced the same issue : https://stackoverflow.com/questions/59222503/use-release-name-in-values-yaml-in-helm , https://github.com/helm/helm/issues/3558 but they didn't find a solution yet.