Hi community, I ran into an issue with the helm chart, where it defaults to appending

:9200

(the port) to the elastic URI, although the AWS ElasticSeararch doesn't work that way (it's reached just

<https://elastic-host.domain.com>

without the port). This causes the elasticearch init-job to fail,

2021/07/22 143855 Waiting for: https://myuser:mypassword@search-mydomain.eu-central-1.es.amazonaws.com:9200

I got past this step by setting it to yaml null, `~`:

global:
    elasticsearch:
        port: ~

However, gms does not heed the port variable, and continues to use

:9200

(same log as above). Are there some env vars I can set on GMS to make it not append a port?

Thanks for reporting this @rapid-sundown-8805 and for filing the issue. We'll get to it 🙂

Seems this can be resolved by using the TLS port, "443"