<p>I would like to run Aerospike cluster on Docker containers managed by Kubernetes on CoreOS on Google Compute Engine (GCE). But since GCE does not permit multicast, I have to use Mesh heartbeat as described <a href="http://www.aerospike.com/docs/operations/configure/network/heartbeat/#mesh-unicast-heartbeat" rel="nofollow">here</a>, which has to be set up by specifying all node's IP addresses and ports; it seems so inflexible to me.</p>

<p>Is there any recommended cloud-config settings for Aerospike cluster on Kubernetes/CoreOS/GCE with flexibility of the cluster being kept?</p>

<p>An alternative to specifying all mesh seed IP addresses is to use <code>the asinfo tip command</code>.</p>

<p>Please see:</p>

<p><a href="http://www.aerospike.com/docs/reference/info/#tip" rel="noreferrer">http://www.aerospike.com/docs/reference/info/#tip</a></p>

<p>the tip command</p>

<pre><code>asinfo -v 'tip:host=172.16.121.138;port=3002'
</code></pre>

<p>The above command could be added to a script or orchestration tool with correct ips.</p>

<p>You may also find addtional info on the aerospike Forum:</p>

<p><a href="https://discuss.aerospike.com/" rel="noreferrer">Aerospike Forum</a></p>
