Unable to connect to nodes about libcluster HOT 4 CLOSED

In your config/prod.exs, can you try changing:
kubernetes_selector: "tier=phishx-tier"
to
kubernetes_selector: "app=phishx-app"

Also what does the output of this command show?
kubectl get endpoints

from libcluster.

I think it worked, but I'm not sure.
How to start a pod with "console" as argument? If I try to change from "foreground" it crash.
I'm using "kubectl attach $POD" to see output. Is there any other command to gain access to IEX? (To test node connectivity, etc.)

NAME      ENDPOINTS                                         AGE
phishx    172.17.0.4:4000,172.17.0.5:4000,172.17.0.6:4000   4m

from libcluster.

I haven’t explored kubectl attach”. Generally during my development process I have Docker images built such a way that,containers do sleep to infinity. And then I start app in Kubernetes and then I go into containers via bash and launch application manually and see if it works as expected. Once that process is working I create Docker images to use either console or foreground options to start containers.

from libcluster.

You should start via foreground, and then use kubectl exec -it some-pod -- /bin/bash to connect to the pod and run bash. From there you can use bin/myapp remote_console to pop open IEx and interact with the running node. You can also use Erlang's ssh module to support ssh clients which connect directly to the Erlang shell, but personally I would use the first of my suggestions.

from libcluster.