If you cannot prefix the cluster id at the start of the URL, then you need an nginx or similar in the middle that can inject the header X-Found-Cluster: <GUID>, otherwise the ECE proxy does not know where to send the traffic.
But then why does it work when we have a CNAME to the GUID hostname.
The CNAME does not get added to any headers by default.
This also breaks if you place another CNAME in between.
Ex: CNAME Backup-test -> CNAME Test -> GUID Does not work
Can we have a feature request to add a function to add a specific hostname to a cluster in ECE.
Sort of you are also hostname: INSERT_GOOD_NAME_HERE
There are some annotations that point to xpack.security.public being the solution but the above setup does not work with our nginx.
The nginx is configured to pass all 443 to 9200 on the eceproxys.
But then why does it work when we have a CNAME to the GUID hostname
@tehho There's a bunch of places (headers, Host: header, URL) where we search for a GUID
I haven't specifically looked to see where cname gets embedded in the HTTP request, but if it works then it must be one of the above
Can we have a feature request to add a function to add a specific hostname to a cluster in ECE.
We have such a feature on our roadmap - it's often requested! It's been blocked by a larger change to the proxy architecture. That's mostly done so it should get moving again soon.
There are some annotations that point to xpack.security.public
Not sure what this does, but there's a pretty standard nginx config to do what you state, something along the lines of:
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.