liveBook · Manning

Image pull policy

An image pull policy is a Kubernetes container setting that determines when its image is pulled from a registry onto a node.

How 2 Manning books explain it

Kubernetes for Developers

An image pull policy is a Kubernetes Pod setting that determines when a container image is pulled from a registry.

How it is used
Uses Never to run locally built images without pushing them to a registry during development.
How deep it goes
Explains the local-image configuration and ErrImageNeverPull failure, but does not compare other pull-policy values.
Examples
Demonstrates timeserver:latest with imagePullPolicy: Never and Minikube image loading.
What you can do after
Operate local Kubernetes deployments using locally built images and diagnose ErrImageNeverPull when images are unavailable.

Read how Kubernetes for Developers explains image pull policy →

Kubernetes in Action, Second Edition

An image pull policy is a Kubernetes container setting that determines when its container image is pulled onto a node.

How it is used
Controls whether container startup uses a registry, a worker-node cache, or both.
How deep it goes
Explains three policies, tag-based defaults, restart behavior, caching, and registry failures without descending into image internals.
Examples
Uses Always, Never, and IfNotPresent scenarios involving cached images, failed restarts, corrected tags, and unavailable registries.
What you can do after
Operate/configure container startup by selecting a policy and anticipating its cache, restart, and registry effects.

Read how Kubernetes in Action, Second Edition explains image pull policy →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.