Epic Goal

Address performance and scale issues in Whereabouts IPAM CNI

Why is this important?

Whereabouts is becoming increasingly more popular for use on workloads that operate at scale. Whereabouts was originally built as a convenience function for a handful of IPs, however, more and more customers want to use whereabouts in scale sitatuions.

Notably, for telco and ai/ml scenarios. Some ai/ml scenarios launch a large number of pods that need to use secondary networks for related traffic.

Supporting Documents

Upstream collaboration outline

Acceptance Criteria

• Both original allocation mode, and fast_ranges mode work without user intervention (e.g. backwards compatible)
• Reconciler still works with fast_ranges
• fast_ranges: 50% reduction in allocation time over original allocation method