From 6ad483fb8e7d42bf5c88e9d04a9dab480a418e50 Mon Sep 17 00:00:00 2001 From: wawa0210 Date: Fri, 22 May 2020 17:33:54 +0800 Subject: [PATCH] Clarify behavior of `imagePullPolicy: Always` --- content/en/docs/concepts/configuration/overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/configuration/overview.md b/content/en/docs/concepts/configuration/overview.md index d07bf762bb..b7b7b829db 100644 --- a/content/en/docs/concepts/configuration/overview.md +++ b/content/en/docs/concepts/configuration/overview.md @@ -77,7 +77,7 @@ The [imagePullPolicy](/docs/concepts/containers/images/#updating-images) and the - `imagePullPolicy: IfNotPresent`: the image is pulled only if it is not already present locally. -- `imagePullPolicy: Always`: the image is pulled every time the pod is started. +- `imagePullPolicy: Always`: every time the kubelet launches a container, the kubelet queries the container image registry to resolve the name to an image digest. If the kubelet has a container image with that exact digest cached locally, the kubelet uses its cached image; otherwise, the kubelet downloads (pulls) the image with the resolved digest, and uses that image to launch the container. - `imagePullPolicy` is omitted and either the image tag is `:latest` or it is omitted: `Always` is applied.