Daman Arora fcb595a2df service-ip-alloc: delay ip processing on service recreate ...

Service storage implements transactions. It creates an IPAddress object first and then creates
the Service object, and if the Service object already exists the complete transaction is
reverted. There can be race conditions when the repair loop picks up the new IPAddress object
for reconciliation before the transaction is reverted. This leads to spurious
IPAddressWrongReference warnings, to suppress these warnings we delay the processing of the new
IPAddress object by 5 seconds. The service allocation creates the IPAddress object before creating
the Service object, we easily identify this scenario when the IPAddress object creation timestamp
is after the Service creation timestamp. We do this only when the IPAddress object is created
recently in order to avoid indefinitely requeue/delay in IPAddress cleanup if for some reason
the service transaction revert fails.

Signed-off-by: Daman Arora <aroradaman@gmail.com>

2025-07-14 00:31:53 +05:30

..

controller

service-ip-alloc: delay ip processing on service recreate

2025-07-14 00:31:53 +05:30

storage

…

bitmap_test.go

…

bitmap.go

…

cidrallocator_test.go

modify unit test for compatibility version

2025-05-06 13:29:55 +00:00

cidrallocator.go

cluster ip allocator should check first on the legacy allocators

2025-01-24 15:48:52 +00:00

interfaces.go

…

ipallocator_test.go

update registry

2025-01-20 13:01:53 +00:00

ipallocator.go

update registry

2025-01-20 13:01:53 +00:00

metrics.go

add new metric to record the latency to allocate an IP address

2024-06-27 11:33:35 +00:00