mirror of
https://github.com/k3s-io/kubernetes.git
synced 2025-12-02 19:49:13 +00:00
b276b4775f
The test suite was using a /24 cluster network for the allocator. The ip allocator, if no ip is specified when creating the cluster, picks one randomly, that means that we had 1/256 chances of collision. The TestServiceRegistryUpdateDryRun was creating a service without a ClusterIP, the ip allocator assigned one random, and it was never deleting it. The same test was checking later if one specific IP was not allocated, not taking into consideration that the same ip may have allocated to the first Service. To avoid any randomness, we create the first Service with a specific IP address.