You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 controller aware of disk space constraints, or is it possible for image pulls instigated by the ImageCache resource to cause pod evictions due to low disk space? If so, I was thinking it could be a good approach to add one of the following options to the cacheSpec:
A field for limiting the aggregate size of all images comprising the cacheSpec, or
A field which prevents image pulls if node disk space drops below the configurable threshold (this would be evaluated on a per-node basis)
I could try taking a stab at this if pointed in the right direction, but wanted to confirm that this feature makes sense first.
The text was updated successfully, but these errors were encountered:
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 controller aware of disk space constraints, or is it possible for image pulls instigated by the ImageCache resource to cause pod evictions due to low disk space? If so, I was thinking it could be a good approach to add one of the following options to the
cacheSpec
:cacheSpec
, orI could try taking a stab at this if pointed in the right direction, but wanted to confirm that this feature makes sense first.
The text was updated successfully, but these errors were encountered: