From 280977ecf9b57b02f00f02cb1169d9f52cea4bcf Mon Sep 17 00:00:00 2001 From: Xiaoyu Zhang Date: Wed, 29 Mar 2017 06:07:54 +0800 Subject: [PATCH] Fix error link --- docs/user-guide/pods/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/user-guide/pods/index.md b/docs/user-guide/pods/index.md index 6b1119dc3b..82932a5de4 100644 --- a/docs/user-guide/pods/index.md +++ b/docs/user-guide/pods/index.md @@ -174,7 +174,7 @@ By default, all deletes are graceful within 30 seconds. The `kubectl delete` com Force deletion of a pod is defined as deletion of a pod from the cluster state and etcd immediately. When a force deletion is performed, the apiserver does not wait for confirmation from the kubelet that the pod has been terminated on the node it was running on. It removes the pod in the API immediately so a new pod can be created with the same name. On the node, pods that are set to terminate immediately will still be given a small grace period before being force killed. -Force deletions can be potentially dangerous for some pods and should be performed with caution. In case of StatefulSet pods, please refer to the task documentation for [deleting Pods from a StatefulSet](/docs/tasks/stateful-sets/deleting-pods/). +Force deletions can be potentially dangerous for some pods and should be performed with caution. In case of StatefulSet pods, please refer to the task documentation for [deleting Pods from a StatefulSet](/docs/tasks/manage-stateful-set/delete-pods/#deleting-pods). ## Privileged mode for pod containers