From 10b4afe20f0af0b0d81232a67300738e9550d2e3 Mon Sep 17 00:00:00 2001 From: Xiaoyu Zhang Date: Sat, 15 Apr 2017 07:33:05 +0800 Subject: [PATCH] Fix broken link:determine-reason-pod-failure.md Fix broken link:determine-reason-pod-failure.md --- .../debug-application-cluster/determine-reason-pod-failure.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/tasks/debug-application-cluster/determine-reason-pod-failure.md b/docs/tasks/debug-application-cluster/determine-reason-pod-failure.md index 41a8c27abc..0acc268276 100644 --- a/docs/tasks/debug-application-cluster/determine-reason-pod-failure.md +++ b/docs/tasks/debug-application-cluster/determine-reason-pod-failure.md @@ -13,7 +13,7 @@ be easily retrieved and surfaced by tools like dashboards and monitoring software. In most cases, information that you put in a termination message should also be written to the general -[Kubernetes logs](/docs/user-guide/logging/). +[Kubernetes logs](/docs/concepts/cluster-administration/logging/). {% endcapture %}