I don't know if it's desirable to update the templates to take those parameters into account or if only the documentation should be updated with a warning when using such variables...
Here is what I see as templates updates, but there must be a simpler way (I'm just a newbie with Helm 😅) :
opensearchHosts should take a list of <host>:<port> values
a disableSecurityPlugin boolean value should be added for both opensearch and opensearch-dashboards
an helper function should be created to turn the list into a CSV list and prepending http:// or https:// depending on disableSecurityPlugin value (example skeleton of helper function that should do the job: https://stackoverflow.com/a/49147648)
Hello, After a long time digging in documentation/issues here and directly on https://github.com/opensearch-project/opensearch-build project, I realized there must be a conflict between this chart value: https://github.com/opensearch-project/helm-charts/blob/086c52202c5755d504c6c3462720a57a86cc8998/charts/opensearch-dashboards/values.yaml#L8 and the function triggered by the DISABLE_SECURITY_DASHBOARDS_PLUGIN environment variable defined in the Docker image.
I don't know if it's desirable to update the templates to take those parameters into account or if only the documentation should be updated with a warning when using such variables...
Here is what I see as templates updates, but there must be a simpler way (I'm just a newbie with Helm 😅) :
opensearchHosts
should take a list of<host>:<port>
valuesdisableSecurityPlugin
boolean value should be added for bothopensearch
andopensearch-dashboards
http://
orhttps://
depending ondisableSecurityPlugin
value (example skeleton of helper function that should do the job: https://stackoverflow.com/a/49147648)DISABLE_INSTALL_DEMO_CONFIG
andDISABLE_SECURITY_PLUGIN
should be set to true in opensearch env ifdisableSecurityPlugin
istrue
DISABLE_SECURITY_DASHBOARDS_PLUGIN
should be set to true in opensearch-dashboards env ifdisableSecurityPlugin
istrue
Chart versions tested:
Corresponding Docker images:
But is seems even more recent versions might be affected...
Thanks in advance for your feedbacks 😉