support vpc configuration of multiple external network segments through label and crd

[zhaocongqi]

• Make sure you have followed Kube-OVN Code Style.

What type of this PR

Examples of user facing changes:

• Features

Which issue(s) this PR fixes:

Fixes #(issue-number)

WHAT

🤖 Generated by Copilot at 6ac6836

This pull request adds support for multiple external subnets for a VPC in the kubeovn API and controller. It modifies the VpcSpec and VpcStatus structs, the vpc.go and subnet.go files, and comments out the BFD and custom VPC static route features, which are incompatible with the new feature.

🤖 Generated by Copilot at 6ac6836

No more static routes, no more BFD
We unleash the power of multiple subnets
We reconcile the VPCs with a new spec
We handle the gateways with a new logic

HOW

🤖 Generated by Copilot at 6ac6836

• Add support for multiple external subnets for a VPC (link, link, link, link, link, link, link, link, link, link, link)
• Add a new field ExternalSubnets to the VpcSpec and VpcStatus structs in types.go to store the desired and actual external subnets for a VPC (link, link)
• Import the sort package in vpc.go to sort the external subnets in the handleAddOrUpdateVpc function (link)
• Modify the handleDelVpc function in vpc.go to loop over the external subnets in the VPC spec and call handleDelVpcExternalSubnets for each subnet (link)
• Modify the handleAddOrUpdateVpc function in vpc.go to check the external subnets in the VPC spec and status, and call handleAddVpcExternalSubnets or handleDelVpcExternalSubnets for each subnet that is added or removed (link)
• Rename the handleAddVpcExternal function in vpc.go to handleAddVpcExternalSubnets and add a parameter subnet to specify the external subnet to connect (link)
• Change the references to the c.config.ExternalGatewaySwitch to the subnet parameter in the handleAddVpcExternalSubnets function in vpc.go, and replace the logic to get the gateway chassis from the config map to the node labels (link)
• Change the call to c.acquireIPAddress and c.createOrUpdateCrdOvnEip in the handleAddVpcExternalSubnets function in vpc.go to use the subnet parameter instead of the c.config.ExternalGatewaySwitch (link)
• Change the call to c.OVNNbClient.CreateLogicalPatchPort in the handleAddVpcExternalSubnets function in vpc.go to use the subnet parameter instead of the c.config.ExternalGatewaySwitch, and the lspName and lrpName variables to use the subnet parameter instead of the c.config.ExternalGatewaySwitch (link)
• Append the external subnet to the vpc.Status.ExternalSubnets slice in the handleAddVpcExternalSubnets function in vpc.go if it is not already in the slice (link)
• Rename the handleDelVpcExternal function in vpc.go to handleDelVpcExternalSubnets and add a parameter subnet to specify the external subnet to disconnect (link)
• Change the references to the c.config.ExternalGatewaySwitch to the subnet parameter in the handleDelVpcExternalSubnets function in vpc.go, and the lspName and lrpName variables to use the subnet parameter instead of the c.config.ExternalGatewaySwitch (link)
• Remove the external subnet from the vpc.Status.ExternalSubnets slice in the handleDelVpcExternalSubnets function in vpc.go if it is in the slice (link)
• Comment out the call to reconcileCustomVpcStaticRoute in the reconcileSubnet function in subnet.go, which is used to reconcile the static routes for a custom VPC (link)
• Comment out the code related to the BFD feature in the handleAddOrUpdateVpc function in vpc.go, which is not compatible with the multiple external subnets feature (link)

[lelvisl]

@zcq98 this is a really cool feature! i'm waiting for merging this pr =)

let me know if i can help you.

[zbb88888]

hi @oilbeater , could you help review this ?