📚 Sync docs from alaudadevops/tektoncd-operator on a67165e27d3b04ea51bf6b8d418fb3bd83087841

Source: chore: sync from release-4.1 (1242e8b)
Author: qingliu
Ref: refs/heads/main
Commit: a67165e27d3b04ea51bf6b8d418fb3bd83087841

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

🔗 View source commit: AlaudaDevops/tektoncd-operator@a67165e
🤖 Synced on 2025-07-19 14:19:35 UTC

Author: l-qing

.github/SYNC_INFO.md

@@ -1,10 +1,10 @@
 # Documentation Sync Information
 
-- **Last synced**: 2025-07-19 01:59:32 UTC
+- **Last synced**: 2025-07-19 14:19:35 UTC
 - **Source repository**: alaudadevops/tektoncd-operator
-- **Source commit**: [388ea8bcce1e434b62b6aefd47a51787865809e3](https://github.com/alaudadevops/tektoncd-operator/commit/388ea8bcce1e434b62b6aefd47a51787865809e3)
+- **Source commit**: [a67165e27d3b04ea51bf6b8d418fb3bd83087841](https://github.com/alaudadevops/tektoncd-operator/commit/a67165e27d3b04ea51bf6b8d418fb3bd83087841)
 - **Triggered by**: l-qing
-- **Workflow run**: [#22](https://github.com/alaudadevops/tektoncd-operator/actions/runs/16383726300)
+- **Workflow run**: [#23](https://github.com/alaudadevops/tektoncd-operator/actions/runs/16389565814)
 
 ## Files synced:
 - docs/

docs/en/upgrade.mdx

@@ -78,6 +78,88 @@ Before upgrading the `Alauda DevOps Pipelines` Operator, ensure you:
    - Verify that your Tekton components are functioning correctly
      - Test that your pipelines can run successfully
 
+### Using `kubectl` CLI
+
+You can also upgrade the `Alauda DevOps Pipelines` Operator using the command line interface. This method is useful for automation or when you prefer CLI-based operations.
+
+1. **Check Current Subscription**
+   - First, identify the current subscription and its channel:
+     ```bash
+     $ kubectl get subscriptions.operators.coreos.com -A | grep tektoncd-operator
+
+     NAMESPACE               NAME                    PACKAGE                 SOURCE     CHANNEL
+     tekton-operator         tektoncd-operator       tektoncd-operator       platform   latest
+     ```
+
+2. **Switch to Target Channel**
+   - If you need to upgrade to a version in a different channel, patch the subscription:
+     ```bash
+     $ kubectl patch subscriptions.operators.coreos.com tektoncd-operator --type merge -p '{"spec":{"channel": "<target-channel>"}}' -n tekton-operator
+     ```
+     Replace `<target-channel>` with the desired channel (e.g., `pipelines-4.1`, `latest`).
+
+3. **Wait for UpgradePending State**
+   - Monitor the subscription status until it shows `UpgradePending`:
+     ```bash
+     $ kubectl get subscriptions.operators.coreos.com tektoncd-operator -n tekton-operator -o yaml
+
+     status:
+       installplan:
+         apiVersion: operators.coreos.com/v1alpha1
+         kind: InstallPlan
+         name: install-abc123
+       state: UpgradePending
+     ```
+     Look for the `state: UpgradePending` in the output.
+
+4. **Approve the InstallPlan**
+   - When the subscription is in `UpgradePending` state, find the corresponding InstallPlan:
+     ```bash
+     $ kubectl get installplan -n tekton-operator
+
+     NAME            CSV                        APPROVAL   APPROVED
+     install-abc123  tektoncd-operator.v4.x.x  Manual     false
+     ```
+
+   - Approve the InstallPlan by setting the `approved` field to `true`:
+     ```bash
+     $ kubectl patch installplans.operators.coreos.com <installplan-name> --type merge -p '{"spec":{"approved":true}}' -n tekton-operator
+     ```
+     Replace `<installplan-name>` with the actual InstallPlan name from the previous step.
+
+5. **Monitor the Upgrade Progress**
+   - Watch the subscription status until it becomes ready:
+     ```bash
+     $ kubectl get subscriptions.operators.coreos.com tektoncd-operator -n tekton-operator -o yaml -w
+     ```
+
+   - Check the operator pods status:
+     ```bash
+     $ kubectl get pods -n tekton-operator
+     ```
+     Wait until all pods are in `Running` state.
+
+6. **Verify the Upgrade**
+   - Confirm the 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
+     ```
+
+7. **Monitor Component Upgrades**
+   - The operator will automatically upgrade Tekton components. Monitor their progress:
+     ```bash
+     $ kubectl get tektoninstallerset -A
+     $ kubectl get pods -n tekton-pipelines
+     ```
+     Ensure all components and pods reach `Ready` state.
+
+:::note
+The CLI upgrade process follows the same underlying mechanism as the GUI method. The main difference is that you manually control the channel switching and InstallPlan approval steps.
+:::
+
 ## Post-Upgrade Steps
 
 After the upgrade completes successfully: