docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update upgrade.md

This commit is contained in:
Anne Henmi 2018-11-07 08:14:11 -08:00 committed by GitHub
parent 0d9aebc863
commit ec8c9888d3
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
ee/upgrade.md
View File

@ -20,7 +20,7 @@ Docker Engine - Enterprise upgrades in Swarm clusters should follow these guidel
space exhaustion and associated application downtime.
* New workloads should not be actively scheduled in the cluster during upgrades.
* Differences in the major (X.y.z.) or minor (x.Y.z) version numbers between the managers and workers can cause mismatches between managers and workers can cause unintended consequences when new workloads are scheduled.
* Differences in the major (X.y.z.) or minor (x.Y.z) version numbers between the managers and workers can cause unintended consequences when new workloads are scheduled.
* Manager nodes should all be upgraded first before upgrading worker nodes. Upgrading manager nodes sequentially is recommended if live workloads are running in the cluster during the upgrade.
* Once manager nodes are upgraded worker nodes should be upgraded next and then the Swarm cluster upgrade is complete.
* If running UCP, the UCP upgrade should follow once all of the Swarm engines have been upgraded.