Antonio Ojea d3e8572d70 cluster ip allocator should check first on the legacy allocators ...

Kubernetes clusters allow to define an IPv6 range of /108 for IPv6
despite the old allocators will only use the first /112 of that range.

The new allocators does not have this limitation, so they can allocate
IPs on the whole space, the problem happens on upgrades from clusters
that were already using this size, since the new allocators by default
will try to allocate addresses that works for both new and old allocatos
to allow safe upgrades.

The new allocators, when configured to keep compatibility with the old
allocators, must try first to allocate an IP that is compatible with the
old allocators and only fall back to the new behavior if it is not
possible.

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

..

dualstack_endpoints_test.go

kube-controller-manager: readjust log verbosity

2024-02-26 14:51:56 +08:00

dualstack_test.go

cluster ip allocator should check first on the legacy allocators

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

main_test.go

…