You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Stack updates should support rollback of the entire stack in cases where some of the service update fails.
Currently the docker stack deploy command offers the ability to automatically rollback failing service via the deploy -> update_config -> failure_action configuration but the rollback action is applied on a service by service basis.
If only some of the services fails during an update the above behaviour will rollback the failing services but update the healthy ones leaving the stack in an inconsistent state.
Furthermore the stack update is done non-interactively meaning that the only way to detect inconsistent state after an update is to actively monitor the state of all services in the stack and try to reconcile it with their respective desired state.
Stack updates should support rollback of the entire stack in cases where some of the service update fails.
Currently the docker stack deploy command offers the ability to automatically rollback failing service via the deploy -> update_config -> failure_action configuration but the rollback action is applied on a service by service basis.
If only some of the services fails during an update the above behaviour will rollback the failing services but update the healthy ones leaving the stack in an inconsistent state.
Furthermore the stack update is done non-interactively meaning that the only way to detect inconsistent state after an update is to actively monitor the state of all services in the stack and try to reconcile it with their respective desired state.
Moved from moby/moby#34712
The text was updated successfully, but these errors were encountered: