Update the global ip pool

Signed-off-by: Jian Wang <jian.wang@suse.com>

Author: w13915984028

docs/networking/ippool.md

@@ -31,7 +31,7 @@ To create a new IP pool:
 1. Specify the **Name** of the IP pool.
 1. Go to the **Range** tab to specify the **IP ranges** for the IP pool. You can add multiple IP ranges.
    ![](/img/v1.2/networking/multiple-ranges.png)
-1. Go to the **Selector** tab to specify the **Scope** and **Priority** of the IP pool.
+1. Go to the **Selector** tab to specify the **Selector**, **Scope** and **Priority** of the IP pool.
    ![](/img/v1.2/networking/ippool-scope.png)
 
 When you operate from the Harvester UI, the `Scope` only includes `Namespace`. Click `Add Scope` to add new items.
@@ -47,17 +47,18 @@ The `Scope` includes `Project`, `Namespace` and `Guest Kubernetes Cluster`. For
 When a pool has only one `Scope` and each selects `All`, then this IP Pool is marked as `global` automatically.
 
 ## Selection policy
+
 Each IP pool will have a specific range, and you can specify the corresponding requirements in the LB `annotations`. IP pools that meet the specified requirements will automatically assign IP addresses to LBs.
 
 - LBs utilize the following annotations to express requirements (all annotations are optional):
-  - `loadbalancer.harvesterhci.io/network` specifies the VM network the guest cluster nodes use.
+  - `loadbalancer.harvesterhci.io/network` specifies the VM network the guest cluster nodes use, if it is not carried, the mutator selects the first multus network from the virtual machine instances of the the guest cluster.
   - `loadbalancer.harvesterhci.io/project` and `loadbalancer.harvesterhci.io/namespace` identify the project and namespace of the VMs that comprise the guest cluster.
   - `loadbalancer.harvesterhci.io/cluster` denotes the name of the guest cluster.
 - The IP pool has a selector, including network and scope, to match the requirements of the LB.
-  - Network is a hard condition. The optional IP pool must match the value of the LB annotation `loadbalancer.harvesterhci.io/network`.
+  - Network is a **hard condition**. The optional IP pool must match the value of the LB annotation `loadbalancer.harvesterhci.io/network`.
   - Every IP pool, except the global IP pool, has a unique scope different from others if its priority is `0`. The project, namespace, or cluster name of LBs should be in the scope of the IP pool if they want to get an IP from this pool.
 - `spec.selector.priority` specifies the priority of the IP Pool. The larger the number, the higher the priority. If the priority is not `0`, the value should differ. The priority helps you to migrate the old IP pool to the new one.
-- If the IP Pool has a scope that matches all projects, namespaces, and guest clusters, it's called a global IP pool, and only one global IP pool is allowed. If there is no IP pool matching the requirements of the LB, the IPAM will allocate an IP address from the global IP pool if it exists.
+- If the IP Pool has a scope that matches all projects, namespaces, and guest clusters, it's called a global IP pool, and only one global IP pool is allowed under one **Network**. If there is no IP pool matching the requirements of the LB, the IPAM will allocate an IP address from the global IP pool if it exists and matches the **Network**.
 
 ### Examples
 - **Example 1:** You wish to set up an IP pool within the range `192.168.100.0/24` for the `default` namespace. In this scenario, all load balancers within the `default` namespace will receive an IP address from this designated IP pool:
@@ -120,11 +121,12 @@ Each IP pool will have a specific range, and you can specify the corresponding r
   metadata:
     name: global-ip-pool
   labels:
-    loadbalancer.harvesterhci.io/global-ip-pool: 'true' # Added by the controller automatically
+    loadbalancer.harvesterhci.io/global-ip-pool: 'true' # Added by the mutator automatically
   spec:
     ranges:
     - subnet: 192.168.20.0/24
     selector:
+      network: default/vlan1
       scope:
       - project: "*"
         namespace: "*"
@@ -149,3 +151,4 @@ Each IP pool will have a specific range, and you can specify the corresponding r
 
 1. Be careful when creating global IP pool as one guest cluster might allocate too many IPs and starve other clusters. The pool can't be deleted if any of the IPs is still in use.
 
+1. If an IP pool has empty `.spec.selector.network`, it will not be selected after v1.9.0 version.