Hi, I’ve deployed my application, and livebook within kubernetes. I’m now trying to get livebook to work with remote execution against my running application, and I’m struggling to get the connection working. for the application: deployment has epmd port configured service for both web endpoints…

Exactly! You need RELEASE_DISTRIBUTION=name to use full node names with ip/domain, and that’s necessary to connect across nodes. Then, when you do Node.ping from Livebook, you want to use exactly the same node name as specified in RELEASE_NODE.

:wave: hi I don’t have that file, but if I go onto the node and look at the RELEASE env vars, I see this {"RELEASE_COOKIE", "..."}, {"RELEASE_REMOTE_VM_ARGS", "/app/releases/0.1.0/remote.vm.args"}, {"RELEASE_BOOT_SCRIPT", "start"}, {"RELEASE_VSN", "0.1.0"}, {"RELEASE_ENVIRONMENT", "produ…

I think your comment has started pointing me in the right way… I didn’t think I needed to follow all the clustering setup guides I had found so far, but it seems like I need to make changes, something like below, to make nodes connectable. {"RELEASE_NODE", "myapplication@[pod-ip]"}, {"RELEASE_DIST…

great, thanks for the confirmation. one question I have, specific to kubernetes setup. It would be much easier to connect in livebook based on a service name, and not a pod name. i.e With the setup from the last comment, each node will startup with a unique app-name-123-456-678@something.internal o…

Yeah, I think generally it would be app-name@[pod-ip-addr], and then you do a DNS lookup. Though, if you are running a single node, then RELEASE_NODE=app-name@something.internal should also work, as long as something.internal is resolvable from the Livebook pod : )

Elixir Programming Language Forum

LiveBook remote execution within Kubernetes

Questions & Help Questions

jonatanklosko April 13, 2025, 9:18am 2

Hey @duncanphillips, what RELEASE_NODE do you set in rel/env.sh.eex?