whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update secrets documentation in 1.13 (#15532)

Browse Source
This commit is contained in:
Wojciech Tyczynski
2019-07-26 05:07:59 +02:00
committed by Kubernetes Prow Robot
parent a0be0517fd
commit 00dd4cb337
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/configuration/secret.md
+1 -1
View File
@@ -471,7 +471,7 @@ Kubelet is checking whether the mounted secret is fresh on every periodic sync.
However, it is using its local cache for getting the current value of the Secret. However, it is using its local cache for getting the current value of the Secret.
The type of the cache is configurable using the (`ConfigMapAndSecretChangeDetectionStrategy` field in The type of the cache is configurable using the (`ConfigMapAndSecretChangeDetectionStrategy` field in
[KubeletConfiguration struct](https://github.com/kubernetes/kubernetes/blob/{{< param "docsbranch" >}}/staging/src/k8s.io/kubelet/config/v1beta1/types.go)). [KubeletConfiguration struct](https://github.com/kubernetes/kubernetes/blob/{{< param "docsbranch" >}}/staging/src/k8s.io/kubelet/config/v1beta1/types.go)).
It can be either propagated via watch (default), ttl-based, or simply redirecting It can be either propagated via watch, ttl-based (default), or simply redirecting
all requests to directly kube-apiserver. all requests to directly kube-apiserver.
As a result, the total delay from the moment when the Secret is updated to the moment As a result, the total delay from the moment when the Secret is updated to the moment
when new keys are projected to the Pod can be as long as kubelet sync period + cache when new keys are projected to the Pod can be as long as kubelet sync period + cache