kube-fledged icon indicating copy to clipboard operation
kube-fledged copied to clipboard

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

Results 42 kube-fledged issues
Sort by recently updated
recently updated
newest added

In AWS EKS, we intensively use auto scaling clusters. It would be handy if the controller knows when a new node is spin up and directly starts to cache the...

Bumps [github.com/docker/docker](https://github.com/docker/docker) from 20.10.20+incompatible to 20.10.24+incompatible. Release notes Sourced from github.com/docker/docker's releases. v20.10.24 20.10.24 Bug fixes and enhancements Fixed a number of issues that can cause Swarm encrypted overlay networks...

dependencies

My use case involves initializing an ImageCache resource out of band, and then having a separate service dynamically add and remove images from the cache. As part of this, I...

Hi there! I'm currently looking at using kube-fledged, but am concerned that a large image cache may eat up an unreasonable amount of disk space on the nodes. Is the...

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...

question

Hi! We want to cache images to nodes where only pods can be scheduled. It would be better if `ImageCache` CR support node affinity and tolerations just as pods do....

The syncHandler() method of the controller is where the controller reconciles the desired state of ImageCache with actual state. The syncHandler, before starting the reconciliation, updates the status of ImageCache...

enhancement
done

Whilst experimenting with kube-fledged we added and destroyed a number of nodes in our test cluster, and a handful of pods got stuck. Kube-fledged logged an error reporting that a...

bug
done

There seems to be an issue with the rendered yaml when setting `controller.hostNetwork=true`. The spec: and hostNetwork: keys end up on the same line and helm fails to process it...

bug
done

image cache failing-No images were pulled or deleted because nodeSelector specified did not match any nodes when trying without node selector. It is failing even when we add correct node...