The default deployment strategy was explained in another thread:
What I would like to see instead is an option, or a new default, where once the canary succeeds and replaces the instance it was meant to replace, a new instance is booted up and the old instance is taken down after the new instance is running and health checks are passing.
This was how I had docker swarm configured (using the
update-order: start-first flag). This prevents an issue where a client connected to a killed instance gets booted off to a) an instance in a further-away region, and/or b) an instance that is about to be killed as the rolling deployment progresses.
Probably not the hugest deal, but a nice-to-have…