k8s-imagePullPolicy拉取策略

imagePullPolicy
Always
总是拉取 pull

imagePullPolicy: Always
1
IfNotPresent
默认值,本地有则使用本地镜像,不拉取

imagePullPolicy: IfNotPresent
1
Never
只使用本地镜像,从不拉取

imagePullPolicy: Never
1
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
————————————————
版权声明:本文为CSDN博主「中国lanwp」的原创文章,遵循CC 4.0 BY-SA版权协议,转载请附上原文出处链接及本声明。
原文链接:https://blog.csdn.net/lanwp5302/java/article/details/87348132

posted @ 2020-05-25 10:37  gao88  阅读(923)  评论(0编辑  收藏  举报