Containerized Jobs from automation nodes give connection refused errors

DrissiReda Registered Posts: 57 ✭✭✭✭✭
edited July 16 in Using Dataiku

I'm running a design and an automation node.

I execute all of my recipe workloads in a kubernetes cluster.

When I launch a project's visual recipe from the design node. It works well, the job is launched in kubernetes and is successful.

Does this mean I need to open more ports on the Design node? Is there any way to overwrite the port range?
What limitations would I face if I limit it to 10 or less ports?

When I launch the same visual recipe from the same project from the automation node I get the following error:

Connect to dataiku-0.dataiku.processing.svc.cluster.local:35543 [dataiku-0.dataiku.processing.svc.cluster.local/] failed: Connection refused (Connection refused), caused by: ConnectException: Connection refused (Connection refused)

The configuration is the same between the automation and design nodes.

The whole output is attached.


Setup Info
      Help me…