k8s-imagePullPolicy拉取策略

关注

原创最新推荐文章于 2026-09-06 14:06:31 发布 7.7w 阅读 AI 写同款· GEO 优化 ›

k8s 的 pod 基础 2 Pod 的核心是运行容器，必须指定容器引擎，比如 Docker，启动容器时，需要拉取镜像，k8s 的镜像拉取策略可以由用户指定：1、：优先使用本地已存在的镜像，若没有则去仓库拉取镜像，默认的镜像拉取策略2、：每次创建 Pod 都会从仓库拉取镜像，无论本地是否已存在镜像；3、：总是不去仓库拉取镜像，仅使用本地镜像。注意：对于标签为“:latest”的镜像文件，其默认的镜像获取策略即为“Always”；而对于其他标签的镜像，其默认策略则为“IfNotPresent”。阅读详情

kubernetes官网参考imagePullPolicy

imagePullPolicy

Always

总是拉取 pull

imagePullPolicy: Always

IfNotPresent

默认值,本地有则使用本地镜像,不拉取

imagePullPolicy: IfNotPresent

Never

只使用本地镜像，从不拉取

imagePullPolicy: Never

Pre-pulling Images
Note: If you are running on Google Kubernetes Engine, there will already be a .dockercfg on each node with credentials for Google Container Registry. You cannot use this approach.
Note: This approach is suitable if you can control node configuration. It will not work reliably on GCE, and any other cloud provider that does automatic node replacement.
By default, the kubelet will try to pull each image from the specified registry. However, if the imagePullPolicy property of the container is set to IfNotPresent or Never, then a local image is used (preferentially or exclusively, respectively).

If you want to rely on pre-pulled images as a substitute for registry authentication, you must ensure all nodes in the cluster have the same pre-pulled images.

This can be used to preload certain images for speed or as an alternative to authenticating to a private registry.

All pods will have read access to any pre-pulled images

收录于