importer-prime fetching the docker image every time.

[cybercoder]

The pod:

      image: quay.io/kubevirt/cdi-importer:v1.60.3
      imagePullPolicy: IfNotPresent

But it seems it getting deleted after a success.

 Normal   Pulling                 99s   kubelet                  Pulling image "quay.io/kubevirt/cdi-importer:v1.60.3"

And the node has enough disk space and there's no disk pressure:

/dev/mapper/ubuntu--vg-ubuntu--lv   30G   13G   16G  47% /

There's image when importer prime working (inevitable):

sudo ctr --namespace k8s.io images ls | grep cdi-import

quay.io/kubevirt/cdi-importer:v1.60.3                                                                                          application/vnd.docker.distribution.manifest.v2+json      sha256:14de12bf71e7050d5abaf96176da8f09f3d689a1e6f44958b17216dc6bf8a9a7 120.0 MiB linux/amd64                                                                              io.cri-containerd.image=managed
quay.io/kubevirt/cdi-importer@sha256:14de12bf71e7050d5abaf96176da8f09f3d689a1e6f44958b17216dc6bf8a9a7                          application/vnd.docker.distribution.manifest.v2+json      sha256:14de12bf71e7050d5abaf96176da8f09f3d689a1e6f44958b17216dc6bf8a9a7 120.0 MiB linux/amd64

But it disapears after the pod complete or error and destroy.

Environment:

• CDI version: v1.60.3

[awels]

So CDI doesn't influence the behavior of kubernetes. As you can see we set the policy to IfNotPresent, and it downloads the image if it is not present. But what kubernetes does afterwards we as CDI cannot influence.

[kubevirt-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[kubevirt-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

[kubevirt-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

[kubevirt-bot]

@kubevirt-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.