AKS Cross-Cluster-Replication using Azure Load Balancer

[mrvdcsg]

I hope someone can point me in the right direction. I'm running OS in AKS for my "Master" cluster and I'm running remote "Follower" clusters that have access to Azure using an express-route. However, I am trying to set up cross-cluster-replication and I have exposed 9300 to internal traffic through an Azure Load Balancer. The traffic makes it to the master nodes but then switches to the AKS internal kubenet address of the master node which isn't externally routable. All the examples I can find use cross-cluster-replication use multiple clusters on the same Kubernetes cluster so the traffic can natively go over kubenet without issues.

How do I make Opensearch recognize the DNS used for my loadbalancer (certificates are all correct for admin certs and http) instead of switching to internal IP address?

Has anyone used Cross-cluster-replication outside of the same kube cluters?

Any help appreciated!

[mrvdcsg]

This should be resolved using the newer features allowing for definition of remote clusters by proxy rather than seed ip. This isn't fully tested yet but initial tests appear successful.

Seed Example

PUT /_cluster/settings?pretty
{
  "persistent": {
    "cluster": {
      "remote": {
        "master": {
          "seeds": ["10.10.10.10:9300"]
        }
      }
    }
  }
}

Proxy Example

PUT /_cluster/settings?pretty
{
  "persistent": {
    "cluster": {
      "remote": {
        "master": {
          "mode": "proxy",
          "proxy_address": "my_dns_name_for_azureLB.com:9300"
        }
      }
    }
  }

}