whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

add zh pages

Browse Source
This commit is contained in:
Karen Bradshaw
2020-06-01 09:23:39 -04:00
parent 21fd0a12f9
commit 4b35d4d401
303 changed files with 2764 additions and 2439 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/zh/docs/tasks/debug-application-cluster/audit.md
+5 -5
View File
@@ -3,11 +3,11 @@ reviewers:
- soltysh
- sttts
- ericchiang
content_template: templates/concept
content_type: concept
title: Auditing
---
{{% capture overview %}}
<!-- overview -->
{{< feature-state state="beta" >}}
@@ -37,11 +37,11 @@ Kubernetes 审计功能提供了与安全相关的按时间顺序排列的记录
- 它从哪触发的？
- 活动的后续处理行为是什么？
{{% /capture %}}
{{< toc >}}
{{% capture body %}}
<!-- body -->
<!--
[Kube-apiserver][kube-apiserver] performs auditing. Each request on each stage
@@ -609,4 +609,4 @@ Kubernetes 可能会在创建新的日志文件时删除旧的日志文件; 您
[logstash_install_doc]: https://www.elastic.co/guide/en/logstash/current/installing-logstash.html
[kube-aggregator]: /docs/concepts/api-extension/apiserver-aggregation
{{% /capture %}}
content/zh/docs/tasks/debug-application-cluster/crictl.md
+11 -10
View File
@@ -4,7 +4,7 @@ reviewers:
- feiskyer
- mrunalp
title: 使用 crictl 对 Kubernetes 节点进行调试
content_template: templates/task
content_type: task
---
<!--
@@ -14,12 +14,12 @@ reviewers:
- feiskyer
- mrunalp
title: Debugging Kubernetes nodes with crictl
content_template: templates/task
content_type: task
---
-->
{{% capture overview %}}
<!-- overview -->
{{< feature-state for_k8s_version="v1.11" state="stable" >}}
@@ -34,9 +34,10 @@ Kubernetes node. `crictl` and its source are hosted in the
您可以使用它来检查和调试 Kubernetes 节点上的容器运行时和应用程序。
`crictl`和它的源代码在 [cri-tools](https://github.com/kubernetes-incubator/cri-tools) 代码库。
{{% /capture %}}
{{% capture prerequisites %}}
## {{% heading "prerequisites" %}}
<!--
`crictl` requires a Linux operating system with a CRI runtime.
@@ -44,9 +45,9 @@ Kubernetes node. `crictl` and its source are hosted in the
`crictl` 需要带有 CRI 运行时的 Linux 操作系统。
{{% /capture %}}
{{% capture steps %}}
<!-- steps -->
<!--
## Installing crictl
@@ -473,10 +474,10 @@ CONTAINER ID IMAGE CREATED STATE
3e025dd50a72d busybox About a minute ago Running busybox 0
```
{{% /capture %}}
{{% capture discussion %}}
<!-- discussion -->
<!--
See [kubernetes-incubator/cri-tools](https://github.com/kubernetes-incubator/cri-tools)
@@ -485,4 +486,4 @@ for more information.
更多信息请参考 [kubernetes-incubator/cri-tools](https://github.com/kubernetes-incubator/cri-tools)。
{{% /capture %}}
content/zh/docs/tasks/debug-application-cluster/debug-application-introspection.md
+8 -7
View File
@@ -2,11 +2,11 @@
reviewers:
- janetkuo
- thockin
content_template: templates/concept
content_type: concept
title: 应用自测与调试
---
{{% capture overview %}}
<!-- overview -->
<!--
Once your application is running, you'll inevitably need to debug problems with it.
@@ -17,10 +17,10 @@ your pods. But there are a number of ways to get even more information about you
前面我们介绍了如何使用 `kubectl get pods` 来查询 pod 的简单信息。
除此之外，还有一系列的方法来获取应用的更详细信息。
{{% /capture %}}
{{% capture body %}}
<!-- body -->
<!--
## Using `kubectl describe pod` to fetch details about pods
@@ -518,9 +518,10 @@ status:
systemUUID: ABE5F6B4-D44B-108B-C46A-24CCE16C8B6E
```
{{% /capture %}}
{{% capture whatsnext %}}
## {{% heading "whatsnext" %}}
<!--
Learn about additional debugging tools, including:
@@ -542,4 +543,4 @@ Learn about additional debugging tools, including:
* [使用端口转发连接容器](/docs/tasks/access-application-cluster/port-forward-access-application-cluster/)
* [使用 crictl 检查节点](/docs/tasks/debug-application-cluster/crictl/)
{{% /capture %}}
content/zh/docs/tasks/debug-application-cluster/debug-init-containers.md
+11 -10
View File
@@ -8,7 +8,7 @@ reviewers:
- kow3ns
- smarterclayton
title: 调试 Init 容器
content_template: templates/task
content_type: task
---
<!--
@@ -22,11 +22,11 @@ reviewers:
- kow3ns
- smarterclayton
title: Debug Init Containers
content_template: templates/task
content_type: task
---
-->
{{% capture overview %}}
<!-- overview -->
<!--
This page shows how to investigate problems related to the execution of
@@ -38,9 +38,10 @@ Init Containers. The example command lines below refer to the Pod as
此页显示如何核查与 init 容器执行相关的问题。
下面的示例命令行将 Pod 称为 `<pod-name>`，而 init 容器称为 `<init-container-1>` 和 `<init-container-2>`。
{{% /capture %}}
{{% capture prerequisites %}}
## {{% heading "prerequisites" %}}
{{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}
@@ -53,9 +54,9 @@ Init Containers. The example command lines below refer to the Pod as
* 您应该熟悉 [Init 容器](/docs/concepts/abstractions/init-containers/)的基础知识。
* 您应该已经[配置好一个 Init 容器](/docs/tasks/configure-pod-container/configure-pod-initialization/#creating-a-pod-that-has-an-init-container/)。
{{% /capture %}}
{{% capture steps %}}
<!-- steps -->
<!--
## Checking the status of Init Containers
@@ -183,9 +184,9 @@ commands as they're executed. For example, you can do this in Bash by running
运行 shell 脚本打印命令的init容器,执行 shell 脚本。
例如，您可以在 Bash 中通过在脚本的开头运行 `set -x` 来实现。
{{% /capture %}}
{{% capture discussion %}}
<!-- discussion -->
<!--
## Understanding Pod status
@@ -220,5 +221,5 @@ Status | Meaning
`Pending` | Pod 还没有开始执行 Init 容器。
`PodInitializing` or `Running` | Pod 已经完成执行 Init 容器。
{{% /capture %}}
content/zh/docs/tasks/debug-application-cluster/debug-pod-replication-controller.md
+9 -8
View File
@@ -2,27 +2,28 @@
reviewers:
- bprashanth
title: 调试 Pods 和 Replication Controllers
content_template: templates/task
content_type: task
---
<!--
---
reviewers:
- bprashanth
title: Debug Pods and ReplicationControllers
content_template: templates/task
content_type: task
---
-->
{{% capture overview %}}
<!-- overview -->
<!--
This page shows how to debug Pods and ReplicationControllers.
-->
此页面告诉您如何调试 Pod 和 ReplicationController。
{{% /capture %}}
{{% capture prerequisites %}}
## {{% heading "prerequisites" %}}
{{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}
@@ -33,9 +34,9 @@ This page shows how to debug Pods and ReplicationControllers.
* 您应该先熟悉
[Pods](/docs/concepts/workloads/pods/pod/) 和 [Pod Lifecycle](/docs/concepts/workloads/pods/pod-lifecycle/) 的基础概念。
{{% /capture %}}
{{% capture steps %}}
<!-- steps -->
<!--
## Debugging Pods
@@ -247,4 +248,4 @@ related to the replication controller.
-->
您也可以使用`kubectl describe rc ${CONTROLLER_NAME}`来检查和Replication Controllers有关的事件。
{{% /capture %}}
content/zh/docs/tasks/debug-application-cluster/debug-service.md
+9 -8
View File
@@ -2,7 +2,7 @@
reviewers:
- thockin
- bowei
content_template: templates/concept
content_type: concept
title: 调试 Service
---
@@ -11,12 +11,12 @@ title: 调试 Service
reviewers:
- thockin
- bowei
content_template: templates/concept
content_type: concept
title: Debug Services
---
-->
{{% capture overview %}}
<!-- overview -->
<!--
An issue that comes up rather frequently for new installations of Kubernetes is
that a `Service` is not working properly. You've run your `Deployment` and
@@ -25,10 +25,10 @@ This document will hopefully help you to figure out what's going wrong.
-->
对于新安装的 Kubernetes，经常出现的一个问题是 `Service` 没有正常工作。如果您已经运行了 `Deployment` 并创建了一个 `Service`，但是当您尝试访问它时没有得到响应，希望这份文档能帮助您找出问题所在。
{{% /capture %}}
{{% capture body %}}
<!-- body -->
<!--
## Conventions
@@ -1167,14 +1167,15 @@ Contact us on
使用 [Slack](/docs/troubleshooting/#slack) 或者 [Forum](https://discuss.kubernetes.io) 或者 [GitHub](https://github.com/kubernetes/kubernetes) 联系我们。
{{% /capture %}}
{{% capture whatsnext %}}
## {{% heading "whatsnext" %}}
<!--
Visit [troubleshooting document](/docs/troubleshooting/) for more information.
-->
访问[故障排查文档](/docs/troubleshooting/)获取更多信息。
{{% /capture %}}
content/zh/docs/tasks/debug-application-cluster/debug-stateful-set.md
+11 -9
View File
@@ -1,23 +1,24 @@
---
title: 调试StatefulSet
content_template: templates/task
content_type: task
---
{{% capture overview %}}
<!-- overview -->
此任务展示如何调试StatefulSet。
{{% /capture %}}
{{% capture prerequisites %}}
## {{% heading "prerequisites" %}}
* 你需要有一个Kubernetes集群，通过必要的配置使kubectl命令行工具与您的集群进行通信。
* 你应该有一个运行中的StatefulSet，以便用于调试。
{{% /capture %}}
{{% capture steps %}}
<!-- steps -->
## 调试StatefulSet
@@ -67,12 +68,13 @@ spec:
kubectl annotate pods <pod-name> pod.alpha.kubernetes.io/initialized="true" --overwrite
```
{{% /capture %}}
{{% capture whatsnext %}}
## {{% heading "whatsnext" %}}
点击链接[调试init-container](/docs/tasks/troubleshoot/debug-init-containers/)，了解更多信息。
{{% /capture %}}
content/zh/docs/tasks/debug-application-cluster/determine-reason-pod-failure.md
+12 -10
View File
@@ -1,16 +1,16 @@
---
title: 确定 Pod 失败的原因
content_template: templates/task
content_type: task
---
<!--
---
title: Determine the Reason for Pod Failure
content_template: templates/task
content_type: task
---
-->
{{% capture overview %}}
<!-- overview -->
<!--
This page shows how to write and read a Container
@@ -32,17 +32,18 @@ you put in a termination message should also be written to the general
{{% /capture %}}
{{% capture prerequisites %}}
## {{% heading "prerequisites" %}}
{{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}
{{% /capture %}}
{{% capture steps %}}
<!-- steps -->
<!--
## Writing and reading a termination message
@@ -151,9 +152,10 @@ is empty and the container exited with an error. The log output is limited to
通过将 `terminationMessagePolicy` 设置为 "`FallbackToLogsOnError`"，你就可以告诉 Kubernetes，在容器因错误退出时，如果终止消息文件为空，则使用容器日志输出的最后一块作为终止消息。
日志输出限制为 2048 字节或 80 行，以较小者为准。
{{% /capture %}}
{{% capture whatsnext %}}
## {{% heading "whatsnext" %}}
<!--
* See the `terminationMessagePath` field in
@@ -166,7 +168,7 @@ is empty and the container exited with an error. The log output is limited to
* 了解[接收日志](/docs/concepts/cluster-administration/logging/)。
* 了解 [Go 模版](https://golang.org/pkg/text/template/)。
{{% /capture %}}
content/zh/docs/tasks/debug-application-cluster/events-stackdriver.md
+6 -6
View File
@@ -2,7 +2,7 @@
reviewers:
- piosz
- x13n
content_template: templates/concept
content_type: concept
title: StackDriver 中的事件
---
@@ -11,12 +11,12 @@ title: StackDriver 中的事件
reviewers:
- piosz
- x13n
content_template: templates/concept
content_type: concept
title: Events in Stackdriver
---
-->
{{% capture overview %}}
<!-- overview -->
<!--
Kubernetes events are objects that provide insight into what is happening
@@ -66,10 +66,10 @@ of the potential inaccuracy.
[sdLogMetrics]: https://cloud.google.com/logging/docs/view/logs_based_metrics
[sdAlerts]: https://cloud.google.com/logging/docs/view/logs_based_metrics#creating_an_alerting_policy
{{% /capture %}}
{{% capture body %}}
<!-- body -->
<!--
## Deployment
@@ -164,4 +164,4 @@ jsonPayload.involvedObject.name:"nginx-deployment"
{{< figure src="/images/docs/stackdriver-event-exporter-filter.png" alt="Filtered events in the Stackdriver Logging interface" width="500" >}}
{{% /capture %}}
content/zh/docs/tasks/debug-application-cluster/falco.md
+6 -6
View File
@@ -3,7 +3,7 @@ reviewers:
- soltysh
- sttts
- ericchiang
content_template: templates/concept
content_type: concept
title: 使用 Falco 审计
---
<!--
@@ -12,11 +12,11 @@ reviewers:
- soltysh
- sttts
- ericchiang
content_template: templates/concept
content_type: concept
title: Auditing with Falco
---
-->
{{% capture overview %}}
<!-- overview -->
<!--
### Use Falco to collect audit events
-->
@@ -28,9 +28,9 @@ This section describes how to set up Falco, how to send audit events to the Kube
-->
[Falco](https://falco.org/)是一个开源项目，用于为云原生平台提供入侵和异常检测。本节介绍如何设置 Falco、如何将审计事件发送到 Falco 公开的 Kubernetes Audit 端点、以及 Falco 如何应用一组规则来自动检测可疑行为。
{{% /capture %}}
{{% capture body %}}
<!-- body -->
<!--
#### Install Falco
@@ -236,4 +236,4 @@ For further details, see [Kubernetes Audit Events][falco_ka_docs] in the Falco d
[falco_installation]: https://falco.org/docs/installation
[falco_helm_chart]: https://github.com/helm/charts/tree/master/stable/falco
{{% /capture %}}
content/zh/docs/tasks/debug-application-cluster/get-shell-running-container.md
+14 -12
View File
@@ -3,7 +3,7 @@ reviewers:
- caesarxuchao
- mikedanese
title: 获取正在运行容器的 Shell
content_template: templates/task
content_type: task
---
<!--
@@ -12,11 +12,11 @@ reviewers:
- caesarxuchao
- mikedanese
title: Get a Shell to a Running Container
content_template: templates/task
content_type: task
---
-->
{{% capture overview %}}
<!-- overview -->
<!--
This page shows how to use `kubectl exec` to get a shell to a
@@ -25,17 +25,18 @@ running Container.
本文介绍怎样使用 `kubectl exec` 命令获取正在运行容器的 Shell。
{{% /capture %}}
{{% capture prerequisites %}}
## {{% heading "prerequisites" %}}
{{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}
{{% /capture %}}
{{% capture steps %}}
<!-- steps -->
<!--
## Getting a shell to a Container
@@ -202,9 +203,9 @@ kubectl exec shell-demo ls /
kubectl exec shell-demo cat /proc/1/mounts
```
{{% /capture %}}
{{% capture discussion %}}
<!-- discussion -->
<!--
## Opening a shell when a Pod has more than one Container
@@ -228,14 +229,15 @@ shell to the main-app Container.
kubectl exec -it my-pod --container main-app -- /bin/bash
```
{{% /capture %}}
{{% capture whatsnext %}}
## {{% heading "whatsnext" %}}
* [kubectl exec](/docs/reference/generated/kubectl/kubectl-commands/#exec)
{{% /capture %}}
content/zh/docs/tasks/debug-application-cluster/local-debugging.md
+12 -10
View File
@@ -1,16 +1,16 @@
---
title: 在本地开发和调试服务
content_template: templates/task
content_type: task
---
<!--
---
title: Developing and debugging services locally
content_template: templates/task
content_type: task
---
-->
{{% capture overview %}}
<!-- overview -->
<!--
Kubernetes applications usually consist of multiple, separate services, each running in its own container. Developing and debugging these services on a remote Kubernetes cluster can be cumbersome, requiring you to [get a shell on a running container](/docs/tasks/debug-application-cluster/get-shell-running-container/) and running your tools inside the remote shell.
@@ -32,9 +32,10 @@ This document describes using `telepresence` to develop and debug services runni
本文档描述如何在本地使用 `telepresence` 开发和调试远程集群上运行的服务。
{{% /capture %}}
{{% capture prerequisites %}}
## {{% heading "prerequisites" %}}
<!--
* Kubernetes cluster is installed
@@ -46,9 +47,9 @@ This document describes using `telepresence` to develop and debug services runni
* 配置好 `kubectl` 与集群交互
* [Telepresence](https://www.telepresence.io/reference/install) 安装完毕
{{% /capture %}}
{{% capture steps %}}
<!-- steps -->
<!--
## Getting a shell on a remote cluster
@@ -103,9 +104,10 @@ Running this command spawns a shell. In the shell, start your service. You can t
运行此命令将生成 shell。在 shell 中，启动您的服务。
然后，您就可以在本地对源代码进行编辑、保存并能看到更改立即生效。您还可以在调试器或任何其他本地开发工具中运行服务。
{{% /capture %}}
{{% capture whatsnext %}}
## {{% heading "whatsnext" %}}
<!--
If you're interested in a hands-on tutorial, check out [this tutorial](https://cloud.google.com/community/tutorials/developing-services-with-k8s) that walks through locally developing the Guestbook application on Google Kubernetes Engine.
@@ -123,4 +125,4 @@ Telepresence 有[多种代理选项](https://www.telepresence.io/reference/metho
要了解更多信息，请访问 [Telepresence 网站](https://www.telepresence.io)。
{{% /capture %}}
content/zh/docs/tasks/debug-application-cluster/logging-elasticsearch-kibana.md
+9 -8
View File
@@ -2,7 +2,7 @@
reviewers:
- piosz
- x13n
content_template: templates/concept
content_type: concept
title: 使用 ElasticSearch 和 Kibana 进行日志管理
---
@@ -11,12 +11,12 @@ title: 使用 ElasticSearch 和 Kibana 进行日志管理
reviewers:
- piosz
- x13n
content_template: templates/concept
content_type: concept
title: Logging Using Elasticsearch and Kibana
---
-->
{{% capture overview %}}
<!-- overview -->
<!--
On the Google Compute Engine (GCE) platform, the default logging support targets
@@ -42,9 +42,9 @@ You cannot automatically deploy Elasticsearch and Kibana in the Kubernetes clust
您不能在 Google Kubernetes Engine 平台运行的 Kubernetes 集群上自动的部署 Elasticsearch 和 Kibana。您必须手动部署它们。
{{< /note >}}
{{% /capture %}}
{{% capture body %}}
<!-- body -->
<!--
To use Elasticsearch and Kibana for cluster logging, you should set the
@@ -179,9 +179,10 @@ Here is a typical view of ingested logs from the Kibana viewer:
![Kibana logs](/images/docs/kibana-logs.png)
{{% /capture %}}
{{% capture whatsnext %}}
## {{% heading "whatsnext" %}}
<!--
Kibana opens up all sorts of powerful options for exploring your logs! For some
@@ -190,4 +191,4 @@ ideas on how to dig into it, check out [Kibana's documentation](https://www.elas
Kibana 为浏览您的日志提供了各种强大的选项！有关如何深入研究它的一些想法，请查看 [Kibana 的文档](https://www.elastic.co/guide/en/kibana/current/discover.html)。
{{% /capture %}}
content/zh/docs/tasks/debug-application-cluster/monitor-node-health.md
+11 -10
View File
@@ -1,5 +1,5 @@
---
content_template: templates/task
content_type: task
title: 节点健康监测
---
<!--
@@ -7,12 +7,12 @@ title: 节点健康监测
reviewers:
- Random-Liu
- dchen1107
content_template: templates/task
content_type: task
title: Monitor Node Health
---
-->
{{% capture overview %}}
<!-- overview -->
*节点问题探测器* 是一个 [DaemonSet](/docs/concepts/workloads/controllers/daemonset/) 用来监控节点健康。它从各种守护进程收集节点问题，并以[NodeCondition](/docs/concepts/architecture/nodes/#condition) 和 [Event](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#event-v1-core) 的形式报告给 apiserver 。
<!--
@@ -41,15 +41,16 @@ See more information
-->
更多信息请参阅 [这里](https://github.com/kubernetes/node-problem-detector)。
{{% /capture %}}
{{% capture prerequisites %}}
## {{% heading "prerequisites" %}}
{{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}
{{% /capture %}}
{{% capture steps %}}
<!-- steps -->
<!--
## Limitations
@@ -285,9 +286,9 @@ plugin to translate kernel log the internal data structure. It is easy to
implement a new translator for a new log format.
-->
内核监视器使用 [`Translator`] 插件将内核日志转换为内部数据结构。我们可以很容易为新的日志格式实现新的翻译器。
{{% /capture %}}
{{% capture discussion %}}
<!-- discussion -->
<!--
## Caveats
@@ -312,4 +313,4 @@ resource overhead on each node. Usually this is fine, because:
* 即使在高负载下，资源使用也是可以接受的。
(参阅 [基准测试结果](https://github.com/kubernetes/node-problem-detector/issues/2#issuecomment-220255629))
{{% /capture %}}
content/zh/docs/tasks/debug-application-cluster/resource-metrics-pipeline.md
+6 -6
View File
@@ -3,7 +3,7 @@ reviewers:
- fgrzadkowski
- piosz
title: 资源指标管道
content_template: templates/concept
content_type: concept
---
<!--
---
@@ -11,11 +11,11 @@ reviewers:
- fgrzadkowski
- piosz
title: Resource metrics pipeline
content_template: templates/concept
content_type: concept
---
-->
{{% capture overview %}}
<!-- overview -->
<!--
Starting from Kubernetes 1.8, resource usage metrics, such as container CPU and memory usage,
@@ -25,10 +25,10 @@ Horizontal Pod Autoscaler, to make decisions.
-->
从 Kubernetes 1.8开始，资源使用指标，例如容器 CPU 和内存使用率，可通过 Metrics API 在 Kubernetes 中获得。这些指标可以直接被用户访问，比如使用`kubectl top`命令行，或者这些指标由集群中的控制器使用，例如，Horizontal Pod Autoscaler，使用这些指标来做决策。
{{% /capture %}}
{{% capture body %}}
<!-- body -->
<!--
## The Metrics API
@@ -102,4 +102,4 @@ Learn more about the metrics server in [the design doc](https://github.com/kuber
-->
在[设计文档](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/instrumentation/metrics-server.md)中可以了解到有关 Metrics Server 的更多信息。
{{% /capture %}}
content/zh/docs/tasks/debug-application-cluster/resource-usage-monitoring.md
+6 -6
View File
@@ -1,19 +1,19 @@
---
reviewers:
- mikedanese
content_template: templates/concept
content_type: concept
title: 资源监控工具
---
<!--
---
reviewers:
- mikedanese
content_template: templates/concept
content_type: concept
title: Tools for Monitoring Resources
---
-->
{{% capture overview %}}
<!-- overview -->
<!--
To scale an application and provide a reliable service, you need to
@@ -30,9 +30,9 @@ where bottlenecks can be removed to improve overall performance.
Kubernetes 在每个级别上提供有关应用程序资源使用情况的详细信息。
此信息使您可以评估应用程序的性能，以及在何处可以消除瓶颈以提高整体性能。
{{% /capture %}}
{{% capture body %}}
<!-- body -->
<!--
In Kubernetes, application monitoring does not depend on a single monitoring solution. On new clusters, you can use [resource metrics](#resource-metrics-pipeline) or [full metrics](#full-metrics-pipeline) pipelines to collect monitoring statistics.
@@ -101,5 +101,5 @@ Full metrics pipeline projects that are not part of the CNCF are outside the sco
Prometheus 本身。
完整度量管道项目不属于 CNCF 的一部分，不在 Kubernetes 文档的范围之内。
{{% /capture %}}
content/zh/docs/tasks/debug-application-cluster/troubleshooting.md
+6 -6
View File
@@ -2,7 +2,7 @@
reviewers:
- brendandburns
- davidopp
content_template: templates/concept
content_type: concept
title: 排错
---
@@ -11,12 +11,12 @@ title: 排错
reviewers:
- brendandburns
- davidopp
content_template: templates/concept
content_type: concept
title: Troubleshooting
---
-->
{{% capture overview %}}
<!-- overview -->
<!--
Sometimes things go wrong. This guide is aimed at making them right. It has
@@ -40,10 +40,10 @@ you're using.
您也应该查看所用[版本](https://github.com/kubernetes/kubernetes/releases)的已知问题。
{{% /capture %}}
{{% capture body %}}
<!-- body -->
<!--
## Getting help
@@ -217,4 +217,4 @@ problem, such as:
* 云提供商，OS 发行版、网络配置和 Docker 版本
* 重现问题的步骤
{{% /capture %}}