Thanks, Gene, now I got it previously I already tried with load balancer but at that time I was using single instance mode, that why it did not work when I run two tinode servers,
now I run with cluster mode in Kubernetes , I updated config file like this :
"cluster_config": {
// Name of this node. Can be assigned from the command line as --cluster_self.
// Empty string disables clustering.
"self": "tinode-1",
// List of available nodes.
"nodes": [
// Name and TCP address of every node in the cluster. The ports 12001..12003
// are cluster communication ports. They don't need to be exposed to end-users.
{"name": "tinode-1", "addr": "tinode-1.tinode.svc.cluster.local:12001"}
],
Now I just run only one server with cluster mode, but seems like have some issues, this is a private link for tinode-1 ("tinode-1.tinode.svc.cluster.local:12001")
When I check log I see a connection fail error for tinode-1 ""error: unable to upgrade connection: container not found ("tinode-1")""
error may be I don't know try to call that endpoint but at that time, the service is not ready yet.
I already tryed with docker-compose , it is working fine, having issue in Kubernetes
Thanks