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/concepts/extend-kubernetes/api-extension/apiserver-aggregation.md
+9 -8
View File
@@ -1,6 +1,6 @@
---
title: 通过聚合层扩展 Kubernetes API
content_template: templates/concept
content_type: concept
weight: 10
---
<!--
@@ -10,21 +10,21 @@ reviewers:
- lavalamp
- cheftako
- chenopis
content_template: templates/concept
content_type: concept
weight: 10
---
-->
{{% capture overview %}}
<!-- overview -->
<!--
The aggregation layer allows Kubernetes to be extended with additional APIs, beyond what is offered by the core Kubernetes APIs.
-->
聚合层允许 Kubernetes 通过额外的 API 进行扩展，而不局限于 Kubernetes 核心 API 提供的功能。
{{% /capture %}}
{{% capture body %}}
<!-- body -->
<!--
## Overview
@@ -57,9 +57,10 @@ extension-apiserver 与 kube-apiserver 之间的连接应具有低延迟。
特别是，发现请求需要在五秒钟或更短的时间内从 kube-apiserver 往返。
如果您的部署无法实现此目的，则应考虑如何进行更改。目前，在 kube-apiserver 上设置 `EnableAggregatedDiscoveryTimeout=false` 功能开关将禁用超时限制。它将在将来的版本中被删除。
{{% /capture %}}
{{% capture whatsnext %}}
## {{% heading "whatsnext" %}}
<!--
* To get the aggregator working in your environment, [configure the aggregation layer](/docs/tasks/access-kubernetes-api/configure-aggregation-layer/).
@@ -70,6 +71,6 @@ extension-apiserver 与 kube-apiserver 之间的连接应具有低延迟。
* 然后[安装扩展的 api-server](/docs/tasks/access-kubernetes-api/setup-extension-api-server/) 来开始使用聚合层。
* 也可以学习怎样 [使用自定义资源定义扩展 Kubernetes API](/docs/tasks/access-kubernetes-api/extend-api-custom-resource-definitions/)。
{{% /capture %}}
content/zh/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins.md
+8 -7
View File
@@ -1,11 +1,11 @@
---
title: 设备插件
description: 使用 Kubernetes 设备插件框架来实现适用于 GPU、NIC、FPGA、InfiniBand 以及类似的需要特定于供应商设置的资源的插件。
content_template: templates/concept
content_type: concept
weight: 20
---
{{% capture overview %}}
<!-- overview -->
{{< feature-state for_k8s_version="v1.10" state="beta" >}}
<!--
@@ -23,9 +23,9 @@ Kubernetes 提供了一个[设备插件框架](https://github.com/kubernetes/com
供应商可以实现设备插件，由您手动部署或作为 {{< glossary_tooltip term_id="daemonset" >}} 来部署，而不必定制 Kubernetes 本身的代码。目标设备包括 GPU、高性能 NIC、FPGA、InfiniBand 适配器以及其他类似的、可能需要特定于供应商的初始化和设置的计算资源。
{{% /capture %}}
{{% capture body %}}
<!-- body -->
## 注册设备插件
@@ -339,8 +339,9 @@ Here are some examples of device plugin implementations:
* [SR-IOV Network device plugin](https://github.com/intel/sriov-network-device-plugin)
* [Xilinx FPGA device plugins](https://github.com/Xilinx/FPGA_as_a_Service/tree/master/k8s-fpga-device-plugin/trunk)
{{% /capture %}}
{{% capture whatsnext %}}
## {{% heading "whatsnext" %}}
<!--
* Learn about [scheduling GPU resources](/docs/tasks/manage-gpus/scheduling-gpus/) using device plugins
@@ -353,4 +354,4 @@ Here are some examples of device plugin implementations:
* 阅读如何在 Kubernetes 中如何使用 [TLS 入口的硬件加速](https://kubernetes.io/blog/2019/04/24/hardware-accelerated-ssl/tls-termination-in-ingress-controllers-using-kubernetes-device-plugins-and-runtimeclass/)
* 学习 [Topology Manager] (/docs/tasks/adminster-cluster/topology-manager/)
{{% /capture %}}
content/zh/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins.md
+9 -8
View File
@@ -1,16 +1,16 @@
---
title: 网络插件
content_template: templates/concept
content_type: concept
weight: 10
---
<!--
title: Network Plugins
content_template: templates/concept
content_type: concept
weight: 10
-->
{{% capture overview %}}
<!-- overview -->
{{< feature-state state="alpha" >}}
<!--
@@ -29,9 +29,9 @@ Kubernetes中的网络插件有几种类型：
* CNI 插件： 遵守 appc/CNI 规约，为互操作性设计。
* Kubenet 插件：使用 `bridge` 和 `host-local` CNI 插件实现了基本的 `cbr0`。
{{% /capture %}}
{{% capture body %}}
<!-- body -->
<!--
## Installation
@@ -266,8 +266,9 @@ This option is provided to the network-plugin; currently **only kubenet supports
* `--network-plugin=kubenet` 用来表明我们要使用 `kubenet` 网络插件，CNI `bridge` 和 `host-local` 插件位于 `/opt/cni/bin` 或 `cni-bin-dir` 中。
* `--network-plugin-mtu=9001` 指定了我们使用的 MTU，当前仅被 `kubenet` 网络插件使用。
{{% /capture %}}
{{% capture whatsnext %}}
{{% /capture %}}
## {{% heading "whatsnext" %}}
content/zh/docs/concepts/extend-kubernetes/extend-cluster.md
+9 -8
View File
@@ -1,6 +1,6 @@
---
title: 扩展 Kubernetes 集群
content_template: templates/concept
content_type: concept
weight: 10
---
<!--
@@ -11,12 +11,12 @@ reviewers:
- lavalamp
- cheftako
- chenopis
content_template: templates/concept
content_type: concept
weight: 10
---
-->
{{% capture overview %}}
<!-- overview -->
<!--
Kubernetes is highly configurable and extensible. As a result,
@@ -34,10 +34,10 @@ Kubernetes 是高度可配置和可扩展的。因此，极少需要分发或提
本文档介绍自定义 Kubernetes 集群的选项。本文档的目标读者 {{< glossary_tooltip text="cluster operators" term_id="cluster-operator" >}} 是希望了解如何使 Kubernetes 集群满足其业务环境需求的集群运维人员。Kubernetes 项目的贡献者 {{< glossary_tooltip text="Contributors" term_id="contributor" >}} 或潜在的平台开发人员 {{< glossary_tooltip text="Platform Developers" term_id="platform-developer" >}} 也可以从本文找到有用的信息，如对已存在扩展点和模式的介绍，以及它们的权衡和限制。
{{% /capture %}}
{{% capture body %}}
<!-- body -->
<!--
## Overview
@@ -343,10 +343,11 @@ the nodes chosen for a pod.
调度器也支持 [webhook](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/scheduling/scheduler_extender.md)，它允许一个 webhook 后端（调度器扩展程序）为 pod 筛选节点和确定节点的优先级。
{{% /capture %}}
{{% capture whatsnext %}}
## {{% heading "whatsnext" %}}
<!--
* Learn more about [Custom Resources](/docs/concepts/api-extension/custom-resources/)
@@ -365,4 +366,4 @@ the nodes chosen for a pod.
* 了解 [kubectl 插件](/docs/tasks/extend-kubectl/kubectl-plugins/)
* 了解[操作者模式](/docs/concepts/extend-kubernetes/operator/)
{{% /capture %}}
content/zh/docs/concepts/extend-kubernetes/operator.md
+9 -8
View File
@@ -1,18 +1,18 @@
---
title: Operator 模式
content_template: templates/concept
content_type: concept
weight: 30
---
<!--
---
title: Operator pattern
content_template: templates/concept
content_type: concept
weight: 30
---
-->
{{% capture overview %}}
<!-- overview -->
<!--
Operators are software extensions to Kubernetes that make use of [custom
@@ -24,9 +24,9 @@ Kubernetes principles, notably the [control loop](/docs/concepts/#kubernetes-con
Operator 是 Kubernetes 的扩展软件，它利用[自定义资源](/docs/concepts/extend-kubernetes/api-extension/custom-resources/)管理应用及其组件。
Operator 遵循 Kubernetes 的理念，特别是在[控制回路](/docs/concepts/#kubernetes-control-plane)方面。
{{% /capture %}}
{{% capture body %}}
<!-- body -->
<!--
## Motivation
@@ -200,9 +200,10 @@ that can act as a [client for the Kubernetes API](/docs/reference/using-api/clie
您还可以使用任何支持 [Kubernetes API 客户端](/docs/reference/using-api/client-libraries/)的语言或运行时来实现 Operator（即控制器）。
{{% /capture %}}
{{% capture whatsnext %}}
## {{% heading "whatsnext" %}}
<!--
* Learn more about [Custom Resources](/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
@@ -229,4 +230,4 @@ that can act as a [client for the Kubernetes API](/docs/reference/using-api/clie
* 阅读 [CoreOS 原文](https://coreos.com/blog/introducing-operators.html)，其介绍了 Operator 介绍
* 阅读这篇来自谷歌云的关于构建 Operator 最佳实践的[文章](https://cloud.google.com/blog/products/containers-kubernetes/best-practices-for-building-kubernetes-operators-and-stateful-apps)
{{% /capture %}}
content/zh/docs/concepts/extend-kubernetes/service-catalog.md
+9 -8
View File
@@ -2,7 +2,7 @@
title: 服务目录
reviewers:
- chenopis
content_template: templates/concept
content_type: concept
weight: 40
---
<!--
@@ -10,12 +10,12 @@ weight: 40
title: Service Catalog
reviewers:
- chenopis
content_template: templates/concept
content_type: concept
weight: 40
---
-->
{{% capture overview %}}
<!-- overview -->
{{< glossary_definition term_id="service-catalog" length="all" prepend="" >}}
<!--
@@ -29,10 +29,10 @@ Using Service Catalog, a {{< glossary_tooltip text="cluster operator" term_id="c
使用服务目录，集群操作者可以浏览其提供的托管服务列表，提供托管服务实例并与之绑定，以使其可以被 Kubernetes 集群中的应用程序使用。
{{% /capture %}}
{{% capture body %}}
<!-- body -->
<!--
## Example use case
@@ -437,10 +437,11 @@ The following example describes how to map secret values into application enviro
key: topic
```
{{% /capture %}}
{{% capture whatsnext %}}
## {{% heading "whatsnext" %}}
<!--
* If you are familiar with {{< glossary_tooltip text="Helm Charts" term_id="helm-chart" >}}, [install Service Catalog using Helm](/docs/tasks/service-catalog/install-service-catalog-using-helm/) into your Kubernetes cluster. Alternatively, you can [install Service Catalog using the SC tool](/docs/tasks/service-catalog/install-service-catalog-using-sc/).
* View [sample service brokers](https://github.com/openservicebrokerapi/servicebroker/blob/master/gettingStarted.md#sample-service-brokers).
@@ -451,7 +452,7 @@ The following example describes how to map secret values into application enviro
* 查看[服务代理示例](https://github.com/openservicebrokerapi/servicebroker/blob/master/gettingStarted.md#sample-service-brokers)。
* 浏览 [kubernetes-incubator/service-catalog](https://github.com/kubernetes-incubator/service-catalog) 项目。
* 查看 [svc-cat.io](https://svc-cat.io/docs/)。
{{% /capture %}}