k8s imagePullPolicy拉取策略

Posted supery007

tags:

篇首语:本文由小常识网(cha138.com)小编为大家整理,主要介绍了k8s 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

 

以上是关于k8s imagePullPolicy拉取策略的主要内容,如果未能解决你的问题,请参考以下文章

Kubernetes imagePullPolicy 拉取策略

Kubernetes imagePullPolicy 拉取策略

yaml文件中镜像拉取策略

k8s从私有仓库拉取镜像创建pod时ImagePullBackOff

Kubernetes之Pod镜像拉取策略配置

k8s部署mysql