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

Remove stale pool entries from the store #25

Closed
ykulazhenkov opened this issue Aug 4, 2023 · 0 comments · Fixed by #26
Closed

Remove stale pool entries from the store #25

ykulazhenkov opened this issue Aug 4, 2023 · 0 comments · Fixed by #26
Assignees
Labels
enhancement New feature or request

Comments

@ykulazhenkov
Copy link
Collaborator

The current implementation keeps pool entry in the store even if the pool has no active IP allocations. This is needed to preserve information about the latest allocated IP address. We need this info to support round-robin IP address allocation for use-case when the pool has few users on the node. The downside of the current implementation is that we may have a lot of stale pool entries in the store.
The proposed solution is to remove stale pool entries from the store within the cleaner loop (which cleans stale IP address allocations). The logic is quite simple: we need to remove the pool data from the store if the pool has no allocations and if information about the pool is unavailable in the Kubernetes API.

@ykulazhenkov ykulazhenkov added the enhancement New feature or request label Aug 4, 2023
@ykulazhenkov ykulazhenkov self-assigned this Aug 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant