Update content/en/docs/tasks/configure-pod-container/configure-pod-configmap.md

Co-authored-by: Shannon Kularathna <ax3shannonkularathna@gmail.com>
This commit is contained in:
Tom Kivlin
2022-07-26 09:19:15 +01:00
committed by GitHub
parent 7e16543b9d
commit c3f86b7fc0
@@ -746,7 +746,7 @@ If you run this pod, and there is no ConfigMap named `no-config`, the mounted vo
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.
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
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.