From d07cf9ec9b11fb7eb4bd90ae2b77b434089f7ec6 Mon Sep 17 00:00:00 2001
From: SataQiu <1527062125@qq.com>
Date: Wed, 26 Dec 2018 21:45:09 +0800
Subject: [PATCH] zh-trans:add content/zh/docs/reference/issues-security
 (#11890)

---
 .../docs/reference/issues-security/_index.md  |  13 ++
 .../docs/reference/issues-security/issues.md  |  16 +++
 .../reference/issues-security/security.md     | 129 ++++++++++++++++++
 3 files changed, 158 insertions(+)
 create mode 100644 content/zh/docs/reference/issues-security/_index.md
 create mode 100644 content/zh/docs/reference/issues-security/issues.md
 create mode 100644 content/zh/docs/reference/issues-security/security.md

diff --git a/content/zh/docs/reference/issues-security/_index.md b/content/zh/docs/reference/issues-security/_index.md
new file mode 100644
index 0000000000..222e543541
--- /dev/null
+++ b/content/zh/docs/reference/issues-security/_index.md
@@ -0,0 +1,13 @@
+---
+title: Kubernetes 问题和安全
+weight: 10
+toc-hide: true
+---
+
+<!--
+---
+title: Kubernetes Issues and Security
+weight: 10
+toc-hide: true
+---
+-->
\ No newline at end of file
diff --git a/content/zh/docs/reference/issues-security/issues.md b/content/zh/docs/reference/issues-security/issues.md
new file mode 100644
index 0000000000..7976be7684
--- /dev/null
+++ b/content/zh/docs/reference/issues-security/issues.md
@@ -0,0 +1,16 @@
+---
+title: Kubernetes 问题追踪
+weight: 10
+---
+
+<!--
+---
+title: Kubernetes Issue Tracker
+weight: 10
+---
+-->
+
+<!--
+Work on Kubernetes code is tracked using [GitHub Issues](https://github.com/kubernetes/kubernetes/issues/).
+-->
+Kubernetes 代码的问题追踪基于 [GitHub Issues](https://github.com/kubernetes/kubernetes/issues/) 进行。
diff --git a/content/zh/docs/reference/issues-security/security.md b/content/zh/docs/reference/issues-security/security.md
new file mode 100644
index 0000000000..a0fe43786a
--- /dev/null
+++ b/content/zh/docs/reference/issues-security/security.md
@@ -0,0 +1,129 @@
+---
+title: Kubernetes 安全和信息披露
+aliases: [/security/]
+content_template: templates/concept
+weight: 20
+---
+
+<!--
+---
+title: Kubernetes Security and Disclosure Information
+aliases: [/security/]
+reviewers:
+- eparis
+- erictune
+- philips
+- jessfraz
+content_template: templates/concept
+weight: 20
+---
+-->
+
+{{% capture overview %}}
+<!--
+This page describes Kubernetes security and disclosure information.
+-->
+本页面介绍 Kubernetes 安全和信息披露相关的内容。
+{{% /capture %}}
+
+{{% capture body %}}
+<!--
+## Security Announcements
+-->
+## 安全公告
+
+<!--
+Join the [kubernetes-announce](https://groups.google.com/forum/#!forum/kubernetes-announce) group for emails about security and major API announcements.
+-->
+加入 [kubernets-announce](https://groups.google.com/forum/#!forum/kubernetes-announce) 组，以获取关于安全性和主要 API 公告的电子邮件。
+
+<!--
+## Report a Vulnerability
+-->
+## 报告一个漏洞
+
+<!--
+We’re extremely grateful for security researchers and users that report vulnerabilities to the Kubernetes Open Source Community. All reports are thoroughly investigated by a set of community volunteers.
+-->
+我们非常感谢向 Kubernetes 开源社区报告漏洞的安全研究人员和用户。
+所有的报告都由社区志愿者进行彻底调查。
+
+<!--
+To make a report, please email the private [security@kubernetes.io](mailto:security@kubernetes.io) list with the security details and the details expected for [all Kubernetes bug reports](https://git.k8s.io/kubernetes/.github/ISSUE_TEMPLATE/bug-report.md).
+-->
+如需报告，请连同安全细节以及预期的[所有 Kubernetes bug 报告](https://git.k8s.io/kubernetes/.github/ISSUE_TEMPLATE/bug-report.md)详细信息电邮到[security@kubernetes.io](mailto:security@kubernetes.io) 列表。
+
+<!--
+You may encrypt your email to this list using the GPG keys of the [Product Security Team members](https://git.k8s.io/sig-release/security-release-process-documentation/security-release-process.md#product-security-team-pst). Encryption using GPG is NOT required to make a disclosure.
+-->
+您可以使用[产品安全团队成员](https://git.k8s.io/sig-release/security-release-process-documentation/security-release-process.md#product-security-team-pst)的 GPG 密钥加密您的电子邮件到此列表。
+使用 GPG 加密不需要公开。
+
+<!--
+### When Should I Report a Vulnerability?
+-->
+### 我应该在什么时候报告漏洞？
+
+<!--
+- You think you discovered a potential security vulnerability in Kubernetes
+- You are unsure how a vulnerability affects Kubernetes
+- You think you discovered a vulnerability in another project that Kubernetes depends on (e.g. docker, rkt, etcd)
+-->
+- 您认为在 Kubernetes 中发现了一个潜在的安全漏洞
+- 您不确定漏洞如何影响 Kubernetes
+- 您认为您在 Kubernetes 依赖的另一个项目中发现了一个漏洞（例如 docker、rkt、etcd）
+
+<!--
+### When Should I NOT Report a Vulnerability?
+-->
+### 我什么时候不应该报告漏洞？
+
+<!--
+- You need help tuning Kubernetes components for security
+- You need help applying security related updates
+- Your issue is not security related
+-->
+- 您需要帮助调整 Kubernetes 组件的安全性
+- 您需要帮助应用与安全相关的更新
+- 您的问题与安全无关
+
+<!--
+## Security Vulnerability Response
+-->
+## 安全漏洞响应
+
+<!--
+Each report is acknowledged and analyzed by Product Security Team members within 3 working days. This will set off the [Security Release Process](https://git.k8s.io/sig-release/security-release-process-documentation/security-release-process.md#disclosures).
+-->
+每个报告在 3 个工作日内由产品安全团队成员确认和分析。这将启动[安全发布过程](https://git.k8s.io/sig-release/security-release-process-documentation/security-release-process.md#disclosures)。
+
+<!--
+Any vulnerability information shared with Product Security Team stays within Kubernetes project and will not be disseminated to other projects unless it is necessary to get the issue fixed.
+-->
+与产品安全团队共享的任何漏洞信息都保留在 Kubernetes 项目中，除非有必要修复该问题，否则不会传播到其他项目。
+
+<!--
+As the security issue moves from triage, to identified fix, to release planning we will keep the reporter updated.
+-->
+随着安全问题从分类、识别修复、发布计划等方面的进展，我们将不断更新报告。
+
+<!--
+## Public Disclosure Timing
+-->
+## 公开披露时间
+
+<!--
+A public disclosure date is negotiated by the Kubernetes product security team and the bug submitter. We prefer to fully disclose the bug as soon as possible once a user mitigation is available.
+-->
+公开披露日期由 Kubernetes 产品安全团队和 bug 提交者协商。我们倾向于在用户缓解措施可用时尽快完全披露该 bug。
+
+<!--
+It is reasonable to delay disclosure when the bug or the fix is not yet fully understood, the solution is not well-tested, or for vendor coordination. 
+-->
+当 bug 或其修复还没有被完全理解，解决方案没有经过良好的测试，或者为了处理供应商协调问题时，延迟披露是合理的。
+
+<!--
+The timeframe for disclosure is from immediate (especially if it's already publicly known) to a few weeks. As a basic default, we expect report date to disclosure date to be on the order of 7 days. The Kubernetes product security team holds the final say when setting a disclosure date.
+-->
+信息披露的时间范围从即时（尤其是已经公开的）到几周。作为一个基本的约定，我们希望报告日期到披露日期的间隔是 7 天。在设置披露日期时，Kubernetes 产品安全团队拥有最终决定权。
+{{% /capture %}}