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
Is your feature request related to a problem? Please describe.
Follow-up item for: #521
Main problem is, that Proxies who are in charge of IP allocation/release might disappear abruptly and along with it so can NSM connections they hosted providing no second chance to release the allocated IPs. (Same can happen during planned termination of Proxy if IPAM POD is not available.)
There should be an option to lease IPs for a certain amount of time. This could secure that IP allocations are not leaked.
For this, the db model should be extended to support expiration time like features.
NSM connections are refreshed periodically. During each refresh the IP allocation is verified, which could be used to update the db entry in IPAM. A garbage collector could be introduced to reap db entries with lifetime who haven't prolonged their leases and thus expired.
Upon upgrade, the new IPAM instance should migrate the existing database to introduce expiration time support for old db entries that belong to NSM connections. (Obviously rollback could result in serious disturbances.)
Describe the solution you'd like
See above.
Describe alternatives you've considered
NA
Additional context
NA
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Follow-up item for: #521
Main problem is, that Proxies who are in charge of IP allocation/release might disappear abruptly and along with it so can NSM connections they hosted providing no second chance to release the allocated IPs. (Same can happen during planned termination of Proxy if IPAM POD is not available.)
There should be an option to lease IPs for a certain amount of time. This could secure that IP allocations are not leaked.
For this, the db model should be extended to support expiration time like features.
NSM connections are refreshed periodically. During each refresh the IP allocation is verified, which could be used to update the db entry in IPAM. A garbage collector could be introduced to reap db entries with lifetime who haven't prolonged their leases and thus expired.
Upon upgrade, the new IPAM instance should migrate the existing database to introduce expiration time support for old db entries that belong to NSM connections. (Obviously rollback could result in serious disturbances.)
Describe the solution you'd like
See above.
Describe alternatives you've considered
NA
Additional context
NA
The text was updated successfully, but these errors were encountered: