Skip to content

docs: update DevOps v3.20 plugin release notes #148

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
tik-seven merged 1 commit into from
May 25, 2026
+34 −6
Merged

docs: update DevOps v3.20 plugin release notes #148

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 27 additions & 0 deletions docs/en/install/installing-devops.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down
13 changes: 7 additions & 6 deletions docs/en/overview/release_notes.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down