From 219b8f07a77b7a9e031883934aa9f710aaa86001 Mon Sep 17 00:00:00 2001
From: shub-asa1 <48909477+shub-asa1@users.noreply.github.com>
Date: Fri, 19 Apr 2019 06:33:54 +0530
Subject: [PATCH] updated link for this guide (#13870)

fixed the invalid link referred by "this guide" in "In Kubernetes v1.11.0 and later, you can use kubeadm upgrade diff to see the changes that would be applied to static pod manifests."
this is fix for issue #13869
---
 .../en/docs/reference/setup-tools/kubeadm/kubeadm-upgrade.md    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/docs/reference/setup-tools/kubeadm/kubeadm-upgrade.md b/content/en/docs/reference/setup-tools/kubeadm/kubeadm-upgrade.md
index b525a62edc..5c2300214b 100644
--- a/content/en/docs/reference/setup-tools/kubeadm/kubeadm-upgrade.md
+++ b/content/en/docs/reference/setup-tools/kubeadm/kubeadm-upgrade.md
@@ -28,7 +28,7 @@ _For older versions, please refer to older documentation sets on the Kubernetes
 In Kubernetes v1.11.0 and later, you can use `kubeadm upgrade diff` to see the changes that would be
 applied to static pod manifests.
 
-To use kube-dns with upgrades in Kubernetes v1.13.0 and later please follow [this guide](docs/reference/setup-tools/kubeadm/kubeadm-init-phase/#cmd-phase-addon).
+To use kube-dns with upgrades in Kubernetes v1.13.0 and later please follow [this guide](/docs/reference/setup-tools/kubeadm/kubeadm-init-phase/#cmd-phase-addon).
 
 ## kubeadm upgrade plan {#cmd-upgrade-plan}
 {{< include "generated/kubeadm_upgrade_plan.md" >}}