📚 Sync docs from alaudadevops/tektoncd-operator on 12d51820e10eedb971f26ee983479c3d9eccd2f6

Source: docs: add upgrade path documentation (#210)
Author: l-qing
Ref: refs/heads/release-4.1
Commit: 12d51820e10eedb971f26ee983479c3d9eccd2f6

This commit automatically syncs documentation changes from the source-docs repository.

🔗 View source commit: AlaudaDevops/tektoncd-operator@12d5182
🤖 Synced on 2025-07-12 05:31:28 UTC

Author: l-qing

.github/SYNC_INFO.md

@@ -1,10 +1,10 @@
 # Documentation Sync Information
 
-- **Last synced**: 2025-07-11 10:00:14 UTC
+- **Last synced**: 2025-07-12 05:31:28 UTC
 - **Source repository**: alaudadevops/tektoncd-operator
-- **Source commit**: [5dfce6070a942c49ecdaba66b9e1551404f72792](https://github.com/alaudadevops/tektoncd-operator/commit/5dfce6070a942c49ecdaba66b9e1551404f72792)
-- **Triggered by**: lentil1016
-- **Workflow run**: [#12](https://github.com/alaudadevops/tektoncd-operator/actions/runs/16217299572)
+- **Source commit**: [12d51820e10eedb971f26ee983479c3d9eccd2f6](https://github.com/alaudadevops/tektoncd-operator/commit/12d51820e10eedb971f26ee983479c3d9eccd2f6)
+- **Triggered by**: l-qing
+- **Workflow run**: [#13](https://github.com/alaudadevops/tektoncd-operator/actions/runs/16234824150)
 
 ## Files synced:
 - docs/

docs/en/overview/lifecycle_policy.mdx

@@ -8,12 +8,12 @@ weight: 35
 
 Below is the lifecycle schedule for released versions of the `Alauda DevOps Pipelines` operator:
 
-| Alauda DevOps Pipelines Version | Release Date | End of Support  |
-| :----: | :----------: | :--------------: |
-| v4.1.x | 2025-07-14 | 2025-11-14 |
-| v4.0.x (LTS) | 2025-04-08 | 2026-04-08 |
+| Alauda DevOps Pipelines Version | Release Date | End of Support | Version Type |
+| :----: | :----------: | :--------------: | :----: |
+| 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, see the [Compatibility and support matrix](./release_notes.mdx#compatibility-and-support-matrix)
+> For detailed component versions in each version, see the [Compatibility and support matrix](./release_notes.mdx#compatibility-and-support-matrix)
 
 ## Release Policy
 
@@ -25,12 +25,16 @@ During these four months, we will update to the latest or second [LTS](https://g
 
 ## Maintenance Policy
 
-Alauda provides maintenance support for 12 months for LTS versions and 4 months for non-LTS versions 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

docs/en/upgrade/upgrade.mdx

@@ -1,5 +1,5 @@
 ---
-weight: 10
+weight: 20
 ---
 
 # Upgrade `Alauda DevOps Pipelines` Operator

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 |
+|:---------------:|:-----------:|:------------------:|
+| release-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.