<p>I have a 3 node system, on which I have hosted a basic ArangoDB cluster having 3 dbservers. I am using Python-arango library, which says that to connect to the clusters, we need to supply the list of IPs with the port 8529 to ArangoClient class.My Python code is running in a different pod.</p>
<p>Using Arangosh, I can access the coordinator pods using localhost:8529 configuration. However, on Arangosh, I can only access one coordinator pod at once. Since the Arango arrangement is a cluster, I would want to connect to all three coordinator pods at once in a roundrobin manner. Now as per the Kubernetes documentation in case of <a href="https://kubernetes.io/blog/2017/01/running-mongodb-on-kubernetes-with-statefulsets/" rel="nofollow noreferrer">MongoDB</a>, I can supply the list of the &lt;pod_name.service_name&gt; to the MongoClient and it would get connected. I am trying something similar with the Arango coordinator pods, but that does not seem to work. The examples in Arango documentation only point to writing 'localhost-1','localhost-2', etc.</p>
<p>To summarize, the issue in hand is that I do not know how to identify the IP of the Arango coordinator pods. I tried using the internal IPs of the coordinators, I tried using the <em>http://pod_name.8529</em> and I have tried using the end point of the coordinator that shows in the Web UI (which begins with ssl, but I had replaced ssl with http) and yet got no success.</p>
<p>Would be grateful for any help in this context. Please let me know if some additional information is needed. Am stuck with this problem since a week now.</p>

<p>if you follow this : <a href="https://www.arangodb.com/2018/12/deploying-arangodb-3-4-on-kubernetes/" rel="nofollow noreferrer">https://www.arangodb.com/2018/12/deploying-arangodb-3-4-on-kubernetes/</a></p>
<p>there is YAML config files it's creating multiple PODs. How your application should be connecting with ArragoDB is using the <code>Kubernetes service</code>.</p>
<p>So your application will be connecting to Kubernetes service and by default kubernets service manage the RoundRobin load balancing.</p>
<p>in example you can see it's creating three services</p>
<pre><code>my-arangodb-cluster          ClusterIP      10.11.247.191   &lt;none&gt;           8529/TCP         46m
my-arangodb-cluster-ea       LoadBalancer   10.11.241.253   35.239.220.180   8529:31194/TCP   46m
my-arangodb-cluster-int      ClusterIP      None            &lt;none&gt;           8529/TCP         46m
</code></pre>
<p>service <code>my-arangodb-cluster-ea</code> publicly open. While service <code>my-arangodb-cluster</code> can be accessed internally using the application.</p>
<p>Your flow will be something like</p>
<pre><code>Application &gt; Arango service (Round robin) &gt; Arango Pods   
</code></pre>
