Merge pull request #25405 from tengqm/zh-fix-links-4

[zh] Fix links in zh localization (4)

Author: k8s-ci-robot

content/zh/docs/reference/_index.md

@@ -70,7 +70,8 @@ client libraries:
 ## CLI 参考
 
 * [kubectl](/zh/docs/reference/kubectl/overview/) - 主要的 CLI 工具，用于运行命令和管理 Kubernetes 集群。
-    * [JSONPath](/zh/docs/reference/kubectl/jsonpath/) - 通过 kubectl 使用 [JSONPath 表达式](http://goessner.net/articles/JsonPath/) 的语法指南。
+    * [JSONPath](/zh/docs/reference/kubectl/jsonpath/) - 通过 kubectl 使用
+      [JSONPath 表达式](https://goessner.net/articles/JsonPath/) 的语法指南。
 * [kubeadm](/zh/docs/reference/setup-tools/kubeadm/) - 此 CLI 工具可轻松配置安全的 Kubernetes 集群。
 
 <!--
@@ -100,5 +101,8 @@ An archive of the design docs for Kubernetes functionality. Good starting points
 -->
 ## 设计文档
 
-Kubernetes 功能的设计文档归档，不妨考虑从 [Kubernetes 架构](https://git.k8s.io/community/contributors/design-proposals/architecture/architecture.md) 和 [Kubernetes 设计概述](https://git.k8s.io/community/contributors/design-proposals)开始阅读。
+Kubernetes 功能的设计文档归档，不妨考虑从
+[Kubernetes 架构](https://git.k8s.io/community/contributors/design-proposals/architecture/architecture.md) 和
+[Kubernetes 设计概述](https://git.k8s.io/community/contributors/design-proposals)
+开始阅读。
 

content/zh/docs/reference/access-authn-authz/admission-controllers.md

@@ -5,7 +5,6 @@ weight: 30
 ---
 
 <!--
----
 reviewers:
 - lavalamp
 - davidopp
@@ -16,17 +15,14 @@ reviewers:
 title: Using Admission Controllers
 content_type: concept
 weight: 30
----
 -->
 
-
 <!-- overview -->
 <!--
 This page provides an overview of Admission Controllers.
 -->
 此页面概述了准入控制器。
 
-
 <!-- body -->
 
 <!--
@@ -228,7 +224,7 @@ to perform different actions on CertificateSigningRequest resources.
 -->
 
 有关对证书签名请求资源执行不同操作所需权限的详细信息，
-请参阅[证书签名请求](/docs/reference/access-authn-authz/certificate-signing-requests/)
+请参阅[证书签名请求](/zh/docs/reference/access-authn-authz/certificate-signing-requests/)
 
 ### CertificateSigning
 

content/zh/docs/reference/access-authn-authz/extensible-admission-controllers.md

@@ -28,7 +28,7 @@ This document describes how to authenticate and authorize access to the kubelet'
 <!-- 
 ## Kubelet authentication 
 -->
-## Kubelet 认证 
+## Kubelet 身份认证 
 
 <!-- 
 By default, requests to the kubelet's HTTPS endpoint that are not rejected by other configured
@@ -56,11 +56,12 @@ To enable X509 client certificate authentication to the kubelet's HTTPS endpoint
 <!--  
 * start the kubelet with the `--client-ca-file` flag, providing a CA bundle to verify client certificates with
 * start the apiserver with `--kubelet-client-certificate` and `--kubelet-client-key` flags
-* see the [apiserver authentication documentation](/docs/admin/authentication/#x509-client-certs) for more details
+* see the [apiserver authentication documentation](/docs/reference/access-authn-authz/authentication/#x509-client-certs) for more details
 -->
 * 带 `--client-ca-file` 标志启动 kubelet，提供一个 CA 证书包以供验证客户端证书
 * 带 `--kubelet-client-certificate` 和 `--kubelet-client-key` 标志启动 apiserver
-* 有关更多详细信息，请参见 [apiserver 身份验证文档](/zh/docs/admin/authentication/#x509-client-certs)
+* 有关更多详细信息，请参见
+  [apiserver 身份验证文档](/zh/docs/reference/access-authn-authz/authentication/#x509-client-certs)
 
 <!--  
 To enable API bearer tokens (including service account tokens) to be used to authenticate to the kubelet's HTTPS endpoint:
@@ -113,12 +114,15 @@ To subdivide access to the kubelet API, delegate authorization to the API server
 -->
 * 确保在 API 服务器中启用了 `authorization.k8s.io/v1beta1` API 组
 * 带 `--authorization-mode=Webhook` 和 `--kubeconfig` 标志启动 kubelet
-* kubelet 调用已配置的 API 服务器上的 `SubjectAccessReview` API，以确定每个请求是否得到鉴权
+* kubelet 调用已配置的 API 服务器上的 `SubjectAccessReview` API，
+  以确定每个请求是否得到鉴权
 
 <!--  
-The kubelet authorizes API requests using the same [request attributes](/docs/admin/authorization/#request-attributes) approach as the apiserver.
+The kubelet authorizes API requests using the same [request attributes](/docs/reference/access-authn-authz/authorization/#review-your-request-attributes) approach as the apiserver.
 -->
-kubelet 使用与 apiserver 相同的[请求属性](/zh/docs/admin/authorization/#request-attributes)方法对 API 请求执行鉴权。
+kubelet 使用与 apiserver 相同的
+[请求属性](/zh/docs/reference/access-authn-authz/authorization/#review-your-request-attributes)
+方法对 API 请求执行鉴权。
 
 <!--  
 The verb is determined from the incoming request's HTTP verb:
@@ -170,4 +174,4 @@ flags passed to the apiserver is authorized for the following attributes:
 * verb=\*, resource=nodes, subresource=stats
 * verb=\*, resource=nodes, subresource=log
 * verb=\*, resource=nodes, subresource=spec
-* verb=\*, resource=nodes, subresource=metrics
+* verb=\*, resource=nodes, subresource=metrics

content/zh/docs/reference/command-line-tools-reference/feature-gates.md

@@ -16,7 +16,7 @@ and progress on the feature is being tracked as [feature #43](https://github.com
 
 ## kube-apiserver configuration
 
-The API server should be configured with an [authenticator](/docs/admin/authentication/) that can authenticate tokens as a user in the `system:bootstrappers` group.
+The API server should be configured with an [authenticator](/zh/docs/reference/access-authn-authz/authentication/) that can authenticate tokens as a user in the `system:bootstrappers` group.
 
 This group will later be used in the controller-manager configuration to scope approvals in the default approval
 controller. As this feature matures, you should ensure tokens are bound to a Role-Based Access Control (RBAC) policy which limits requests

content/zh/docs/reference/command-line-tools-reference/kubelet-authentication-authorization.md

@@ -10,10 +10,8 @@ tags:
 - fundamental
 - extension
 ---
-  扩展组件是扩展并与 Kubernetes 深度集成以支持新型硬件的软件组件。
 
 <!--
----
 title: Extensions
 id: Extensions
 date: 2019-02-01
@@ -25,9 +23,11 @@ aka:
 tags:
 - fundamental
 - extension
----
+-->
+<!--
  Extensions are software components that extend and deeply integrate with Kubernetes to support new types of hardware.
 -->
+  扩展组件是扩展并与 Kubernetes 深度集成以支持新型硬件的软件组件。
 
 <!--more-->
 
@@ -36,5 +36,5 @@ Most cluster administrators will use a hosted or distribution instance of Kubern
 -->
 
 大多数集群管理员会使用托管的 Kubernetes 或其某种发行包。因此，大多数 Kubernetes 用户将需要
-安装 [扩展组件](/docs/concepts/extend-kubernetes/extend-cluster/#extensions)，
-较少用户会需要编写新的扩展组件。
+安装[扩展组件](/zh/docs/concepts/extend-kubernetes/extend-cluster/#extensions)，
+较少用户会需要编写新的扩展组件。

content/zh/docs/reference/command-line-tools-reference/kubelet-tls-bootstrapping.md

@@ -4,31 +4,32 @@ id: flexvolume
 date: 2018-06-25
 full_link: /zh/docs/concepts/storage/volumes/#flexvolume
 short_description: >
-    Flexvolume 是创建 out-of-tree 卷插件的一种接口。 {{< glossary_tooltip text="容器存储接口（CSI）" term_id="csi" >}} 是比 Flexvolume 更新的接口，它解决了 Flexvolumes 的一些问题。
-
+  Flexvolume 是创建树外卷插件的一种接口。
+  {{< glossary_tooltip text="容器存储接口（CSI）" term_id="csi" >}}
+  是比 Flexvolume 更新的接口，它解决了 Flexvolumes 的一些问题。
 
 aka: 
 tags:
 - storage 
 ---
 
-<!-- ---
+<!--
 title: FlexVolume
 id: flexvolume
 date: 2018-06-25
 full_link: /docs/concepts/storage/volumes/#flexvolume
 short_description: >
     FlexVolume is an interface for creating out-of-tree volume plugins. The {{< glossary_tooltip text="Container Storage Interface" term_id="csi" >}} is a newer interface which addresses several problems with FlexVolumes.
-
-
 aka: 
 tags:
 - storage 
---- -->
- <!-- 
- FlexVolume is an interface for creating out-of-tree volume plugins. The {{< glossary_tooltip text="Container Storage Interface" term_id="csi" >}} is a newer interface which addresses several problems with FlexVolumes.
- -->
- Flexvolume 是创建 out-of-tree 卷插件的一种接口。 {{< glossary_tooltip text="容器存储接口（CSI）" term_id="csi" >}} 是比 Flexvolume 更新的接口，它解决了 Flexvolume 的一些问题。
+-->
+<!-- 
+FlexVolume is an interface for creating out-of-tree volume plugins. The {{< glossary_tooltip text="Container Storage Interface" term_id="csi" >}} is a newer interface which addresses several problems with FlexVolumes.
+-->
+Flexvolume 是创建树外卷插件的一种接口。
+{{< glossary_tooltip text="容器存储接口（CSI）" term_id="csi" >}}
+是比 Flexvolume 更新的接口，它解决了 Flexvolume 的一些问题。
 
 <!--more--> 
 
@@ -37,14 +38,15 @@ FlexVolumes enable users to write their own drivers and add support for their vo
 -->
 Flexvolume 允许用户编写自己的驱动程序，并在 Kubernetes 中加入对用户自己的数据卷的支持。
 FlexVolume 驱动程序的二进制文件和依赖项必须安装在主机上。
-这需要 root 权限。如果可能的话，SIG Storage 建议实现 {{< glossary_tooltip text="CSI" term_id="csi" >}} 驱动程序，
+这需要 root 权限。如果可能的话，SIG Storage 建议实现
+{{< glossary_tooltip text="CSI" term_id="csi" >}} 驱动程序，
 因为它解决了 Flexvolumes 的限制。
 
 <!-- 
 * [FlexVolume in the Kubernetes documentation](/docs/concepts/storage/volumes/#flexvolume)
 * [More information on FlexVolumes](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-storage/flexvolume.md)
 * [Volume Plugin FAQ for Storage Vendors](https://github.com/kubernetes/community/blob/master/sig-storage/volume-plugin-faq.md) 
 -->
-* [Kubernetes 文档中的 Flexvolume](/docs/concepts/storage/volumes/#flexvolume)
+* [Kubernetes 文档中的 Flexvolume](/zh/docs/concepts/storage/volumes/#flexvolume)
 * [更多关于 Flexvolumes 的信息](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-storage/flexvolume.md)
-* [存储供应商的卷插件 FAQ](https://github.com/kubernetes/community/blob/master/sig-storage/volume-plugin-faq.md)
+* [存储供应商的卷插件 FAQ](https://github.com/kubernetes/community/blob/master/sig-storage/volume-plugin-faq.md)

content/zh/docs/reference/glossary/extensions.md

@@ -27,16 +27,16 @@ tags:
 <!--
  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" >}}所提供的托管服务。
+[服务目录](/zh/docs/concepts/extend-kubernetes/service-catalog/)
+提供了一种方法用来列举、制备和绑定到
+{{< glossary_tooltip text="服务代理商" term_id="service-broker" >}}
+所提供的托管服务。

content/zh/docs/reference/glossary/flexvolume.md

@@ -10,10 +10,8 @@ aka:
 tags:
 - architecture
 ---
- [operator 模式](/docs/concepts/extend-kubernetes/operator/) 是一个系统设计, 将 {{< glossary_tooltip term_id="controller" >}} 关联到一个或多个自定义资源。
 
 <!--
----
 title: Operator pattern
 id: operator-pattern
 date: 2019-05-21
@@ -24,12 +22,14 @@ short_description: >
 aka:
 tags:
 - architecture
----
- The [operator pattern](/docs/concepts/extend-kubernetes/operator/) is a system
+-->
+<!--
+The [operator pattern](/docs/concepts/extend-kubernetes/operator/) is a system
 design that links a {{< glossary_tooltip term_id="controller" >}} to one or more custom
 resources.
 -->
-
+[operator 模式](/zh/docs/concepts/extend-kubernetes/operator/) 是一种系统设计, 
+将 {{< glossary_tooltip term_id="controller" >}} 关联到一个或多个自定义资源。
 <!--more-->
 
 <!--
@@ -40,7 +40,9 @@ If a running application acts as a controller and has API access to carry out ta
 against a custom resource that's defined in the control plane, that's an example of
 the Operator pattern.
 -->
+除了使用作为 Kubernetes 自身一部分的内置控制器之外，你还可以通过
+将控制器添加到集群中来扩展 Kubernetes。
 
-除了使用作为 Kubernetes 自身一部分的内置控制器之外，您还可以通过将控制器添加到集群中来扩展 Kubernetes。
+如果正在运行的应用程序能够充当控制器并通过 API 访问的方式来执行任务操控
+那些在控制平面中定义的自定义资源，这就是一个 operator 模式的示例。
 
-如果正在运行的应用程序能够充当控制器并通过 API 访问的方式来执行任务操控那些在控制平面中定义的自定义资源，这就是一个 operator 模式的示例。