From my testing, it appears you cannot use publish_port in a Transport profile. In my case, I need Elasticsearch to be accessible via a local port that I specify and perform a port forward with (Ex.50000) (I query this from another node using cross cluster search) AND I need to be able to have another node connect to my Elasticsearch instance from external.
I tried doing this with transport profiles likes so:
transport.profiles.internal.bind_host: 172.18.0.1
transport.profiles.internal.port: 50000
transport.profiles.external.publish_host: 192.168.1.5
The external node is able to connect and join the cluster, etc, but my cross cluster node cannot query this node -- the CCS node's _cluster/settings are configured to query 172.18.0.1:50000
The CCS portion works if I do:
transport.bind_host: 0.0.0.0
transport.publish_host: 172.18.0.1
transport.publish_port: 50000
The problem comes when I try to combine the two.
Logically, I would like for the transport profiles to work like:
transport.profiles.internal.bind_host: 0.0.0.0
transport.profiles.internal.port: 9300
transport.profiles.internal.publish_host: 172.18.0.1
transport.profiles.internal.publish_port: 50000
Is something like this possible?
Thanks,
Cappy