Skip to content

Commit 5214deb

Browse files
committed
[zh] Sync concepts pages for configuration\configmap.md
* Sync with english version in 'clarify: add that binaryData is base64-encoded (#27066)' Signed-off-by: ydFu <[email protected]>
1 parent 52997fc commit 5214deb

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

content/zh/docs/concepts/configuration/configmap.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,7 @@ Kubernetes objects that have a `spec`, a ConfigMap has `data` and `binaryData`
6666
fields. These fields accept key-value pairs as their values. Both the `data`
6767
field and the `binaryData` are optional. The `data` field is designed to
6868
contain UTF-8 byte sequences while the `binaryData` field is designed to
69-
contain binary data.
69+
contain binary data as base64-encoded strings.
7070
7171
The name of a ConfigMap must be a valid
7272
[DNS subdomain name](/docs/concepts/overview/working-with-objects/names#dns-subdomain-names).
@@ -78,7 +78,7 @@ ConfigMap 是一个 API [对象](/zh/docs/concepts/overview/working-with-objects
7878
和其他 Kubernetes 对象都有一个 `spec` 不同的是,ConfigMap 使用 `data`
7979
`binaryData` 字段。这些字段能够接收键-值对作为其取值。`data``binaryData`
8080
字段都是可选的。`data` 字段设计用来保存 UTF-8 字节序列,而 `binaryData`
81-
被设计用来保存二进制数据
81+
被设计用来保存二进制数据作为 base64 编码的字串
8282

8383
ConfigMap 的名字必须是一个合法的
8484
[DNS 子域名](/zh/docs/concepts/overview/working-with-objects/names#dns-subdomain-names)
@@ -361,15 +361,15 @@ kubelet 组件会在每次周期性同步时检查所挂载的 ConfigMap 是否
361361
的 `ConfigMapAndSecretChangeDetectionStrategy` 字段来配置。
362362

363363
<!--
364-
A ConfigMap can be either propagated by watch (default), ttl-based, or simply redirecting
364+
A ConfigMap can be either propagated by watch (default), ttl-based, or by redirecting
365365
all requests directly to the API server.
366366
As a result, the total delay from the moment when the ConfigMap is updated to the moment
367367
when new keys are projected to the Pod can be as long as the kubelet sync period + cache
368368
propagation delay, where the cache propagation delay depends on the chosen cache type
369369
(it equals to watch propagation delay, ttl of cache, or zero correspondingly).
370370
-->
371371
ConfigMap 既可以通过 watch 操作实现内容传播(默认形式),也可实现基于 TTL
372-
的缓存,还可以直接将所有请求重定向到 API 服务器。
372+
的缓存,还可以直接经过所有请求重定向到 API 服务器。
373373
因此,从 ConfigMap 被更新的那一刻算起,到新的主键被投射到 Pod 中去,这一
374374
时间跨度可能与 kubelet 的同步周期加上高速缓存的传播延迟相等。
375375
这里的传播延迟取决于所选的高速缓存类型

0 commit comments

Comments
 (0)