You need to enable JavaScript to run this app.
Volcengine Kubernetes Engine

Volcengine Kubernetes Engine

Copy page
Download PDF
FAQs
How do I avoid pulling images after using an image cache?
Copy page
Download PDF
How do I avoid pulling images after using an image cache?
Problem description​
After an image cache is used, you may still encounter situations where image pulling is required due to the following reasons:​
  • The image cache matches based on image tags. If you re-push an image with the same tag after creating the image cache, image pulling may be triggered.​
  • You are using the image cache by specifying its ID, but some pod images are not included in the image cache.​
  • You specify ImagePullPolicy: Always. In this case, even if the image is not updated, the system still needs to access the image repository to retrieve metadata such as the image manifest.​
Solution​
If you need to avoid accessing the image repository (for example, the image has been deleted or network issues prevent connection to the repository), you can set ImagePullPolicy to IfNotPresent or Never, and disable the AlwaysPullImages admission controller of the cluster. For detailed steps, see the following:​
Last updated: 2026.07.24 16:18:05