From 8f50b05a884cb48d9e51b28c138001ef9c48d11c Mon Sep 17 00:00:00 2001
From: sv <bozhou@alauda.io>
Date: Sat, 23 May 2026 23:00:39 +0800
Subject: [PATCH] docs: update DevOps v3.20 plugin release notes

---
 docs/en/install/installing-devops.mdx | 27 +++++++++++++++++++++++++++
 docs/en/overview/release_notes.mdx    | 13 +++++++------
 2 files changed, 34 insertions(+), 6 deletions(-)

diff --git a/docs/en/install/installing-devops.mdx b/docs/en/install/installing-devops.mdx
index 2a430d4..b7ac61b 100644
--- a/docs/en/install/installing-devops.mdx
+++ b/docs/en/install/installing-devops.mdx
@@ -243,6 +243,33 @@ spec:
 
 This configuration directs Katanomi components to use /tmp/audit as the audit log storage path, ensuring compatibility with environments that enforce a read-only root filesystem. Adjust the path as needed to meet your security and operational requirements.
 
+### How to Configure Custom Scheduling Policies for Katanomi \{#how-to-configure-custom-scheduling-policies-for-katanomi}
+
+To schedule Katanomi components on specific nodes, configure `nodeSelector`, `tolerations`, or `affinity` under `spec.helmValues.global`. For example:
+
+```yaml
+spec:
+  helmValues:
+    global:
+      nodeSelector:
+        custom.node/role: devops
+      tolerations:
+        - key: custom-taint
+          operator: Exists
+          effect: NoSchedule
+      affinity:
+        nodeAffinity:
+          requiredDuringSchedulingIgnoredDuringExecution:
+            nodeSelectorTerms:
+              - matchExpressions:
+                  - key: custom.node/role
+                    operator: In
+                    values:
+                      - devops
+```
+
+If these fields are not configured, Katanomi components continue to use the default scheduling policy.
+
 ### How to Configure a Custom ImagePullSecret When Deploying Katanomi
 
 To specify a custom ImagePullSecret for your Katanomi instance, add the following configuration:
diff --git a/docs/en/overview/release_notes.mdx b/docs/en/overview/release_notes.mdx
index 2207f09..60e7083 100644
--- a/docs/en/overview/release_notes.mdx
+++ b/docs/en/overview/release_notes.mdx
@@ -13,18 +13,19 @@ weight: 20
 - Users can integrate `Alauda DevOps Jenkins v3` & `Alauda DevOps v3` with the newest DevOps Toolchain.
 - Pipeline execution forms support filling in default values.
 - The `Builds` and `Releases` pipeline has refactored the parameter rendering logic, and the parameters support referencing artifact attribute values and mapping expressions.
+- In `Alauda DevOps v3.20.36`, Katanomi components support custom scheduling policies through the Katanomi CR, including `nodeSelector`, `tolerations`, and `affinity`. Default scheduling behavior remains unchanged when these options are not configured. For an example, see [How to Configure Custom Scheduling Policies for Katanomi](../install/installing-devops.mdx#how-to-configure-custom-scheduling-policies-for-katanomi).
 
 Other changes:
 
 - Fixed vulnerabilities in `Alauda DevOps v3`, `Alauda DevOps Jenkins v3` and `Alauda DevOps Eventing v3`.
 
-The newest version of plugins are as follows:
+The newest versions of plugins are as follows:
 
-| Plugin Name | Latest Plugin Version |
-| - | - |
-| Alauda DevOps v3 | 3.20.35 |
-| Alauda DevOps Jenkins v3 | 3.20.17 |
-| Alauda DevOps Eventing v3 | 3.20.8 |
+| Plugin Name | Latest Plugin Version | ACP Version |
+| - | - | - |
+| Alauda DevOps v3 | 3.20.36 | 4.0, 4.1, 4.2, 4.3 |
+| Alauda DevOps Jenkins v3 | 3.20.18 | 4.0, 4.1, 4.2, 4.3 |
+| Alauda DevOps Eventing v3 | 3.20.9 | 4.0, 4.1, 4.2, 4.3 |
 
 ### Breaking Changes