From 75647524c64366b237bcd51349314704c7929ba6 Mon Sep 17 00:00:00 2001 From: yuxiaobo96 <41496192+yuxiaobo96@users.noreply.github.com> Date: Mon, 11 Nov 2019 12:45:53 +0800 Subject: [PATCH] zh-translation:/about/bugs/index.md (#5374) --- content/zh/about/bugs/index.md | 58 ++++++++++++++-------------------- 1 file changed, 23 insertions(+), 35 deletions(-) diff --git a/content/zh/about/bugs/index.md b/content/zh/about/bugs/index.md index efcf454517..959cf6b9b7 100644 --- a/content/zh/about/bugs/index.md +++ b/content/zh/about/bugs/index.md @@ -1,70 +1,62 @@ --- -title: Reporting Bugs -description: What to do if you find a bug. +title: 报告错误 +description: 如果发现错误该怎么办。 weight: 34 aliases: - - /bugs.html - - /bugs/index.html - - /help/bugs/ + - /zh/bugs.html + - /zh/bugs/index.html + - /zh/help/bugs/ icon: bugs --- -Oh no! You found a bug? We'd love to hear about it. +不好!您发现了一个错误?我们希望知道这一点。 -## Product bugs +## 产品错误{#product-bugs} -Search our [issue database](https://github.com/istio/istio/issues/) to see if -we already know about your problem and learn about when we think we can fix -it. If you don't find your problem in the database, please open a [new -issue](https://github.com/istio/istio/issues/new/choose) and let us know -what's going on. +搜索我们的 [问题数据库](https://github.com/istio/istio/issues/) 来查看是否我们已经知道您的问题,并了解何时可以解决它。如果您在该数据库中没有找到你的问题,请打开一个 [新问题](https://github.com/istio/istio/issues/new/choose) 让我们知道出现了什么错误。 -If you think a bug is in fact a security vulnerability, please visit [Reporting Security Vulnerabilities](/about/security-vulnerabilities/) -to learn what to do. +如果您认为错误实际上是一个安全漏洞,请访问 [报告安全漏洞](/about/security-vulnerabilities/) 了解如何处理。 -### Kubernetes cluster state archives +### Kubernetes 集群状态档案{#Kubernetes-cluster-state-archives} -If you're running on Kubernetes, consider including a cluster state -archive with your bug report. -For convenience, you can run a dump script to produce an archive containing -all of the relevant state from your Kubernetes cluster: +如果您正在运行 Kubernetes,请考虑使用错误报告将集群状态存档。为了方便起见,您可以运行转储脚本生成一个档案,该档案包含 Kubernetes 集群中所有相关的状态: -* Run via `curl`: +* 运行 `curl`: {{< text bash >}} $ curl {{< github_file >}}/tools/dump_kubernetes.sh | sh -s -- -z {{< /text >}} -* Run locally, from the release directory's root: +* 在发布版本目录的根目录本地运行: {{< text bash >}} $ @tools/dump_kubernetes.sh@ -z {{< /text >}} -Then attach the produced `istio-dump.tar.gz` with your reported problem. +然后,将产生的 `istio-dump.tar.gz` 与您的报告问题连接。 -If you are unable to use the dump script, please attach your own archive -containing: +如果您无法使用转储脚本,请附加自己的存档 +包含: -* Pods, services, deployments, and endpoints across all namespaces: +* 在所有命名空间中的 pods、services、deployments 和 endpoints: {{< text bash >}} $ kubectl get pods,services,deployments,endpoints --all-namespaces -o yaml > k8s_resources.yaml {{< /text >}} -* Secret names in `istio-system`: +* 在 `istio-system` 中的密名: {{< text bash >}} $ kubectl --namespace istio-system get secrets {{< /text >}} -* configmaps in the `istio-system` namespace: +* 在 `istio-system` 命名空间的 configmap: {{< text bash >}} $ kubectl --namespace istio-system get cm -o yaml {{< /text >}} -* Current and previous logs from all Istio components and sidecar +* 所有 Istio 组件和 sidecar 的当前和以前的日志 * Mixer logs: @@ -81,16 +73,12 @@ containing: $ kubectl logs -n istio-system -l istio=pilot -c istio-proxy {{< /text >}} -* All Istio configuration artifacts: +* 所有 Istio 配置工件: {{< text bash >}} $ kubectl get $(kubectl get crd --no-headers | awk '{printf "%s,",$1}END{printf "attributemanifests.config.istio.io\n"}') --all-namespaces {{< /text >}} -## Documentation bugs +## 文档错误{#documentation-bugs} -Search our [documentation issue database](https://github.com/istio/istio.io/issues/) to see if -we already know about your problem and learn about when we think we can fix -it. If you don't find your problem in the database, please navigate to the page -with the problem, then select the gear menu at the -top right of this page, and finally chose *Report a Site Bug*. +搜索我们的 [文档问题数据库](https://github.com/istio/istio.io/issues/) 以查看是否我们已经知道您的问题,并了解何时可以解决它。如果您在该数据库中找不到问题,请导航到这个问题的页面,然后在页面的右上角选择齿轮菜单,最后选择 *Report a Site Bug*。