Kubernetes Container Image Pull Concepts: Difference between revisions
Jump to navigation
Jump to search
| Line 15: | Line 15: | ||
There are three possible values: <code>Always</code>, <code>IfNotPresent</code> and <code>Never</code>. This attribute is optional, and if it is not specified, it is inferred based on the image tag. The default is <code>Always</code> if ":latest" tag is specified, or <code>IfNotPresent</code> otherwise. | There are three possible values: <code>Always</code>, <code>IfNotPresent</code> and <code>Never</code>. This attribute is optional, and if it is not specified, it is inferred based on the image tag. The default is <code>Always</code> if ":latest" tag is specified, or <code>IfNotPresent</code> otherwise. | ||
The pull policy can be also enforced with the [[Kubernetes_Admission_Controller_Concepts#AlwaysPullImages|AlwaysPullImages admission controller]]. | |||
Revision as of 17:27, 26 August 2020
External
- https://kubernetes.io/docs/concepts/containers/images/
- https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/
Internal
Overview
A pod's containers pull their images from their respective repositories while the pod is in Pending phase. Technically, it is the kubelet that performs the image pulling on behalf of the pod.
Pull Policy
The pull policy is configured on a per-container basis using the imagePullPolicy tag in the pod manifest.
There are three possible values: Always, IfNotPresent and Never. This attribute is optional, and if it is not specified, it is inferred based on the image tag. The default is Always if ":latest" tag is specified, or IfNotPresent otherwise.
The pull policy can be also enforced with the AlwaysPullImages admission controller.