-
Notifications
You must be signed in to change notification settings - Fork 7
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
lbaas-controller leaks floating IP addresses #28
Comments
expektorans
pushed a commit
to expektorans/ch-k8s-lbaas
that referenced
this issue
Jun 8, 2022
This commit fixes the collection of ports by storing the actual item instead of the address of the loop variable in the list. An example, because I find pointers confusing: Let's say our actual ports are [1, 2, 3]. Previously, GetPorts returned [3, 3, 3], and now we receive (as expected) [1, 2, 3]. I stumbled over this problem while applying force to lbaas by having a script create and delete services at random intervals as well as manually deleting the lbaas and the workload pod. This should resolve the resource leaks observed in cloudandheat#28. If we're lucky this might also help with lbaas eating FIPs.
expektorans
changed the title
lbaas-controller leaks floating IP addresses (Draft)
lbaas-controller leaks floating IP addresses
Jun 8, 2022
This is my hack-ish stress script which wasn't cleaned up in any way.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've put lbaas under a bit of stress and could observe that it started to "leak" FIPs. "Leak" is here defined as "floating IPs that are allocated by lbaas to an OS project but are no longer actively used by it"
The text was updated successfully, but these errors were encountered: