From 5cefd2c61caf561ebbff8e8023bc830b188c40b3 Mon Sep 17 00:00:00 2001 From: qiankunli Date: Wed, 13 Jul 2022 10:32:21 +0800 Subject: [PATCH] add details Signed-off-by: qiankunli --- docs/design/node-group.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/design/node-group.md b/docs/design/node-group.md index 1597cecca8..fad4125513 100644 --- a/docs/design/node-group.md +++ b/docs/design/node-group.md @@ -12,7 +12,7 @@ case2: recommend queue can use private cloud nodes or public cloud nodes, but tt ## Solution -1. First, we need mark out some nodes(by add specific label for nodes) which are the same group. +1. First, we need mark out some nodes(add `volcano.sh/nodegroup-name` labels) which are the same group. 2. Second, we need to express the relationship between queue and nodegroup, such as affinity and anti-affinity, so I add the `queue.spec.affinity` field in Queue. ```yaml apiVersion: scheduling.volcano.sh/v1beta1 @@ -27,13 +27,13 @@ case2: recommend queue can use private cloud nodes or public cloud nodes, but tt requiredDuringSchedulingIgnoredDuringExecution: - groupname1 - gropuname2 - preferredDuringSchedulingIgnoredDuringExecution + preferredDuringSchedulingIgnoredDuringExecution: - groupname1 nodeGroupAntiAffinity: requiredDuringSchedulingIgnoredDuringExecution: - groupname3 - gropuname4 - preferredDuringSchedulingIgnoredDuringExecution + preferredDuringSchedulingIgnoredDuringExecution: - groupname3 ```