diff --git a/content/zh/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions.md b/content/zh/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions.md
new file mode 100644
index 0000000000..791f46eff0
--- /dev/null
+++ b/content/zh/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions.md
@@ -0,0 +1,1847 @@
+---
+title: 使用 CustomResourceDefinition 扩展 Kubernetes API
+content_type: task
+min-kubernetes-server-version: 1.16
+weight: 20
+---
+<!--
+title: Extend the Kubernetes API with CustomResourceDefinitions
+reviewers:
+- deads2k
+- jpbetz
+- liggitt
+- roycaihw
+- sttts
+content_type: task
+min-kubernetes-server-version: 1.16
+weight: 20
+-->
+
+<!-- overview -->
+本页展示如何使用
+[CustomResourceDefinition](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#customresourcedefinition-v1-apiextensions-k8s-io).
+将
+[自定义资源（Custom Resource）](/zh/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
+安装到 Kubernetes API。
+
+## {{% heading "prerequisites" %}}
+
+{{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}
+
+<!--
+If you are using an older version of Kubernetes that is still supported, switch to
+the documentation for that version to see advice that is relevant for your cluster.
+-->
+如果你在使用较老的、仍处于被支持范围的 Kubernetes 版本，请切换到该版本的
+文档查看对于的集群而言有用的建议。
+
+<!-- steps -->
+
+<!--
+## Create a CustomResourceDefinition
+
+When you create a new CustomResourceDefinition (CRD), the Kubernetes API Server
+creates a new RESTful resource path for each version you specify. The CRD can be
+either namespaced or cluster-scoped, as specified in the CRD's `scope` field. As
+with existing built-in objects, deleting a namespace deletes all custom objects
+in that namespace. CustomResourceDefinitions themselves are non-namespaced and
+are available to all namespaces.
+
+For example, if you save the following CustomResourceDefinition to `resourcedefinition.yaml`:
+-->
+## 创建 CustomResourceDefinition  {#create-a-customresourcedefinition}
+
+当你创建新的 CustomResourceDefinition（CRD）时，Kubernetes API 服务器会为你所
+指定的每一个版本生成一个 RESTful 的 资源路径。CRD 可以是名字空间作用域的，也可以
+是集群作用域的，取决于 CRD 的 `scope` 字段设置。和其他现有的内置对象一样，删除
+一个名字空间时，该名字空间下的所有定制对象也会被删除。CustomResourceDefinition
+本身是不受名字空间限制的，对所有名字空间可用。
+
+例如，如果你将下面的 CustomResourceDefinition 保存到 `resourcedefinition.yaml`
+文件：
+
+<!--
+```yaml
+apiVersion: apiextensions.k8s.io/v1
+kind: CustomResourceDefinition
+metadata:
+  # name must match the spec fields below, and be in the form: <plural>.<group>
+  name: crontabs.stable.example.com
+spec:
+  # group name to use for REST API: /apis/<group>/<version>
+  group: stable.example.com
+  # list of versions supported by this CustomResourceDefinition
+  versions:
+    - name: v1
+      # Each version can be enabled/disabled by Served flag.
+      served: true
+      # One and only one version must be marked as the storage version.
+      storage: true
+      schema:
+        openAPIV3Schema:
+          type: object
+          properties:
+            spec:
+              type: object
+              properties:
+                cronSpec:
+                  type: string
+                image:
+                  type: string
+                replicas:
+                  type: integer
+  # either Namespaced or Cluster
+  scope: Namespaced
+  names:
+    # plural name to be used in the URL: /apis/<group>/<version>/<plural>
+    plural: crontabs
+    # singular name to be used as an alias on the CLI and for display
+    singular: crontab
+    # kind is normally the CamelCased singular type. Your resource manifests use this.
+    kind: CronTab
+    # shortNames allow shorter string to match your resource on the CLI
+    shortNames:
+    - ct
+```
+-->
+```yaml
+apiVersion: apiextensions.k8s.io/v1
+kind: CustomResourceDefinition
+metadata:
+  # 名字必需与下面的 spec 字段匹配，并且格式为 '<名称的复数形式>.<组名>'
+  name: crontabs.stable.example.com
+spec:
+  # 组名称，用于 REST API: /apis/<组>/<版本>
+  group: stable.example.com
+  # 列举此 CustomResourceDefinition 所支持的版本
+  versions:
+    - name: v1
+      # 每个版本都可以通过 served 标志来独立启用或禁止
+      served: true
+      # 其中一个且只有一个版本必需被标记为存储版本
+      storage: true
+      schema:
+        openAPIV3Schema:
+          type: object
+          properties:
+            spec:
+              type: object
+              properties:
+                cronSpec:
+                  type: string
+                image:
+                  type: string
+                replicas:
+                  type: integer
+  # 可以是 Namespaced 或 Cluster
+  scope: Namespaced
+  names:
+    # 名称的复数形式，用于 URL：/apis/<组>/<版本>/<名称的复数形式>
+    plural: crontabs
+    # 名称的单数形式，作为命令行使用时和显示时的别名
+    singular: crontab
+    # kind 通常是单数形式的驼峰编码（CamelCased）形式。你的资源清单会使用这一形式。
+    kind: CronTab
+    # shortNames 允许你在命令行使用较短的字符串来匹配资源
+    shortNames:
+    - ct
+```
+
+<!--
+and create it:
+-->
+之后创建它：
+
+```shell
+kubectl apply -f resourcedefinition.yaml
+```
+
+<!--
+Then a new namespaced RESTful API endpoint is created at:
+-->
+这样一个新的受名字空间约束的 RESTful API 端点会被创建在：
+
+```
+/apis/stable.example.com/v1/namespaces/*/crontabs/...
+```
+
+<!--
+This endpoint URL can then be used to create and manage custom objects.
+The `kind` of these objects will be `CronTab` from the spec of the
+CustomResourceDefinition object you created above.
+
+It might take a few seconds for the endpoint to be created.
+You can watch the `Established` condition of your CustomResourceDefinition
+to be true or watch the discovery information of the API server for your
+resource to show up.
+-->
+此端点 URL 自此可以用来创建和管理定制对象。对象的 `kind` 将是来自你上面创建时
+所用的 spec 中指定的 `CronTab`。
+
+创建端点的操作可能需要几秒钟。你可以监测你的 CustomResourceDefinition 的
+`Established` 状况变为 true，或者监测 API 服务器的发现信息等待你的资源出现在
+那里。
+
+<!--
+## Create custom objects
+
+After the CustomResourceDefinition object has been created, you can create
+custom objects. Custom objects can contain custom fields. These fields can
+contain arbitrary JSON.
+In the following example, the `cronSpec` and `image` custom fields are set in a
+custom object of kind `CronTab`.  The kind `CronTab` comes from the spec of the
+CustomResourceDefinition object you created above.
+
+If you save the following YAML to `my-crontab.yaml`:
+-->
+## 创建定制对象   {#create-custom-objects}
+
+在创建了 CustomResourceDefinition 对象之后，你可以创建定制对象（Custom
+Objects）。定制对象可以包含定制字段。这些字段可以包含任意的 JSON 数据。
+在下面的例子中，在类别为 `CrontTab` 的定制对象中，设置了`cronSpec` 和 `image`
+定制字段。类别 `CronTab` 来自你在上面所创建的 CRD 的规约。
+
+如果你将下面的 YAML 保存到 `my-crontab.yaml`：
+
+```yaml
+apiVersion: "stable.example.com/v1"
+kind: CronTab
+metadata:
+  name: my-new-cron-object
+spec:
+  cronSpec: "* * * * */5"
+  image: my-awesome-cron-image
+```
+
+<!--
+and create it:
+-->
+并执行创建命令：
+
+```shell
+kubectl apply -f my-crontab.yaml
+```
+
+<!--
+You can then manage your CronTab objects using kubectl. For example:
+-->
+你就可以使用 kubectl 来管理你的 CronTab 对象了。例如：
+
+```shell
+kubectl get crontab
+```
+
+<!--
+Should print a list like this:
+-->
+应该会输出如下列表：
+
+```none
+NAME                 AGE
+my-new-cron-object   6s
+```
+
+<!--
+Resource names are not case-sensitive when using kubectl, and you can use either
+the singular or plural forms defined in the CRD, as well as any short names.
+
+You can also view the raw YAML data:
+-->
+使用 kubectl 时，资源名称是大小写不敏感的，而且你既可以使用 CRD 中所定义的单数
+形式或复数形式，也可以使用其短名称：
+
+```shell
+kubectl get ct -o yaml
+```
+
+<!--
+You should see that it contains the custom `cronSpec` and `image` fields
+from the yaml you used to create it:
+-->
+你可以看到输出中包含了你创建定制对象时在 YAML 文件中指定的定制字段 `cronSpec`
+和 `image`：
+
+```yaml
+apiVersion: v1
+kind: List
+items:
+- apiVersion: stable.example.com/v1
+  kind: CronTab
+  metadata:
+    creationTimestamp: 2017-05-31T12:56:35Z
+    generation: 1
+    name: my-new-cron-object
+    namespace: default
+    resourceVersion: "285"
+    uid: 9423255b-4600-11e7-af6a-28d2447dc82b
+  spec:
+    cronSpec: '* * * * */5'
+    image: my-awesome-cron-image
+metadata:
+  resourceVersion: ""
+```
+
+<!--
+## Delete a CustomResourceDefinition
+
+When you delete a CustomResourceDefinition, the server will uninstall the RESTful API  endpoint
+and delete all custom objects stored in it.
+-->
+## 删除 CustomResourceDefinition    {#delete-a-customresourcedefinition}
+
+当你删除某 CustomResourceDefinition 时，服务器会卸载其 RESTful API
+端点，并删除服务器上存储的所有定制对象。
+
+```shell
+kubectl delete -f resourcedefinition.yaml
+kubectl get crontabs
+```
+
+```none
+Error from server (NotFound): Unable to list {"stable.example.com" "v1" "crontabs"}: the server could not find the requested resource (get crontabs.stable.example.com)
+```
+
+<!--
+If you later recreate the same CustomResourceDefinition, it will start out empty.
+-->
+如果你在以后创建相同的 CustomResourceDefinition 时，该 CRD 会一个空的结构。
+
+<!--
+## Specifying a structural schema
+
+CustomResources store structured data in custom fiels (alongside the built-in fields `apiVersion`, `kind` and `metadata`, which the API server validates implicitly). With [OpenAPI v3.0 validation](/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/#validation) a schema can be specified, which is validated during creation and updates, compare below for details and limits of such a schema.
+
+With `apiextensions.k8s.io/v1` the definition of a structural schema is mandatory for CustomResourceDefinitions (in the beta version of CustomResourceDefinition, structural schemas were optional).
+-->
+## 设置结构化的模式   {#specifying-a-structural-schema}
+
+CustomResource 对象在定制字段中保存结构化的数据，这些字段和内置的字段
+`apiVersion`、`kind` 和 `metadata` 等一起存储，不过内置的字段都会被 API
+服务器隐式完成合法性检查。
+有了 [OpenAPI v3.0 检查](#validation)
+能力之后，你可以设置一个模式（Schema），在创建和更新定制对象时，这一模式会被用来
+对对象内容进行合法性检查。参阅下文了解这类模式的细节和局限性。
+
+在 `apiextensions.k8s.io/v1` 版本中，CustomResourceDefinition 的这一结构化模式
+定义是必需的（在 CustomResourceDefinition 的 beta
+版本中，结构化模式定义是可选的）。
+
+<!--
+A structural schema is an [OpenAPI v3.0 validation schema](/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/#validation) which:
+
+1. specifies a non-empty type (via `type` in OpenAPI) for the root, for each specified field of an object node (via `properties` or `additionalProperties` in OpenAPI) and for each item in an array node (via `items` in OpenAPI), with the exception of:
+   * a node with `x-kubernetes-int-or-string: true`
+   * a node with `x-kubernetes-preserve-unknown-fields: true`
+2. for each field in an object and each item in an array which is specified within any of `allOf`, `anyOf`, `oneOf` or `not`, the schema also specifies the field/item outside of those logical junctors (compare example 1 and 2).
+3. does not set `description`, `type`, `default`, `additionalProperties`, `nullable` within an `allOf`, `anyOf`, `oneOf` or `not`, with the exception of the two pattern for `x-kubernetes-int-or-string: true` (see below).
+4. if `metadata` is specified, then only restrictions on `metadata.name` and `metadata.generateName` are allowed.
+-->
+结构化模式本身是一个 [OpenAPI v3.0 验证模式](#validation)，其中：
+
+1. 为对象根（root）设置一个非空的 type 值（藉由 OpenAPI 中的 `type`），对每个
+   object 节点的每个字段（藉由 OpenAPI 中的 `properties` 或 `additionalProperties`）以及
+   array 节点的每个条目（藉由 OpenAPI 中的 `items`）也要设置非空的 type 值，
+   除非：
+   * 节点包含属性 `x-kubernetes-int-or-string: true`
+   * 节点包含属性 `x-kubernetes-preserve-unknown-fields: true`
+2. 对于 object 的每个字段或 array 中的每个条目，如果其定义中包含 `allOf`、`anyOf`、`oneOf`
+   或 `not`，则模式也要指定这些逻辑组合之外的字段或条目（试比较例 1 和例 2)。
+3. 在 `allOf`、`anyOf`、`oneOf` 或 `not` 上下文内不设置 `description`、`type`、`default`、
+   `additionalProperties` 或者 `nullable`。此规则的例外是
+   `x-kubernetes-int-or-string` 的两种模式（见下文）。
+4. 如果 `metadata` 被设置，则只允许对 `metadata.name` 和 `metadata.generateName` 设置约束。
+
+<!--
+Non-structural example 1:
+-->
+非结构化的例 1:
+
+```yaml
+allOf:
+- properties:
+    foo:
+      ...
+```
+
+<!--
+conflicts with rule 2. The following would be correct:
+-->
+违反了第 2 条规则。下面的是正确的：
+
+```yaml
+properties:
+  foo:
+    ...
+allOf:
+- properties:
+    foo:
+      ...
+```
+
+<!--
+Non-structural example 2:
+-->
+非结构化的例 2：
+
+```yaml
+allOf:
+- items:
+    properties:
+      foo:
+        ...
+```
+
+<!--
+conflicts with rule 2. The following would be correct:
+-->
+违反了第 2 条规则。下面的是正确的：
+
+```yaml
+items:
+  properties:
+    foo:
+      ...
+allOf:
+- items:
+    properties:
+      foo:
+        ...
+```
+
+<!--
+Non-structural example 3:
+-->
+非结构化的例 3：
+
+```yaml
+properties:
+  foo:
+    pattern: "abc"
+  metadata:
+    type: object
+    properties:
+      name:
+        type: string
+        pattern: "^a"
+      finalizers:
+        type: array
+        items:
+          type: string
+          pattern: "my-finalizer"
+anyOf:
+- properties:
+    bar:
+      type: integer
+      minimum: 42
+  required: ["bar"]
+  description: "foo bar object"
+```
+
+<!--
+is not a structural schema because of the following violations:
+
+* the type at the root is missing (rule 1).
+* the type of `foo` is missing (rule 1).
+* `bar` inside of `anyOf` is not specified outside (rule 2).
+* `bar`'s `type` is within `anyOf` (rule 3).
+* the description is set within `anyOf` (rule 3).
+* `metadata.finalizer` might not be restricted (rule 4).
+-->
+不是一个结构化的模式，因为其中存在以下违例：
+
+* 根节点缺失 type 设置（规则 1）
+* `foo` 的 type 缺失（规则 1）
+* `anyOf` 中的 `bar` 未在外部指定（规则 2）
+* `bar` 的 `type` 位于 `anyOf` 中（规则 3）
+* `anyOf` 中设置了 `description` （规则 3）
+* `metadata.finalizer` 不可以被限制 (规则 4）
+
+<!--
+In contrast, the following, corresponding schema is structural:
+-->
+作为对比，下面的 YAML 所对应的模式则是结构化的：
+
+```yaml
+type: object
+description: "foo bar object"
+properties:
+  foo:
+    type: string
+    pattern: "abc"
+  bar:
+    type: integer
+  metadata:
+    type: object
+    properties:
+      name:
+        type: string
+        pattern: "^a"
+anyOf:
+- properties:
+    bar:
+      minimum: 42
+  required: ["bar"]
+```
+
+<!--
+Violations of the structural schema rules are reported in the `NonStructural` condition in the CustomResourceDefinition.
+-->
+如果违反了结构化模式规则，CustomResourceDefinition 的 `NonStructural` 状况中
+会包含报告信息。
+
+<!--
+### Field pruning
+
+CustomResourceDefinitions store validated resource data in the cluster's persistence store, {{< glossary_tooltip term_id="etcd" text="etcd">}}. As with native Kubernetes resources such as {{< glossary_tooltip text="ConfigMap" term_id="configmap" >}}, if you specify a field that the API server does not recognize, the unknown field  is _pruned_ (removed) before being persisted.
+-->
+### 字段剪裁     {#field-pruning}
+
+CustomResourceDefinition 在集群的持久性存储
+{{< glossary_tooltip term_id="etcd" text="etcd">}}
+中保存经过合法性检查的资源数据。
+就像原生的 Kubernetes 资源，例如 {{< glossary_tooltip text="ConfigMap" term_id="configmap" >}}，
+如果你指定了 API 服务器所无法识别的字段，则该未知字段会在保存资源之前
+被 _剪裁（Pruned）_ 掉（删除）。
+
+<!--
+CRDs converted from `apiextensions.k8s.io/v1beta1` to
+`apiextensions.k8s.io/v1` might lack structural schemas, and
+`spec.preserveUnknownFields` might be `true`.
+
+For migrated CustomResourceDefinitions where `spec.preserveUnknownFields` is
+set, pruning is _not_ enabled and you can store arbitrary data. For best
+compatibility, you should update customer resources to meet an OpenAPI schema,
+and you should set `spec.preserveUnknownFields` true for the
+CustomResourceDefinition itself.
+-->
+{{< note >}}
+从 `apiextensions.k8s.io/v1beta1` 转换到 `apiextensions.k8s.io/v1` 的 CRD
+可能没有结构化的模式定义，因此其 `spec.preserveUnknownFields` 可能为 `true`。
+
+对于迁移而来的 CustomResourceDefinition，如果其 `spec.preserveUnknownFields`
+被设置为 `true`，则 Kubernetes _不会_ 执行剪裁操作，你可以存储任意数据。
+要实现最佳的兼容性，你应该更新定制资源以满足某 OpenAPI 模式定义，并且你
+应该将 CustomResourceDefinition 自身的 `spec.preserveUnknownFields` 设置为
+`true`。
+{{< /note >}}
+
+<!--
+If you save the following YAML to `my-crontab.yaml`:
+-->
+如果你将下面的 YAML 保存到 `my-crontab.yaml` 文件：
+
+```yaml
+apiVersion: "stable.example.com/v1"
+kind: CronTab
+metadata:
+  name: my-new-cron-object
+spec:
+  cronSpec: "* * * * */5"
+  image: my-awesome-cron-image
+  someRandomField: 42
+```
+
+<!--
+and create it:
+-->
+并创建之：
+
+```shell
+kubectl create --validate=false -f my-crontab.yaml -o yaml
+```
+
+<!--
+your output is similar to:
+-->
+输出类似于：
+
+```console
+apiVersion: stable.example.com/v1
+kind: CronTab
+metadata:
+  creationTimestamp: 2017-05-31T12:56:35Z
+  generation: 1
+  name: my-new-cron-object
+  namespace: default
+  resourceVersion: "285"
+  uid: 9423255b-4600-11e7-af6a-28d2447dc82b
+spec:
+  cronSpec: '* * * * */5'
+  image: my-awesome-cron-image
+```
+
+<!--
+Notice that the field `someRandomField` was pruned.
+-->
+注意其中的字段 `someRandomField` 已经被剪裁掉。
+
+<!--
+This example turned off client-side validation to demonstrate the API server's behavior, by adding the `--validate=false` command line option.
+Because the [OpenAPI validation schemas are also published](/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/#publish-validation-schema-in-openapi-v2)
+to clients, `kubectl` also checks for unknown fields and rejects those objects well before they would be sent to the API server.
+-->
+本例中通过 `--validate=false` 命令行选项 关闭了客户端的合法性检查以展示 API 服务器的行为，
+因为 [OpenAPI 合法性检查模式也会发布到](#publish-validation-schema-in-openapi-v2)
+客户端，`kubectl` 也会检查未知的字段并在对象被发送到 API
+服务器之前就拒绝它们。
+
+<!--
+#### Controlling pruning
+
+By default, all unspecified fields for a custom resource, across all versions, are pruned. It is possible though to opt-out of that for specifc sub-trees fof fields by adding `x-kubernetes-preserve-unknown-fields: true` in the [structural OpenAPI v3 validation schema](#specifying-a-structural-schema).  
+For example:
+-->
+#### 控制剪裁   {#controlling-pruning}
+
+默认情况下，定制资源的所有版本中的所有未规定的字段都会被剪裁掉。
+通过在 [结构化 OpenAPI v3 合法性检查模式定](#specifying-a-structural-schema)
+中为特定字段的子树添加 `x-kubernetes-preserve-unknown-fields: true` 属性，可以
+选择不对其执行剪裁操作。
+例如：
+
+```yaml
+type: object
+properties:
+  json:
+    x-kubernetes-preserve-unknown-fields: true
+```
+
+<!--
+The field `json` can store any JSON value, without anything being pruned.
+
+You can also partially specify the permitted JSON; for example:
+-->
+字段 `json` 可以保存任何 JSON 值，其中内容不会被剪裁掉。
+
+你也可以部分地指定允许的 JSON 数据格式；例如：
+
+```yaml
+type: object
+properties:
+  json:
+    x-kubernetes-preserve-unknown-fields: true
+    type: object
+    description: this is arbitrary JSON
+```
+
+<!--
+With this, only `object` type values are allowed.
+
+Pruning is enabled again for each specified property (or `additionalProperties`):
+-->
+通过这样设置，JSON 中只能设置 `object` 类型的值。
+
+对于所指定的每个属性（或 `additionalProperties`），剪裁会再次被启用。
+
+```yaml
+type: object
+properties:
+  json:
+    x-kubernetes-preserve-unknown-fields: true
+    type: object
+    properties:
+      spec:
+        type: object
+        properties:
+          foo:
+            type: string
+          bar:
+            type: string
+```
+
+<!--
+With this, the value:
+-->
+对于上述定义，如果提供的数值如下：
+
+```yaml
+json:
+  spec:
+    foo: abc
+    bar: def
+    something: x
+  status:
+    something: x
+```
+
+<!--
+is pruned to:
+-->
+则该值会被剪裁为：
+
+```yaml
+json:
+  spec:
+    foo: abc
+    bar: def
+  status:
+    something: x
+```
+
+<!--
+This means that the `something` field in the specified `spec` object is pruned, but everything outside is not.
+-->
+这意味着所指定的 `spec` 对象中的 `something` 字段被剪裁掉，而其外部的内容都被保留。
+
+<!--
+### IntOrString
+
+Nodes in a schema with `x-kubernetes-int-or-string: true` are excluded from rule 1, such that the following is structural:
+-->
+### IntOrString
+
+模式定义中标记了 `x-kubernetes-int-or-string: true` 的节点不受前述规则 1
+约束，因此下面的定义是结构化的模式：
+
+```yaml
+type: object
+properties:
+  foo:
+    x-kubernetes-int-or-string: true
+```
+
+<!--
+Also those nodes are partially excluded from rule 3 in the sense that the
+following two patterns are allowed (exactly those, without variations in order
+to additional fields):
+-->
+此外，所有这类节点也不再受规则 3 约束，也就是说，下面两种模式是被允许的
+（注意，仅限于这两种模式，不支持添加新字段的任何其他变种）：
+
+```yaml
+x-kubernetes-int-or-string: true
+anyOf:
+- type: integer
+- type: string
+...
+```
+
+和
+
+```yaml
+x-kubernetes-int-or-string: true
+allOf:
+- anyOf:
+  - type: integer
+  - type: string
+- ... # zero or more
+...
+```
+
+<!--
+With one of those specification, both an integer and a string validate.
+
+In [Validation Schema Publishing](/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/#publish-validation-schema-in-openapi-v2),
+`x-kubernetes-int-or-string: true` is unfolded to one of the two patterns shown above.
+-->
+在以上两种规约中，整数值和字符串值都会被认为是合法的。
+
+在[合法性检查模式定义的发布时](#publish-validation-schema-in-openapi-v2)，
+`x-kubernetes-int-or-string: true` 会被展开为上述两种模式之一。
+
+### RawExtension
+
+<!--
+RawExtensions (as in `runtime.RawExtension` defined in
+[k8s.io/apimachinery](https://github.com/kubernetes/apimachinery/blob/03ac7a9ade429d715a1a46ceaa3724c18ebae54f/pkg/runtime/types.go#L94))
+holds complete Kubernetes objects, i.e. with `apiVersion` and `kind` fields.
+
+It is possible to specify those embedded objects (both completely without constraints or partially specified) by setting `x-kubernetes-embedded-resource: true`. For example:
+-->
+RawExtensions（就像在
+[k8s.io/apimachinery](https://github.com/kubernetes/apimachinery/blob/03ac7a9ade429d715a1a46ceaa3724c18ebae54f/pkg/runtime/types.go#L94)
+项目中 `runtime.RawExtension` 所定义的那样）
+可以保存完整的 Kubernetes 对象，也就是，其中会包含 `apiVersion` 和 `kind`
+字段。
+
+通过 `x-kubernetes-embedded-resource: true` 来设定这些嵌套对象的规约（无论是
+完全无限制还是部分指定都可以）是可能的。例如：
+
+```yaml
+type: object
+properties:
+  foo:
+    x-kubernetes-embedded-resource: true
+    x-kubernetes-preserve-unknown-fields: true
+```
+
+<!--
+Here, the field `foo` holds a complete object, e.g.:
+-->
+这里，字段 `foo` 包含一个完整的对象，例如：
+
+```yaml
+foo:
+  apiVersion: v1
+  kind: Pod
+  spec:
+    ...
+```
+
+<!--
+Because `x-kubernetes-preserve-unknown-fields: true` is specified alongside,
+nothing is pruned. The use of `x-kubernetes-preserve-unknown-fields: true` is
+optional though.
+
+With `x-kubernetes-embedded-resource: true`, the `apiVersion`, `kind` and `metadata` are implicitly specified and validated.
+-->
+由于字段上设置了 `x-kubernetes-preserve-unknown-fields: true`，其中的内容不会
+被剪裁。不过，在这个语境中，`x-kubernetes-preserve-unknown-fields: true` 的
+使用是可选的。
+
+设置了 `x-kubernetes-embedded-resource: true` 之后，`apiVersion`、`kind` 和
+`metadata` 都是隐式设定并隐式完成合法性验证。
+
+<!--
+## Serving multiple versions of a CRD
+
+See [Custom resource definition versioning](/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definition-versioning/)
+for more information about serving multiple versions of your
+CustomResourceDefinition and migrating your objects from one version to another.
+-->
+## 提供 CRD 的多个版本   {#serving-multiple-versions-of-a-crd}
+
+关于如何为你的 CustomResourceDefinition 提供多个版本的支持，以及如何将你的对象
+从一个版本迁移到另一个版本， 详细信息可参阅
+[定制资源定义的版本](/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definition-versioning/)。
+
+<!-- discussion -->
+
+<!--
+## Advanced topics
+
+### Finalizers
+-->
+## 高级主题     {#advanced-topics}
+
+### Finalizers
+
+<!--
+*Finalizers* allow controllers to implement asynchronous pre-delete hooks.
+Custom objects support finalizers just like built-in objects.
+
+You can add a finalizer to a custom object like this:
+-->
+*Finalizer* 能够让控制器实现异步的删除前（Pre-delete）回调。
+定制对象和内置对象一样支持 Finalizer。
+
+你可以像下面一样为定制对象添加 Finalizer：
+
+```yaml
+apiVersion: "stable.example.com/v1"
+kind: CronTab
+metadata:
+  finalizers:
+  - finalizer.stable.example.com
+```
+
+<!--
+Finalizers are arbitrary string values, that when present ensure that a hard delete
+of a resource is not possible while they exist.
+
+The first delete request on an object with finalizers sets a value for the
+`metadata.deletionTimestamp` field but does not delete it. Once this value is set,
+entries in the `finalizer` list can only be removed.
+
+When the `metadata.deletionTimestamp` field is set, controllers watching the object
+execute any finalizers they handle, by polling update requests for that
+object. When all finalizers have been executed, the resource is deleted.
+-->
+Finalizer 可以取任意的字符串值。当资源上存在 Finalizer 时，无法硬性删除该资源。
+
+对带有 Finalizer 的对象的第一个删除请求会为其 `metadata.deletionTimestamp`
+设置一个值，但不会真的删除对象。一旦此值被设置，`finalizers`
+列表中的表项只能被移除。
+
+当 `metadata.deletionTimestamp` 字段被设置时，负责监测该对象的各个控制器会通过
+轮询对该对象的更新请求来执行它们所要处理的所有 Finalizer。
+当所有 Finalizer 都被执行过，资源被删除。
+
+<!--
+The value of `metadata.deletionGracePeriodSeconds` controls the interval between
+polling updates.
+
+It is the responsibility of each controller to remove its finalizer from the list.
+
+Kubernetes only finally deletes the object if the list of finalizers is empty,
+meaning all finalizers have been executed.
+-->
+`metadata.deletionGracePeriodSeconds` 的取值控制对更新的轮询周期。
+
+每个控制器要负责将其 Finalizer 从列表中去除。
+
+只有 `finalizers` 列表为空时，意味着所有 Finalizer 都被执行过之后，
+Kubernetes 才会最终删除对象，
+
+<!--
+### Validation
+
+Custom resources are validated via
+[OpenAPI v3 schemas](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#schemaObject) and you can add additional validation using [admission webhooks](/docs/reference/access-authn-authz/admission-controllers/#validatingadmissionwebhook).
+-->
+### 合法性检查    {#validation}
+
+定制资源是通过
+[OpenAPI v3 模式定义](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#schemaObject)
+来执行合法性检查的，
+你可以通过使用[准入控制 Webhook](/zh/docs/reference/access-authn-authz/admission-controllers/#validatingadmissionwebhook)
+来添加额外的合法性检查逻辑。
+
+<!--
+Additionally, the following restrictions are applied to the schema:
+
+- These fields cannot be set:
+  - `definitions`,
+  - `dependencies`,
+  - `deprecated`,
+  - `discriminator`,
+  - `id`,
+  - `patternProperties`,
+  - `readOnly`,
+  - `writeOnly`,
+  - `xml`,
+  - `$ref`.
+- The field `uniqueItems` cannot be set to _true_.
+- The field `additionalProperties` cannot be set to _false_.
+- The field `additionalProperties` is mutually exclusive with `properties`.
+-->
+此外，对模式定义存在以下限制：
+
+- 以下字段不可设置：
+  - `definitions`
+  - `dependencies`
+  - `deprecated`
+  - `discriminator`
+  - `id`
+  - `patternProperties`
+  - `readOnly`
+  - `writeOnly`
+  - `xml`
+  - `$ref`
+- 字段 `uniqueItems` 不可设置为 `true`
+- 字段 `additionalProperties` 不可设置为 `false`
+- 字段 `additionalProperties` 与 `properties` 互斥，不可同时使用
+
+<!--
+These fields can only be set with specific features enabled:
+
+- `default`: can be set for `apiextensions.k8s.io/v1` CustomResourceDefinitions. Defaulting is in GA since 1.17 (beta since 1.16 with the `CustomResourceDefaulting` feature gate to be enabled, which is the case automatically for many clusters for beta features). Compare [Validation Schema Defaulting](/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/#defaulting).
+-->
+以下字段仅可用于某些条件被满足的情况下：
+
+- `default`：可在 `apiextensions.k8s.io/v1` API 组中的 CustomResourceDefinition 的
+  模式定义中使用。设置默认值的功能特性从 1.17 开始正式发布。该特性在 1.16 版本中处于
+  Beta 状态，要求 `CustomResourceDefaulting` 特性门控被启用。对于大多数集群而言， 
+  Beta 状态的特性门控默认都是自动启用的。
+  你可以将此字段的作用与[合法性检查模式的默认值设定](#defaulting)相比较。
+
+{{< note >}}
+关于对某些 CustomResourceDefinition 特性所必需的限制，可参见
+[结构化的模式定义](#specifying-a-structural-schema)。
+{{< /note >}}
+
+<!--
+The schema is defined in the CustomResourceDefinition. In the following example, the
+CustomResourceDefinition applies the following validations on the custom object:
+
+- `spec.cronSpec` must be a string and must be of the form described by the regular expression.
+- `spec.replicas` must be an integer and must have a minimum value of 1 and a maximum value of 10.
+
+Save the CustomResourceDefinition to `resourcedefinition.yaml`:
+-->
+模式定义是在 CustomResourceDefinition 中设置的。在下面的例子中，
+CustomResourceDefinition 对定制对象执行以下合法性检查：
+
+- `spec.cronSpec` 必须是一个字符串，必须是正则表达式所描述的形式；
+- `spec.replicas` 必须是一个整数，且其最小值为 1、最大值为 10。
+
+将此 CustomResourceDefinition 保存到 `resourcedefinition.yaml` 文件中：
+
+```yaml
+apiVersion: apiextensions.k8s.io/v1
+kind: CustomResourceDefinition
+metadata:
+  name: crontabs.stable.example.com
+spec:
+  group: stable.example.com
+  versions:
+    - name: v1
+      served: true
+      storage: true
+      schema:
+        # openAPIV3Schema is the schema for validating custom objects.
+        openAPIV3Schema:
+          type: object
+          properties:
+            spec:
+              type: object
+              properties:
+                cronSpec:
+                  type: string
+                  pattern: '^(\d+|\*)(/\d+)?(\s+(\d+|\*)(/\d+)?){4}$'
+                image:
+                  type: string
+                replicas:
+                  type: integer
+                  minimum: 1
+                  maximum: 10
+  scope: Namespaced
+  names:
+    plural: crontabs
+    singular: crontab
+    kind: CronTab
+    shortNames:
+    - ct
+```
+
+<!--
+and create it:
+-->
+并创建 CustomResourceDefinition：
+
+```shell
+kubectl apply -f resourcedefinition.yaml
+```
+
+<!--
+A request to create a custom object of kind CronTab is rejected if there are invalid values in its fields.
+In the following example, the custom object contains fields with invalid values:
+
+- `spec.cronSpec` does not match the regular expression.
+- `spec.replicas` is greater than 10.
+
+If you save the following YAML to `my-crontab.yaml`:
+-->
+对于一个创建 CronTab 类别对象的定制对象的请求而言，如果其字段中包含非法值，则
+该请求会被拒绝。
+在下面的例子中，定制对象中包含带非法值的字段：
+
+- `spec.cronSpec` 与正则表达式不匹配
+- `spec.replicas` 数值大于 10。
+
+如果你将下面的 YAML 保存到 `my-crontab.yaml`：
+
+```yaml
+apiVersion: "stable.example.com/v1"
+kind: CronTab
+metadata:
+  name: my-new-cron-object
+spec:
+  cronSpec: "* * * *"
+  image: my-awesome-cron-image
+  replicas: 15
+```
+
+<!--
+and attempt to create it:
+-->
+并尝试创建定制对象：
+
+```shell
+kubectl apply -f my-crontab.yaml
+```
+
+<!--
+then you get an error:
+-->
+你会看到下面的错误信息：
+
+```console
+The CronTab "my-new-cron-object" is invalid: []: Invalid value: map[string]interface {}{"apiVersion":"stable.example.com/v1", "kind":"CronTab", "metadata":map[string]interface {}{"name":"my-new-cron-object", "namespace":"default", "deletionTimestamp":interface {}(nil), "deletionGracePeriodSeconds":(*int64)(nil), "creationTimestamp":"2017-09-05T05:20:07Z", "uid":"e14d79e7-91f9-11e7-a598-f0761cb232d1", "clusterName":""}, "spec":map[string]interface {}{"cronSpec":"* * * *", "image":"my-awesome-cron-image", "replicas":15}}:
+validation failure list:
+spec.cronSpec in body should match '^(\d+|\*)(/\d+)?(\s+(\d+|\*)(/\d+)?){4}$'
+spec.replicas in body should be less than or equal to 10
+```
+
+<!--
+If the fields contain valid values, the object creation request is accepted.
+
+Save the following YAML to `my-crontab.yaml`:
+-->
+如果所有字段都包含合法值，则对象创建的请求会被接受。
+
+将下面的 YAML 保存到 `my-crontab.yaml` 文件：
+
+```yaml
+apiVersion: "stable.example.com/v1"
+kind: CronTab
+metadata:
+  name: my-new-cron-object
+spec:
+  cronSpec: "* * * * */5"
+  image: my-awesome-cron-image
+  replicas: 5
+```
+
+<!--
+And create it:
+-->
+并创建定制对象：
+
+```shell
+kubectl apply -f my-crontab.yaml
+crontab "my-new-cron-object" created
+```
+
+<!--
+### Defaulting
+-->
+### 设置默认值   {#efaulting}
+
+<!--
+To use defaulting, your CustomResourceDefinition must use API version `apiextensions.k8s.io/v1`.
+-->
+{{< note >}}
+要使用设置默认值功能，你的 CustomResourceDefinition 必须使用 API 版本 `apiextensions.k8s.io/v1`。
+{{< /note >}}
+
+<!--
+Defaulting allows to specify default values in the [OpenAPI v3 validation schema](#validation):
+-->
+设置默认值的功能允许在 [OpenAPI v3 合法性检查模式定义](#validation)中设置默认值：
+
+```yaml
+apiVersion: apiextensions.k8s.io/v1
+kind: CustomResourceDefinition
+metadata:
+  name: crontabs.stable.example.com
+spec:
+  group: stable.example.com
+  versions:
+    - name: v1
+      served: true
+      storage: true
+      schema:
+        # openAPIV3Schema 是用来检查定制对象的模式定义
+        openAPIV3Schema:
+          type: object
+          properties:
+            spec:
+              type: object
+              properties:
+                cronSpec:
+                  type: string
+                  pattern: '^(\d+|\*)(/\d+)?(\s+(\d+|\*)(/\d+)?){4}$'
+                  default: "5 0 * * *"
+                image:
+                  type: string
+                replicas:
+                  type: integer
+                  minimum: 1
+                  maximum: 10
+                  default: 1
+  scope: Namespaced
+  names:
+    plural: crontabs
+    singular: crontab
+    kind: CronTab
+    shortNames:
+    - ct
+```
+
+<!--
+With this both `cronSpec` and `replicas` are defaulted:
+-->
+使用此 CRD 定义时，`cronSpec` 和 `replicas` 都会被设置默认值：
+
+```yaml
+apiVersion: "stable.example.com/v1"
+kind: CronTab
+metadata:
+  name: my-new-cron-object
+spec:
+  image: my-awesome-cron-image
+```
+
+<!--
+leads to
+-->
+会生成：
+
+```yaml
+apiVersion: "stable.example.com/v1"
+kind: CronTab
+metadata:
+  name: my-new-cron-object
+spec:
+  cronSpec: "5 0 * * *"
+  image: my-awesome-cron-image
+  replicas: 1
+```
+
+<!--
+Defaulting happens on the object
+
+* in the request to the API server using the request version defaults,
+* when reading from etcd using the storage version defaults,
+* after mutating admission plugins with non-empty patches using the admission webhook object version defaults.
+
+Defaults applied when reading data from etcd are not automatically written back to etcd. An update request via the API is required to persist those defaults back into etcd.
+-->
+默认值设定的行为发生在定制对象上：
+
+* 在向 API 服务器发送的请求中，基于请求版本的设定设置默认值；
+* 在从 etcd 读取对象时，使用存储版本来设置默认值；
+* 在 Mutating 准入控制插件执行非空的补丁操作时，基于准入 Webhook 对象
+  版本设置默认值。
+
+从 etcd 中读取数据时所应用的默认值设置不会被写回到 etcd 中。
+需要通过 API 执行更新请求才能将这种方式设置的默认值写回到 etcd。
+
+<!--
+Default values must be pruned (with the exception of defaults for `metadata` fields) and must validate against a provided schema.
+
+Default values for `metadata` fields of `x-kubernetes-embedded-resources: true` nodes (or parts of a default value covering `metadata`) are not pruned during CustomResourceDefinition creation, but through the pruning step during handling of requests.
+-->
+默认值一定会被剪裁（除了 `metadata` 字段的默认值设置），且必须通过所提供
+的模式定义的检查。
+
+针对 `x-kubernetes-embedded-resource: true` 节点（或者包含 `metadata` 字段的结构的默认值）
+的 `metadata` 字段的默认值设置不会在 CustomResourceDefinition 创建时被剪裁，
+而是在处理请求的字段剪裁阶段被删除。
+
+<!--
+### Publish Validation Schema in OpenAPI v2
+
+CustomResourceDefinition [OpenAPI v3 validation schemas](#validation) which are [structural](#specifying-a-structural-schema) and [enable pruning](#preserving-unknown-fields) are published as part of the [OpenAPI v2 spec](/docs/concepts/overview/kubernetes-api/#openapi-and-swagger-definitions) from Kubernetes API server.
+
+The [kubectl](/docs/reference/kubectl/overview) command-line tool consumes the published schema to perform client-side validation (`kubectl create` and `kubectl apply`), schema explanation (`kubectl explain`) on custom resources. The published schema can be consumed for other purposes as well, like client generation or documentation.
+-->
+### 以 OpenAPI v2 形式发布合法性检查模式      {#publish-validation-schema-in-openapi-v2}
+
+CustomResourceDefinition 的[结构化的](#specifying-a-structural-schema)、
+[启用了剪裁的](#preserving-unknown-fields) [OpenAPI v3 合法性检查模式](#validation)
+会在 Kubernetes API 服务器上作为
+[OpenAPI v2 规约](/zh/docs/concepts/overview/kubernetes-api/#openapi-and-swagger-definitions)
+的一部分发布出来。
+
+[kubectl](/zh/docs/reference/kubectl/overview) 命令行工具会基于所发布的模式定义来执行
+客户端的合法性检查（`kubectl create` 和 `kubectl apply`），为定制资源的模式定义
+提供解释（`kubectl explain`）。
+所发布的模式还可被用于其他目的，例如生成客户端或者生成文档。
+
+<!--
+The OpenAPI v3 validation schema is converted to OpenAPI v2 schema, and
+show up in `definitions` and `paths` fields in the [OpenAPI v2 spec](/docs/concepts/overview/kubernetes-api/#openapi-and-swagger-definitions).
+
+The following modifications are applied during the conversion to keep backwards compatibility with
+kubectl in previous 1.13 version. These modifications prevent kubectl from being over-strict and rejecting
+valid OpenAPI schemas that it doesn't understand. The conversion won't modify the validation schema defined in CRD,
+and therefore won't affect [validation](#validation) in the API server.
+-->
+OpenAPI v3 合法性检查模式定义会被转换为 OpenAPI v2 模式定义，并出现在
+[OpenAPI v2 规范](/zh/docs/concepts/overview/kubernetes-api/#openapi-and-swagger-definitions)
+的 `definitions` 和 `paths` 字段中。
+
+在转换过程中会发生以下修改，目的是保持与 1.13 版本以前的 kubectl 工具兼容。
+这些修改可以避免 kubectl 过于严格，以至于拒绝它无法理解的 OpenAPI 模式定义。
+转换过程不会更改 CRD 中定义的合法性检查模式定义，因此不会影响到 API 服务器中
+的[合法性检查](#validation)。
+
+<!--
+1. The following fields are removed as they aren't supported by OpenAPI v2 (in future versions OpenAPI v3 will be used without these restrictions)
+   - The fields `allOf`, `anyOf`, `oneOf` and `not` are removed
+2. If `nullable: true` is set, we drop `type`, `nullable`, `items` and `properties` because OpenAPI v2 is not able to express nullable. To avoid kubectl to reject good objects, this is necessary.
+-->
+1. 以下字段会被移除，因为它们在 OpenAPI v2 中不支持（在将来版本中将使用 OpenAPI v3，
+   因而不会有这些限制）
+   - 字段 `allOf`、`anyOf`、`oneOf` 和 `not` 会被删除
+2. 如果设置了 `nullable: true`，我们会丢弃 `type`、`nullable`、`items` 和 `properties`
+   OpenAPI v2 无法表达 Nullable。为了避免 kubectl 拒绝正常的对象，这一转换是必要的。
+
+<!--
+### Additional printer columns
+
+The kubectl tool relies on server-side output formatting. Your cluster's API server decides which
+columns are shown by the `kubectl get` command. You can customize these columns for a
+CustomResourceDefinition. The following example adds the `Spec`, `Replicas`, and `Age`
+columns.
+
+Save the CustomResourceDefinition to `resourcedefinition.yaml`:
+-->
+### 额外的打印列    {#additional-printer-columns}
+
+`kubectl` 工具依赖服务器端的输出格式化。你的集群的 API 服务器决定 `kubectl
+get` 命令要显示的列有哪些。
+你可以为 CustomResourceDefinition 定制这些要打印的列。
+下面的例子添加了 `Spec`、`Replicas` 和 `Age` 列：
+
+将此 CustomResourceDefinition 保存到 `resourcedefinition.yaml` 文件：
+
+```yaml
+apiVersion: apiextensions.k8s.io/v1
+kind: CustomResourceDefinition
+metadata:
+  name: crontabs.stable.example.com
+spec:
+  group: stable.example.com
+  scope: Namespaced
+  names:
+    plural: crontabs
+    singular: crontab
+    kind: CronTab
+    shortNames:
+    - ct
+  versions:
+  - name: v1
+    served: true
+    storage: true
+    schema:
+      openAPIV3Schema:
+        type: object
+        properties:
+          spec:
+            type: object
+            properties:
+              cronSpec:
+                type: string
+              image:
+                type: string
+              replicas:
+                type: integer
+    additionalPrinterColumns:
+    - name: Spec
+      type: string
+      description: The cron spec defining the interval a CronJob is run
+      jsonPath: .spec.cronSpec
+    - name: Replicas
+      type: integer
+      description: The number of jobs launched by the CronJob
+      jsonPath: .spec.replicas
+    - name: Age
+      type: date
+      jsonPath: .metadata.creationTimestamp
+```
+
+<!--
+Create the CustomResourceDefinition:
+-->
+创建 CustomResourceDefinition：
+
+```shell
+kubectl apply -f resourcedefinition.yaml
+```
+
+<!--
+Create an instance using the `my-crontab.yaml` from the previous section.
+-->
+使用前文中的 `my-crontab.yaml` 创建一个实例。
+
+<!--
+Invoke the server-side printing:
+-->
+启用服务器端打印输出：
+
+```shell
+kubectl get crontab my-new-cron-object
+```
+
+<!--
+Notice the `NAME`, `SPEC`, `REPLICAS`, and `AGE` columns in the output:
+-->
+注意输出中的 `NAME`、`SPEC`、`REPLICAS` 和 `AGE` 列：
+
+```
+NAME                 SPEC        REPLICAS   AGE
+my-new-cron-object   * * * * *   1          7s
+```
+
+<!--
+The `NAME` column is implicit and does not need to be defined in the CustomResourceDefinition.
+-->
+{{< note >}}
+`NAME` 列是隐含的，不需要在 CustomResourceDefinition 中定义。
+{{< /note >}}
+
+<!--
+#### Priority
+
+Each column includes a `priority` field for each column. Currently, the priority
+differentiates between columns shown in standard view or wide view (using the `-o wide` flag).
+
+- Columns with priority `0` are shown in standard view.
+- Columns with priority greater than `0` are shown only in wide view.
+-->
+#### 优先级    {#priority}
+
+每个列都包含一个 `priority` 字段。当前，优先级用来区分标准视图（Standard
+View）和宽视图（Wide View）（使用 `-o wide` 标志）中显示的列：
+
+- 优先级为 `0` 的列会在标准视图中显示。
+- 优先级大于 `0` 的列只会在宽视图中显示。
+
+<!--
+#### Type
+
+A column's `type` field can be any of the following (compare [OpenAPI v3 data types](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#dataTypes)):
+
+- `integer` – non-floating-point numbers
+- `number` – floating point numbers
+- `string` – strings
+- `boolean` – true or false
+- `date` – rendered differentially as time since this timestamp.
+-->
+#### 类型    {#type}
+
+列的 `type` 字段可以是以下值之一
+（比较 [OpenAPI v3 数据类型](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#dataTypes)）：
+
+- `integer` – 非浮点数字
+- `number` – 浮点数字
+- `string` – 字符串
+- `boolean` – `true` 或 `false`
+- `date` – 显示为以自此时间戳以来经过的时长
+
+<!--
+If the value inside a CustomResource does not match the type specified for the column,
+the value is omitted. Use CustomResource validation to ensure that the value
+types are correct.
+-->
+如果定制资源中的值与列中指定的类型不匹配，该值会被忽略。
+你可以通过定制资源的合法性检查来确保取值类型是正确的。
+
+<!--
+#### Format
+
+A column's `format` field can be any of the following:
+-->
+#### 格式    {#format}
+
+列的 `format` 字段可以是以下值之一：
+
+- `int32`
+- `int64`
+- `float`
+- `double`
+- `byte`
+- `date`
+- `date-time`
+- `password`
+
+<!--
+The column's `format` controls the style used when `kubectl` prints the value.
+-->
+列的 `format` 字段控制 `kubectl` 打印对应取值时采用的风格。
+
+<!--
+### Subresources
+
+Custom resources support `/status` and `/scale` subresources.
+
+The status and scale subresources can be optionally enabled by
+defining them in the CustomResourceDefinition.
+-->
+### 子资源     {#subresources}
+
+定制资源支持 `/status` 和 `/scale` 子资源。
+
+通过在 CustomResourceDefinition 中定义 `status` 和 `scale`，
+可以有选择地启用这些子资源。
+
+<!--
+#### Status subresource
+
+When the status subresource is enabled, the `/status` subresource for the custom resource is exposed.
+
+- The status and the spec stanzas are represented by the `.status` and `.spec` JSONPaths respectively inside of a custom resource.
+- `PUT` requests to the `/status` subresource take a custom resource object and ignore changes to anything except the status stanza.
+- `PUT` requests to the `/status` subresource only validate the status stanza of the custom resource.
+- `PUT`/`POST`/`PATCH` requests to the custom resource ignore changes to the status stanza.
+- The `.metadata.generation` value is incremented for all changes, except for changes to `.metadata` or `.status`.
+-->
+#### Status 子资源  {#status-subresource}
+
+当启用了 status 子资源时，对应定制资源的 `/status` 子资源会被暴露出来。
+
+- status 和 spec 内容分别用定制资源内的 `.status` 和 `.spec` JSON 路径来表达；
+- 对 `/status` 子资源的 `PUT` 请求要求使用定制资源对象作为其输入，但会忽略
+  status 之外的所有内容。
+- 对 `/status` 子资源的 `PUT` 请求仅对定制资源的 status 内容进行合法性检查。
+- 对定制资源的 `PUT`、`POST`、`PATCH` 请求会忽略 status 内容的改变。
+- 对所有变更请求，除非改变是针对 `.metadata` 或 `.status`，`.metadata.generation`
+  的取值都会增加。
+<!--
+- Only the following constructs are allowed at the root of the CRD OpenAPI validation schema:
+
+  - Description
+  - Example
+  - ExclusiveMaximum
+  - ExclusiveMinimum
+  - ExternalDocs
+  - Format
+  - Items
+  - Maximum
+  - MaxItems
+  - MaxLength
+  - Minimum
+  - MinItems
+  - MinLength
+  - MultipleOf
+  - Pattern
+  - Properties
+  - Required
+  - Title
+  - Type
+  - UniqueItems
+-->
+- 在 CRD OpenAPI 合法性检查模式定义的根节点，只允许存在以下结构：
+
+  - `description`
+  - `example`
+  - `exclusiveMaximum`
+  - `exclusiveMinimum`
+  - `externalDocs`
+  - `format`
+  - `items`
+  - `maximum`
+  - `maxItems`
+  - `maxLength`
+  - `minimum`
+  - `minItems`
+  - `minLength`
+  - `multipleOf`
+  - `pattern`
+  - `properties`
+  - `required`
+  -` title`
+  - `type`
+  - `uniqueItems`
+
+<!--
+#### Scale subresource
+
+When the scale subresource is enabled, the `/scale` subresource for the custom resource is exposed.
+The `autoscaling/v1.Scale` object is sent as the payload for `/scale`.
+
+To enable the scale subresource, the following values are defined in the CustomResourceDefinition.
+-->
+#### Scale 子资源   {#scale-subresource}
+
+当启用了 scale 子资源时，定制资源的 `/scale` 子资源就被暴露出来。
+针对 `/scale` 所发送的对象是 `autoscaling/v1.Scale`。
+
+为了启用 scale 子资源，CustomResourceDefinition 定义了以下字段：
+
+<!--
+- `specReplicasPath` defines the JSONPath inside of a custom resource that corresponds to `scale.spec.replicas`.
+
+  - It is a required value.
+  - Only JSONPaths under `.spec` and with the dot notation are allowed.
+  - If there is no value under the `SpecReplicasPath` in the custom resource,
+the `/scale` subresource will return an error on GET.
+-->
+- `specReplicasPath` 指定定制资源内与 `scale.spec.replicas` 对应的 JSON 路径。
+
+  - 此字段为必需值。
+  - 只可以使用 `.spec` 下的 JSON 路径，只可使用带句点的路径。
+  - 如果定制资源的 `specReplicasPath` 下没有取值，则针对 `/scale` 子资源执行 GET
+    操作时会返回错误。
+
+<!--
+- `statusReplicasPath` defines the JSONPath inside of a custom resource that corresponds to `scale.status.replicas`.
+
+  - It is a required value.
+  - Only JSONPaths under `.status` and with the dot notation are allowed.
+  - If there is no value under the `statusReplicasPath` in the custom resource,
+the status replica value in the `/scale` subresource will default to 0.
+-->
+- `statusReplicasPath` 指定定制资源内与 `scale.status.replicas` 对应的 JSON 路径。
+
+  - 此字段为必需值。
+  - 只可以使用 `.status` 下的 JSON 路径，只可使用带句点的路径。
+  - 如果定制资源的 `statusReplicasPath` 下没有取值，则针对 `/scale` 子资源的
+    副本个数状态值默认为 0。
+
+<!--
+- `labelSelectorPath` defines the JSONPath inside of a custom resource that corresponds to `scale.status.selector`.
+
+  - It is an optional value.
+  - It must be set to work with HPA.
+  - Only JSONPaths under `.status` or `.spec` and with the dot notation are allowed.
+  - If there is no value under the `labelSelectorPath` in the custom resource,
+the status selector value in the `/scale` subresource will default to the empty string.
+  - The field pointed by this JSON path must be a string field (not a complex selector struct) which contains a serialized label selector in string form.
+-->
+- `labelSelectorPath` 指定定制资源内与 `scale.status.selector` 对应的 JSON 路径。
+
+  - 此字段为可选值。
+  - 此字段必须设置才能使用 HPA。
+  - 只可以使用 `.status` 或 `.spec` 下的 JSON 路径，只可使用带句点的路径。
+  - 如果定制资源的 `labelSelectorPath` 下没有取值，则针对 `/scale` 子资源的
+    选择算符状态值默认为空字符串。
+  - 此 JSON 路径所指向的字段必须是一个字符串字段（而不是复合的选择算符结构），
+    其中包含标签选择算符串行化的字符串形式。
+
+<!--
+In the following example, both status and scale subresources are enabled.
+
+Save the CustomResourceDefinition to `resourcedefinition.yaml`:
+-->
+在下面的例子中，`status` 和 `scale` 子资源都被启用。
+
+将此 CustomResourceDefinition 保存到 `resourcedefinition.yaml` 文件：
+
+```yaml
+apiVersion: apiextensions.k8s.io/v1
+kind: CustomResourceDefinition
+metadata:
+  name: crontabs.stable.example.com
+spec:
+  group: stable.example.com
+  versions:
+    - name: v1
+      served: true
+      storage: true
+      schema:
+        openAPIV3Schema:
+          type: object
+          properties:
+            spec:
+              type: object
+              properties:
+                cronSpec:
+                  type: string
+                image:
+                  type: string
+                replicas:
+                  type: integer
+            status:
+              type: object
+              properties:
+                replicas:
+                  type: integer
+                labelSelector:
+                  type: string
+      # subresources 描述定制资源的子资源
+      subresources:
+        # status 启用 status 子资源
+        status: {}
+        # scale 启用 scale 子资源
+        scale:
+          # specReplicasPath 定义定制资源中对应 scale.spec.replicas 的 JSON 路径
+          specReplicasPath: .spec.replicas
+          # statusReplicasPath 定义定制资源中对应 scale.status.replicas 的 JSON 路径 
+          statusReplicasPath: .status.replicas
+          # labelSelectorPath  定义定制资源中对应 scale.status.selector 的 JSON 路径 
+          labelSelectorPath: .status.labelSelector
+  scope: Namespaced
+  names:
+    plural: crontabs
+    singular: crontab
+    kind: CronTab
+    shortNames:
+    - ct
+```
+
+<!--
+And create it:
+-->
+之后创建此 CustomResourceDefinition：
+
+```shell
+kubectl apply -f resourcedefinition.yaml
+```
+
+<!--
+After the CustomResourceDefinition object has been created, you can create custom objects.
+
+If you save the following YAML to `my-crontab.yaml`:
+-->
+CustomResourceDefinition 对象创建完毕之后，你可以创建定制对象，。
+
+如果你将下面的 YAML 保存到 `my-crontab.yaml` 文件：
+
+```yaml
+apiVersion: "stable.example.com/v1"
+kind: CronTab
+metadata:
+  name: my-new-cron-object
+spec:
+  cronSpec: "* * * * */5"
+  image: my-awesome-cron-image
+  replicas: 3
+```
+
+<!--
+and create it:
+-->
+并创建定制对象：
+
+```shell
+kubectl apply -f my-crontab.yaml
+```
+
+<!--
+Then new namespaced RESTful API endpoints are created at:
+-->
+那么会创建新的、命名空间作用域的 RESTful  API 端点：
+
+```
+/apis/stable.example.com/v1/namespaces/*/crontabs/status
+```
+
+<!-- and -->
+和
+
+```
+/apis/stable.example.com/v1/namespaces/*/crontabs/scale
+```
+
+<!--
+A custom resource can be scaled using the `kubectl scale` command.
+For example, the following command sets `.spec.replicas` of the
+custom resource created above to 5:
+-->
+定制资源可以使用 `kubectl scale` 命令来扩缩其规模。
+例如下面的命令将前面创建的定制资源的 `.spec.replicas` 设置为 5：
+
+```shell
+kubectl scale --replicas=5 crontabs/my-new-cron-object
+```
+```
+crontabs "my-new-cron-object" scaled
+```
+```shell
+kubectl get crontabs my-new-cron-object -o jsonpath='{.spec.replicas}'
+```
+```
+5
+```
+
+<!--
+You can use a [PodDisruptionBudget](/docs/tasks/run-application/configure-pdb/) to protect custom
+resources that have the scale subresource enabled.
+-->
+你可以使用 [PodDisruptionBudget](/zh/docs/tasks/run-application/configure-pdb/)
+来保护启用了 scale 子资源的定制资源。
+
+<!--
+### Categories
+-->
+### 分类   {#categories}
+
+{{< feature-state state="beta" for_k8s_version="v1.10" >}}
+
+<!--
+Categories is a list of grouped resources the custom resource belongs to (eg. `all`).
+You can use `kubectl get <category-name>` to list the resources belonging to the category.
+
+The following example adds `all` in the list of categories in the CustomResourceDefinition
+and illustrates how to output the custom resource using `kubectl get all`.
+
+Save the following CustomResourceDefinition to `resourcedefinition.yaml`:
+-->
+分类（Categories）是定制资源所归属的分组资源列表（例如，`all`）。
+你可以使用 `kubectl get <分类名称>` 来列举属于某分类的所有资源。
+
+下面的示例在 CustomResourceDefinition 中将 `all` 添加到分类列表中，
+并展示了如何使用 `kubectl get all` 来输出定制资源：
+
+将下面的 CustomResourceDefinition 保存到 `resourcedefinition.yaml` 文件中：
+
+```yaml
+apiVersion: apiextensions.k8s.io/v1
+kind: CustomResourceDefinition
+metadata:
+  name: crontabs.stable.example.com
+spec:
+  group: stable.example.com
+  versions:
+    - name: v1
+      served: true
+      storage: true
+      schema:
+        openAPIV3Schema:
+          type: object
+          properties:
+            spec:
+              type: object
+              properties:
+                cronSpec:
+                  type: string
+                image:
+                  type: string
+                replicas:
+                  type: integer
+  scope: Namespaced
+  names:
+    plural: crontabs
+    singular: crontab
+    kind: CronTab
+    shortNames:
+    - ct
+    # categories 是定制资源所归属的分类资源列表
+    categories:
+    - all
+```
+
+<!--
+and create it:
+-->
+之后创建此 CRD：
+
+```shell
+kubectl apply -f resourcedefinition.yaml
+```
+
+<!--
+After the CustomResourceDefinition object has been created, you can create custom objects.
+
+Save the following YAML to `my-crontab.yaml`:
+-->
+创建了 CustomResourceDefinition 对象之后，你可以创建定制对象。
+
+将下面的 YAML 保存到 `my-crontab.yaml` 中：
+
+```yaml
+apiVersion: "stable.example.com/v1"
+kind: CronTab
+metadata:
+  name: my-new-cron-object
+spec:
+  cronSpec: "* * * * */5"
+  image: my-awesome-cron-image
+```
+
+<!--
+and create it:
+-->
+并创建定制对象：
+
+```shell
+kubectl apply -f my-crontab.yaml
+```
+
+<!--
+You can specify the category using `kubectl get`:
+-->
+你可以在使用 `kubectl get` 时指定分类：
+
+```shell
+kubectl get all
+```
+
+<!--
+The output will include the custom resources of kind `CronTab`:
+-->
+输出中会包含类别为 `CronTab` 的定制资源：
+
+```console
+NAME                          AGE
+crontabs/my-new-cron-object   3s
+```
+
+## {{% heading "whatsnext" %}}
+
+<!--
+* Read about [custom resources](/docs/concepts/extend-kubernetes/api-extension/custom-resources/).
+
+* See [CustomResourceDefinition](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#customresourcedefinition-v1-apiextensions-k8s-io).
+
+* Serve [multiple versions](/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definition-versioning/) of a
+  CustomResourceDefinition.
+-->
+* 阅读了解[定制资源](/zh/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
+* 参阅 [CustomResourceDefinition](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#customresourcedefinition-v1-apiextensions-k8s-io)
+* 参阅支持 CustomResourceDefinition 的[多个版本](/zh/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definition-versioning/)
+