Take a look at PodDisruptionBudget. It allows you to specify the minimum
number of pods that must be kept running when removing pods voluntarily
(draining nodes is an example of this). But this feature may not be in
OpenShift yet (IIRC draining nodes in Kubernetes honors the
PodDisruptionBudget from version 1.6 onwards).
On 20. 04. 2017 10:11, Andrew Lau wrote:
Is there any way to evacuate a node using the rolling deployment
process where a the new pod can start up first before being deleted
from the current node?
Drain seems to only delete the pod straight away. If there is a grace
period set, it would be nice if the new pod could atleast have its
image pulled into a new node first before being deleted from the
drained more.
_______________________________________________
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
_______________________________________________
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
