Fix broken link (#9880)

* Fix broken link

* turned URL into clickable link

* Fixed the link
This commit is contained in:
Rupak Ganguly 2019-11-15 11:25:59 -05:00 committed by lena-larionova
parent c64bea3bba
commit 2c15849430
1 changed files with 1 additions and 2 deletions

View File

@ -296,8 +296,7 @@ nodes in the cluster at one time.
- Upgrade failures - Upgrade failures
- For worker nodes, an upgrade failure can be rolled back by changing the node label back - For worker nodes, an upgrade failure can be rolled back by changing the node label back
to the previous target version. Rollback of manager nodes is not supported. to the previous target version. Rollback of manager nodes is not supported.
- Kubernetes errors in node state messages after upgrading UCP - [Kubernetes errors in node state messages after upgrading UCP](https://success.docker.com/article/how-to-resolve-kubernetes-errors-after-upgrading-ucp)
(from https://github.com/docker/kbase/how-to-resolve-kubernetes-errors-after-upgrading-ucp/readme.md)
- The following information applies if you have upgraded to UCP 3.0.0 or newer: - The following information applies if you have upgraded to UCP 3.0.0 or newer:
- After performing a UCP upgrade from 2.2.x to 3.x.x, you might see unhealthy nodes in your UCP - After performing a UCP upgrade from 2.2.x to 3.x.x, you might see unhealthy nodes in your UCP
dashboard with any of the following errors listed: dashboard with any of the following errors listed: