From 6f0de11cc38a76bf6675c903c8b47f3e256ecf9f Mon Sep 17 00:00:00 2001
From: "xin.li" <xin.li@daocloud.io>
Date: Mon, 18 Apr 2022 23:25:13 +0800
Subject: [PATCH] [zh] Update  debug-pod-replication-controller.md

Signed-off-by: xin.li <xin.li@daocloud.io>
---
 .../determine-reason-pod-failure.md                      | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/content/zh/docs/tasks/debug-application-cluster/determine-reason-pod-failure.md b/content/zh/docs/tasks/debug-application-cluster/determine-reason-pod-failure.md
index 19f29d781b..db2bdae03c 100644
--- a/content/zh/docs/tasks/debug-application-cluster/determine-reason-pod-failure.md
+++ b/content/zh/docs/tasks/debug-application-cluster/determine-reason-pod-failure.md
@@ -99,6 +99,15 @@ the container starts.
    ```shell
    kubectl get pod termination-demo -o go-template="{{range .status.containerStatuses}}{{.lastState.terminated.message}}{{end}}"
    ```
+   
+<!
+If you are running a multi-container pod, you can use a Go template to include the container's name. By doing so, you can discover which of the containers is failing:
+-->
+如果你正在运行多容器 Pod，则可以使用 Go 模板来包含容器的名称。这样，你可以发现哪些容器出现故障:
+
+```shell
+kubectl get pod multi-container-pod -o go-template='{{range .status.containerStatuses}}{{printf "%s:\n%s\n\n" .name .lastState.terminated.message}}{{end}}'
+```
 
 <!--
 ## Customizing the termination message