<p>I have a Job pod with two containers, <em>worker</em> and <em>sidecar</em>. The sidecar container exposes a REST API via a service.</p>

<p>While the worker container is active, the sidecar container REST API functions as expected.</p>

<p>However, after the worker completes/exits, the sidecar is no longer reachable. I was able to determine that the network endpoints become disabled once the worker container exits.</p>

<p>Is it possible to configure the pod such that the network endpoints remain active as long as there are still containers running in the pod?</p>

arosca
<p>This is expected behaviour as of <a href="https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/#job-termination-and-cleanup" rel="nofollow noreferrer">https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/#job-termination-and-cleanup</a>.</p>
