<p>We have a docker image and a corresponding yaml file for the deployment using kubernetes. The application we have built is in scala with akka-http. We have used akka-cluster. We have a particular variable(seed-nodes in our case - akka cluster) in the configuration file which is used in our application code that uses the pod ip. But, we will not get the pod ip unless the deployment is done. How should we go about tackling the issue? Will environment variables help, if yes how? </p>

<p>More specifically, Once the docker images is deployed in the container in a pod, and when the container starts, the pod ip is already assigned. So, can we programmatically or otherwise configure the pod ips in our code or config file before the process starts in the container?  </p>

<p>For reference, this is our configuration file : </p>

<pre><code>akka {
  actor {
    provider = "akka.cluster.ClusterActorRefProvider"
  }    
  remote {
    log-remote-lifecycle-events = off
    netty.tcp {
      hostname = "127.0.0.1"
      port = 0
    }
  }
  cluster {
    seed-nodes = [
      "akka.tcp://our-system@127.0.0.1:3000",
      "akka.tcp://our-system@127.0.0.1:3001",
    ],
    metrics {
      enabled = off
    }
  }    
}
service {
  validateTokenService {
     ml.pubkey.path = "&lt;filePath&gt;"
  }
  ml_repository {
    url = &lt;url address&gt;
  }
  replication.factor = 3
  http.service.interface = "0.0.0.0"
  http.service.port = 8080
}
</code></pre>

<p>In the above file, instead of having akka.remote.netty.tcp.hostname as "127.0.0.1", we need to have the pod-ip.
So, that we can use it in the seed nodes as : </p>

<pre><code>seed-nodes = [
          "akka.tcp://our-system@hostname:3000",
          "akka.tcp://our-system@hostname:3001",
        ],
</code></pre>

<p>How can we do so?
Thanks in advance.</p>

<p>As of 2018 the ideal way to initialize a Akka Cluster within kubernetes is the <a href="https://developer.lightbend.com/docs/akka-management/current/bootstrap/kubernetes.html" rel="nofollow noreferrer">akka-management</a>.</p>

<p>It uses the Kubernetes API to fetch a list of all running pods and bootstrap the cluster.
There's no need to configure any seed nodes.</p>

<p>It does also provice a readiness check that waits until the pod has joined the cluster. And a alive check.</p>
