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
While volume claims have been moved into a volumewatcher, we don't have any GC mechanism for volumes themselves or for CSI plugins. Create a periodic job similar to the existing job GC that splits the work out among many separate GC evals. (This will also help in cases where there are bugs with plugin cleanup.)
The text was updated successfully, but these errors were encountered:
A design note on this: we don't want to GC volumes, as they're persistent data. But we should GC periodically GC all their claims (for nil allocs) and the plugins that don't have plugin jobs or registered volumes.
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Pulled out of #7794.
While volume claims have been moved into a volumewatcher, we don't have any GC mechanism for volumes themselves or for CSI plugins. Create a periodic job similar to the existing job GC that splits the work out among many separate GC evals. (This will also help in cases where there are bugs with plugin cleanup.)
The text was updated successfully, but these errors were encountered: