diff --git a/content/zh-cn/docs/tasks/configure-pod-container/configure-pod-configmap.md b/content/zh-cn/docs/tasks/configure-pod-container/configure-pod-configmap.md
index ce863b1e9a5cd..ccec13bd1bf47 100644
--- a/content/zh-cn/docs/tasks/configure-pod-container/configure-pod-configmap.md
+++ b/content/zh-cn/docs/tasks/configure-pod-container/configure-pod-configmap.md
@@ -1,7 +1,7 @@
 ---
 title: 配置 Pod 使用 ConfigMap
 content_type: task
-weight: 150
+weight: 190
 card:
   name: tasks
   weight: 50
@@ -9,7 +9,7 @@ card:
 <!--
 title: Configure a Pod to Use a ConfigMap
 content_type: task
-weight: 150
+weight: 190
 card:
   name: tasks
   weight: 50
@@ -18,39 +18,64 @@ card:
 <!-- overview -->
 <!--
 Many applications rely on configuration which is used during either application initialization or runtime.
-Most of the times there is a requirement to adjust values assigned to configuration parameters.
-ConfigMaps are the Kubernetes way to inject application pods with configuration data.
-ConfigMaps allow you to decouple configuration artifacts from image content to keep containerized applications portable. This page provides a series of usage examples demonstrating how to create ConfigMaps and configure Pods using data stored in ConfigMaps.
+Most times, there is a requirement to adjust values assigned to configuration parameters.
+ConfigMaps are a Kubernetes mechanism that let you inject configuration data into application
+{{< glossary_tooltip text="pods" term_id="pod" >}}.
 -->
-很多应用在其初始化或运行期间要依赖一些配置信息。大多数时候，
-存在要调整配置参数所设置的数值的需求。
-ConfigMap 是 Kubernetes 用来向应用 Pod 中注入配置数据的方法。
+很多应用在其初始化或运行期间要依赖一些配置信息。
+大多数时候，存在要调整配置参数所设置的数值的需求。
+ConfigMap 是 Kubernetes 的一种机制，可让你将配置数据注入到应用的
+{{< glossary_tooltip text="Pod" term_id="pod" >}} 内部。
 
-ConfigMap 允许你将配置文件与镜像文件分离，以使容器化的应用程序具有可移植性。
+<!--
+The ConfigMap concept allow you to decouple configuration artifacts from image content to
+keep containerized applications portable. For example, you can download and run the same
+{{< glossary_tooltip text="container image" term_id="image" >}} to spin up containers for the purposes of local development, system test, or running a live end-user workload.
+-->
+ConfigMap 概念允许你将配置清单与镜像内容分离，以保持容器化的应用程序的可移植性。
+例如，你可以下载并运行相同的{{< glossary_tooltip text="容器镜像" term_id="image" >}}来启动容器，
+用于本地开发、系统测试或运行实时终端用户工作负载。
+
+<!--
+This page provides a series of usage examples demonstrating how to create ConfigMaps and
+configure Pods using data stored in ConfigMaps.
+-->
 本页提供了一系列使用示例，这些示例演示了如何创建 ConfigMap 以及配置 Pod
 使用存储在 ConfigMap 中的数据。
 
 ## {{% heading "prerequisites" %}}
 
