Add some translations - Chinese (#11313)

* Fix netlify

This PR also includes some translations for glossary which have to be
included to make gate happy.

* Delete label-new.md

* Update node.md

* Update managed-service.md

* Update sig.md
This commit is contained in:
Qiming
2018-11-30 17:44:02 +08:00
committed by GitHub
parent a7b2730118
commit 17c7f60e14
8 changed files with 188 additions and 19 deletions
@@ -1,4 +1,17 @@
---
title: 贡献者
id: contributor
date: 2018-04-12
full_link:
short_description: >
通过贡献代码、文档或者投入时间等方式来帮助 Kubernetes 项目或社区的人。
aka:
tags:
- community
---
<!--
title: Contributor
id: contributor
date: 2018-04-12
@@ -9,10 +22,18 @@ short_description: >
aka:
tags:
- community
---
-->
<!--
Someone who donates code, documentation, or their time to help the Kubernetes project or community.
-->
通过贡献代码、文档或者投入时间等方式来帮助 Kubernetes 项目或社区的人。
<!--more-->
<!--
Contributions include pull requests (PRs), issues, feedback, {{< glossary_tooltip text="special interest groups (SIG)" term_id="sig" >}} participation, or organizing community events.
-->
贡献形式包括提交拉取请求(PRs)、问题报告(Issues)、反馈、参与{{< glossary_tooltip text="特别兴趣小组(SIG" term_id="sig" >}}或者组织社区活动等等。
@@ -3,6 +3,20 @@ title: kube-apiserver
id: kube-apiserver
date: 2018-04-12
full_link: /docs/reference/generated/kube-apiserver/
short_description: >
主节点上负责提供 Kubernetes API 服务的组件;它是 Kubernetes 控制面的前端。
aka:
tags:
- architecture
- fundamental
---
<!--
title: kube-apiserver
id: kube-apiserver
date: 2018-04-12
full_link: /docs/reference/generated/kube-apiserver/
short_description: >
Component on the master that exposes the Kubernetes API. It is the front-end for the Kubernetes control plane.
@@ -10,10 +24,21 @@ aka:
tags:
- architecture
- fundamental
---
-->
<!--
Component on the master that exposes the Kubernetes API. It is the front-end for the Kubernetes control plane.
-->
主节点上负责提供 Kubernetes API 服务的组件;它是 Kubernetes 控制面的前端。
<!--more-->
It is designed to scale horizontally -- that is, it scales by deploying more instances. See [Building High-Availability Clusters](/docs/admin/high-availability/).
<!--
It is designed to scale horizontally - that is, it scales by deploying more instances. See [Building High-Availability Clusters](/docs/admin/high-availability/).
-->
kube-apiserver 在设计上考虑了水平扩缩的需要。
换言之,通过部署多个实例可以实现扩缩。
参见[构造高可用集群](/docs/admin/high-availability/)。
+24 -1
View File
@@ -1,4 +1,17 @@
---
title: 标签
id: label
date: 2018-04-12
full_link: /docs/concepts/overview/working-with-objects/labels
short_description: >
用来为对象设置可标识的属性标记;这些标记对用户而言是有意义且重要的。
aka:
tags:
- fundamental
---
<!--
title: Label
id: label
date: 2018-04-12
@@ -9,10 +22,20 @@ short_description: >
aka:
tags:
- fundamental
---
-->
<!--
Tags objects with identifying attributes that are meaningful and relevant to users.
-->
用来为对象设置可标识的属性标记;这些标记对用户而言是有意义且重要的。
<!--more-->
<!--
Labels are key/value pairs that are attached to objects such as {{< glossary_tooltip text="Pods" term_id="pod" >}}. They are used to organize and to select subsets of objects.
-->
标签是一些关联到 {{< glossary_tooltip text="Pods" term_id="pod" >}} 这类对象上的键值对。
它们通常用来组织和选择对象子集。
@@ -1,4 +1,17 @@
---
title: 托管服务
id: managed-service
date: 2018-04-12
full_link:
short_description: >
由第三方供应商负责维护的一种软件产品。
aka:
tags:
- extension
---
<!--
title: Managed Service
id: managed-service
date: 2018-04-12
@@ -9,9 +22,21 @@ short_description: >
aka:
tags:
- extension
---
-->
<!--
A software offering maintained by a third-party provider.
-->
由第三方供应商负责维护的一种软件产品。
<!--more-->
<!--
Some examples of Managed Services are AWS EC2, Azure SQL Database, and GCP Pub/Sub, but they can be any software offering that can be used by an application. [Service Catalog](/docs/concepts/service-catalog/) provides a way to list, provision, and bind with Managed Services offered by {{< glossary_tooltip text="Service Brokers" term_id="service-broker" >}}.
-->
托管服务的一些例子有 AWS EC2、Azure SQL 数据库和 GCP Pub/Sub 等,
不过它们也可以是可以被某应用使用的任何软件交付件。
[服务目录](/docs/concepts/service-catalog/)提供了一种方法用来列举、供应和绑定到
{{< glossary_tooltip text="服务代理商" term_id="service-broker" >}}所提供的托管服务。
+27 -2
View File
@@ -1,4 +1,17 @@
---
title: 节点
id: node
date: 2018-04-12
full_link: /docs/concepts/architecture/nodes/
short_description: >
Kubernetes 中的工作机器称作节点。
aka:
tags:
- fundamental
---
<!--
title: Node
id: node
date: 2018-04-12
@@ -9,10 +22,22 @@ short_description: >
aka:
tags:
- fundamental
---
A node is a worker machine in Kubernetes.
-->
<!--
A node is a worker machine in Kubernetes.
-->
Kubernetes 中的工作机器称作节点。
<!--more-->
<!--
A worker machine may be a VM or physical machine, depending on the cluster. It has the {{< glossary_tooltip text="Services" term_id="service" >}} necessary to run {{< glossary_tooltip text="Pods" term_id="pod" >}} and is managed by the master components. The {{< glossary_tooltip text="Services" term_id="service" >}} on a node include Docker, kubelet and kube-proxy.
-->
工作机器可以是虚拟机也可以是物理机,取决于集群的配置。
其上部署了运行 {{< glossary_tooltip text="Pods" term_id="pod" >}} 所必需的{{< glossary_tooltip text="服务" term_id="service" >}}
并由主控组件来管理。
节点上的{{< glossary_tooltip text="服务" term_id="service" >}}包括 Docker、kubelet 和 kube-proxy。
@@ -4,7 +4,7 @@ id: service-broker
date: 2018-04-12
full_link:
short_description: >
由第三方提供维护的一组托管服务的端点。
由第三方提供维护的一组托管服务的访问端点。
aka:
tags:
@@ -12,7 +12,6 @@ tags:
---
<!--
---
title: Service Broker
id: service-broker
date: 2018-04-12
@@ -23,14 +22,13 @@ short_description: >
aka:
tags:
- extension
---
-->
<!--
An endpoint for a set of {{< glossary_tooltip text="Managed Services" term_id="managed-service" >}} offered and maintained by a third-party.
An endpoint for a set of {{< glossary_tooltip text="Managed Service" term_id="managed-service">}} offered and maintained by a third-party.
-->
由第三方提供维护的一组 {{< glossary_tooltip text="托管服务" term_id="managed-service" >}} 的端点。
由第三方提供维护的一组{{< glossary_tooltip text="托管服务" term_id="managed-service">}} 的访问端点。
<!--more-->
@@ -38,6 +36,7 @@ tags:
{{< glossary_tooltip text="Service Brokers" term_id="service-broker" >}} implement the [Open Service Broker API spec](https://github.com/openservicebrokerapi/servicebroker/blob/v2.13/spec.md) and provide a standard interface for applications to use their Managed Services. [Service Catalog](/docs/concepts/service-catalog/) provides a way to list, provision, and bind with Managed Services offered by Service Brokers.
-->
{{< glossary_tooltip text="服务代理Service Broker" term_id="service-broker" >}} 实现了 [Open Service Broker API 规范](https://github.com/openservicebrokerapi/servicebroker/blob/v2.13/spec.md),并为应用程序提供了使用它所托管服务的标准接口。
[服务目录(Service Catalog](/docs/concepts/service-catalog/) 提供了一种检索、提供和绑定服务代理所提供的托管服务的方法。
{{< glossary_tooltip text="服务代理" term_id="service-broker">}}实现
[开放服务代理 API 规范](https://github.com/openservicebrokerapi/servicebroker/blob/v2.13/spec.md)
并为应用提供使用其托管服务的标准接口。
[服务目录(Service Catalog](/docs/concepts/service-catalog/)则提供一种方法,用来列举、供应和绑定服务代理商所提供的托管服务。
+28 -1
View File
@@ -1,4 +1,17 @@
---
title: SIG (特别兴趣小组)
id: sig
date: 2018-04-12
full_link: https://github.com/kubernetes/community/blob/master/sig-list.md#master-sig-list
short_description: >
共同管理大范畴 Kubernetes 开源项目中某组件或方面的一组社区成员。
aka:
tags:
- community
---
<!--
title: SIG (special interest group)
id: sig
date: 2018-04-12
@@ -9,13 +22,27 @@ short_description: >
aka:
tags:
- community
---
-->
<!--
{{< glossary_tooltip text="Community members" term_id="member" >}} who collectively manage an ongoing piece or aspect of the larger Kubernetes open source project.
-->
共同管理大范畴 Kubernetes 开源项目中某组件或方面的一组{{< glossary_tooltip text="社区成员" term_id="member" >}}。
<!--more-->
<!--
Members within a SIG have a shared interest in advancing a specific area, such as architecture, API machinery, or documentation.
SIGs must follow the [SIG Governance](https://github.com/kubernetes/community/blob/master/sig-governance.md) guidelines but can have their own contribution policy and channels of communication.
For more information, see the [kubernetes/community](https://github.com/kubernetes/community) repo and the current list of [SIGs and Working Groups](https://github.com/kubernetes/community/blob/master/sig-list.md).
-->
SIG 中的成员对推进某个领域(如体系结构、API 机制构件或者文档)具有相同的兴趣。
SIGs 必须遵从 [SIG Governance](https://github.com/kubernetes/community/blob/master/sig-governance.md) 的规定,
不过可以有自己的贡献策略以及通信渠道(方式)。
更多的详细信息可参阅 [kubernetes/community](https://github.com/kubernetes/community) 仓库以及
[SIGs 和工作组(Working Groups](https://github.com/kubernetes/community/blob/master/sig-list.md)的最新列表。
+26 -2
View File
@@ -1,4 +1,18 @@
---
title: 卷
id: volume
date: 2018-04-12
full_link: /docs/concepts/storage/volumes/
short_description: >
包含可被 Pod 中容器访问的数据的目录。
aka:
tags:
- core-object
- fundamental
---
<!--
title: Volume
id: volume
date: 2018-04-12
@@ -10,10 +24,20 @@ aka:
tags:
- core-object
- fundamental
---
-->
<!--
A directory containing data, accessible to the containers in a {{< glossary_tooltip text="pod" term_id="pod" >}}.
-->
包含可被 {{< glossary_tooltip text="pod" term_id="pod" >}} 中容器访问的数据的目录。
<!--more-->
<!--
A Kubernetes volume lives as long as the {{< glossary_tooltip text="pod" term_id="pod" >}} that encloses it. Consequently, a volume outlives any {{< glossary_tooltip text="containers" term_id="container" >}} that run within the {{< glossary_tooltip text="pod" term_id="pod" >}}, and data is preserved across {{< glossary_tooltip text="container" term_id="container" >}} restarts.
-->
每个 Kubernetes 卷在所处的{{< glossary_tooltip text="pod" term_id="pod" >}} 存在期间保持存在状态。
因此,卷的生命期会超出 {{< glossary_tooltip text="pod" term_id="pod" >}} 中运行的{{< glossary_tooltip text="容器" term_id="container" >}}
并且保证{{< glossary_tooltip text="容器" term_id="container" >}}重启之后仍保留数据。