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

Merge pull request #9465 from traci-morrison/engdocs-162 

Fix broken links
This commit is contained in:
Traci Morrison 2019-09-23 10:27:16 -04:00 committed by GitHub
parent a556c61cf7 cfc9a64b8c
commit 132f2bed14
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
ee/ucp/admin/install/upgrade.md
View File

@ -80,7 +80,7 @@ with a new worker node. The type of upgrade you perform depends on what is neede
- Manual cluster upgrade: Performed using the CLI or the UCP UI. Automatically upgrades manager
nodes and allows you to control the upgrade order of worker nodes. This type of upgrade is more
advanced than the automated, in-place cluster upgrade.
- [Upgrade existing nodes in place](#upgrade-existing-nodes-in-place): Performed using the CLI.
- [Upgrade existing nodes in place](#phased-in-place-cluster-upgrade): Performed using the CLI.
Automatically upgrades manager nodes and allows you to control the order of worker node upgrades.
- [Replace all worker nodes using blue-green deployment](#replace-existing-worker-nodes-using-blue-green-deployment):
Performed using the CLI. This type of upgrade allows you to
@ -95,7 +95,7 @@ with a new worker node. The type of upgrade you perform depends on what is neede
Before starting an upgrade, make sure that your cluster is healthy. If a problem
occurs, this makes it easier to find and troubleshoot it.
[Create a backup](/ee/ucp/admin/backup/) of your cluster.
[Create a backup](/ee/admin/backup/back-up-ucp/) of your cluster.
This allows you to recover if something goes wrong during the upgrade process.
> The backup archive is version-specific, so you can't use it during the
@ -128,7 +128,7 @@ manager node. Automatically upgrades the entire cluster.
- Manual cluster upgrade: Performed using the CLI or the UCP UI. Automatically upgrades manager
nodes and allows you to control the upgrade order of worker nodes. This type of upgrade is more
advanced than the automated, in-place cluster upgrade.
- [Upgrade existing nodes in place](#upgrade-existing-nodes-in-place): Performed using the CLI.
- [Upgrade existing nodes in place](#phased-in-place-cluster-upgrade): Performed using the CLI.
Automatically upgrades manager nodes and allows you to control the order of worker node upgrades.
- [Replace all worker nodes using blue-green deployment](#replace-existing-worker-nodes-using-blue-green-deployment):
Performed using the CLI. This type of upgrade allows you to