kubernetes/pkg/controller/nodeipam
Sarvesh Rangnekar 02d944d046 Add a priority queue to implement MultiCIDR tie-breaks
The Priority is determined as follows:
P0: ClusterCIDR with higher number of matching labels has highest
priority.
P1: ClusterCIDR having cidrSet with fewer allocatable Pod CIDRs has
higher priority.
P2: ClusterCIDR with a PerNodeMaskSize having fewer IPs has higher
priority.
P3: ClusterCIDR having label with lower alphanumeric value has higher
priority.
P4: ClusterCIDR with a cidrSet having a smaller IP address value has
higher priority.
2022-08-05 01:06:43 +00:00
..
config OWNERS cleanup - Jan 2021 Week 1 2022-01-10 08:14:29 -05:00
ipam Add a priority queue to implement MultiCIDR tie-breaks 2022-08-05 01:06:43 +00:00
doc.go
legacyprovider.go generated: Run hack/update-gofmt.sh 2021-08-24 15:47:49 -04:00
node_ipam_controller_test.go generated: Run hack/update-gofmt.sh 2021-08-24 15:47:49 -04:00
node_ipam_controller.go Enable 'running_managed_controllers' for KCM nodeipam controller 2022-07-27 14:30:40 +00:00
nolegacyprovider.go generated: Run hack/update-gofmt.sh 2021-08-24 15:47:49 -04:00
OWNERS Cleanup OWNERS files (No Activity in the last year) 2021-12-15 10:34:02 -05:00