Re: Marathon deployment without "blue/green" (need to free resources before deploying)

Thanks a lot! On 11/28/2017 02:44 PM, Tomek Janiszewski wrote: Hi It's described here https://mesosphere.github.io/marathon/docs/deployments.html#rolling-restarts > minimumHealthCapacity == 0 : All old instances can be killed before the new version is deployed. Best Tomek wt., 28 lis 2017

Re: Marathon deployment without "blue/green" (need to free resources before deploying)

Hi It's described here https://mesosphere.github.io/marathon/docs/deployments.html#rolling-restarts > minimumHealthCapacity == 0 : All old instances can be killed before the new version is deployed. Best Tomek wt., 28 lis 2017 o 14:42 użytkownik Adam Cecile napisał: > Hi

Marathon deployment without "blue/green" (need to free resources before deploying)

Hi there, We have a limited amount of GPU so when a new deployment occurs (replacing an existing one) in Marathon it gets locked because there's no GPUs left to deploy new version before killing the previous one. Is there any API parameter to force kill of the old instance first ? Thanks