is there any option not to cache the image to the nodes but to a common place like a statefulet? so that any node needs the image can pull from the common cache instead of pulling from external registry.

senthilrch / kube-fledged

A kubernetes operator for creating and managing a cache of container images directly on the cluster worker nodes, so application pods start almost instantly

Apache License 2.0

1.26k stars 119 forks source link

is there any option not to cache the image to the nodes but to a common place like a statefulet? so that any node needs the image can pull from the common cache instead of pulling from external registry. #196

Closed sangamgo closed 1 year ago

roee-landesman commented 1 year ago

My understanding of Kubefledged is that it is purpose-built to cache the images on the cluster worker nodes directly in order to increase image pull times from the pods. If all the images were stored in a central repository then pods on nodes not co-scheduled with that repository would need to download the images across a network which defeats the purpose of the controller. That said, there are centralized self-hosted repositories such as Harbor that you may find useful.

senthilrch commented 1 year ago

Yes kube-fledged's purpose is to allow caching images directly on the worker nodes. There are other projects that support the use case mentioned by @sangamgo