add zh pages

content/zh/docs/reference/access-authn-authz/abac.md

@@ -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

@@ -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

@@ -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

@@ -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

@@ -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

@@ -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

@@ -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 %}}
+