Stop and restart same container currently not possible

[benbierens]

We can BringOffline some nodes, and then BringOnline again on the same object... BUT!
The underlying containers will be disposed after BringOffline. And new instances will be created afterwards.

What if we want a test in which the same node goes dark for a while, then comes back? The container (+ its filesystem) will need to survive.

Investigate and implement a way to make this happen. Change the BringOnline/BringOffline terminology to more clearly reflect when a node and all of its state is being destroyed.

[veaceslavdoina]

BringOnline/BringOffline is about testing framework actions?

When we run a Pod we can use Persistent Volumes to persist its data during restarts.
If BringOffline means deleting Deployment and BringOnline recreate it back, we may re-use previous Deployment PVC and mount it and data will be in place.

[veaceslavdoina]

We can probably set Replicas = 0 and then return back to 1.