Kube.netes 不断重新拉取镜像

Question

使用microk8s安装。 图像已标记，因此应使用IfNotPresent策略。

apiVersion: apps/v1
  2 kind: Deployment
  3 metadata:
  4   name: lh-graphql
  5   labels:
  6     app: lh-graphql 
  7 spec:
  8   selector:
  9     matchLabels:
 10       app: lh-graphql
 11   strategy:
 12     type: Recreate
 13   template:
 14     metadata:
 15       labels:
 16         app: lh-graphql
 17     spec:
 18       containers:
 19       - image: hasura/graphql-engine:v2.13.2.cli-migrations-v3 
 20         name: lh-graphql 
 21         ports:
 22         - containerPort: 8080
 23           name: lh-graphql        
 24         env:
 25         - name: HASURA_GRAPHQL_DATABASE_URL  
 26           value: postgresql://postgres:postgres@$(ORCH_POSTGRES_IP):5432/lh

图片已经拉到docker：

light@siddhalok:~$ docker image ls
REPOSITORY                                                   TAG                         IMAGE ID       CREATED        SIZE
postgres                                                     12                          3d6880d04326   2 weeks ago    373MB
hasura/graphql-engine                                        v2.13.2.cli-migrations-v3   4cd490369623   2 months ago   570MB

但是，在删除并重新创建部署后，它会一直拉动。

Events:
  Type    Reason     Age   From               Message
  ----    ------     ----  ----               -------
  Normal  Scheduled  112s  default-scheduler  Successfully assigned default/lh-graphql-6db75544cf-j65wp to siddhalok
  Normal  Pulling    112s  kubelet            Pulling image "hasura/graphql-engine:v2.13.2.cli-migrations-v3"

更新：

从命令行创建时也会发生同样的情况：

microk8s kubectl run det2 --image=registry.dev.mpksoft.ru/lighthouse/lh-detector/lh-detector:current --image-pull-policy=IfNotPresent

REPOSITORY                                                   TAG                         IMAGE ID       CREATED        SIZE
postgres                                                     12                          3d6880d04326   2 weeks ago    373MB
lh-develop.img                                               latest                      f26c3c667fbe   5 weeks ago    2.82GB
dpage/pgadmin4                                               latest                      4d5afde0a02e   6 weeks ago    361MB
detector                                                     latest                      e6f7e6567b73   7 weeks ago    3.81GB
lh-detetctor.img                                             latest                      e6f7e6567b73   7 weeks ago    3.81GB
registry.dev.mpksoft.ru/lighthouse/lh-detector/lh-detector   current                     e6f7e6567b73   7 weeks ago    3.81GB

Answer 1

如果您正在运行microK8s和 Docker，仍然需要microk8s来了解您机器上运行的 docker。 本地 Docker 守护进程不是MicroK8s Kube.netes 集群的一部分。

您可以导出图像并注入缓存

docker save <image name> > myimage.tar
microk8s ctr image import myimage.tar

参考：文件