-{{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}
+{{< include "task-tutorial-prereqs.md" >}}
+
+<!--
+You need to have the `wget` tool installed. If you have a different tool
+such as `curl`, and you do not have `wget`, you will need to adapt the
+step that downloads example data.
+-->
+你需要安装 `wget` 工具。如果你有不同的工具，例如 `curl`，而没有 `wget`，
+则需要调整下载示例数据的步骤。
 
 <!-- steps -->
+
 <!--
 ## Create a ConfigMap
 
-You can use either `kubectl create configmap` or a ConfigMap generator in `kustomization.yaml` to create a ConfigMap. Note that `kubectl` starts to support `kustomization.yaml` since 1.14.
+You can use either `kubectl create configmap` or a ConfigMap generator in `kustomization.yaml`
+to create a ConfigMap.
 -->
 ## 创建 ConfigMap    {#create-a-configmap}
 
 你可以使用 `kubectl create configmap` 或者在 `kustomization.yaml` 中的 ConfigMap
-生成器来创建 ConfigMap。注意，`kubectl` 从 1.14 版本开始支持 `kustomization.yaml`。
+生成器来创建 ConfigMap。
 
 <!--
-### Create a ConfigMap Using kubectl create configmap
+### Create a ConfigMap using `kubectl create configmap`
 
-Use the `kubectl create configmap` command to create ConfigMaps from [directories](#create-configmaps-from-directories), [files](#create-configmaps-from-files), or [literal values](#create-configmaps-from-literal-values):
+Use the `kubectl create configmap` command to create ConfigMaps from
+[directories](#create-configmaps-from-directories), [files](#create-configmaps-from-files),
+or [literal values](#create-configmaps-from-literal-values):
 -->
-### 使用 kubectl create configmap 创建 ConfigMap    {#create-a-configmap-using-kubectl-create-configmap}
+### 使用 `kubectl create configmap` 创建 ConfigMap    {#create-a-configmap-using-kubectl-create-configmap}
 
 你可以使用 `kubectl create configmap` 命令基于[目录](#create-configmaps-from-directories)、
 [文件](#create-configmaps-from-files)或者[字面值](#create-configmaps-from-literal-values)来创建
@@ -66,7 +91,8 @@ kubectl create configmap <映射名称> <数据源>
 ```
 
 <!--
-where \<map-name> is the name you want to assign to the ConfigMap and \<data-source> is the directory, file, or literal value to draw the data from.
+where \<map-name> is the name you want to assign to the ConfigMap and \<data-source> is the
+directory, file, or literal value to draw the data from.
 The name of a ConfigMap object must be a valid
 [DNS subdomain name](/docs/concepts/overview/working-with-objects/names#dns-subdomain-names).
 -->
@@ -75,7 +101,8 @@ The name of a ConfigMap object must be a valid
 [DNS 子域名](/zh-cn/docs/concepts/overview/working-with-objects/names#dns-subdomain-names).
 
 <!--
-When you are creating a ConfigMap based on a file, the key in the \<data-source> defaults to the basename of the file, and the value defaults to the file content.
+When you are creating a ConfigMap based on a file, the key in the \<data-source> defaults to
+the basename of the file, and the value defaults to the file content.
 -->
 在你基于文件来创建 ConfigMap 时，`<数据源>` 中的键名默认取自文件的基本名，
 而对应的值则默认为文件的内容。
@@ -89,47 +116,65 @@ about a ConfigMap.
 [`kubectl get`](/docs/reference/generated/kubectl/kubectl-commands/#get) 获取有关 ConfigMap 的信息。
 
 <!--
-#### Create ConfigMaps from directories
+#### Create a ConfigMap from a directory {#create-configmaps-from-directories}
 
-You can use `kubectl create configmap` to create a ConfigMap from multiple files in the same directory. When you are creating a ConfigMap based on a directory, kubectl identifies files whose basename is a valid key in the directory and packages each of those files into the new ConfigMap. Any directory entries except regular files are ignored (e.g. subdirectories, symlinks, devices, pipes, etc).
-For example:
+You can use `kubectl create configmap` to create a ConfigMap from multiple files in the same
+directory. When you are creating a ConfigMap based on a directory, kubectl identifies files
+whose filename is a valid key in the directory and packages each of those files into the new
+ConfigMap. Any directory entries except regular files are ignored (for example: subdirectories,
+symlinks, devices, pipes, and more).
 -->
-#### 基于目录创建 ConfigMap     {#create-configmaps-from-directories}
+#### 基于一个目录来创建 ConfigMap     {#create-configmaps-from-directories}
 
 你可以使用 `kubectl create configmap` 基于同一目录中的多个文件创建 ConfigMap。
-当你基于目录来创建 ConfigMap 时，kubectl 识别目录下基本名可以作为合法键名的文件，
+当你基于目录来创建 ConfigMap 时，kubectl 识别目录下文件名可以作为合法键名的文件，
 并将这些文件打包到新的 ConfigMap 中。普通文件之外的所有目录项都会被忽略
 （例如：子目录、符号链接、设备、管道等等）。
 
-例如：
+{{< note >}}
+<!--
+Each filename being used for ConfigMap creation must consist of only acceptable characters, which are: letters (`A` to `Z` and `a` to z`), digits (`0` to `9`), '-', '_', or '.'.
+If you use `kubectl create configmap` with a directory where any of the file names contains an unacceptable character, the `kubectl` command may fail.
+-->
+用于创建 ConfigMap 的每个文件名必须由可接受的字符组成，即：字母（`A` 到 `Z` 和
+`a` 到 `z`）、数字（`0` 到 `9`）、'-'、'_'或'.'。
+如果在一个目录中使用 `kubectl create configmap`，而其中任一文件名包含不可接受的字符，
+则 `kubectl` 命令可能会失败。
 
 <!--
-```shell
-# Create the local directory
-mkdir -p configure-pod-container/configmap/
+The `kubectl` command does not print an error when it encounters an invalid filename.
+-->
+`kubectl` 命令在遇到不合法的文件名时不会打印错误。
 
-# Download the sample files into `configure-pod-container/configmap/` directory
-wget https://kubernetes.io/examples/configmap/game.properties -O configure-pod-container/configmap/game.properties
-wget https://kubernetes.io/examples/configmap/ui.properties -O configure-pod-container/configmap/ui.properties
+{{< /note >}}
 
-# Create the configmap
-kubectl create configmap game-config --from-file=configure-pod-container/configmap/
-```
+<!--
+Create the local directory:
 -->
+创建本地目录：
+
 ```shell
-# 创建本地目录
 mkdir -p configure-pod-container/configmap/
+```
 
+<!--
+Now, download the sample configuration and create the ConfigMap:
+-->
+现在，下载示例的配置并创建 ConfigMap：
+
+```shell
 # 将示例文件下载到 `configure-pod-container/configmap/` 目录
 wget https://kubernetes.io/examples/configmap/game.properties -O configure-pod-container/configmap/game.properties
 wget https://kubernetes.io/examples/configmap/ui.properties -O configure-pod-container/configmap/ui.properties
 
-# 创建 configmap
+# 创建 ConfigMap
 kubectl create configmap game-config --from-file=configure-pod-container/configmap/
 ```
 
 <!--
-The above command packages each file, in this case, `game.properties` and `ui.properties` in the `configure-pod-container/configmap/` directory into the game-config ConfigMap. You can display details of the ConfigMap using the following command:
+The above command packages each file, in this case, `game.properties` and `ui.properties`
+in the `configure-pod-container/configmap/` directory into the game-config ConfigMap. You can
+display details of the ConfigMap using the following command:
 -->
 以上命令将 `configure-pod-container/configmap` 目录下的所有文件，也就是
 `game.properties` 和 `ui.properties` 打包到 game-config ConfigMap
@@ -170,7 +215,8 @@ how.nice.to.look=fairlyNice
 ```
 
 <!--
-The `game.properties` and `ui.properties` files in the `configure-pod-container/configmap/` directory are represented in the `data` section of the ConfigMap.
+The `game.properties` and `ui.properties` files in the `configure-pod-container/configmap/`
+directory are represented in the `data` section of the ConfigMap.
 -->
 `configure-pod-container/configmap/` 目录中的 `game.properties` 和 `ui.properties`
 文件出现在 ConfigMap 的 `data` 部分。
@@ -188,7 +234,7 @@ The output is similar to this:
 apiVersion: v1
 kind: ConfigMap
 metadata:
-  creationTimestamp: 2016-02-18T18:52:05Z
+  creationTimestamp: 2022-02-18T18:52:05Z
   name: game-config
   namespace: default
   resourceVersion: "516"
@@ -212,7 +258,8 @@ data:
 <!--
 #### Create ConfigMaps from files
 
-You can use `kubectl create configmap` to create a ConfigMap from an individual file, or from multiple files.
+You can use `kubectl create configmap` to create a ConfigMap from an individual file, or from
+multiple files.
 
 For example,
 -->
@@ -260,7 +307,8 @@ secret.code.lives=30
 ```
 
 <!--
-You can pass in the `--from-file` argument multiple times to create a ConfigMap from multiple data sources.
+You can pass in the `--from-file` argument multiple times to create a ConfigMap from multiple
+data sources.
 -->
 你可以多次使用 `--from-file` 参数，从多个数据源创建 ConfigMap。
 
@@ -308,33 +356,23 @@ how.nice.to.look=fairlyNice
 ```
 
 <!--
-When `kubectl` creates a ConfigMap from inputs that are not ASCII or UTF-8, the tool puts these into the `binaryData` field of the ConfigMap, and not in `data`. Both text and binary data sources can be combined in one ConfigMap.
-If you want to view the `binaryData` keys (and their values) in a ConfigMap, you can run `kubectl get configmap -o jsonpath='{.binaryData}' <name>`.
-
 Use the option `--from-env-file` to create a ConfigMap from an env-file, for example:
 -->
-当 `kubectl` 基于非 ASCII 或 UTF-8 的输入创建 ConfigMap 时，
-该工具将这些输入放入 ConfigMap 的 `binaryData` 字段，而不是 `data` 中。
-同一个 ConfigMap 中可同时包含文本数据和二进制数据源。
-如果你想查看 ConfigMap 中的 `binaryData` 键（及其值），
-你可以运行 `kubectl get configmap -o jsonpath='{.binaryData}' <name>`。
+使用 `--from-env-file` 选项基于 env 文件创建 ConfigMap，例如：
 
-使用 `--from-env-file` 选项从环境文件创建 ConfigMap，例如：
-
-<!--
 ```shell
-# Env-files contain a list of environment variables.
-# These syntax rules apply:
-#   Each line in an env file has to be in VAR=VAL format.
-#   Lines beginning with # (i.e. comments) are ignored.
-#   Blank lines are ignored.
-#   There is no special handling of quotation marks (i.e. they will be part of the ConfigMap value)).
-
-# Download the sample files into `configure-pod-container/configmap/` directory
+# Env 文件包含环境变量列表。其中适用以下语法规则:
+# 这些语法规则适用：
+#   Env 文件中的每一行必须为 VAR=VAL 格式。
+#   以＃开头的行（即注释）将被忽略。
+#   空行将被忽略。
+#   引号不会被特殊处理（即它们将成为 ConfigMap 值的一部分）。
+
+# 将示例文件下载到 `configure-pod-container/configmap/` 目录
 wget https://kubernetes.io/examples/configmap/game-env-file.properties -O configure-pod-container/configmap/game-env-file.properties
 wget https://kubernetes.io/examples/configmap/ui-env-file.properties -O configure-pod-container/configmap/ui-env-file.properties
 
-# The env-file `game-env-file.properties` looks like below
+# Env 文件 `game-env-file.properties` 如下所示
 cat configure-pod-container/configmap/game-env-file.properties
 enemies=aliens
 lives=3
@@ -342,32 +380,6 @@ allowed="true"
 
 # This comment and the empty line above it are ignored
 ```
--->
-Env 文件包含环境变量列表。其中适用以下语法规则:
-
-- Env 文件中的每一行必须为 VAR=VAL 格式。
-- 以＃开头的行（即注释）将被忽略。
-- 空行将被忽略。
-- 引号不会被特殊处理（即它们将成为 ConfigMap 值的一部分）。
-
-将示例文件下载到 `configure-pod-container/configmap/` 目录：
-
-```shell
-wget https://kubernetes.io/examples/configmap/game-env-file.properties -O configure-pod-container/configmap/game-env-file.properties
-wget https://kubernetes.io/examples/configmap/ui-env-file.properties -O configure-pod-container/configmap/ui-env-file.properties
-```
-
-Env 文件 `game-env-file.properties` 如下所示：
-
-```shell
-cat configure-pod-container/configmap/game-env-file.properties
-```
-
-```
-enemies=aliens
-lives=3
-allowed="true"
-```
 
 ```shell
 kubectl create configmap game-config-env-file \
@@ -375,16 +387,16 @@ kubectl create configmap game-config-env-file \
 ```
 
 <!--
-would produce the following ConfigMap:
+would produce a ConfigMap. View the ConfigMap:
 -->
-将产生以下 ConfigMap：
+将产生以下 ConfigMap。查看 ConfigMap：
 
 ```shell
 kubectl get configmap game-config-env-file -o yaml
 ```
 
 <!--
-where the output is similar to this:
+the output is similar to:
 -->
 输出类似以下内容：
 
@@ -392,7 +404,7 @@ where the output is similar to this:
 apiVersion: v1
 kind: ConfigMap
 metadata:
-  creationTimestamp: 2017-12-27T18:36:28Z
+  creationTimestamp: 2019-12-27T18:36:28Z
   name: game-config-env-file
   namespace: default
   resourceVersion: "809965"
@@ -434,7 +446,7 @@ where the output is similar to this:
 apiVersion: v1
 kind: ConfigMap
 metadata:
-  creationTimestamp: 2017-12-27T18:38:34Z
+  creationTimestamp: 2019-12-27T18:38:34Z
   name: config-multi-env-files
   namespace: default
   resourceVersion: "810136"
@@ -451,7 +463,8 @@ data:
 <!--
 #### Define the key to use when creating a ConfigMap from a file
 
-You can define a key other than the file name to use in the `data` section of your ConfigMap when using the `--from-file` argument:
+You can define a key other than the file name to use in the `data` section of your ConfigMap
+when using the `--from-file` argument:
 -->
 #### 定义从文件创建 ConfigMap 时要使用的键    {#define-the-key-to-use-when-generating-a-configmap-from-a-file}
 
@@ -468,7 +481,8 @@ kubectl create configmap game-config-3 --from-file=<我的键名>=<文件路径>
 ```
 
 <!--
-where `<my-key-name>` is the key you want to use in the ConfigMap and `<path-to-file>` is the location of the data source file you want the key to represent.
+where `<my-key-name>` is the key you want to use in the ConfigMap and `<path-to-file>` is the
+location of the data source file you want the key to represent.
 -->
 `<我的键名>` 是你要在 ConfigMap 中使用的键名，`<文件路径>` 是你想要键所表示的数据源文件的位置。
 
@@ -499,7 +513,7 @@ where the output is similar to this:
 apiVersion: v1
 kind: ConfigMap
 metadata:
-  creationTimestamp: 2016-02-18T18:54:22Z
+  creationTimestamp: 2022-02-18T18:54:22Z
   name: game-config-3
   namespace: default
   resourceVersion: "530"
@@ -518,7 +532,8 @@ data:
 <!--
 #### Create ConfigMaps from literal values
 
-You can use `kubectl create configmap` with the `--from-literal` argument to define a literal value from the command line:
+You can use `kubectl create configmap` with the `--from-literal` argument to define a literal
+value from the command line:
 -->
 #### 根据字面值创建 ConfigMap         {#create-configmaps-from-literal-values}
 
@@ -530,7 +545,8 @@ kubectl create configmap special-config --from-literal=special.how=very --from-l
 ```
 
 <!--
-You can pass in multiple key-value pairs. Each pair provided on the command line is represented as a separate entry in the `data` section of the ConfigMap.
+You can pass in multiple key-value pairs. Each pair provided on the command line is represented
+as a separate entry in the `data` section of the ConfigMap.
 -->
 你可以传入多个键值对。命令行中提供的每对键值在 ConfigMap 的 `data` 部分中均表示为单独的条目。
 
@@ -547,7 +563,7 @@ The output is similar to this:
 apiVersion: v1
 kind: ConfigMap
 metadata:
-  creationTimestamp: 2016-02-18T19:14:38Z
+  creationTimestamp: 2022-02-18T19:14:38Z
   name: special-config
   namespace: default
   resourceVersion: "651"
@@ -560,15 +576,13 @@ data:
 <!--
 ### Create a ConfigMap from generator
 
-`kubectl` supports `kustomization.yaml` since 1.14.
-You can also create a ConfigMap from generators and then apply it to create the object on
-the Apiserver. The generators
-should be specified in a `kustomization.yaml` inside a directory.
+You can also create a ConfigMap from generators and then apply it to create the object
+in the cluster's API server.
+You should specify the generators in a `kustomization.yaml` file within a directory.
 -->
 ### 基于生成器创建 ConfigMap    {#create-a-configmap-from-generator}
 
-自 1.14 开始，`kubectl` 开始支持 `kustomization.yaml`。
-你还可以基于生成器（Generators）创建 ConfigMap，然后将其应用于 API 服务器上创建对象。
+你还可以基于生成器（Generators）创建 ConfigMap，然后将其应用于集群的 API 服务器上创建对象。
 生成器应在目录内的 `kustomization.yaml` 中指定。
 
 <!--
@@ -581,29 +595,20 @@ For example, to generate a ConfigMap from files `configure-pod-container/configm
 例如，要基于 `configure-pod-container/configmap/game.properties`
 文件生成一个 ConfigMap：
 
-<!--
-```shell
-# Create a kustomization.yaml file with ConfigMapGenerator
-cat <<EOF >./kustomization.yaml
-configMapGenerator:
-- name: game-config-4
-  files:
-  - configure-pod-container/configmap/game.properties
-EOF
-```
--->
 ```shell
 # 创建包含 ConfigMapGenerator 的 kustomization.yaml 文件
 cat <<EOF >./kustomization.yaml
 configMapGenerator:
 - name: game-config-4
+  labels:
+    game-config: config-4
   files:
   - configure-pod-container/configmap/game.properties
 EOF
 ```
 
 <!--
-Apply the kustomization directory to create the ConfigMap object.
+Apply the kustomization directory to create the ConfigMap object:
 -->
 应用（Apply）kustomization 目录创建 ConfigMap 对象：
 
@@ -618,21 +623,26 @@ configmap/game-config-4-m9dm2f92bt created
 <!--
 You can check that the ConfigMap was created like this:
 -->
-你可以检查 ConfigMap 被创建如下：
+你可以像这样检查 ConfigMap 已经被创建：
 
 ```shell
 kubectl get configmap
 ```
-
 ```
 NAME                       DATA   AGE
 game-config-4-m9dm2f92bt   1      37s
+```
 
+<!-- and also: -->
+也可以这样：
 
+```shell
 kubectl describe configmaps/game-config-4-m9dm2f92bt
+```
+```
 Name:         game-config-4-m9dm2f92bt
 Namespace:    default
-Labels:       <none>
+Labels:       game-config=config-4
 Annotations:  kubectl.kubernetes.io/last-applied-configuration:
                 {"apiVersion":"v1","data":{"game.properties":"enemies=aliens\nlives=3\nenemies.cheat=true\nenemies.cheat.level=noGoodRotten\nsecret.code.p...
 
@@ -651,8 +661,8 @@ Events:  <none>
 ```
 
 <!--
-Note that the generated ConfigMap name has a suffix appended by hashing the contents. This ensures that a
-new ConfigMap is generated each time the content is modified.
+Notice that the generated ConfigMap name has a suffix appended by hashing the contents. This
+ensures that a new ConfigMap is generated each time the content is modified.
 -->
 请注意，生成的 ConfigMap 名称具有通过对内容进行散列而附加的后缀，
 这样可以确保每次修改内容时都会生成新的 ConfigMap。
@@ -670,22 +680,13 @@ with the key `game-special-key`
 例如，从 `configure-pod-container/configmap/game.properties` 文件生成 ConfigMap，
 但使用 `game-special-key` 作为键名：
 
-<!--
-```shell
-# Create a kustomization.yaml file with ConfigMapGenerator
-cat <<EOF >./kustomization.yaml
-configMapGenerator:
-- name: game-config-5
-  files:
-  - game-special-key=configure-pod-container/configmap/game.properties
-EOF
-```
--->
 ```shell
 # 创建包含 ConfigMapGenerator 的 kustomization.yaml 文件
 cat <<EOF >./kustomization.yaml
 configMapGenerator:
 - name: game-config-5
+  labels:
+    game-config: config-5
   files:
   - game-special-key=configure-pod-container/configmap/game.properties
 EOF
@@ -699,37 +700,28 @@ Apply the kustomization directory to create the ConfigMap object.
 ```shell
 kubectl apply -k .
 ```
-
 ```
 configmap/game-config-5-m67dt67794 created
 ```
 
 <!--
-#### Generate ConfigMaps from Literals
+#### Generate ConfigMaps from literals
 
-To generate a ConfigMap from literals `special.type=charm` and `special.how=very`,
-you can specify the ConfigMap generator in `kustomization.yaml` as
+This example shows you how to create a `ConfigMap` from two literal key/value pairs:
+`special.type=charm` and `special.how=very`, using Kustomize and kubectl. To achieve
+this, you can specify the `ConfigMap` generator. Create (or replace)
+`kustomization.yaml` so that it has the following contents:
 -->
 #### 基于字面值生成 ConfigMap    {#generate-configmaps-from-literals}
 
-要基于字符串 `special.type=charm` 和 `special.how=very` 生成 ConfigMap，
-可以在 `kustomization.yaml` 中配置 ConfigMap 生成器：
+此示例向你展示如何使用 Kustomize 和 kubectl，基于两个字面键/值对
+`special.type=charm` 和 `special.how=very` 创建一个 `ConfigMap`。
+为了实现这一点，你可以配置 `ConfigMap` 生成器。
+创建（或替换）`kustomization.yaml`，使其具有以下内容。
 
-<!--
-```shell
-# Create a kustomization.yaml file with ConfigMapGenerator
-cat <<EOF >./kustomization.yaml
-configMapGenerator:
-- name: special-config-2
-  literals:
-  - special.how=very
-  - special.type=charm
-EOF
-```
--->
-```shell
-# 创建带有 ConfigMapGenerator 的 kustomization.yaml 文件
-cat <<EOF >./kustomization.yaml
+```yaml
+---
+# 基于字面创建 ConfigMap 的 kustomization.yaml 内容
 configMapGenerator:
 - name: special-config-2
   literals:
@@ -739,18 +731,40 @@ EOF
 ```
 
 <!--
-Apply the kustomization directory to create the ConfigMap object.
+Apply the kustomization directory to create the ConfigMap object:
 -->
 应用 Kustomization 目录创建 ConfigMap 对象。
 
 ```shell
 kubectl apply -k .
 ```
-
 ```
 configmap/special-config-2-c92b5mmcf2 created
 ```
 
+<!--
+## Interim cleanup
+
+Before proceeding, clean up some of the ConfigMaps you made:
+-->
+## 临时清理    {#interim-cleanup}
+
+在继续之前，清理你创建的一些 ConfigMap：
+
+```bash
+kubectl delete configmap special-config
+kubectl delete configmap env-config
+kubectl delete configmap -l 'game-config in (config-4,config-5)’
+```
+
+<!--
+Now that you have learned to define ConfigMaps, you can move on to the next
+section, and learn how to use these objects with Pods.
+-->
+现在你已经学会了定义 ConfigMap，你可以继续下一节，学习如何将这些对象与 Pod 一起使用。
+
+---
+
 <!--
 ## Define container environment variables using ConfigMap data
 
@@ -796,16 +810,18 @@ configmap/special-config-2-c92b5mmcf2 created
 ### 使用来自多个 ConfigMap 的数据定义容器环境变量    {#define-container-environment-variables-with-data-from-multiple-configmaps}
 
 <!--
-* As with the previous example, create the ConfigMaps first.
+As with the previous example, create the ConfigMaps first.
+Here is the manifest you will use:
 -->
-* 与前面的示例一样，首先创建 ConfigMap。
+与前面的示例一样，首先创建 ConfigMap。
+这是你将使用的清单：
 
-  {{< codenew file="configmap/configmaps.yaml" >}}
+{{< codenew file="configmap/configmaps.yaml" >}}
 
-  <!--
-  Create the ConfigMap:
-  -->
-  创建 ConfigMap:
+<!--
+* Create the ConfigMap:
+-->
+* 创建 ConfigMap:
 
   ```shell
   kubectl create -f https://kubernetes.io/examples/configmap/configmaps.yaml
@@ -832,6 +848,15 @@ configmap/special-config-2-c92b5mmcf2 created
   -->
   现在，Pod 的输出包含环境变量 `SPECIAL_LEVEL_KEY=very` 和 `LOG_LEVEL=INFO`。
 
+  <!--
+  Once you're happy to move on, delete that Pod:
+  -->
+  一旦你乐意继续前进，删除该 Pod：
+
+  ```shell
+  kubectl delete pod dapi-test-pod --now
+  ```
+
 <!--
 ## Configure all key-value pairs in a ConfigMap as container environment variables
 -->
@@ -854,7 +879,8 @@ configmap/special-config-2-c92b5mmcf2 created
   ```
 
 <!--
-* Use `envFrom` to define all of the ConfigMap's data as container environment variables. The key from the ConfigMap becomes the environment variable name in the Pod.
+* Use `envFrom` to define all of the ConfigMap's data as container environment variables. The
+  key from the ConfigMap becomes the environment variable name in the Pod.
 -->
 * 使用 `envFrom` 将所有 ConfigMap 的数据定义为容器环境变量，ConfigMap
   中的键成为 Pod 中的环境变量名称。
@@ -871,50 +897,72 @@ configmap/special-config-2-c92b5mmcf2 created
   ```
 
   <!--
-  Now, the Pod's output includes environment variables `SPECIAL_LEVEL=very` and `SPECIAL_TYPE=charm`.
+  Now, the Pod's output includes environment variables `SPECIAL_LEVEL=very` and
+  `SPECIAL_TYPE=charm`.
+
+  Once you're happy to move on, delete that Pod:
   -->
   现在，Pod 的输出包含环境变量 `SPECIAL_LEVEL=very` 和 `SPECIAL_TYPE=charm`。
 
+  一旦你乐意继续前进，删除该 Pod：
+
+  ```shell
+  kubectl delete pod dapi-test-pod --now
+  ```
+
 <!--
 ## Use ConfigMap-defined environment variables in Pod commands
 -->
 ## 在 Pod 命令中使用 ConfigMap 定义的环境变量    {#use-configmap-defined-environment-variables-in-pod-commands}
 
 <!--
-You can use ConfigMap-defined environment variables in the `command` and `args` of a container using the `$(VAR_NAME)` Kubernetes substitution syntax.
+You can use ConfigMap-defined environment variables in the `command` and `args` of a container
+using the `$(VAR_NAME)` Kubernetes substitution syntax.
 -->
 你可以使用 `$(VAR_NAME)` Kubernetes 替换语法在容器的 `command` 和 `args`
 属性中使用 ConfigMap 定义的环境变量。
 
 <!--
-For example, the following Pod specification
+For example, the following Pod manifest:
+
 -->
-例如，以下 Pod 规约
+例如，以下 Pod 清单：
 
 {{< codenew file="pods/pod-configmap-env-var-valueFrom.yaml" >}}
 
 <!--
-created by running
+Create that Pod, by running:
 -->
-通过运行下面命令创建 Pod：
+通过运行下面命令创建该 Pod：
 
 ```shell
 kubectl create -f https://kubernetes.io/examples/pods/pod-configmap-env-var-valueFrom.yaml
 ```
 
 <!--
-produces the following output in the `test-container` container:
+That pod produces the following output from the `test-container` container:
 -->
-在 `test-container` 容器中产生以下输出:
+此 Pod 在 `test-container` 容器中产生以下输出:
 
 ```
 very charm
 ```
 
+<!--
+Once you're happy to move on, delete that Pod:
+-->
+一旦你乐意继续前进，删除该 Pod：
+
+```shell
+kubectl delete pod dapi-test-pod --now
+```
+
 <!--
 ## Add ConfigMap data to a Volume
 
-As explained in [Create ConfigMaps from files](#create-configmaps-from-files), when you create a ConfigMap using ``--from-file``, the filename becomes a key stored in the `data` section of the ConfigMap. The file contents become the key's value.
+As explained in [Create ConfigMaps from files](#create-configmaps-from-files), when you create
+a ConfigMap using ``--from-file``, the filename becomes a key stored in the `data` section of
+the ConfigMap. The file contents become the key's value.
 -->
 ## 将 ConfigMap 数据添加到一个卷中    {#add-configmap-data-to-a-volume}
 
@@ -923,9 +971,9 @@ As explained in [Create ConfigMaps from files](#create-configmaps-from-files), w
 文件内容成为键对应的值。
 
 <!--
-The examples in this section refer to a ConfigMap named special-config, shown below.
+The examples in this section refer to a ConfigMap named `special-config`:
 -->
-本节中的示例引用了一个名为 'special-config' 的 ConfigMap，如下所示：
+本节中的示例引用了一个名为 `special-config` 的 ConfigMap：
 
 {{< codenew file="configmap/configmap-multikeys.yaml" >}}
 
@@ -942,8 +990,9 @@ kubectl create -f https://kubernetes.io/examples/configmap/configmap-multikeys.y
 ### Populate a Volume with data stored in a ConfigMap
 
 Add the ConfigMap name under the `volumes` section of the Pod specification.
-This adds the ConfigMap data to the directory specified as `volumeMounts.mountPath` (in this case, `/etc/config`).
-The `command` section lists directory files with names that match the keys in ConfigMap.
+This adds the ConfigMap data to the directory specified as `volumeMounts.mountPath` (in this
+case, `/etc/config`). The `command` section lists directory files with names that match the
+keys in ConfigMap.
 -->
 ### 使用存储在 ConfigMap 中的数据填充卷    {#populate-a-volume-with-data-stored-in-a-configmap}
 
@@ -973,21 +1022,32 @@ SPECIAL_LEVEL
 SPECIAL_TYPE
 ```
 
-{{< caution >}}
 <!--
-If there are some files in the `/etc/config/` directory, they will be deleted.
+Text data is exposed as files using the UTF-8 character encoding. To use some other
+character encoding, use `binaryData` (see [ConfigMap object](/docs/concepts/configuration/configmap/#configmap-object) for more details).
 -->
-如果在 `/etc/config/` 目录中有一些文件，这些文件将被删除。
-{{< /caution >}}
+文本数据会展现为 UTF-8 字符编码的文件。如果使用其他字符编码，
+可以使用 `binaryData`（详情参阅 [ConfigMap 对象](/zh-cn/docs/concepts/configuration/configmap/#configmap-object)）。
 
 {{< note >}}
+
 <!--
-Text data is exposed as files using the UTF-8 character encoding. To use some other character encoding, use binaryData.
+If there are any files in the `/etc/config` directory of that container image, the volume
+mount will make those files from the image inaccessible.
 -->
-文本数据会展现为 UTF-8 字符编码的文件。如果使用其他字符编码，
-可以使用 `binaryData`。
+如果该容器镜像的 `/etc/config`
+目录中有一些文件，卷挂载将使该镜像中的这些文件无法访问。
 {{< /note >}}
 
+<!--
+Once you're happy to move on, delete that Pod:
+-->
+一旦你乐意继续前进，删除该 Pod：
+
+```shell
+kubectl delete pod dapi-test-pod --now
+```
+
 <!--
 ### Add ConfigMap data to a specific path in the Volume
 
@@ -1005,7 +1065,7 @@ In this case, the `SPECIAL_LEVEL` item will be mounted in the `config-volume` vo
 <!--
 Create the Pod:
 -->
-创建Pod：
+创建 Pod：
 
 ```shell
 kubectl create -f https://kubernetes.io/examples/pods/pod-configmap-volume-specific-key.yaml
@@ -1027,26 +1087,89 @@ Like before, all previous files in the `/etc/config/` directory will be deleted.
 如前，`/etc/config/` 目录中所有先前的文件都将被删除。
 {{< /caution >}}
 
+<!--
+Delete that Pod:
+-->
+删除该 Pod:
+
+```shell
+kubectl delete pod dapi-test-pod --now
+```
+
 <!--
 ### Project keys to specific paths and file permissions
 
 You can project keys to specific paths and specific permissions on a per-file
-basis. The [Secrets](/docs/concepts/configuration/secret/#using-secrets-as-files-from-a-pod) user guide explains the syntax.
+basis. The
+[Secrets](/docs/concepts/configuration/secret/#using-secrets-as-files-from-a-pod)
+guide explains the syntax.
 -->
+
 ### 映射键到指定路径并设置文件访问权限    {#project-keys-to-specific-paths-and-file-permissions}
 
 你可以将指定键名投射到特定目录，也可以逐个文件地设定访问权限。
-[Secret 用户指南](/zh-cn/docs/concepts/configuration/secret/#using-secrets-as-files-from-a-pod)
-中为这一语法提供了解释。
+[Secret](/zh-cn/docs/concepts/configuration/secret/#using-secrets-as-files-from-a-pod)
+指南中为这一语法提供了解释。
+
+<!--
+### Optional references
+
+A ConfigMap reference may be marked _optional_.  If the ConfigMap is non-existent, the mounted
+volume will be empty. If the ConfigMap exists, but the referenced key is non-existent, the path
+will be absent beneath the mount point. See [Optional ConfigMaps](#optional-configmaps) for more
+details.
+-->
+### 可选引用    {#optional-references}
+
+ConfigMap 引用可以被标记为**可选**。
+如果 ConfigMap 不存在，则挂载的卷将为空。
+如果 ConfigMap 存在，但引用的键不存在，则挂载点下的路径将不存在。
+有关更多信息，请参阅[可选 ConfigMap](#optional-configmaps) 细节。
+
+<!--
+### Mounted ConfigMaps are updated automatically
+
+When a mounted ConfigMap is updated, the projected content is eventually updated too.
+This applies in the case where an optionally referenced ConfigMap comes into
+existence after a pod has started.
+-->
+### 挂载的 ConfigMap 会被自动更新    {#mounted-configMaps-are-updated-automatically}
 
+当已挂载的 ConfigMap 被更新时，所投射的内容最终也会被更新。
+这适用于 Pod 启动后可选引用的 ConfigMap 重新出现的情况。
 
+<!--
+Kubelet checks whether the mounted ConfigMap is fresh on every periodic sync. However,
+it uses its local TTL-based cache for getting the current value of the ConfigMap. As a
+result, the total delay from the moment when the ConfigMap is updated to the moment
+when new keys are projected to the pod can be as long as kubelet sync period (1
+minute by default) + TTL of ConfigMaps cache (1 minute by default) in kubelet. You
+can trigger an immediate refresh by updating one of the pod's annotations.
+-->
+Kubelet 在每次定期同步时都会检查所挂载的 ConfigMap 是否是最新的。
+然而，它使用其基于 TTL 机制的本地缓存来获取 ConfigMap 的当前值。
+因此，从 ConfigMap 更新到新键映射到 Pod 的总延迟可能与 kubelet
+同步周期（默认为1分钟）+ kubelet 中 ConfigMap 缓存的 TTL（默认为1分钟）一样长。
+你可以通过更新 Pod 的一个注解来触发立即刷新。
+
+{{< note >}}
+<!--
+A container using a ConfigMap as a [subPath](/docs/concepts/storage/volumes/#using-subpath) volume will not receive ConfigMap updates.
+-->
+使用 ConfigMap 作为 [subPath](/zh-cn/docs/concepts/storage/volumes/#using-subpath)
+卷的容器将不会收到 ConfigMap 更新。
+{{< /note >}}
 
 <!-- discussion -->
 
 <!--
 ## Understanding ConfigMaps and Pods
 
-The ConfigMap API resource stores configuration data as key-value pairs. The data can be consumed in pods or provide the configurations for system components such as controllers. ConfigMap is similar to [Secrets](/docs/concepts/configuration/secret/), but provides a means of working with strings that don't contain sensitive information. Users and system components alike can store configuration data in ConfigMap.
+The ConfigMap API resource stores configuration data as key-value pairs. The data can be consumed
+in pods or provide the configurations for system components such as controllers. ConfigMap is
+similar to [Secrets](/docs/concepts/configuration/secret/), but provides a means of working
+with strings that don't contain sensitive information. Users and system components alike can
+store configuration data in ConfigMap.
 -->
 ## 了解 ConfigMap 和 Pod    {#understanding-configmaps-and-pods}
 
@@ -1058,7 +1181,10 @@ ConfigMap 与 [Secret](/zh-cn/docs/concepts/configuration/secret/) 类似，
 
 {{< note >}}
 <!--
-ConfigMaps should reference properties files, not replace them. Think of the ConfigMap as representing something similar to the Linux `/etc` directory and its contents. For example, if you create a [Kubernetes Volume](/docs/concepts/storage/volumes/) from a ConfigMap, each data item in the ConfigMap is represented by an individual file in the volume.
+ConfigMaps should reference properties files, not replace them. Think of the ConfigMap as
+representing something similar to the Linux `/etc` directory and its contents. For example,
+if you create a [Kubernetes Volume](/docs/concepts/storage/volumes/) from a ConfigMap, each
+data item in the ConfigMap is represented by an individual file in the volume.
 -->
 ConfigMap 应该引用属性文件，而不是替换它们。可以将 ConfigMap 理解为类似于 Linux
 `/etc` 目录及其内容的东西。例如，如果你基于 ConfigMap 创建
@@ -1067,12 +1193,13 @@ ConfigMap 应该引用属性文件，而不是替换它们。可以将 ConfigMap
 {{< /note >}}
 
 <!--
-The ConfigMap's `data` field contains the configuration data. As shown in the example below, this can be simple -- like individual properties defined using `--from-literal` -- or complex -- like configuration files or JSON blobs defined using `--from-file`.
+The ConfigMap's `data` field contains the configuration data. As shown in the example below,
+this can be simple (like individual properties defined using `--from-literal`) or complex
+(like configuration files or JSON blobs defined using `--from-file`).
 -->
 ConfigMap 的 `data` 字段包含配置数据。如下例所示，它可以简单
 （如用 `--from-literal` 的单个属性定义）或复杂
-（如用 `--from-file` 的配置文件或 JSON blob定义）。
-
+（如用 `--from-file` 的配置文件或 JSON blob 定义）。
 
 ```yaml
 apiVersion: v1
@@ -1093,66 +1220,44 @@ data:
 ```
 
 <!--
-### Restrictions
-
-- You must create the `ConfigMap` object before you reference it in a Pod specification. Alternatively, mark the ConfigMap reference as `optional` in the Pod spec (see [Optional ConfigMaps](#optional-configmaps)). If you reference a ConfigMap that doesn't exist and you don't mark the reference as `optional`, the Pod won't start. Similarly, references to keys that don't exist in the ConfigMap will also prevent the Pod from starting, unless you mark the key references as `optional`.
+When `kubectl` creates a ConfigMap from inputs that are not ASCII or UTF-8, the tool puts
+these into the `binaryData` field of the ConfigMap, and not in `data`. Both text and binary
+data sources can be combined in one ConfigMap.
 -->
-### 限制   {#restrictions}
-
-- 在 Pod 规约中引用某个 `ConfigMap` 之前，必须先创建这个对象，
-或者在 Pod 规约中将 ConfigMap 标记为 `optional`（请参阅[可选的 ConfigMaps](#optional-configmaps)）。
-如果所引用的 ConfigMap 不存在，并且没有将应用标记为 `optional` 则 Pod 将无法启动。
-同样，引用 ConfigMap 中不存在的主键也会令 Pod 无法启动，除非你将 Configmap 标记为 `optional`。
+当 `kubectl` 从非 ASCII 或 UTF-8 编码的输入创建 ConfigMap 时，
+该工具将这些输入放入 ConfigMap 的 `binaryData` 字段，而不是 `data` 字段。
+文本和二进制数据源都可以组合在一个 ConfigMap 中。
 
 <!--
-- If you use `envFrom` to define environment variables from ConfigMaps, keys that are considered invalid will be skipped. The pod will be allowed to start, but the invalid names will be recorded in the event log (`InvalidVariableNames`). The log message lists each skipped key. For example:
+If you want to view the `binaryData` keys (and their values) in a ConfigMap, you can run
+`kubectl get configmap -o jsonpath='{.binaryData}' <name>`.
 -->
-- 如果你使用 `envFrom` 来基于 ConfigMap 定义环境变量，那么无效的键将被忽略。
-  Pod 可以被启动，但无效名称将被记录在事件日志中（`InvalidVariableNames`）。
-  日志消息列出了每个被跳过的键。例如:
-
-  ```shell
-  kubectl get events
-  ```
-
-  <!--
-  The output is similar to this:
-  -->
-  输出与此类似:
-
-  ```
-  LASTSEEN FIRSTSEEN COUNT NAME          KIND  SUBOBJECT  TYPE      REASON                            SOURCE                MESSAGE
-  0s       0s        1     dapi-test-pod Pod              Warning   InvalidEnvironmentVariableNames   {kubelet, 127.0.0.1}  Keys [1badkey, 2alsobad] from the EnvFrom configMap default/myconfig were skipped since they are considered invalid environment variable names.
-  ```
-
-<!--
-- ConfigMaps reside in a specific {{< glossary_tooltip term_id="namespace" >}}. A ConfigMap can only be referenced by pods residing in the same namespace.
--->
-- ConfigMap 位于确定的{{< glossary_tooltip term_id="namespace" text="名字空间" >}}中。
-  每个 ConfigMap 只能被同一名字空间中的 Pod 引用.
+如果你想查看 ConfigMap 中的 `binaryData` 键（及其值），
+可以运行 `kubectl get configmap -o jsonpath='{.binaryData}' <name>`。
 
 <!--
-- You can't use ConfigMaps for {{< glossary_tooltip text="static pods" term_id="static-pod" >}}, because the Kubelet does not support this.
+Pods can load data from a ConfigMap that uses either `data` or `binaryData`.
 -->
-- 你不能将 ConfigMap 用于{{< glossary_tooltip text="静态 Pod" term_id="static-pod" >}}，
-  因为 Kubernetes 不支持这种用法。
+Pod 可以从使用 `data` 或 `binaryData` 的 ConfigMap 中加载数据。
 
 <!--
-### Optional ConfigMaps
+## Optional ConfigMaps
 -->
 ### 可选的 ConfigMap {#optional-configmaps}
 
 <!--
 You can mark a reference to a ConfigMap as _optional_ in a Pod specification.
-If the ConfigMap doesn't exist, the configuration for which it provides data in the Pod (e.g. environment variable, mounted volume) will be empty.
+If the ConfigMap doesn't exist, the configuration for which it provides data in the Pod
+(for example: environment variable, mounted volume) will be empty.
 If the ConfigMap exists, but the referenced key is non-existent the data is also empty.
 -->
 你可以在 Pod 规约中将对 ConfigMap 的引用标记为 **可选（optional）**。
-如果 ConfigMap 不存在，那么它在 Pod 中为其提供数据的配置（例如环境变量、挂载的卷）将为空。
+如果 ConfigMap 不存在，那么它在 Pod 中为其提供数据的配置（例如：环境变量、挂载的卷）将为空。
 如果 ConfigMap 存在，但引用的键不存在，那么数据也是空的。
 
 <!--
-For example, the following Pod specification marks an environment variable from a ConfigMap as optional:
+For example, the following Pod specification marks an environment variable from a ConfigMap
+as optional:
 -->
 例如，以下 Pod 规约将 ConfigMap 中的环境变量标记为可选：
 
@@ -1165,7 +1270,7 @@ spec:
   containers:
     - name: test-container
       image: gcr.io/google_containers/busybox
-      command: [ "/bin/sh", "-c", "env" ]
+      command: ["/bin/sh", "-c", "env"]
       env:
         - name: SPECIAL_LEVEL_KEY
           valueFrom:
@@ -1175,6 +1280,7 @@ spec:
               optional: true # 将环境变量标记为可选
   restartPolicy: Never
 ```
+
 <!--
 If you run this pod, and there is no ConfigMap named `a-config`, the output is empty.
 If you run this pod, and there is a ConfigMap named `a-config` but that ConfigMap doesn't have
@@ -1188,14 +1294,14 @@ ConfigMap, this pod prints that value and then terminates.
 那么这个 Pod 会打印该值，然后终止。
 
 <!--
-You can also mark the volumes and files provided by a ConfigMap as optional. Kubernetes always creates the mount paths for the volume, even if the referenced ConfigMap or key doesn't exist. For example, the following
-Pod specification marks a volume that references a ConfigMap as optional:
+You can also mark the volumes and files provided by a ConfigMap as optional. Kubernetes always
+creates the mount paths for the volume, even if the referenced ConfigMap or key doesn't exist. For
+example, the following Pod specification marks a volume that references a ConfigMap as optional:
 -->
 你也可以在 Pod 规约中将 ConfigMap 提供的卷和文件标记为可选。
 此时 Kubernetes 将总是为卷创建挂载路径，即使引用的 ConfigMap 或键不存在。
 例如，以下 Pod 规约将所引用得 ConfigMap 的卷标记为可选：
 
-
 ```yaml
 apiVersion: v1
 kind: Pod
@@ -1205,7 +1311,7 @@ spec:
   containers:
     - name: test-container
       image: gcr.io/google_containers/busybox
-      command: [ "/bin/sh", "-c", "ls /etc/config" ]
+      command: ["/bin/sh", "-c", "ls /etc/config"]
       volumeMounts:
       - name: config-volume
         mountPath: /etc/config
@@ -1217,20 +1323,25 @@ spec:
   restartPolicy: Never
 ```
 
-### 挂载的 ConfigMap 将被自动更新   {#mounted-configmaps-are-updated-automatically}
-
 <!--
-When a mounted ConfigMap is updated, the projected content is eventually updated too.  This applies in the case where an optionally referenced ConfigMap comes into
-existence after a pod has started.
+### Mounted ConfigMaps are updated automatically
+
+When a mounted ConfigMap is updated, the projected content is eventually updated too.
+This applies in the case where an optionally referenced ConfigMap comes into existence after
+a pod has started.
 -->
+### 挂载的 ConfigMap 将被自动更新   {#mounted-configmaps-are-updated-automatically}
+
 当某个已被挂载的 ConfigMap 被更新，所投射的内容最终也会被更新。
 对于 Pod 已经启动之后所引用的、可选的 ConfigMap 才出现的情形，
 这一动态更新现象也是适用的。
 
 <!--
-The kubelet checks whether the mounted ConfigMap is fresh on every periodic sync. However, it uses its local TTL-based cache for getting the current value of the
-ConfigMap. As a result, the total delay from the moment when the ConfigMap is updated to the moment when new keys are projected to the pod can be as long as
-kubelet sync period (1 minute by default) + TTL of ConfigMaps cache (1 minute by default) in kubelet.
+The kubelet checks whether the mounted ConfigMap is fresh on every periodic sync. However, it
+uses its local TTL-based cache for getting the current value of the ConfigMap. As a result,
+the total delay from the moment when the ConfigMap is updated to the moment when new keys
+are projected to the pod can be as long as kubelet sync period (1 minute by default) + TTL of
+ConfigMaps cache (1 minute by default) in kubelet.
 -->
 kubelet 在每次周期性同步时都会检查已挂载的 ConfigMap 是否是最新的。
 但是，它使用其本地的基于 TTL 的缓存来获取 ConfigMap 的当前值。
@@ -1244,11 +1355,92 @@ A container using a ConfigMap as a [subPath](/docs/concepts/storage/volumes/#usi
 使用 ConfigMap 作为 [subPath](/zh-cn/docs/concepts/storage/volumes/#using-subpath)
 的数据卷将不会收到 ConfigMap 更新。
 {{< /note >}}
+
+<!--
+## Restrictions
+-->
+### 限制   {#restrictions}
+
+<!--
+- You must create the `ConfigMap` object before you reference it in a Pod
+  specification. Alternatively, mark the ConfigMap reference as `optional` in the Pod spec (see
+  [Optional ConfigMaps](#optional-configmaps)). If you reference a ConfigMap that doesn't exist
+  and you don't mark the reference as `optional`, the Pod won't start. Similarly, references
+  to keys that don't exist in the ConfigMap will also prevent the Pod from starting, unless
+  you mark the key references as `optional`.
+-->
+- 在 Pod 规约中引用某个 `ConfigMap` 之前，必须先创建这个对象，
+  或者在 Pod 规约中将 ConfigMap 标记为 `optional`（请参阅[可选的 ConfigMaps](#optional-configmaps)）。
+  如果所引用的 ConfigMap 不存在，并且没有将应用标记为 `optional` 则 Pod 将无法启动。
+  同样，引用 ConfigMap 中不存在的主键也会令 Pod 无法启动，除非你将 Configmap 标记为 `optional`。
+
+<!--
+- If you use `envFrom` to define environment variables from ConfigMaps, keys that are considered
+  invalid will be skipped. The pod will be allowed to start, but the invalid names will be
+  recorded in the event log (`InvalidVariableNames`). The log message lists each skipped
+  key. For example:
+-->
+- 如果你使用 `envFrom` 来基于 ConfigMap 定义环境变量，那么无效的键将被忽略。
+  Pod 可以被启动，但无效名称将被记录在事件日志中（`InvalidVariableNames`）。
+  日志消息列出了每个被跳过的键。例如:
+
+  ```shell
+  kubectl get events
+  ```
+
+  <!--
+  The output is similar to this:
+  -->
+  输出与此类似:
+  ```
+  LASTSEEN FIRSTSEEN COUNT NAME          KIND  SUBOBJECT  TYPE      REASON                            SOURCE                MESSAGE
+  0s       0s        1     dapi-test-pod Pod              Warning   InvalidEnvironmentVariableNames   {kubelet, 127.0.0.1}  Keys [1badkey, 2alsobad] from the EnvFrom configMap default/myconfig were skipped since they are considered invalid environment variable names.
+  ```
+
+<!--
+- ConfigMaps reside in a specific {{< glossary_tooltip term_id="namespace" >}}.
+  Pods can only refer to ConfigMaps that are in the same namespace as the Pod.
+-->
+- ConfigMap 位于确定的{{< glossary_tooltip term_id="namespace" text="名字空间" >}}中。
+  每个 ConfigMap 只能被同一名字空间中的 Pod 引用.
+
+<!--
+- You can't use ConfigMaps for
+  {{< glossary_tooltip text="static pods" term_id="static-pod" >}}, because the
+  kubelet does not support this.
+-->
+- 你不能将 ConfigMap 用于{{< glossary_tooltip text="静态 Pod" term_id="static-pod" >}}，
+  因为 Kubernetes 不支持这种用法。
+
+## {{% heading "cleanup" %}}
+
+<!--
+Delete the ConfigMaps and Pods that you made:
+-->
+删除你创建那些的 ConfigMap 和 Pod：
+
+```bash
+kubectl delete configmaps/game-config configmaps/game-config-2 configmaps/game-config-3 \
+               configmaps/game-config-env-file
+kubectl delete pod dapi-test-pod --now
+
+# 你可能已经删除了下一组内容
+kubectl delete configmaps/special-config configmaps/env-config
+kubectl delete configmap -l 'game-config in (config-4,config-5)’
+```
+
+<!--
+If you created a directory `configure-pod-container` and no longer need it, you should remove that too,
+or move it into the trash can / deleted files location.
+-->
+如果你创建了一个目录 `configure-pod-container` 并且不再需要它，你也应该删除这个目录，
+或者将该目录移动到回收站/删除文件的位置。
+
 ## {{% heading "whatsnext" %}}
 
 <!--
-* Follow a real world example of [Configuring Redis using a ConfigMap](/docs/tutorials/configuration/configure-redis-using-configmap/).
+* Follow a real world example of
+  [Configuring Redis using a ConfigMap](/docs/tutorials/configuration/configure-redis-using-configmap/).
 -->
 * 浏览[使用 ConfigMap 配置 Redis](/zh-cn/docs/tutorials/configuration/configure-redis-using-configmap/)
   真实示例。
-