Skip to content

Commit

Permalink
Update ConfigMap doc to explain TTL-based cache updates (#3989)
Browse files Browse the repository at this point in the history
* Update ConfigMap doc to explain TTL-based cache updates

* swap word order

Change "When a ConfigMap being already consumed..." to "When a ConfigMap already being consumed..."
  • Loading branch information
shyamjvs authored and chenopis committed Jun 5, 2017
1 parent 36b4721 commit f214805
Showing 1 changed file with 4 additions and 0 deletions.
4 changes: 4 additions & 0 deletions docs/tasks/configure-pod-container/configure-pod-configmap.md
Original file line number Diff line number Diff line change
Expand Up @@ -273,6 +273,10 @@ very
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.

### Mounted ConfigMaps are updated automatically

When a ConfigMap already being consumed in a volume is updated, projected keys are eventually updated as well. Kubelet is checking whether the mounted ConfigMap is fresh on every periodic sync. However, it is using 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 + ttl of ConfigMaps cache in kubelet.

{% endcapture %}

{% capture discussion %}
Expand Down

0 comments on commit f214805

Please sign in to comment.