This PR updates the helm chart to conditionally include the Elasticsearch username and password in the command for the check-elasticsearch, check-elasticsearch-index, and create-elasticsearch-index containers.
Why?
These changes were made to allow the helm chart to be used in situations where the Elasticsearch instance does not require authentication. For example Opensearch is in a private network and doesn't have fine-grained auth in place. (If we pass any arbitrary/default username and password we will get 403)
Checklist
How was this tested:
test these changes by deploying the helm chart to a Kubernetes cluster with an Elasticsearch instance that does not require authentication, to ensure that the commands run successfully without the --user flag. Additionally, tested by deploying to a cluster with an Elasticsearch instance that does require authentication, to verify that the --user flag is properly included when needed.
What was changed
This PR updates the helm chart to conditionally include the Elasticsearch username and password in the
command
for thecheck-elasticsearch
,check-elasticsearch-index
, andcreate-elasticsearch-index
containers.Why?
These changes were made to allow the helm chart to be used in situations where the Elasticsearch instance does not require authentication. For example Opensearch is in a private network and doesn't have fine-grained auth in place. (If we pass any arbitrary/default username and password we will get 403)
Checklist
--user
flag. Additionally, tested by deploying to a cluster with an Elasticsearch instance that does require authentication, to verify that the--user
flag is properly included when needed.