Suppport extra CIDRs in IPv4_POOLS

[ctenberge-oneid]

My clusters are usually EKS, but due to issues with CIDR overlap we use Cilium to manage both Service and Pod CIDRs (192.168.0.0/24 and 172.16.0.0/12 respectively) yet my VPC CIDR is 10.0.0.0/24. I would like to be able to route to RDS endpoints in my VPC through my kubevpn connection, this is needed for my apps to access the DB.
I think the solution would be adding my VPC CIDR to the IPv4_POOLS.

[wencaiwulue]

@ctenberge-oneid Yes, of course support.
you can reference this issue #283

• use option --extra-cidr add custom cidr to route table, we can access those cidr network on local PC via k8s network

    --extra-cidr=[]:
	Extra cidr string, add those cidr network to route table, eg:
	--extra-cidr 192.168.0.159/24 --extra-cidr 192.168.1.160/32

• use k8s network to resolve domain dns and then add ip to route table, we can access extra-domain on local PC via k8s network

    --extra-domain=[]:
	Extra domain string, the resolved ip will add to route table, eg:
	--extra-domain test.abc.com --extra-domain foo.test.com

• add node ip to route table, we can access nodeIP on local PC via k8s network

    --extra-node-ip=false:
	Extra node ip, add cluster node ip to route table.