From 02bc93a15eaeba708643d99cb2ffd9a491dd909c Mon Sep 17 00:00:00 2001 From: ls-2018 Date: Thu, 14 Sep 2023 10:08:10 +0800 Subject: [PATCH] [FIX] workloadspread yaml format error (#134) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: 刘硕 Co-authored-by: 刘硕 --- docs/user-manuals/workloadspread.md | 18 +++++------ .../current/user-manuals/workloadspread.md | 18 +++++------ .../user-manuals/workloadspread.md | 28 ++++++++--------- .../user-manuals/workloadspread.md | 28 ++++++++--------- .../user-manuals/workloadspread.md | 28 ++++++++--------- .../user-manuals/workloadspread.md | 28 ++++++++--------- .../user-manuals/workloadspread.md | 28 ++++++++--------- .../user-manuals/workloadspread.md | 28 ++++++++--------- .../user-manuals/workloadspread.md | 18 +++++------ .../user-manuals/workloadspread.md | 30 +++++++++---------- .../user-manuals/workloadspread.md | 30 +++++++++---------- .../user-manuals/workloadspread.md | 30 +++++++++---------- .../user-manuals/workloadspread.md | 30 +++++++++---------- .../user-manuals/workloadspread.md | 30 +++++++++---------- .../user-manuals/workloadspread.md | 30 +++++++++---------- .../user-manuals/workloadspread.md | 18 +++++------ 16 files changed, 210 insertions(+), 210 deletions(-) diff --git a/docs/user-manuals/workloadspread.md b/docs/user-manuals/workloadspread.md index 99ba5df75..fec618b2a 100644 --- a/docs/user-manuals/workloadspread.md +++ b/docs/user-manuals/workloadspread.md @@ -49,16 +49,16 @@ spec: operator: In values: - zone-a - preferredNodeSelectorTerms: - - weight: 1 - preference: - matchExpressions: - - key: another-node-label-key - operator: In - values: - - another-node-label-value + preferredNodeSelectorTerms: + - weight: 1 + preference: + matchExpressions: + - key: another-node-label-key + operator: In + values: + - another-node-label-value maxReplicas: 3 - tolertions: [] + tolerations: [ ] patch: metadata: labels: diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-manuals/workloadspread.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-manuals/workloadspread.md index 6aa3f4086..335cba186 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/user-manuals/workloadspread.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/user-manuals/workloadspread.md @@ -48,16 +48,16 @@ spec: operator: In values: - zone-a - preferredNodeSelectorTerms: - - weight: 1 - preference: - matchExpressions: - - key: another-node-label-key - operator: In - values: - - another-node-label-value + preferredNodeSelectorTerms: + - weight: 1 + preference: + matchExpressions: + - key: another-node-label-key + operator: In + values: + - another-node-label-value maxReplicas: 3 - tolertions: [] + tolerations: [ ] patch: metadata: labels: diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-v0.10/user-manuals/workloadspread.md b/i18n/zh/docusaurus-plugin-content-docs/version-v0.10/user-manuals/workloadspread.md index e27771954..3ef2af4d5 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-v0.10/user-manuals/workloadspread.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-v0.10/user-manuals/workloadspread.md @@ -42,16 +42,16 @@ spec: operator: In values: - zone-a - preferredNodeSelectorTerms: - - weight: 1 - preference: - matchExpressions: - - key: another-node-label-key - operator: In - values: - - another-node-label-value + preferredNodeSelectorTerms: + - weight: 1 + preference: + matchExpressions: + - key: another-node-label-key + operator: In + values: + - another-node-label-value maxReplicas: 3 - tolertions: [] + tolerations: [ ] patch: metadata: labels: @@ -78,12 +78,12 @@ spec: ### sub-fields - `name`: subset的名称，在同一个WorkloadSpread下name唯一，代表一个topology区域。 - + - `maxReplicas`：该subset所期望调度的最大副本数，需为 >= 0的整数。若设置为空，代表不限制subset的副本数。 > 当前版本暂不支持百分比类型。 - `requiredNodeSelectorTerm`: 强制匹配到某个zone。 - + - `preferredNodeSelectorTerms`: 尽量匹配到某个zone。 **注意**：requiredNodeSelectorTerm对应k8s nodeAffinity的requiredDuringSchedulingIgnoredDuringExecution。 @@ -144,10 +144,10 @@ WorkloadSpread提供了两种调度策略，默认为`Fixed`: rescheduleCriticalSeconds: 30 ``` -- Fixed: +- Fixed: workload严格按照`subsets`定义分布。 - + - Adaptive: **Reschedule**：Kruise检查`subset`中调度失败的Pod，若超过用户定义的时间就将其调度到其他有可用的`subset`上。 @@ -178,7 +178,7 @@ WorkloadSpread所管理的workload会按照`subsets`中定义的顺序扩缩容 ### 扩容 - 按照`spec.subsets`中`subset`定义的顺序调度Pod，当前`subset`的active Pod数量达到`maxReplicas`时再调度到下一个`subset`。 - + ### 缩容 - 当`subset`的副本数(active)大于定义的maxReplicas时，优先缩容多余的Pod。 - 依据`spec.subsets`中`subset`定义的顺序，后面`subset`的Pod先于前面的被删除。 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-v1.0/user-manuals/workloadspread.md b/i18n/zh/docusaurus-plugin-content-docs/version-v1.0/user-manuals/workloadspread.md index e27771954..3ef2af4d5 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-v1.0/user-manuals/workloadspread.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-v1.0/user-manuals/workloadspread.md @@ -42,16 +42,16 @@ spec: operator: In values: - zone-a - preferredNodeSelectorTerms: - - weight: 1 - preference: - matchExpressions: - - key: another-node-label-key - operator: In - values: - - another-node-label-value + preferredNodeSelectorTerms: + - weight: 1 + preference: + matchExpressions: + - key: another-node-label-key + operator: In + values: + - another-node-label-value maxReplicas: 3 - tolertions: [] + tolerations: [ ] patch: metadata: labels: @@ -78,12 +78,12 @@ spec: ### sub-fields - `name`: subset的名称，在同一个WorkloadSpread下name唯一，代表一个topology区域。 - + - `maxReplicas`：该subset所期望调度的最大副本数，需为 >= 0的整数。若设置为空，代表不限制subset的副本数。 > 当前版本暂不支持百分比类型。 - `requiredNodeSelectorTerm`: 强制匹配到某个zone。 - + - `preferredNodeSelectorTerms`: 尽量匹配到某个zone。 **注意**：requiredNodeSelectorTerm对应k8s nodeAffinity的requiredDuringSchedulingIgnoredDuringExecution。 @@ -144,10 +144,10 @@ WorkloadSpread提供了两种调度策略，默认为`Fixed`: rescheduleCriticalSeconds: 30 ``` -- Fixed: +- Fixed: workload严格按照`subsets`定义分布。 - + - Adaptive: **Reschedule**：Kruise检查`subset`中调度失败的Pod，若超过用户定义的时间就将其调度到其他有可用的`subset`上。 @@ -178,7 +178,7 @@ WorkloadSpread所管理的workload会按照`subsets`中定义的顺序扩缩容 ### 扩容 - 按照`spec.subsets`中`subset`定义的顺序调度Pod，当前`subset`的active Pod数量达到`maxReplicas`时再调度到下一个`subset`。 - + ### 缩容 - 当`subset`的副本数(active)大于定义的maxReplicas时，优先缩容多余的Pod。 - 依据`spec.subsets`中`subset`定义的顺序，后面`subset`的Pod先于前面的被删除。 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-v1.1/user-manuals/workloadspread.md b/i18n/zh/docusaurus-plugin-content-docs/version-v1.1/user-manuals/workloadspread.md index e27771954..3ef2af4d5 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-v1.1/user-manuals/workloadspread.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-v1.1/user-manuals/workloadspread.md @@ -42,16 +42,16 @@ spec: operator: In values: - zone-a - preferredNodeSelectorTerms: - - weight: 1 - preference: - matchExpressions: - - key: another-node-label-key - operator: In - values: - - another-node-label-value + preferredNodeSelectorTerms: + - weight: 1 + preference: + matchExpressions: + - key: another-node-label-key + operator: In + values: + - another-node-label-value maxReplicas: 3 - tolertions: [] + tolerations: [ ] patch: metadata: labels: @@ -78,12 +78,12 @@ spec: ### sub-fields - `name`: subset的名称，在同一个WorkloadSpread下name唯一，代表一个topology区域。 - + - `maxReplicas`：该subset所期望调度的最大副本数，需为 >= 0的整数。若设置为空，代表不限制subset的副本数。 > 当前版本暂不支持百分比类型。 - `requiredNodeSelectorTerm`: 强制匹配到某个zone。 - + - `preferredNodeSelectorTerms`: 尽量匹配到某个zone。 **注意**：requiredNodeSelectorTerm对应k8s nodeAffinity的requiredDuringSchedulingIgnoredDuringExecution。 @@ -144,10 +144,10 @@ WorkloadSpread提供了两种调度策略，默认为`Fixed`: rescheduleCriticalSeconds: 30 ``` -- Fixed: +- Fixed: workload严格按照`subsets`定义分布。 - + - Adaptive: **Reschedule**：Kruise检查`subset`中调度失败的Pod，若超过用户定义的时间就将其调度到其他有可用的`subset`上。 @@ -178,7 +178,7 @@ WorkloadSpread所管理的workload会按照`subsets`中定义的顺序扩缩容 ### 扩容 - 按照`spec.subsets`中`subset`定义的顺序调度Pod，当前`subset`的active Pod数量达到`maxReplicas`时再调度到下一个`subset`。 - + ### 缩容 - 当`subset`的副本数(active)大于定义的maxReplicas时，优先缩容多余的Pod。 - 依据`spec.subsets`中`subset`定义的顺序，后面`subset`的Pod先于前面的被删除。 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-v1.2/user-manuals/workloadspread.md b/i18n/zh/docusaurus-plugin-content-docs/version-v1.2/user-manuals/workloadspread.md index e27771954..3ef2af4d5 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-v1.2/user-manuals/workloadspread.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-v1.2/user-manuals/workloadspread.md @@ -42,16 +42,16 @@ spec: operator: In values: - zone-a - preferredNodeSelectorTerms: - - weight: 1 - preference: - matchExpressions: - - key: another-node-label-key - operator: In - values: - - another-node-label-value + preferredNodeSelectorTerms: + - weight: 1 + preference: + matchExpressions: + - key: another-node-label-key + operator: In + values: + - another-node-label-value maxReplicas: 3 - tolertions: [] + tolerations: [ ] patch: metadata: labels: @@ -78,12 +78,12 @@ spec: ### sub-fields - `name`: subset的名称，在同一个WorkloadSpread下name唯一，代表一个topology区域。 - + - `maxReplicas`：该subset所期望调度的最大副本数，需为 >= 0的整数。若设置为空，代表不限制subset的副本数。 > 当前版本暂不支持百分比类型。 - `requiredNodeSelectorTerm`: 强制匹配到某个zone。 - + - `preferredNodeSelectorTerms`: 尽量匹配到某个zone。 **注意**：requiredNodeSelectorTerm对应k8s nodeAffinity的requiredDuringSchedulingIgnoredDuringExecution。 @@ -144,10 +144,10 @@ WorkloadSpread提供了两种调度策略，默认为`Fixed`: rescheduleCriticalSeconds: 30 ``` -- Fixed: +- Fixed: workload严格按照`subsets`定义分布。 - + - Adaptive: **Reschedule**：Kruise检查`subset`中调度失败的Pod，若超过用户定义的时间就将其调度到其他有可用的`subset`上。 @@ -178,7 +178,7 @@ WorkloadSpread所管理的workload会按照`subsets`中定义的顺序扩缩容 ### 扩容 - 按照`spec.subsets`中`subset`定义的顺序调度Pod，当前`subset`的active Pod数量达到`maxReplicas`时再调度到下一个`subset`。 - + ### 缩容 - 当`subset`的副本数(active)大于定义的maxReplicas时，优先缩容多余的Pod。 - 依据`spec.subsets`中`subset`定义的顺序，后面`subset`的Pod先于前面的被删除。 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-v1.3/user-manuals/workloadspread.md b/i18n/zh/docusaurus-plugin-content-docs/version-v1.3/user-manuals/workloadspread.md index 6bcb84937..d905e4156 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-v1.3/user-manuals/workloadspread.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-v1.3/user-manuals/workloadspread.md @@ -46,16 +46,16 @@ spec: operator: In values: - zone-a - preferredNodeSelectorTerms: - - weight: 1 - preference: - matchExpressions: - - key: another-node-label-key - operator: In - values: - - another-node-label-value + preferredNodeSelectorTerms: + - weight: 1 + preference: + matchExpressions: + - key: another-node-label-key + operator: In + values: + - another-node-label-value maxReplicas: 3 - tolertions: [] + tolerations: [ ] patch: metadata: labels: @@ -82,12 +82,12 @@ spec: ### sub-fields - `name`: subset的名称，在同一个WorkloadSpread下name唯一，代表一个topology区域。 - + - `maxReplicas`：该subset所期望调度的最大副本数，需为 >= 0的整数。若设置为空，代表不限制subset的副本数。 > 当前版本暂不支持百分比类型。 - `requiredNodeSelectorTerm`: 强制匹配到某个zone。 - + - `preferredNodeSelectorTerms`: 尽量匹配到某个zone。 **注意**：requiredNodeSelectorTerm对应k8s nodeAffinity的requiredDuringSchedulingIgnoredDuringExecution。 @@ -148,10 +148,10 @@ WorkloadSpread提供了两种调度策略，默认为`Fixed`: rescheduleCriticalSeconds: 30 ``` -- Fixed: +- Fixed: workload严格按照`subsets`定义分布。 - + - Adaptive: **Reschedule**：Kruise检查`subset`中调度失败的Pod，若超过用户定义的时间就将其调度到其他有可用的`subset`上。 @@ -182,7 +182,7 @@ WorkloadSpread所管理的workload会按照`subsets`中定义的顺序扩缩容 ### 扩容 - 按照`spec.subsets`中`subset`定义的顺序调度Pod，当前`subset`的active Pod数量达到`maxReplicas`时再调度到下一个`subset`。 - + ### 缩容 - 当`subset`的副本数(active)大于定义的maxReplicas时，优先缩容多余的Pod。 - 依据`spec.subsets`中`subset`定义的顺序，后面`subset`的Pod先于前面的被删除。 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-v1.4/user-manuals/workloadspread.md b/i18n/zh/docusaurus-plugin-content-docs/version-v1.4/user-manuals/workloadspread.md index 6bcb84937..d905e4156 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-v1.4/user-manuals/workloadspread.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-v1.4/user-manuals/workloadspread.md @@ -46,16 +46,16 @@ spec: operator: In values: - zone-a - preferredNodeSelectorTerms: - - weight: 1 - preference: - matchExpressions: - - key: another-node-label-key - operator: In - values: - - another-node-label-value + preferredNodeSelectorTerms: + - weight: 1 + preference: + matchExpressions: + - key: another-node-label-key + operator: In + values: + - another-node-label-value maxReplicas: 3 - tolertions: [] + tolerations: [ ] patch: metadata: labels: @@ -82,12 +82,12 @@ spec: ### sub-fields - `name`: subset的名称，在同一个WorkloadSpread下name唯一，代表一个topology区域。 - + - `maxReplicas`：该subset所期望调度的最大副本数，需为 >= 0的整数。若设置为空，代表不限制subset的副本数。 > 当前版本暂不支持百分比类型。 - `requiredNodeSelectorTerm`: 强制匹配到某个zone。 - + - `preferredNodeSelectorTerms`: 尽量匹配到某个zone。 **注意**：requiredNodeSelectorTerm对应k8s nodeAffinity的requiredDuringSchedulingIgnoredDuringExecution。 @@ -148,10 +148,10 @@ WorkloadSpread提供了两种调度策略，默认为`Fixed`: rescheduleCriticalSeconds: 30 ``` -- Fixed: +- Fixed: workload严格按照`subsets`定义分布。 - + - Adaptive: **Reschedule**：Kruise检查`subset`中调度失败的Pod，若超过用户定义的时间就将其调度到其他有可用的`subset`上。 @@ -182,7 +182,7 @@ WorkloadSpread所管理的workload会按照`subsets`中定义的顺序扩缩容 ### 扩容 - 按照`spec.subsets`中`subset`定义的顺序调度Pod，当前`subset`的active Pod数量达到`maxReplicas`时再调度到下一个`subset`。 - + ### 缩容 - 当`subset`的副本数(active)大于定义的maxReplicas时，优先缩容多余的Pod。 - 依据`spec.subsets`中`subset`定义的顺序，后面`subset`的Pod先于前面的被删除。 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-v1.5/user-manuals/workloadspread.md b/i18n/zh/docusaurus-plugin-content-docs/version-v1.5/user-manuals/workloadspread.md index 6aa3f4086..335cba186 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-v1.5/user-manuals/workloadspread.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-v1.5/user-manuals/workloadspread.md @@ -48,16 +48,16 @@ spec: operator: In values: - zone-a - preferredNodeSelectorTerms: - - weight: 1 - preference: - matchExpressions: - - key: another-node-label-key - operator: In - values: - - another-node-label-value + preferredNodeSelectorTerms: + - weight: 1 + preference: + matchExpressions: + - key: another-node-label-key + operator: In + values: + - another-node-label-value maxReplicas: 3 - tolertions: [] + tolerations: [ ] patch: metadata: labels: diff --git a/versioned_docs/version-v0.10/user-manuals/workloadspread.md b/versioned_docs/version-v0.10/user-manuals/workloadspread.md index 270820e60..e13f1051a 100644 --- a/versioned_docs/version-v0.10/user-manuals/workloadspread.md +++ b/versioned_docs/version-v0.10/user-manuals/workloadspread.md @@ -43,16 +43,16 @@ spec: operator: In values: - zone-a - preferredNodeSelectorTerms: - - weight: 1 - preference: - matchExpressions: - - key: another-node-label-key - operator: In - values: - - another-node-label-value + preferredNodeSelectorTerms: + - weight: 1 + preference: + matchExpressions: + - key: another-node-label-key + operator: In + values: + - another-node-label-value maxReplicas: 3 - tolertions: [] + tolerations: [ ] patch: metadata: labels: @@ -99,7 +99,7 @@ tolerations: effect: "NoSchedule" ``` -- `patch`: customize the Pod configuration of `subset`, such as Annotations, Labels, Env. +- `patch`: customize the Pod configuration of `subset`, such as Annotations, Labels, Env. Example: @@ -145,10 +145,10 @@ WorkloadSpread provides two kind strategies, the default strategy is `Fixed`. rescheduleCriticalSeconds: 30 ``` -- Fixed: +- Fixed: + + Workload is strictly spread according to the definition of the subset. - Workload is strictly spread according to the definition of the subset. - - Adaptive: **Reschedule**: Kruise will check the unschedulable Pods of subset. If it exceeds the defined duration, the failed Pods will be rescheduled to the other `subset`. @@ -179,8 +179,8 @@ The workload managed by WorkloadSpread will scale according to the defined order ### Scale out -- The Pods are scheduled in the subset order defined in the `spec.subsets`. It will be scheduled in the next `subset` while the replica number reaches the maxReplicas of `subset` - +- The Pods are scheduled in the subset order defined in the `spec.subsets`. It will be scheduled in the next `subset` while the replica number reaches the maxReplicas of `subset` + ### Scale in - When the replica number of the `subset` is greater than the `maxReplicas`, the extra Pods will be removed in a high priority. diff --git a/versioned_docs/version-v1.0/user-manuals/workloadspread.md b/versioned_docs/version-v1.0/user-manuals/workloadspread.md index 270820e60..e13f1051a 100644 --- a/versioned_docs/version-v1.0/user-manuals/workloadspread.md +++ b/versioned_docs/version-v1.0/user-manuals/workloadspread.md @@ -43,16 +43,16 @@ spec: operator: In values: - zone-a - preferredNodeSelectorTerms: - - weight: 1 - preference: - matchExpressions: - - key: another-node-label-key - operator: In - values: - - another-node-label-value + preferredNodeSelectorTerms: + - weight: 1 + preference: + matchExpressions: + - key: another-node-label-key + operator: In + values: + - another-node-label-value maxReplicas: 3 - tolertions: [] + tolerations: [ ] patch: metadata: labels: @@ -99,7 +99,7 @@ tolerations: effect: "NoSchedule" ``` -- `patch`: customize the Pod configuration of `subset`, such as Annotations, Labels, Env. +- `patch`: customize the Pod configuration of `subset`, such as Annotations, Labels, Env. Example: @@ -145,10 +145,10 @@ WorkloadSpread provides two kind strategies, the default strategy is `Fixed`. rescheduleCriticalSeconds: 30 ``` -- Fixed: +- Fixed: + + Workload is strictly spread according to the definition of the subset. - Workload is strictly spread according to the definition of the subset. - - Adaptive: **Reschedule**: Kruise will check the unschedulable Pods of subset. If it exceeds the defined duration, the failed Pods will be rescheduled to the other `subset`. @@ -179,8 +179,8 @@ The workload managed by WorkloadSpread will scale according to the defined order ### Scale out -- The Pods are scheduled in the subset order defined in the `spec.subsets`. It will be scheduled in the next `subset` while the replica number reaches the maxReplicas of `subset` - +- The Pods are scheduled in the subset order defined in the `spec.subsets`. It will be scheduled in the next `subset` while the replica number reaches the maxReplicas of `subset` + ### Scale in - When the replica number of the `subset` is greater than the `maxReplicas`, the extra Pods will be removed in a high priority. diff --git a/versioned_docs/version-v1.1/user-manuals/workloadspread.md b/versioned_docs/version-v1.1/user-manuals/workloadspread.md index 270820e60..e13f1051a 100644 --- a/versioned_docs/version-v1.1/user-manuals/workloadspread.md +++ b/versioned_docs/version-v1.1/user-manuals/workloadspread.md @@ -43,16 +43,16 @@ spec: operator: In values: - zone-a - preferredNodeSelectorTerms: - - weight: 1 - preference: - matchExpressions: - - key: another-node-label-key - operator: In - values: - - another-node-label-value + preferredNodeSelectorTerms: + - weight: 1 + preference: + matchExpressions: + - key: another-node-label-key + operator: In + values: + - another-node-label-value maxReplicas: 3 - tolertions: [] + tolerations: [ ] patch: metadata: labels: @@ -99,7 +99,7 @@ tolerations: effect: "NoSchedule" ``` -- `patch`: customize the Pod configuration of `subset`, such as Annotations, Labels, Env. +- `patch`: customize the Pod configuration of `subset`, such as Annotations, Labels, Env. Example: @@ -145,10 +145,10 @@ WorkloadSpread provides two kind strategies, the default strategy is `Fixed`. rescheduleCriticalSeconds: 30 ``` -- Fixed: +- Fixed: + + Workload is strictly spread according to the definition of the subset. - Workload is strictly spread according to the definition of the subset. - - Adaptive: **Reschedule**: Kruise will check the unschedulable Pods of subset. If it exceeds the defined duration, the failed Pods will be rescheduled to the other `subset`. @@ -179,8 +179,8 @@ The workload managed by WorkloadSpread will scale according to the defined order ### Scale out -- The Pods are scheduled in the subset order defined in the `spec.subsets`. It will be scheduled in the next `subset` while the replica number reaches the maxReplicas of `subset` - +- The Pods are scheduled in the subset order defined in the `spec.subsets`. It will be scheduled in the next `subset` while the replica number reaches the maxReplicas of `subset` + ### Scale in - When the replica number of the `subset` is greater than the `maxReplicas`, the extra Pods will be removed in a high priority. diff --git a/versioned_docs/version-v1.2/user-manuals/workloadspread.md b/versioned_docs/version-v1.2/user-manuals/workloadspread.md index 270820e60..e13f1051a 100644 --- a/versioned_docs/version-v1.2/user-manuals/workloadspread.md +++ b/versioned_docs/version-v1.2/user-manuals/workloadspread.md @@ -43,16 +43,16 @@ spec: operator: In values: - zone-a - preferredNodeSelectorTerms: - - weight: 1 - preference: - matchExpressions: - - key: another-node-label-key - operator: In - values: - - another-node-label-value + preferredNodeSelectorTerms: + - weight: 1 + preference: + matchExpressions: + - key: another-node-label-key + operator: In + values: + - another-node-label-value maxReplicas: 3 - tolertions: [] + tolerations: [ ] patch: metadata: labels: @@ -99,7 +99,7 @@ tolerations: effect: "NoSchedule" ``` -- `patch`: customize the Pod configuration of `subset`, such as Annotations, Labels, Env. +- `patch`: customize the Pod configuration of `subset`, such as Annotations, Labels, Env. Example: @@ -145,10 +145,10 @@ WorkloadSpread provides two kind strategies, the default strategy is `Fixed`. rescheduleCriticalSeconds: 30 ``` -- Fixed: +- Fixed: + + Workload is strictly spread according to the definition of the subset. - Workload is strictly spread according to the definition of the subset. - - Adaptive: **Reschedule**: Kruise will check the unschedulable Pods of subset. If it exceeds the defined duration, the failed Pods will be rescheduled to the other `subset`. @@ -179,8 +179,8 @@ The workload managed by WorkloadSpread will scale according to the defined order ### Scale out -- The Pods are scheduled in the subset order defined in the `spec.subsets`. It will be scheduled in the next `subset` while the replica number reaches the maxReplicas of `subset` - +- The Pods are scheduled in the subset order defined in the `spec.subsets`. It will be scheduled in the next `subset` while the replica number reaches the maxReplicas of `subset` + ### Scale in - When the replica number of the `subset` is greater than the `maxReplicas`, the extra Pods will be removed in a high priority. diff --git a/versioned_docs/version-v1.3/user-manuals/workloadspread.md b/versioned_docs/version-v1.3/user-manuals/workloadspread.md index 8d7ecf8be..6697419da 100644 --- a/versioned_docs/version-v1.3/user-manuals/workloadspread.md +++ b/versioned_docs/version-v1.3/user-manuals/workloadspread.md @@ -47,16 +47,16 @@ spec: operator: In values: - zone-a - preferredNodeSelectorTerms: - - weight: 1 - preference: - matchExpressions: - - key: another-node-label-key - operator: In - values: - - another-node-label-value + preferredNodeSelectorTerms: + - weight: 1 + preference: + matchExpressions: + - key: another-node-label-key + operator: In + values: + - another-node-label-value maxReplicas: 3 - tolertions: [] + tolerations: [ ] patch: metadata: labels: @@ -103,7 +103,7 @@ tolerations: effect: "NoSchedule" ``` -- `patch`: customize the Pod configuration of `subset`, such as Annotations, Labels, Env. +- `patch`: customize the Pod configuration of `subset`, such as Annotations, Labels, Env. Example: @@ -149,10 +149,10 @@ WorkloadSpread provides two kind strategies, the default strategy is `Fixed`. rescheduleCriticalSeconds: 30 ``` -- Fixed: +- Fixed: + + Workload is strictly spread according to the definition of the subset. - Workload is strictly spread according to the definition of the subset. - - Adaptive: **Reschedule**: Kruise will check the unschedulable Pods of subset. If it exceeds the defined duration, the failed Pods will be rescheduled to the other `subset`. @@ -183,8 +183,8 @@ The workload managed by WorkloadSpread will scale according to the defined order ### Scale out -- The Pods are scheduled in the subset order defined in the `spec.subsets`. It will be scheduled in the next `subset` while the replica number reaches the maxReplicas of `subset` - +- The Pods are scheduled in the subset order defined in the `spec.subsets`. It will be scheduled in the next `subset` while the replica number reaches the maxReplicas of `subset` + ### Scale in - When the replica number of the `subset` is greater than the `maxReplicas`, the extra Pods will be removed in a high priority. diff --git a/versioned_docs/version-v1.4/user-manuals/workloadspread.md b/versioned_docs/version-v1.4/user-manuals/workloadspread.md index 4cda97a2b..681cc7787 100644 --- a/versioned_docs/version-v1.4/user-manuals/workloadspread.md +++ b/versioned_docs/version-v1.4/user-manuals/workloadspread.md @@ -47,16 +47,16 @@ spec: operator: In values: - zone-a - preferredNodeSelectorTerms: - - weight: 1 - preference: - matchExpressions: - - key: another-node-label-key - operator: In - values: - - another-node-label-value + preferredNodeSelectorTerms: + - weight: 1 + preference: + matchExpressions: + - key: another-node-label-key + operator: In + values: + - another-node-label-value maxReplicas: 3 - tolertions: [] + tolerations: [ ] patch: metadata: labels: @@ -103,7 +103,7 @@ tolerations: effect: "NoSchedule" ``` -- `patch`: customize the Pod configuration of `subset`, such as Annotations, Labels, Env. +- `patch`: customize the Pod configuration of `subset`, such as Annotations, Labels, Env. Example: @@ -149,10 +149,10 @@ WorkloadSpread provides two kind strategies, the default strategy is `Fixed`. rescheduleCriticalSeconds: 30 ``` -- Fixed: +- Fixed: + + Workload is strictly spread according to the definition of the subset. - Workload is strictly spread according to the definition of the subset. - - Adaptive: **Reschedule**: Kruise will check the unschedulable Pods of subset. If it exceeds the defined duration, the failed Pods will be rescheduled to the other `subset`. @@ -183,8 +183,8 @@ The workload managed by WorkloadSpread will scale according to the defined order ### Scale out -- The Pods are scheduled in the subset order defined in the `spec.subsets`. It will be scheduled in the next `subset` while the replica number reaches the maxReplicas of `subset` - +- The Pods are scheduled in the subset order defined in the `spec.subsets`. It will be scheduled in the next `subset` while the replica number reaches the maxReplicas of `subset` + ### Scale in - When the replica number of the `subset` is greater than the `maxReplicas`, the extra Pods will be removed in a high priority. diff --git a/versioned_docs/version-v1.5/user-manuals/workloadspread.md b/versioned_docs/version-v1.5/user-manuals/workloadspread.md index 99ba5df75..fec618b2a 100644 --- a/versioned_docs/version-v1.5/user-manuals/workloadspread.md +++ b/versioned_docs/version-v1.5/user-manuals/workloadspread.md @@ -49,16 +49,16 @@ spec: operator: In values: - zone-a - preferredNodeSelectorTerms: - - weight: 1 - preference: - matchExpressions: - - key: another-node-label-key - operator: In - values: - - another-node-label-value + preferredNodeSelectorTerms: + - weight: 1 + preference: + matchExpressions: + - key: another-node-label-key + operator: In + values: + - another-node-label-value maxReplicas: 3 - tolertions: [] + tolerations: [ ] patch: metadata: labels: