uddate proposal with podGroup crd update

Signed-off-by: LiZhenCheng9527 <lizhencheng6@huawei.com>

Author: LiZhenCheng9527

docs/proposal/network-topology.md

@@ -125,8 +125,11 @@ spec:
     - subGroupSize: 3
       minSubGroups: 2
       name: task
-      matchPolicy:
-        - labelKey: volcano.sh/task-subgroup-id
+      labelSelector:
+        modelserving.volcano.sh/name: sample
+        modelserving.volcano.sh/role: prefill
+      matchLabelKeys:
+        modelserving.volcano.sh/role-id
       networkTopology:
         mode: hard 
         highestTierAllowed: 1
@@ -136,7 +139,7 @@ A `subGroupPolicy` has been added to the `podGroup` to ensure task-level gang sc
 
 - `subGroupSize`: The number of pods in a subGroup.
 - `minSubGroups`: The minimum replicas of subGroups.
-- `matchPolicy`: The label key used to match pods.
+- `matchLabelKeys`: The label key used to match pods.
 - `networkTopology`: The network topology of a subGroup.
 
 This YAML specifies that the PodGroup requires six pods to be deployed together, and all six pods must be scheduled on nodes with a maximum network topology distance of 2. Among these, the six pods are divided into two subGroups of three based on the value of the `volcano.sh/task-subgroup-id` label, and each group must be strictly scheduled on nodes with a network topology distance of 1.
@@ -169,9 +172,11 @@ spec:
   minResources:
   subGroupPolicy: 
     - name: network-topology
-      matchPolicy:
-        - labelKey: "modelserving.volcano.sh/role"
-        - labelKey: "modelserving.volcano.sh/role-id"
+      labelSelector:
+        modelserving.volcano.sh/name: sample
+        modelserving.volcano.sh/role: prefill
+      matchLabelKeys:
+        modelserving.volcano.sh/role-id
       networkTopology:
         mode: hard 
         highestTierAllowed: 1