File tree Expand file tree Collapse file tree 1 file changed +0
-33
lines changed
content/zh-cn/docs/tasks/configure-pod-container Expand file tree Collapse file tree 1 file changed +0
-33
lines changed Original file line number Diff line number Diff line change @@ -1323,39 +1323,6 @@ spec:
1323
1323
restartPolicy: Never
1324
1324
` ` `
1325
1325
1326
- < ! --
1327
- # ## Mounted ConfigMaps are updated automatically
1328
-
1329
- When a mounted ConfigMap is updated, the projected content is eventually updated too.
1330
- This applies in the case where an optionally referenced ConfigMap comes into existence after
1331
- a pod has started.
1332
- -->
1333
- # ## 挂载的 ConfigMap 将被自动更新 {#mounted-configmaps-are-updated-automatically}
1334
-
1335
- 当某个已被挂载的 ConfigMap 被更新,所投射的内容最终也会被更新。
1336
- 对于 Pod 已经启动之后所引用的、可选的 ConfigMap 才出现的情形,
1337
- 这一动态更新现象也是适用的。
1338
-
1339
- < ! --
1340
- The kubelet checks whether the mounted ConfigMap is fresh on every periodic sync. However, it
1341
- uses its local TTL-based cache for getting the current value of the ConfigMap. As a result,
1342
- the total delay from the moment when the ConfigMap is updated to the moment when new keys
1343
- are projected to the pod can be as long as kubelet sync period (1 minute by default) + TTL of
1344
- ConfigMaps cache (1 minute by default) in kubelet.
1345
- -->
1346
- kubelet 在每次周期性同步时都会检查已挂载的 ConfigMap 是否是最新的。
1347
- 但是,它使用其本地的基于 TTL 的缓存来获取 ConfigMap 的当前值。
1348
- 因此,从更新 ConfigMap 到将新键映射到 Pod 的总延迟可能等于 kubelet 同步周期
1349
- (默认 1 分钟) + ConfigMap 在 kubelet 中缓存的 TTL(默认 1 分钟)。
1350
-
1351
- {{< note >}}
1352
- <!--
1353
- A container using a ConfigMap as a [subPath](/docs/concepts/storage/volumes/#using-subpath) volume will not receive ConfigMap updates.
1354
- -->
1355
- 使用 ConfigMap 作为 [subPath](/zh-cn/docs/concepts/storage/volumes/# using-subpath)
1356
- 的数据卷将不会收到 ConfigMap 更新。
1357
- {{< /note > }}
1358
-
1359
1326
< ! --
1360
1327
# # Restrictions
1361
1328
-->
You can’t perform that action at this time.
0 commit comments