Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CSI: periodic volume and plugin cleanup #7825

Closed
tgross opened this issue Apr 28, 2020 · 3 comments
Closed

CSI: periodic volume and plugin cleanup #7825

tgross opened this issue Apr 28, 2020 · 3 comments

Comments

@tgross
Copy link
Member

tgross commented Apr 28, 2020

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

@tgross
Copy link
Member Author

tgross commented May 1, 2020

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.

@tgross tgross self-assigned this May 5, 2020
@tgross
Copy link
Member Author

tgross commented May 11, 2020

Closed by #7878 and #7881

@tgross tgross closed this as completed May 11, 2020
@github-actions
Copy link

github-actions bot commented Nov 7, 2022

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 7, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant