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/reference/_index.md
+6 -6
View File
@@ -3,7 +3,7 @@ title: 参考
linkTitle: "参考"
main_menu: true
weight: 70
content_template: templates/concept
content_type: concept
---
<!--
@@ -14,20 +14,20 @@ approvers:
linkTitle: "Reference"
main_menu: true
weight: 70
content_template: templates/concept
content_type: concept
---
-->
{{% capture overview %}}
<!-- overview -->
<!--
This section of the Kubernetes documentation contains references.
-->
这是 Kubernetes 文档的参考部分。
{{% /capture %}}
{{% capture body %}}
<!-- body -->
## API 参考
@@ -122,4 +122,4 @@ Kubernetes 功能的设计文档归档，不妨考虑从 [Kubernetes 架构](htt
An archive of the design docs for Kubernetes functionality. Good starting points are [Kubernetes Architecture](https://git.k8s.io/community/contributors/design-proposals/architecture/architecture.md) and [Kubernetes Design Overview](https://git.k8s.io/community/contributors/design-proposals).
-->
{{% /capture %}}
content/zh/docs/reference/access-authn-authz/abac.md
+6 -6
View File
@@ -5,7 +5,7 @@ approvers:
- deads2k
- liggitt
title: 使用 ABAC 鉴权
content_template: templates/concept
content_type: concept
---
<!--
@@ -16,21 +16,21 @@ reviewers:
- deads2k
- liggitt
title: Using ABAC Authorization
content_template: templates/concept
content_type: concept
weight: 80
---
-->
{{% capture overview %}}
<!-- overview -->
<!--
Attribute-based access control (ABAC) defines an access control paradigm whereby access rights are granted to users through the use of policies which combine attributes together.
-->
基于属性的访问控制（Attribute-based access control - ABAC）定义了访问控制范例，其中通过使用将属性组合在一起的策略来向用户授予访问权限。
{{% /capture %}}
{{% capture body %}}
<!-- body -->
<!--
## Policy File Format
@@ -311,5 +311,5 @@ system:serviceaccount:<namespace>:default
需要重新启动 apiserver 以获取新的策略行。
{{% /capture %}}
content/zh/docs/reference/access-authn-authz/admission-controllers.md
+6 -6
View File
@@ -1,6 +1,6 @@
---
title: 使用准入控制器
content_template: templates/concept
content_type: concept
weight: 30
---
@@ -14,20 +14,20 @@ reviewers:
- janetkuo
- thockin
title: Using Admission Controllers
content_template: templates/concept
content_type: concept
weight: 30
---
-->
{{% capture overview %}}
<!-- overview -->
<!--
This page provides an overview of Admission Controllers.
-->
此页面概述了准入控制器。
{{% /capture %}}
{{% capture body %}}
<!-- body -->
<!--
## What are they?
@@ -1218,4 +1218,4 @@ admission controllers ran in the exact order specified.
-->
对于更早期版本，没有验证和变更的概念，并且准入控制器按照指定的确切顺序运行。
{{% /capture %}}
content/zh/docs/reference/access-authn-authz/authorization.md
+7 -7
View File
@@ -8,17 +8,17 @@ cnapprove:
- fatalc
<!-- title: Authorization Overview -->
title: 授权概述
content_template: templates/concept
content_type: concept
weight: 60
---
{{% capture overview %}}
<!-- overview -->
<!-- Learn more about Kubernetes authorization, including details about creating
policies using the supported authorization modules. -->
了解有关 Kubernetes 授权的更多信息，包括使用支持的授权模块创建策略的详细信息。
{{% /capture %}}
{{% capture body %}}
<!-- body -->
<!-- In Kubernetes, you must be authenticated (logged in) before your request can be
authorized (granted permission to access). For information about authentication,
see [Accessing Control Overview](/docs/reference/access-authn-authz/controlling-access/).
@@ -292,13 +292,13 @@ mode.
并模拟命名空间中的任何服务帐户并执行帐户可以执行的任何操作。
无论采用何种授权方式，这都适用。
{{< /caution >}}
{{% /capture %}}
{{% capture whatsnext %}}
## {{% heading "whatsnext" %}}
<!--
* To learn more about Authentication, see **Authentication** in [Controlling Access to the Kubernetes API](/docs/reference/access-authn-authz/controlling-access/).
* To learn more about Admission Control, see [Using Admission Controllers](/docs/reference/access-authn-authz/admission-controllers/).
-->
* 要了解有关身份验证的更多信息，请参阅 **身份验证** [控制对 Kubernetes API 的访问](/docs/reference/access-authn-authz/controlling-access/)。
* 要了解有关准入控制的更多信息，请参阅 [使用准入控制器](/docs/reference/access-authn-authz/admission-controllers/)。
{{% /capture %}}
content/zh/docs/reference/access-authn-authz/extensible-admission-controllers.md
+6 -6
View File
@@ -1,18 +1,18 @@
---
title: 动态准入控制
content_template: templates/concept
content_type: concept
weight: 40
---
<!--
---
title: Dynamic Admission Control
content_template: templates/concept
content_type: concept
weight: 40
---
-->
{{% capture overview %}}
<!-- overview -->
<!--
In addition to [compiled-in admission plugins](/docs/reference/access-authn-authz/admission-controllers/),
admission plugins can be developed as extensions and run as webhooks configured at runtime.
@@ -20,9 +20,9 @@ This page describes how to build, configure, use, and monitor admission webhooks
-->
除了[内置的 admission 插件](/docs/reference/access-authn-authz/admission-controllers/)，admission 插件可以作为扩展独立开发，并以运行时所配置的 webhook 的形式运行。
此页面描述了如何构建、配置、使用和监视 admission webhook。
{{% /capture %}}
{{% capture body %}}
<!-- body -->
<!--
## What are admission webhooks?
-->
@@ -2174,4 +2174,4 @@ plane, exclude the `kube-system` namespace from being intercepted using a
意外更改或拒绝 `kube-system` 命名空间中的请求可能会导致控制平面组件停止运行或者导致未知行为发生。
如果您的 admission webhook 不想修改 Kubernetes 控制平面的行为，请使用 [`namespaceSelector`](#matching-requests-namespaceselector) 避免拦截 `kube-system` 命名空间。
{{% /capture %}}
content/zh/docs/reference/access-authn-authz/node.md
+6 -6
View File
@@ -1,6 +1,6 @@
---
title: 使用 Node 鉴权
content_template: templates/concept
content_type: concept
weight: 90
---
<!--
@@ -11,19 +11,19 @@ reviewers:
- liggitt
- ericchiang
title: Using Node Authorization
content_template: templates/concept
content_type: concept
weight: 90
---
-->
{{% capture overview %}}
<!-- overview -->
节点鉴权是一种特殊用途的鉴权模式，专门对 kubelet 发出的 API 请求进行鉴权。
<!--
Node authorization is a special-purpose authorization mode that specifically authorizes API requests made by kubelets.
-->
{{% /capture %}}
{{% capture body %}}
<!-- body -->
## 概述
<!--
## Overview
@@ -201,4 +201,4 @@ In 1.8, the binding will not be created at all.
When using RBAC, the `system:node` cluster role will continue to be created,
for compatibility with deployment methods that bind other users or groups to that role.
-->
{{% /capture %}}
content/zh/docs/reference/access-authn-authz/rbac.md
+6 -6
View File
@@ -1,6 +1,6 @@
---
title: 使用 RBAC 鉴权
content_template: templates/concept
content_type: concept
weight: 70
---
@@ -11,19 +11,19 @@ reviewers:
- deads2k
- liggitt
title: Using RBAC Authorization
content_template: templates/concept
content_type: concept
weight: 70
---
-->
{{% capture overview %}}
<!-- overview -->
<!--
Role-based access control (RBAC) is a method of regulating access to computer or network resources based on the roles of individual users within an enterprise.
-->
基于角色（Role）的访问控制（RBAC）是一种基于企业中用户的角色来调节控制对计算机或网络资源的访问方法。
{{% /capture %}}
{{% capture body %}}
<!-- body -->
<!--
`RBAC` uses the `rbac.authorization.k8s.io` {{< glossary_tooltip text="API Group" term_id="api-group" >}}
to drive authorization decisions, allowing admins to dynamically configure policies
@@ -2135,4 +2135,4 @@ kubectl create clusterrolebinding permissive-binding \
```
{{< /warning >}}
{{% /capture %}}
content/zh/docs/reference/access-authn-authz/webhook.md
+6 -6
View File
@@ -5,7 +5,7 @@ reviewers:
- deads2k
- liggitt
title: Webhook 模式
content_template: templates/concept
content_type: concept
weight: 95
---
<!--
@@ -16,19 +16,19 @@ reviewers:
- deads2k
- liggitt
title: Webhook Mode
content_template: templates/concept
content_type: concept
weight: 95
---
-->
{{% capture overview %}}
<!-- overview -->
<!--
A WebHook is an HTTP callback: an HTTP POST that occurs when something happens; a simple event-notification via HTTP POST. A web application implementing WebHooks will POST a message to a URL when certain things happen.
-->
WebHook 是一种 HTTP 回调：某些条件下触发的 HTTP POST 请求；通过 HTTP POST 发送的简单事件通知。一个基于 web 应用实现的 WebHook 会在特定事件发生时把消息发送给特定的 URL。
{{% /capture %}}
{{% capture body %}}
<!-- body -->
<!--
When specified, mode `Webhook` causes Kubernetes to query an outside REST
service when determining user privileges.
@@ -270,6 +270,6 @@ For further documentation refer to the authorization.v1beta1 API objects and
-->
更多信息可以参考 authorization.v1beta1 API 对象和[webhook.go](https://github.com/kubernetes/kubernetes/blob/{{< param "githubbranch" >}}/staging/src/k8s.io/apiserver/plugin/pkg/authorizer/webhook/webhook.go)。
{{% /capture %}}
content/zh/docs/reference/command-line-tools-reference/feature-gates.md
+9 -8
View File
@@ -1,18 +1,18 @@
---
weight: 10
title: 特性门控
content_template: templates/concept
content_type: concept
---
<!--
---
weight: 10
title: Feature Gates
content_template: templates/concept
content_type: concept
---
-->
{{% capture overview %}}
<!-- overview -->
<!--
This page contains an overview of the various feature gates an administrator
can specify on different Kubernetes components.
@@ -24,9 +24,9 @@ See [feature stages](#feature-stages) for an explanation of the stages for a fea
关于特性各个阶段的说明，请参见[特性阶段](#feature-stages)。
{{% /capture %}}
{{% capture body %}}
<!-- body -->
<!--
## Overview
@@ -776,8 +776,9 @@ Each feature gate is designed for enabling/disabling a specific feature:
- `WinDSR`：允许 kube-proxy 为 Windows 创建 DSR 负载均衡。
- `WinOverlay`：允许 kube-proxy 在 Windows 的 overlay 模式下运行。
{{% /capture %}}
{{% capture whatsnext %}}
## {{% heading "whatsnext" %}}
<!--
* The [deprecation policy](/docs/reference/using-api/deprecation-policy/) for Kubernetes explains
@@ -786,4 +787,4 @@ Each feature gate is designed for enabling/disabling a specific feature:
* Kubernetes 的 [弃用策略](/docs/reference/using-api/deprecation-policy/) 介绍了项目已移除的特性部件和组件的方法。
{{% /capture %}}
content/zh/docs/reference/command-line-tools-reference/kube-proxy.md
+6 -4
View File
@@ -11,7 +11,8 @@ weight: 28
---
-->
{{% capture synopsis %}}
## {{% heading "synopsis" %}}
<!--
@@ -29,9 +30,10 @@ Kubernetes 网络代理在每个节点上运行。网络代理反映了每个节
kube-proxy [flags]
```
{{% /capture %}}
{{% capture options %}}
## {{% heading "options" %}}
<table style="width: 100%; table-layout: fixed;">
<colgroup>
@@ -637,4 +639,4 @@ If set, write the default configuration values to this file and exit.
{{% /capture %}}
content/zh/docs/reference/command-line-tools-reference/kube-scheduler.md
+6 -4
View File
@@ -11,7 +11,8 @@ weight: 28
---
-->
{{% capture synopsis %}}
## {{% heading "synopsis" %}}
<!--
@@ -29,9 +30,10 @@ Kubernetes 调度器是一个策略丰富、拓扑感知、工作负载特定的
kube-scheduler [flags]
```
{{% /capture %}}
{{% capture options %}}
## {{% heading "options" %}}
<table style="width: 100%; table-layout: fixed;">
<colgroup>
@@ -1013,5 +1015,5 @@ kube-scheduler [flags]
{{% /capture %}}
content/zh/docs/reference/command-line-tools-reference/kubelet.md
+6 -4
View File
@@ -4,7 +4,8 @@ content_template: templates/tool-reference
weight: 28
---
{{% capture synopsis %}}
## {{% heading "synopsis" %}}
<!--
The kubelet is the primary "node agent" that runs on each node. It can register the node with the apiserver using one of: the hostname; a flag to override the hostname; or specific logic for a cloud provider.
@@ -41,10 +42,11 @@ HTTP server（HTTP 服务器）：kubelet 还可以侦听 HTTP 并响应简单
kubelet [flags]
```
{{% /capture %}}
{{% capture options %}}
## {{% heading "options" %}}
<table style="width: 100%; table-layout: fixed;">
<colgroup>
@@ -2158,4 +2160,4 @@ Specifies interval for kubelet to calculate and cache the volume disk usage for
</tbody>
</table>
{{% /capture %}}
content/zh/docs/reference/issues-security/security.md
+6 -6
View File
@@ -1,7 +1,7 @@
---
title: Kubernetes 安全和信息披露
aliases: [security/]
content_template: templates/concept
content_type: concept
weight: 20
---
@@ -13,18 +13,18 @@ reviewers:
- erictune
- philips
- jessfraz
content_template: templates/concept
content_type: concept
weight: 20
-->
{{% capture overview %}}
<!-- overview -->
<!--
This page describes Kubernetes security and disclosure information.
-->
本页面介绍 Kubernetes 安全和信息披露相关的内容。
{{% /capture %}}
{{% capture body %}}
<!-- body -->
<!--
## Security Announcements
-->
@@ -135,4 +135,4 @@ It is reasonable to delay disclosure when the bug or the fix is not yet fully un
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 %}}
content/zh/docs/reference/kubectl/cheatsheet.md
+9 -8
View File
@@ -4,7 +4,7 @@ reviewers:
- erictune
- krousey
- clove
content_template: templates/concept
content_type: concept
card:
name: reference
weight: 30
@@ -15,13 +15,13 @@ reviewers:
- erictune
- krousey
- clove
content_template: templates/concept
content_type: concept
card:
name: reference
weight: 30
--- -->
{{% capture overview %}}
<!-- overview -->
<!-- See also: [Kubectl Overview](/docs/reference/kubectl/overview/) and [JsonPath Guide](/docs/reference/kubectl/jsonpath). -->
也可以看下: [Kubectl 概述](/docs/reference/kubectl/overview/) 和 [JsonPath 指南](/docs/reference/kubectl/jsonpath)。
@@ -29,9 +29,9 @@ card:
<!-- This page is an overview of the `kubectl` command. -->
本页面是 `kubectl` 命令的概述。
{{% /capture %}}
{{% capture body %}}
<!-- body -->
<!-- # kubectl - Cheat Sheet -->
## kubectl - 备忘单
@@ -657,9 +657,10 @@ Kubectl 日志输出详细程度是通过 `-v` 或者 `--v` 来控制的，参
`--v=8` | 显示 HTTP 请求内容。
`--v=9` | 显示 HTTP 请求内容而不截断内容。
{{% /capture %}}
{{% capture whatsnext %}}
## {{% heading "whatsnext" %}}
<!-- * Learn more about [Overview of kubectl](/docs/reference/kubectl/overview/).
@@ -676,4 +677,4 @@ Kubectl 日志输出详细程度是通过 `-v` 或者 `--v` 来控制的，参
* 查看更多社区 [kubectl 备忘单](https://github.com/dennyzhang/cheatsheet-kubernetes-A4)。
{{% /capture %}}
content/zh/docs/reference/kubectl/conventions.md
+6 -6
View File
@@ -2,7 +2,7 @@
title: kubectl 的用法约定
reviewers:
- janetkuo
content_template: templates/concept
content_type: concept
---
<!--
@@ -10,18 +10,18 @@ content_template: templates/concept
title: kubectl Usage Conventions
reviewers:
- janetkuo
content_template: templates/concept
content_type: concept
---
-->
{{% capture overview %}}
<!-- overview -->
<!--
Recommended usage conventions for `kubectl`.
-->
`kubectl` 的推荐用法约定
{{% /capture %}}
{{% capture body %}}
<!-- body -->
<!--
## Using `kubectl` in Reusable Scripts
@@ -157,4 +157,4 @@ You can use the `--dry-run` flag to preview the object that would be sent to you
* 您可以使用 `kubectl apply` 命令创建或更新资源。有关使用 kubectl apply 更新资源的详细信息，请参阅 [Kubectl 文档](https://kubectl.docs.kubernetes.io)。
{{% /capture %}}
content/zh/docs/reference/kubectl/docker-cli-to-kubectl.md
+6 -6
View File
@@ -1,6 +1,6 @@
---
title: 适用于 Docker 用户的 kubectl
content_template: templates/concept
content_type: concept
reviewers:
- brendandburns
- thockin
@@ -8,21 +8,21 @@ reviewers:
<!--
---
title: kubectl for Docker Users
content_template: templates/concept
content_type: concept
reviewers:
- brendandburns
- thockin
---
-->
{{% capture overview %}}
<!-- overview -->
<!--
You can use the Kubernetes command line tool kubectl to interact with the API Server. Using kubectl is straightforward if you are familiar with the Docker command line tool. However, there are a few differences between the docker commands and the kubectl commands. The following sections show a docker sub-command and describe the equivalent kubectl command.
-->
您可以使用 Kubernetes 命令行工具 kubectl 与 API 服务器进行交互。如果您熟悉 Docker 命令行工具，则使用 kubectl 非常简单。但是，docker 命令和 kubectl 命令之间有一些区别。以下显示了 docker 子命令，并描述了等效的 kubectl 命令。
{{% /capture %}}
{{% capture body %}}
<!-- body -->
## docker run
<!--
@@ -487,4 +487,4 @@ Grafana is running at https://108.59.85.141/api/v1/namespaces/kube-system/servic
Heapster is running at https://108.59.85.141/api/v1/namespaces/kube-system/services/monitoring-heapster/proxy
InfluxDB is running at https://108.59.85.141/api/v1/namespaces/kube-system/services/monitoring-influxdb/proxy
```
{{% /capture %}}
content/zh/docs/reference/kubectl/jsonpath.md
+6 -6
View File
@@ -1,24 +1,24 @@
---
title: JSONPath 支持
content_template: templates/concept
content_type: concept
weight: 25
---
<!--
---
title: JSONPath Support
content_template: templates/concept
content_type: concept
weight: 25
---
-->
{{% capture overview %}}
<!-- overview -->
<!--
Kubectl supports JSONPath template.
-->
Kubectl 支持 JSONPath 模板。
{{% /capture %}}
{{% capture body %}}
<!-- body -->
<!--
JSONPath template is composed of JSONPath expressions enclosed by curly braces {}.
@@ -140,4 +140,4 @@ C:\> kubectl get pods -o=jsonpath="{range .items[*]}{.metadata.name}{'\t'}{.stat
C:\> kubectl get pods -o=jsonpath="{range .items[*]}{.metadata.name}{\"\t\"}{.status.startTime}{\"\n\"}{end}"
```
{{% /capture %}}
content/zh/docs/reference/kubectl/kubectl.md
+9 -6
View File
@@ -11,7 +11,8 @@ weight: 28
---
-->
{{% capture synopsis %}}
## {{% heading "synopsis" %}}
<!--
@@ -29,9 +30,10 @@ Find more information at: https://kubernetes.io/docs/reference/kubectl/overview/
kubectl [flags]
```
{{% /capture %}}
{{% capture options %}}
## {{% heading "options" %}}
<table style="width: 100%; table-layout: fixed;">
<colgroup>
@@ -513,9 +515,10 @@ kubectl [flags]
{{% /capture %}}
{{% capture seealso %}}
## {{% heading "seealso" %}}
<!--
* [kubectl annotate](/docs/reference/generated/kubectl/kubectl-commands#annotate) - Update the annotations on a resource
@@ -622,5 +625,5 @@ kubectl [flags]
* [kubectl version](/docs/reference/generated/kubectl/kubectl-commands#version) - 打印客户端和服务器的版本信息
* [kubectl wait](/docs/reference/generated/kubectl/kubectl-commands#wait) - 实验性：等待一个或多个资源达到某种状态
{{% /capture %}}
content/zh/docs/reference/kubectl/overview.md
+9 -8
View File
@@ -2,7 +2,7 @@
reviewers:
- hw-qiaolei
title: kubectl 概述
content_template: templates/concept
content_type: concept
weight: 20
card:
name: reference
@@ -14,7 +14,7 @@ reviewers:
- bgrant0607
- hw-qiaolei
title: Overview of kubectl
content_template: templates/concept
content_type: concept
weight: 20
card:
name: reference
@@ -22,7 +22,7 @@ card:
---
-->
{{% capture overview %}}
<!-- overview -->
<!--
Kubectl is a command line interface for running commands against Kubernetes clusters. `kubectl` looks for a file named config in the $HOME/.kube directory. You can specify other [kubeconfig](https://kubernetes.io/docs/concepts/configuration/organize-cluster-access-kubeconfig/) files by setting the KUBECONFIG environment variable or by setting the [`--kubeconfig`](https://kubernetes.io/docs/concepts/configuration/organize-cluster-access-kubeconfig/) flag.
@@ -34,9 +34,9 @@ This overview covers `kubectl` syntax, describes the command operations, and pro
-->
本文概述了 `kubectl` 语法和命令操作描述，并提供了常见的示例。有关每个命令的详细信息，包括所有受支持的参数和子命令，请参阅 [kubectl](/docs/reference/generated/kubectl/kubectl-commands/) 参考文档。有关安装说明，请参见 [安装 kubectl](/docs/tasks/kubectl/install/) 。
{{% /capture %}}
{{% capture body %}}
<!-- body -->
<!--
## Syntax
@@ -909,13 +909,14 @@ To find out more about plugins, take a look at the [example cli plugin](https://
-->
要了解关于插件的更多信息，请查看[示例 cli 插件](https://github.com/kubernetes/sample-cli-plugin)。
{{% /capture %}}
{{% capture whatsnext %}}
## {{% heading "whatsnext" %}}
<!--
Start using the [kubectl](/docs/reference/generated/kubectl/kubectl-commands/) commands.
-->
开始使用 [kubectl](/docs/reference/generated/kubectl/kubectl-commands/) 命令。
{{% /capture %}}
content/zh/docs/reference/kubernetes-api/labels-annotations-taints.md
+5 -5
View File
@@ -1,10 +1,10 @@
---
title: 知名标签（Label）、注解（Annotation）和 Taints
content_template: templates/concept
content_type: concept
weight: 60
---
{{% capture overview %}}
<!-- overview -->
<!--
Kubernetes reserves all labels and annotations in the kubernetes.io namespace.
@@ -16,9 +16,9 @@ Kubernetes 保留了 kubernetes.io 命名空间下的所有标签和注解。
本文既作为这些标签和注解的参考，也就这些标签和注解的赋值进行了说明。
{{% /capture %}}
{{% capture body %}}
<!-- body -->
## kubernetes.io/arch
@@ -272,4 +272,4 @@ adding the labels manually (or adding support for `PersistentVolumeLabel`). With
如果 `PersistentVolumeLabel` 准入控制器不支持自动为 PersistentVolume 打标签，且用户希望防止 pod 跨区域进行卷的挂载，
应考虑手动打标签 (或对 `PersistentVolumeLabel` 增加支持）。如果用户的基础设施没有这种约束，则不需要为卷添加区域标签。
{{% /capture %}}
content/zh/docs/reference/setup-tools/kubeadm/kubeadm-config.md
+8 -7
View File
@@ -1,10 +1,10 @@
---
title: kubeadm config
content_template: templates/concept
content_type: concept
weight: 50
---
{{% capture overview %}}
<!-- overview -->
<!--
Beginning with v1.8.0, kubeadm uploads the configuration of your cluster to a ConfigMap called
`kubeadm-config` in the `kube-system` namespace, and later reads the ConfigMap when upgrading.
@@ -33,9 +33,9 @@ to list and pull the images that kubeadm requires.
打印默认配置，可以用 kubeadm config migrate 来将旧的配置文件转换到较新的版本，还可以使用 kubeadm config images list 和 kubeadm config images pull
列出并拉取 kubeadm 所需的镜像。
{{% /capture %}}
{{% capture body %}}
<!-- body -->
## kubeadm config upload from-file {#cmd-config-from-file}
## kubeadm config view {#cmd-config-view}
@@ -56,14 +56,15 @@ to list and pull the images that kubeadm requires.
## kubeadm config images pull {#cmd-config-images-pull}
{{< include "generated/kubeadm_config_images_pull.md" >}}
{{% /capture %}}
{{% capture whatsnext %}}
## {{% heading "whatsnext" %}}
<!--
* [kubeadm upgrade](/docs/reference/setup-tools/kubeadm/kubeadm-upgrade/) to upgrade a Kubernetes cluster to a newer version
-->
* [kubeadm upgrade](/docs/reference/setup-tools/kubeadm/kubeadm-upgrade/) 将 Kubernetes 集群升级到更新版本 [kubeadm upgrade]
{{% /capture %}}
content/zh/docs/reference/setup-tools/kubeadm/kubeadm-init.md
+9 -8
View File
@@ -1,6 +1,6 @@
---
title: kubeadm init
content_template: templates/concept
content_type: concept
weight: 20
---
@@ -11,18 +11,18 @@ reviewers:
- luxas
- jbeda
title: kubeadm init
content_template: templates/concept
content_type: concept
weight: 20
---
-->
{{% capture overview %}}
<!-- overview -->
<!--
This command initializes a Kubernetes control-plane node.
-->
此命令初始化一个 Kubernetes 控制平面节点。
{{% /capture %}}
{{% capture body %}}
<!-- body -->
{{< include "generated/kubeadm_init.md" >}}
@@ -461,9 +461,10 @@ provisioned). For details, see the [kubeadm join](/docs/reference/setup-tools/ku
-->
注意这种搭建集群的方式在安全保证上会有一些宽松，因为这种方式不允许使用 `--discovery-token-ca-cert-hash` 来验证根 CA 的哈希值（因为当配置节点的时候，它还没有被生成）。获取需更多信息请参阅[kubeadm join](/docs/reference/setup-tools/kubeadm/kubeadm-join/)文档。
{{% /capture %}}
{{% capture whatsnext %}}
## {{% heading "whatsnext" %}}
<!--
* [kubeadm init phase](/docs/reference/setup-tools/kubeadm/kubeadm-init-phase/) to understand more about
`kubeadm init` phases
@@ -475,4 +476,4 @@ provisioned). For details, see the [kubeadm join](/docs/reference/setup-tools/ku
* [kubeadm join](/docs/reference/setup-tools/kubeadm/kubeadm-join/)启动一个 Kubernetes 工作节点并且将其加入到集群
* [kubeadm upgrade](/docs/reference/setup-tools/kubeadm/kubeadm-upgrade/)将 Kubernetes 集群升级到新版本
* [kubeadm reset](/docs/reference/setup-tools/kubeadm/kubeadm-reset/)使用 `kubeadm init` 或 `kubeadm join` 来恢复对节点的变更
{{% /capture %}}
content/zh/docs/reference/setup-tools/kubeadm/kubeadm-join.md
+8 -7
View File
@@ -4,17 +4,17 @@ reviewers:
- luxas
- jbeda
title: kubeadm join
content_template: templates/concept
content_type: concept
weight: 30
---
{{% capture overview %}}
<!-- overview -->
<!--
This command initializes a Kubernetes worker node and joins it to the cluster.
-->
此命令用来初始化 Kubernetes 工作节点并将其加入集群。
{{% /capture %}}
{{% capture body %}}
<!-- body -->
{{< include "generated/kubeadm_join.md" >}}
<!--
@@ -385,9 +385,10 @@ For details on individual fields in `JoinConfiguration` see [the godoc](https://
-->
要了解 `JoinConfiguration` 中各个字段的详细信息请参考 [godoc](https://godoc.org/k8s.io/kubernetes/cmd/kubeadm/app/apis/kubeadm#JoinConfiguration)。
{{% /capture %}}
{{% capture whatsnext %}}
## {{% heading "whatsnext" %}}
<!--
* [kubeadm init](/docs/reference/setup-tools/kubeadm/kubeadm-init/) to bootstrap a Kubernetes master node
* [kubeadm token](/docs/reference/setup-tools/kubeadm/kubeadm-token/) to manage tokens for `kubeadm join`
@@ -396,4 +397,4 @@ For details on individual fields in `JoinConfiguration` see [the godoc](https://
* [kubeadm init](/docs/reference/setup-tools/kubeadm/kubeadm-init/) 初始化 Kubernetes 主节点
* [kubeadm token](/docs/reference/setup-tools/kubeadm/kubeadm-token/) 管理 `kubeadm join` 的令牌
* [kubeadm reset](/docs/reference/setup-tools/kubeadm/kubeadm-reset/) 将 `kubeadm init` 或 `kubeadm join` 对主机的更改恢复到之前状态
{{% /capture %}}
content/zh/docs/reference/setup-tools/kubeadm/kubeadm-reset.md
+9 -8
View File
@@ -1,6 +1,6 @@
---
title: kubeadm reset
content_template: templates/concept
content_type: concept
weight: 60
---
<!-- ---
@@ -9,16 +9,16 @@ reviewers:
- luxas
- jbeda
title: kubeadm reset
content_template: templates/concept
content_type: concept
weight: 60
--- -->
{{% capture overview %}}
<!-- overview -->
<!-- Performs a best effort revert of changes made by `kubeadm init` or `kubeadm join`. -->
该命令尽力还原由 `kubeadm init` 或 `kubeadm join` 所做的更改。
{{% /capture %}}
{{% capture body %}}
<!-- body -->
{{< include "generated/kubeadm_reset.md" >}}
<!-- ### Reset workflow {#reset-workflow} -->
@@ -52,11 +52,12 @@ etcdctl del "" --prefix
<!-- See the [etcd documentation](https://github.com/coreos/etcd/tree/master/etcdctl) for more information. -->
更多详情请参考 [etcd 文档](https://github.com/coreos/etcd/tree/master/etcdctl)。
{{% /capture %}}
{{% capture whatsnext %}}
## {{% heading "whatsnext" %}}
<!-- * [kubeadm init](/docs/reference/setup-tools/kubeadm/kubeadm-init/) to bootstrap a Kubernetes control-plane node
* [kubeadm join](/docs/reference/setup-tools/kubeadm/kubeadm-join/) to bootstrap a Kubernetes worker node and join it to the cluster -->
* 参考 [kubeadm init](/docs/reference/setup-tools/kubeadm/kubeadm-init/) 来初始化 Kubernetes 主节点。
* 参考 [kubeadm join](/docs/reference/setup-tools/kubeadm/kubeadm-join/) 来初始化 Kubernetes 工作节点并加入集群。
{{% /capture %}}
content/zh/docs/reference/setup-tools/kubeadm/kubeadm-token.md
+9 -8
View File
@@ -1,6 +1,6 @@
---
title: kubeadm 令牌
content_template: templates/concept
content_type: concept
weight: 70
---
@@ -11,12 +11,12 @@ reviewers:
- luxas
- jbeda
title: kubeadm token
content_template: templates/concept
content_type: concept
weight: 70
---
-->
{{% capture overview %}}
<!-- overview -->
<!--
Bootstrap tokens are used for establishing bidirectional trust between a node joining
the cluster and a master node, as described in [authenticating with bootstrap tokens](/docs/reference/access-authn-authz/bootstrap-tokens/).
@@ -31,9 +31,9 @@ such a token and also to create and manage new ones.
`kubeadm init` 创建了一个有效期为 24 小时的令牌，下面的命令允许您管理令牌，也可以创建和管理新的令牌。
{{% /capture %}}
{{% capture body %}}
<!-- body -->
## kubeadm token create {#cmd-token-create}
{{< include "generated/kubeadm_token_create.md" >}}
@@ -45,11 +45,12 @@ such a token and also to create and manage new ones.
## kubeadm token list {#cmd-token-list}
{{< include "generated/kubeadm_token_list.md" >}}
{{% /capture %}}
{{% capture whatsnext %}}
## {{% heading "whatsnext" %}}
* [kubeadm join](/docs/reference/setup-tools/kubeadm/kubeadm-join/) 引导 Kubernetes 工作节点并将其加入群集
{{% /capture %}}
<!--
* [kubeadm join](/docs/reference/setup-tools/kubeadm/kubeadm-join/) to bootstrap a Kubernetes worker node and join it to the cluster
-->
content/zh/docs/reference/setup-tools/kubeadm/kubeadm-upgrade.md
+9 -8
View File
@@ -1,6 +1,6 @@
---
title: kubeadm upgrade
content_template: templates/concept
content_type: concept
weight: 40
---
<!-- ---
@@ -9,18 +9,18 @@ reviewers:
- luxas
- jbeda
title: kubeadm upgrade
content_template: templates/concept
content_type: concept
weight: 40
--- -->
{{% capture overview %}}
<!-- overview -->
<!--
`kubeadm upgrade` is a user-friendly command that wraps complex upgrading logic
behind one command, with support for both planning an upgrade and actually performing it. -->
`kubeadm upgrade` 是一个对用户友好的命令，它将复杂的升级逻辑包装在一个命令后面，支持升级的规划和实际执行。
{{% /capture %}}
{{% capture body %}}
<!-- body -->
<!--
## kubeadm upgrade guidance
@@ -66,10 +66,11 @@ renewal see the [certificate management documentation](/docs/tasks/administer-cl
## kubeadm upgrade node {#cmd-upgrade-node}
{{< include "generated/kubeadm_upgrade_node.md" >}}
{{% /capture %}}
{{% capture whatsnext %}}
## {{% heading "whatsnext" %}}
<!--
* [kubeadm config](/docs/reference/setup-tools/kubeadm/kubeadm-config/) if you initialized your cluster using kubeadm v1.7.x or lower, to configure your cluster for `kubeadm upgrade` -->
* 如果您使用 kubeadm v1.7.x 或更低版本初始化集群，则可以参考[kubeadm 配置](/docs/reference/setup-tools/kubeadm/kubeadm-config/)配置集群用于 `kubeadm upgrade`。
{{% /capture %}}
content/zh/docs/reference/setup-tools/kubeadm/kubeadm-version.md
+5 -5
View File
@@ -4,19 +4,19 @@ reviewers:
- luxas
- jbeda
title: kubeadm version
content_template: templates/concept
content_type: concept
weight: 80
---
{{% capture overview %}}
<!-- overview -->
<!--
This command prints the version of kubeadm.
-->
此命令用来查询 kubeadm 的版本。
{{% /capture %}}
{{% capture body %}}
<!-- body -->
{{< include "generated/kubeadm_version.md" >}}
{{% /capture %}}
content/zh/docs/reference/tools.md
+6 -6
View File
@@ -2,7 +2,7 @@
reviewers:
- janetkuo
title: 工具
content_template: templates/concept
content_type: concept
---
<!--
@@ -10,7 +10,7 @@ content_template: templates/concept
reviewers:
- janetkuo
title: Tools
content_template: templates/concept
content_type: concept
---
-->
@@ -19,11 +19,11 @@ content_template: templates/concept
<!--
Kubernetes contains several built-in tools to help you work with the Kubernetes system.
-->
{{% capture overview %}}
<!-- overview -->
Kubernetes 包含一些内置工具，可以帮助用户更好的使用 Kubernetes 系统。
{{% /capture %}}
{{% capture body %}}
<!-- body -->
## Kubectl
<!--
@@ -109,4 +109,4 @@ Use Kompose to:
* 将一个 Docker Compose 文件解释成 Kubernetes 对象
* 将本地 Docker 开发 转变成通过 Kubernetes 来管理
* 转换 v1 或 v2 Docker Compose `yaml` 文件 或 [分布式应用程序包](https://docs.docker.com/compose/bundles/)
{{% /capture %}}
content/zh/docs/reference/using-api/api-overview.md
+6 -6
View File
@@ -1,6 +1,6 @@
---
title: Kubernetes API 总览
content_template: templates/concept
content_type: concept
weight: 10
card:
name: reference
@@ -15,7 +15,7 @@ reviewers:
- erictune
- lavalamp
- jbeda
content_template: templates/concept
content_type: concept
weight: 10
card:
name: reference
@@ -24,16 +24,16 @@ card:
---
-->
{{% capture overview %}}
<!-- overview -->
<!--
This page provides an overview of the Kubernetes API.
-->
此页提供 Kubernetes API 的总览
{{% /capture %}}
{{% capture body %}}
<!-- body -->
<!--
The REST API is the fundamental fabric of Kubernetes. All operations and communications between components, and external user commands are REST API calls that the API Server handles. Consequently, everything in the Kubernetes
@@ -229,4 +229,4 @@ Individual resource enablement/disablement is only supported in the `extensions/
{{< /note >}}
{{% /capture %}}
content/zh/docs/reference/using-api/client-libraries.md
+6 -6
View File
@@ -1,6 +1,6 @@
---
title: 客户端库
content_template: templates/concept
content_type: concept
weight: 30
---
@@ -9,20 +9,20 @@ weight: 30
title: Client Libraries
reviewers:
- ahmetb
content_template: templates/concept
content_type: concept
weight: 30
---
-->
{{% capture overview %}}
<!-- overview -->
<!--
This page contains an overview of the client libraries for using the Kubernetes
API from various programming languages.
-->
本页面包含基于各种编程语言使用 Kubernetes API 的客户端库概述。
{{% /capture %}}
{{% capture body %}}
<!-- body -->
<!--
To write applications using the [Kubernetes REST API](/docs/reference/using-api/api-overview/),
you do not need to implement the API calls and request/response types yourself.
@@ -144,6 +144,6 @@ their authors, not the Kubernetes team.
| DotNet (RestSharp) | [github.com/masroorhasan/Kubernetes.DotNet](https://github.com/masroorhasan/Kubernetes.DotNet) |
| Elixir | [github.com/obmarg/kazan](https://github.com/obmarg/kazan/) |
| Haskell | [github.com/soundcloud/haskell-kubernetes](https://github.com/soundcloud/haskell-kubernetes) |
{{% /capture %}}