📚 Sync docs from alaudadevops/tektoncd-operator on 35ba952dfbc3aafa0cda22b01ee0868ed455a5eb

l-qing · l-qing · commit d4c254b5aa00 · 2025-07-15T05:55:52.000Z
Source: chore: sync from release-4.1(6f953) (#216) Author: l-qing Ref: refs/heads/main Commit: 35ba952dfbc3aafa0cda22b01ee0868ed455a5eb This commit automatically syncs documentation changes from the source-docs repository. 🔗 View source commit: AlaudaDevops/tektoncd-operator@35ba952 🤖 Synced on 2025-07-15 05:55:52 UTC
diff --git a/.github/SYNC_INFO.md b/.github/SYNC_INFO.md
@@ -1,10 +1,10 @@
 # Documentation Sync Information
 
-- **Last synced**: 2025-07-11 09:18:17 UTC
+- **Last synced**: 2025-07-15 05:55:52 UTC
 - **Source repository**: alaudadevops/tektoncd-operator
-- **Source commit**: [40f6c8755d6c858cb92086b18bfbfbf4b3733a5f](https://github.com/alaudadevops/tektoncd-operator/commit/40f6c8755d6c858cb92086b18bfbfbf4b3733a5f)
-- **Triggered by**: lentil1016
-- **Workflow run**: [#11](https://github.com/alaudadevops/tektoncd-operator/actions/runs/16216475919)
+- **Source commit**: [35ba952dfbc3aafa0cda22b01ee0868ed455a5eb](https://github.com/alaudadevops/tektoncd-operator/commit/35ba952dfbc3aafa0cda22b01ee0868ed455a5eb)
+- **Triggered by**: l-qing
+- **Workflow run**: [#16](https://github.com/alaudadevops/tektoncd-operator/actions/runs/16285294447)
 
 ## Files synced:
 - docs/
diff --git a/docs/en/overview/lifecycle_policy.mdx b/docs/en/overview/lifecycle_policy.mdx
@@ -1,5 +1,5 @@
 ---
-weight: 30
+weight: 35
 ---
 
 # Lifecycle Policy
@@ -8,22 +8,34 @@ weight: 30
 
 Below is the lifecycle schedule for released versions of the `Alauda DevOps Pipelines` operator:
 
-| Alauda DevOps Pipelines Version | Tekton Component Versions | Release Date | End of Support  |
-| :----: | ------------------------ | :----------: | :--------------: |
-| v4.1.z | Pipelines: v0.65.z<br />Chains: v0.23.z<br />Pipelines-as-Code: v0.32.z<br />Results: v0.13.z<br />Triggers: v0.30.z<br />Tekton Hub: v1.19.z | 2025-?-? | 2026-?-? |
+| Alauda DevOps Pipelines Version | Release Date | End of Support | Version Type |
+| :----: | :----------: | :--------------: | :----: |
+| v4.2.x | 2025-08-? | 2026-08-? | LTS |
+| v4.1.x | 2025-07-14 | 2025-11-14 | Non-LTS |
+| v4.0.x | 2025-04-08 | 2026-04-08 | LTS |
+
+> For detailed component versions in each version, see the [Compatibility and support matrix](./release_notes.mdx#compatibility-and-support-matrix)
 
 ## Release Policy
 
-The `Alauda DevOps Pipelines` operator releases a new version every four to six months, updating the operator to the latest or second latest [LTS](https://github.com/tektoncd/community/blob/main/releases.md#support-policy) version officially released by Tekton.
+A new minor version of the `Alauda DevOps Pipelines` operator is released every month.
+
+Within every 4-month period, the last minor version will be selected as a Long Term Support (LTS) version. LTS versions are supported for 12 months, while non-LTS versions are supported four months.
+
+During these four months, we will update to the latest or second [LTS](https://github.com/tektoncd/community/blob/main/releases.md#support-policy) version officially released by Tekton.
 
 ## Maintenance Policy
 
-Alauda provides 12 months of maintenance support for each released version of the Tekton operator.
+Alauda provides comprehensive maintenance support for the `Alauda DevOps Pipelines` operator with different support durations based on version type.
 
-During the maintenance period, Alauda will provide the following services to customers:
+| Version Type | Support Duration | Examples |
+|:------------:|:----------------:|:--------:|
+| LTS (Long Term Support) | 12 months | 4.0.x |
+| Non-LTS | 4 months | 4.1.x |
 
-1. Track the patch versions released by Tekton and promptly provide patches containing bug fixes and security updates.
-2. Provide security updates that comply with Alauda's security standards.
-3. Assist customers in smoothly upgrading the Tekton operator to new versions.
+During the maintenance period, Alauda provides the following services:
 
-Additionally, Alauda will release a security update every two months during the maintenance period to ensure the security and stability of the operator.
+1. **Security Updates**: Regular security patches and updates that comply with Alauda's security standards
+2. **Bug Fixes**: Prompt delivery of bug fixes from upstream Tekton releases
+3. **Upgrade Assistance**: Support for smooth operator upgrades to newer versions
+4. **Regular Maintenance**: Security updates released every two months to ensure stability
diff --git a/docs/en/overview/release_notes.mdx b/docs/en/overview/release_notes.mdx
@@ -10,28 +10,28 @@ title: Release Notes
 # Release Notes
 
 ::: tip
-The maintenance period for version **v4.1.z** is from ? ?, 2025 to ? ?, 2026.
+The maintenance period for version **v4.2.x** is from ? ?, 2025 to ? ?, 2026.
 :::
 
 ## Compatibility and support matrix
 
 The following table shows the compatibility and support matrix between the `Alauda DevOps Pipelines` operator and ACP versions.
 
-| Alauda DevOps Pipelines Version | Tekton Component Versions |  ACP Version |
-| :------: | ------------------------- | :----------: |
-| v4.1.z  | Pipelines: v0.65.5<br />Chains: v0.23.0<br />Pipelines-as-Code: v0.32.0<br />Results: v0.13.2<br />Triggers: v0.30.1<br />Tekton Hub: v1.19.2 | v4.0, v4.1 |
+| Alauda DevOps Pipelines Version | Component Version | | | | | | ACP Version |
+|:------:|:------:|:------:|:------:|:------:|:------:|:------:|:------:|
+| **Operator** | **Pipelines** | **Triggers** | **CLI** | **Chains** | **Hub** | **Results** | |
+| 4.2.x (LTS) | ? | ? | ? | ? | ? | ? | 4.0 |
+| 4.1.x | 0.65.x | 0.30.x | 0.39.x | 0.23.x | 1.19.x | 0.14.x | 4.0 |
+| 4.0.x (LTS) | 0.65.x | 0.30.x | 0.39.x | 0.23.x | 1.19.x | 0.13.x | 4.0 |
 
-## v4.1.0
+## v4.2.0
 
 ### New and Optimized Features
 
-TODO: Add new features and optimizations for v4.1.0
-
 ### Fixed Issues
 
-{/* release-notes-for-bugs?template=fixed&project=DEVOPS&version=v4.1 (next) */}
+{/* release-notes-for-bugs?template=fixed&project=DEVOPS&version=v4.2(next) */}
 
 ### Known Issues
 
-{/* release-notes-for-bugs?template=unfixed&project=DEVOPS&version=v4.1 (next) */}
-
+{/* release-notes-for-bugs?template=unfixed&project=DEVOPS&version=v4.2(next) */}
diff --git a/docs/en/upgrade/index.mdx b/docs/en/upgrade/index.mdx
@@ -0,0 +1,7 @@
+---
+weight: 245
+---
+
+# Upgrade
+
+<Overview />
diff --git a/docs/en/upgrade/upgrade.mdx b/docs/en/upgrade/upgrade.mdx
@@ -0,0 +1,141 @@
+---
+weight: 20
+---
+
+# Upgrade `Alauda DevOps Pipelines` Operator
+
+This document provides instructions for upgrading the `Alauda DevOps Pipelines` Operator to a newer version using the `Marketplace`/`OperatorHub` interface in your cluster. The upgrade process is designed to be straightforward while ensuring minimal disruption to existing Tekton resources.
+
+## Upgrade Overview
+
+Upgrading the `Alauda DevOps Pipelines` Operator allows you to access new features, bug fixes, and improvements to the Tekton ecosystem. The `Alauda DevOps Pipelines` Operator handles the upgrade of all Tekton components (Pipelines, Triggers, Hub, etc.) according to your configuration.
+
+## Before You Begin
+
+Before upgrading the `Alauda DevOps Pipelines` Operator, ensure you:
+
+- Have administrative access to your cluster
+- Review the release notes for the new version to understand any breaking changes
+- Verify that your existing Tekton component configurations are compatible with the new version
+- Confirm that all Tekton components are in a ready state
+
+## Upgrade Process
+
+### Using `Marketplace`/`OperatorHub`
+
+1. **Access the `Marketplace`/`OperatorHub`**
+   - Log in to your cluster's management console
+   - Navigate to the `Marketplace` or `OperatorHub` section
+
+2. **Locate the `Alauda DevOps Pipelines` Operator**
+   - Search for `Alauda DevOps Pipelines` in the search bar
+   - Click on the `Alauda DevOps Pipelines` card
+
+3. **View Available Versions**
+   - On the `Alauda DevOps Pipelines` Operator details page, you'll see information about the currently installed version
+   - The interface will indicate if a newer version is available
+   - You can click different `Channels` to view all available versions
+
+4. **Initiate the Upgrade**
+   - If the target version is in a different `Channel`, switch to the corresponding `Channel` in the `Subscription` first
+   - If the current `Channel` has a newer version available, you will see a prompt:
+     - **New Version Detected**
+       - To upgrade only the current Operator, click `Confirm` to upgrade.
+
+5. **Configure Upgrade Settings (if applicable)**
+   - Some upgrades may present configuration options
+   - In most cases, the default settings will preserve your existing configuration
+
+6. **Confirm and Start the Upgrade**
+   - Click `Confirm` to begin the process
+   - Review the upgrade details and confirm your selection
+   - The system will update the `Alauda DevOps Pipelines` Operator while maintaining your custom resources
+
+7. **Monitor the Upgrade**
+   - The upgrade progress will be displayed in the `OperatorHub` interface
+   - You can also check the status in the `tekton-operator` namespace:
+     ```bash
+     $ kubectl get pods -n tekton-operator
+     ```
+     When all pods are in `Running` state, the operator upgrade is complete.
+     The operator will then automatically upgrade components such as `Pipelines`, `Triggers`, `Hub`, `Chains`, etc.
+   - Check the components upgrade status:
+     ```bash
+     $ kubectl get tektoninstallerset -A
+     $ kubectl get pods -n tekton-pipelines
+     ```
+     When all components and pods are in `Ready` state, the components upgrade is complete.
+
+8. **Verify the Upgrade**
+   - Check that the `Alauda DevOps Pipelines` Operator version has been updated:
+     ```bash
+     $ kubectl get csv -n tekton-operator
+
+     NAME                        DISPLAY                   VERSION   REPLACES   PHASE
+     tektoncd-operator.v4.x.x    Alauda DevOps Pipelines   4.x.x     x          Succeeded
+     ```
+     When the `VERSION` matches the new version, the upgrade is complete.
+   - Verify that your Tekton components are functioning correctly
+     - Test that your pipelines can run successfully
+
+## Post-Upgrade Steps
+
+After the upgrade completes successfully:
+
+1. **Verify Component Status**
+   - Check that all Tekton components have been updated:
+     ```bash
+     kubectl get tektonconfig,tektonpipeline,tektontrigger -A
+     kubectl get tektoninstallerset -A
+     ```
+
+2. **Test Functionality**
+   - Run a simple pipeline to verify that the system is working correctly
+   - Ensure that all existing integrations continue to function
+
+3. **Update Custom Resources if Needed**
+   - If the new version introduces changes to CRDs, you may need to update your custom resources
+   - Refer to the release notes for specific migration steps
+
+## Rollback Procedure
+
+If you encounter issues with the new version, you can roll back to the previous version:
+
+1. Return to the `Marketplace`/`OperatorHub` interface
+2. Select the `Alauda DevOps Pipelines` Operator
+3. `Uninstall` the current version
+4. Choose the previous version from the version list
+5. Follow the installation process for that version
+
+:::note
+Downgrading may require additional steps to ensure compatibility of your resources with the older version.
+
+This depends on the differences between the version you upgraded from and the version you upgraded to. If the differences are large, you may need to manually migrate resources.
+:::
+
+## Troubleshooting
+
+If you encounter issues during or after the upgrade:
+
+- Check the `Alauda DevOps Pipelines` Operator pod logs:
+  ```bash
+  $ kubectl logs -l name=tekton-operator -n tekton-operator
+  ```
+
+- Verify the status of your Tekton resources:
+  ```bash
+  $ kubectl get tektonconfig config -o yaml
+  ```
+
+- Ensure that all components have the expected status:
+  ```bash
+  $ kubectl get tektoninstallerset
+  ```
+
+## Next Steps
+
+After successfully upgrading the `Alauda DevOps Pipelines` Operator:
+
+- Explore new features introduced in the latest version
+- Update your CI/CD pipelines to leverage new capabilities
+- Consider enabling additional components that may be available in the new version
diff --git a/docs/en/upgrade/upgrade_path.mdx b/docs/en/upgrade/upgrade_path.mdx
@@ -0,0 +1,105 @@
+---
+weight: 10
+---
+
+# Upgrade Path
+
+:::note
+**Important**
+
+This document provides the upgrade path principles and supported version compatibility for `Alauda DevOps Pipelines` Operator.
+For detailed upgrade instructions, please refer to the [Upgrade `Alauda DevOps Pipelines` Operator](./upgrade.mdx).
+:::
+
+## Overview
+
+The `Alauda DevOps Pipelines` Operator follows specific upgrade path principles to ensure compatibility and stability during version transitions.
+
+### Version Types
+
+- **LTS (Long-Term Support) versions**: `4.0.x`, `4.2.x`, `4.6.x`, `4.10.x` - Recommended for production environments
+- **Non-LTS (Short-term) versions**: `4.1.x`, `4.3.x`, `4.5.x`, `4.7.x`, `4.9.x` - For early feature access
+
+### Upgrade Principles
+
+- Upgrades are supported between LTS versions, with the longest supported upgrade path skipping up to two intermediate LTS versions. For example:
+  - A direct LTS upgrade: `4.0.x (LTS)` → `4.2.x (LTS)`
+  - Longest supported upgrade range: `4.0.x (LTS)` → `4.10.x (LTS)` (skipping `4.2.x (LTS)` and `4.6.x (LTS)`)
+- Upgrades from non-LTS versions are only supported to the next immediate LTS version. For example:
+  - `4.3.x` → `4.6.x (LTS)` is supported
+  - `4.3.x` → `4.10.x (LTS)` is not supported
+- **Version Compatibility**: Patch versions within the same minor version are fully compatible
+- **Component Cohesion**: All Tekton components are upgraded together to maintain compatibility
+
+## Upgrade Paths
+
+### `Alauda DevOps Pipelines` v4.1.0
+
+This upgrade path has been tested with `Alauda DevOps Pipelines` Operator version v4.1.0 and ACP version 4.0.3 (the latest LTS patch version available during testing)
+
+| Channel version | ACP version | Kubernetes version |
+|:---------------:|:-----------:|:------------------:|
+| pipelines-4.0 | 4.0.3 | 1.31.6 |
+
+## Prerequisites
+
+Before initiating an upgrade, please ensure the following:
+
+1. **Version Compatibility**: Your current version falls within a supported upgrade path.
+2. **Component Health**: All Tekton components are in a `Ready` state.
+3. **Resource Availability**: The cluster has sufficient resources to support the upgrade process.
+
+## Upgrade Path Guidelines
+
+### LTS-to-LTS Upgrade Paths
+
+Upgrading between Long-Term Support (LTS) versions is recommended for production environments. We support both standard and extended upgrade paths as described below:
+
+- **Primary Path**: **Previous LTS → Current LTS**
+  - *Description*: A direct upgrade from the immediately preceding LTS version.
+  - *Testing Status*: All patch versions tested; latest patch versions receive comprehensive regression testing.
+  - *Example*: `4.0.x (LTS)` → `4.2.x (LTS)`
+
+- **Extended Path**: **Up to two LTS versions back → Current LTS**
+  - *Description*: A direct upgrade path skipping up to two intermediate LTS versions.
+  - *Testing Status*: All patch versions tested; latest patch versions validated through extended testing.
+  - *Example*: `4.0.x (LTS)` → `4.10.x (LTS)` (skipping `4.2.x (LTS)` and `4.6.x (LTS)`)
+
+- **Maintenance Path**: **Non-LTS (still in maintenance) → Current LTS**
+  - *Description*: Direct upgrade from a non-LTS version still under active maintenance.
+  - *Testing Status*: Limited testing scope; theoretically supported.
+  - *Use Case*: For teams looking to upgrade directly from non-LTS environments while staying within support boundaries.
+
+### Upgrades to Non-LTS Versions
+
+When upgrading to a non-LTS release, the following paths are available for environments that need faster access to new features:
+
+- **Primary Path**: **Previous LTS → Current non-LTS**
+  - *Description*: A direct upgrade from the latest LTS version.
+  - *Testing Status*: All patch versions tested; latest patch versions receive comprehensive regression testing.
+  - *Example*: `4.0.x (LTS)` → `4.1.x (non-LTS)`
+
+- **Extended Path**: **Two LTS versions back → Current non-LTS**
+  - *Description*: A direct upgrade path skipping up to two intermediate LTS versions.
+  - *Testing Status*: All patch versions tested; latest patch versions receive comprehensive regression testing.
+  - *Use Case*: For users aiming to minimize the number of upgrade hops.
+  - *Example*: `4.0.x (LTS)` → `4.7.x (non-LTS)` (skipping `4.2.x (LTS)` and `4.6.x (LTS)`)
+
+- **Maintenance Path**: **Non-LTS (still in maintenance) → Current non-LTS**
+  - *Description*: Upgrade path for non-LTS versions still under support.
+  - *Testing Status*: Limited testing scope; theoretically supported.
+  - *Use Case*: For teams rapidly adopting new features from non-LTS releases.
+
+### Patch-Level Compatibility
+
+- **Within the Same Minor Version**: Patch upgrades (e.g., `4.0.1` → `4.0.3`) are completely compatible.
+- **Testing Strategy**: All patch versions within the same minor version are supported for upgrades. The latest patch version undergoes comprehensive regression testing, while earlier patch versions receive limited testing.
+- **Recommendation**: For production stability, we recommend upgrading to the latest patch release before initiating any major or minor version upgrade.
+- **Example**: While `4.0.1`, `4.0.2`, and `4.0.3` may all be eligible for upgrade to `4.1.x`, only the latest (`4.0.3`) is fully tested and validated.
+
+## Upgrade Process Reference
+
+For complete upgrade instructions, including step-by-step procedures, backup guidance, and troubleshooting:
+
+- 📘 **[General Upgrade Guide](./upgrade.mdx)**: Comprehensive documentation for the upgrade process.
+- 📝 **[Release Notes](../overview/release_notes.mdx)**: Version-specific updates, breaking changes, and new features.
diff --git a/package.json b/package.json
@@ -1,6 +1,6 @@
 {
   "devDependencies": {
-    "@alauda/doom": "^1.7.1",
+    "@alauda/doom": "^1.9.1",
     "typescript": "^5.8.3"
   },
   "scripts": {
diff --git a/yarn.lock b/yarn.lock

Original file line number	Diff line number	Diff line change
`@@ -1,6 +1,6 @@`
`1`	`1`	`{`
`2`	`2`	`"devDependencies": {`
`3`		`- "@alauda/doom": "^1.7.1",`
	`3`	`+ "@alauda/doom": "^1.9.1",`
`4`	`4`	`"typescript": "^5.8.3"`
`5`	`5`	`},`
`6`	`6`	`"scripts": {`