We are able to deploy Temporal cluster to kubernetes clusters, however the membership ring (of history service and matcher service) can only be configured to work within the same kubernete cluster. The membership communication seems to be rely on the broadcastAddress configured (https://docs.temporal.io/docs/server/configuration#membership) and it only allows IP address.
We would prefer strong availability over multiple kubernetes clusters. In particular, we would have a distributed database (e.g. Cassandra) cluster deployed across DC, and have Temporal cluster deployed on different kubernete clusters across DC but using same Cassandra cluster, thereby achieving cross-DC availability.
Is there any plan to support above mentioned features?