He isn't performing a rolling upgrade; he just wants to drain a node one
pod at a time.
On 21. 04. 2017 09:18, Michail Kargakis wrote:
If you used those settings and it wasn't honoured then it's a bug.
On Fri, Apr 21, 2017 at 1:38 AM, Andrew Lau <[email protected]
<mailto:[email protected]>> wrote:
I didn't think this was honoured as it just deletes the pods?
On Thu, 20 Apr 2017 at 18:43 Michail Kargakis <[email protected]
<mailto:[email protected]>> wrote:
If you want to scale up first and wait for the new pod to come
up before deleting the old use maxSurge=1, maxUnavailable=0
On Thu, Apr 20, 2017 at 10:11 AM, Andrew Lau
<[email protected] <mailto:[email protected]>> 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
[email protected]
<mailto:[email protected]>
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
<http://lists.openshift.redhat.com/openshiftmm/listinfo/users>
_______________________________________________
users mailing list
[email protected]
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
_______________________________________________
users mailing list
[email protected]
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
