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
Configuration and Troubleshooting- Cache not being used #219
I'm trying to use kube-fledged on a Talos-based (v1.4.7) cluster that hosts a Github Actions Runner Controller. The Talos nodes are using containerd 1.6.21.
The Github action running under ARC pulls and runs an image via docker-compose.
The docker image is being cached by kube-fledged, but I can't seem to get the workers to pull the image from the cache. I don't know if there's additional configuration that's needed beyond what's described on the main page, nor do I even know how to troubleshoot the problem (other than verifying from the logs that the image is being cached).
I'm trying to use kube-fledged on a Talos-based (v1.4.7) cluster that hosts a Github Actions Runner Controller. The Talos nodes are using containerd 1.6.21.
The Github action running under ARC pulls and runs an image via docker-compose.
The docker image is being cached by kube-fledged, but I can't seem to get the workers to pull the image from the cache. I don't know if there's additional configuration that's needed beyond what's described on the main page, nor do I even know how to troubleshoot the problem (other than verifying from the logs that the image is being cached).