Network endpoints are disabled after container in a Job pod exits and sidecar container is still running

4/4/2019

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

While the worker container is active, the sidecar container REST API functions as expected.

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.

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?

-- arosca
kubernetes

1 Answer

4/5/2019
-- Rick Rackow
Source: StackOverflow