spiderpool
spiderpool copied to clipboard
Published
20 hours ago •
spidernet-io
spidernet-io
subnet and ippool confliction
subnet feature is on when two subnet with conflicted subnet are creating or updating at the same time, the two webhook gorouting may fail to check the conflicted IP before both ippool are accepted by the api-server
cause the use case to fail
NAME VERSION SUBNET ALLOCATED-IP-COUNT TOTAL-IP-COUNT
default-v4-subnet 4 172.18.0.0/16 253 253
default-v6-subnet 6 fc00:f853:ccd:e793::/64 253 253
v4-ss-100-356-273420520 4 10.182.173.0/24 0 200
v4-ss-100-73-696162417 4 10.111.121.0/24 0 200
v4-ss-26-73-692975424 4 10.111.121.0/24 0 200
v4-ss-3-73-689402168 4 10.111.121.0/24 0 200
v4-ss-4-04-95342108 4 10.49.68.0/24 0 200
v4-ss-46-04-108741401 4 10.49.68.0/24 0 200
v4-ss-46-73-693888566 4 10.111.121.0/24 0 200
v4-ss-61-04-114741617 4 10.49.68.0/24 0 200
v4-ss-70-04-114972078 4 10.49.68.0/24 0 200
v4-ss-98-04-93407213 4 10.49.68.0/24 0 200
v6-ss-100-356-273428797 6 fd00:49f1::/120 0 200
v6-ss-100-73-696176808 6 fd00:b8b6::/120 0 200
v6-ss-4-04-512937597 6 fd00:7399::/120 0 200
v6-ss-46-04-536719944 6 fd00:7399::/120 0 200
The scenario where this problem occurs is: when two subnets or multiple subnets are created at the same time (concurrency scenario), resources in the same subnet range will be created, which is unexpected.
There is a corresponding e2e, but it is pending.
