I have a deployment that consists on one Job that contains two containers. Due to distribution and economical reasons, I want these two containers to be deployed independently. However, they are still interconnected. This means there should be network communication between both of them.
As far as I know, you can not create a Service over a Job. You need it to be at least a simple Pod. However, this adds another element and modifies the equation: I want to split the Job into two Jobs, not into one Job, one Pod and one Service.
So, with this as context, is there a way to connect to Jobs directly without creating a service? They both are going to be on the same cluster, using the same internal DNS, in different machines.
Basically, something like, from Job1, connect to job1.job1namespace:8080.