From 2c1584943048bfba5a5a3d902cee9c32853c8d4c Mon Sep 17 00:00:00 2001 From: Rupak Ganguly Date: Fri, 15 Nov 2019 11:25:59 -0500 Subject: [PATCH] Fix broken link (#9880) * Fix broken link * turned URL into clickable link * Fixed the link --- ee/ucp/admin/install/upgrade.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/ee/ucp/admin/install/upgrade.md b/ee/ucp/admin/install/upgrade.md index 3de1547b35..72b0a1cfdc 100644 --- a/ee/ucp/admin/install/upgrade.md +++ b/ee/ucp/admin/install/upgrade.md @@ -296,8 +296,7 @@ nodes in the cluster at one time. - Upgrade failures - 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. -- Kubernetes errors in node state messages after upgrading UCP -(from https://github.com/docker/kbase/how-to-resolve-kubernetes-errors-after-upgrading-ucp/readme.md) +- [Kubernetes errors in node state messages after upgrading UCP](https://success.docker.com/article/how-to-resolve-kubernetes-errors-after-upgrading-ucp) - 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 dashboard with any of the following errors listed: