Fix a typo in the configmap concept page

This commit is contained in:
Qiming Teng 2023-04-30 20:08:16 +08:00
parent 7bdcd3da4c
commit 8dda236d6f
1 changed files with 1 additions and 1 deletions

View File

@ -188,7 +188,7 @@ own `volumeMounts` block, but only one `.spec.volumes` is needed per ConfigMap.
When a ConfigMap currently consumed in a volume is updated, projected keys are eventually updated as well.
The kubelet checks whether the mounted ConfigMap is fresh on every periodic sync.
However, the kubelet uses its local cache for getting the current value of the ConfigMap.
The type of the cache is configurable using the `ConfigMapAndSecretChangeDetectionStrategy` field in
The type of the cache is configurable using the `configMapAndSecretChangeDetectionStrategy` field in
the [KubeletConfiguration struct](/docs/reference/config-api/kubelet-config.v1beta1/).
A ConfigMap can be either propagated by watch (default), ttl-based, or by redirecting
all requests directly to the API server.