From 7055a7efb3dbfee26956f2df710b5d47ab478754 Mon Sep 17 00:00:00 2001 From: kadtendulkar Date: Fri, 24 Jun 2022 21:58:44 +0530 Subject: [PATCH] Update content/en/docs/tasks/run-application/force-delete-stateful-set-pod.md --- .../docs/tasks/run-application/force-delete-stateful-set-pod.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/tasks/run-application/force-delete-stateful-set-pod.md b/content/en/docs/tasks/run-application/force-delete-stateful-set-pod.md index a4a145f5b4..dc8aef2857 100644 --- a/content/en/docs/tasks/run-application/force-delete-stateful-set-pod.md +++ b/content/en/docs/tasks/run-application/force-delete-stateful-set-pod.md @@ -51,7 +51,7 @@ Pods may also enter these states when the user attempts graceful deletion of a P on an unreachable Node. The only ways in which a Pod in such a state can be removed from the apiserver are as follows: -* The Node object is deleted (either by you, or by the [Node Controller](/docs/concepts/architecture/nodes/)). +* The Node object is deleted (either by you, or by the [Node Controller](/docs/concepts/architecture/nodes/#node-controller)). * The kubelet on the unresponsive Node starts responding, kills the Pod and removes the entry from the apiserver. * Force deletion of the Pod by the user.