A kubernetes operator for creating and managing a cache of container images directly on the cluster worker nodes, so application pods start almost instantly
Any reason for not using a daemon set with the cri-client image?
and have them work and react to a aggregated configmap with all the image caches?
This way we will eliminate alle jobs, CNI work, kubelet work, kubeproxy work, API work.
We will make sure that we just have an ongoing container on each worker node that will interact with the CRI.
We would also be able to batch process all images updates inside one container pr worker node.
Hey all,
Any reason for not using a daemon set with the cri-client image? and have them work and react to a aggregated configmap with all the image caches? This way we will eliminate alle jobs, CNI work, kubelet work, kubeproxy work, API work. We will make sure that we just have an ongoing container on each worker node that will interact with the CRI. We would also be able to batch process all images updates inside one container pr worker node.
is there something I dont see?