📚 Sync docs from alaudadevops/tektoncd-operator on 8ff6881ccd33fce459233d374d072ac37d861b65

l-qing · l-qing · commit 0fb37b89b3b3 · 2025-07-16T14:03:32.000Z
Source: chore: sync from release-4.1 (d29479) Author: qingliu Ref: refs/heads/main Commit: 8ff6881ccd33fce459233d374d072ac37d861b65 This commit automatically syncs documentation changes from the source-docs repository. 🔗 View source commit: AlaudaDevops/tektoncd-operator@8ff6881 🤖 Synced on 2025-07-16 14:03:32 UTC
diff --git a/.github/SYNC_INFO.md b/.github/SYNC_INFO.md
@@ -1,10 +1,10 @@
 # Documentation Sync Information
 
-- **Last synced**: 2025-07-15 09:15:55 UTC
+- **Last synced**: 2025-07-16 14:03:32 UTC
 - **Source repository**: alaudadevops/tektoncd-operator
-- **Source commit**: [c976658497ec34f8adb9c180191664933c530752](https://github.com/alaudadevops/tektoncd-operator/commit/c976658497ec34f8adb9c180191664933c530752)
+- **Source commit**: [8ff6881ccd33fce459233d374d072ac37d861b65](https://github.com/alaudadevops/tektoncd-operator/commit/8ff6881ccd33fce459233d374d072ac37d861b65)
 - **Triggered by**: l-qing
-- **Workflow run**: [#17](https://github.com/alaudadevops/tektoncd-operator/actions/runs/16289173228)
+- **Workflow run**: [#20](https://github.com/alaudadevops/tektoncd-operator/actions/runs/16321670900)
 
 ## Files synced:
 - docs/
diff --git a/docs/en/development/component-quickstart/index.md b/docs/en/development/component-quickstart/index.md
diff --git a/docs/en/development/run_e2e.mdx b/docs/en/development/run_e2e.mdx
@@ -1,6 +1,6 @@
 ---
 title: Run TektonCD Operator E2E Tests
-weight: 40
+weight: 14
 ---
 
 # TektonCD Operator E2E Testing Guide
@@ -252,13 +252,13 @@ Each toolchain contains the following common configuration items:
    ```bash
    # Create workspace directory
    mkdir -p workspace
-
+   
    # Copy your kubeconfig to workspace directory
    cp /path/to/your/kubeconfig.yaml workspace/config
-
+   
    # Copy your config.yaml to workspace directory
    cp config.yaml workspace/config.yaml
-
+   
    # Set the correct permissions for the workspace directory
    # The container runs as nonroot user (UID 65532), so we need to give write permissions
    chmod -R 777 workspace
@@ -311,7 +311,7 @@ allure open allure-report/
    ```bash
    # Check cluster permissions
    kubectl auth can-i create pods --all-namespaces
-
+   
    # If permissions are insufficient, contact cluster administrator
    ```
 
@@ -322,7 +322,7 @@ allure open allure-report/
    ```bash
    # Ensure workspace directory has write permissions for all users
    chmod -R 777 workspace
-
+   
    # Or set ownership to match the container user (UID 65532)
    sudo chown -R 65532:65532 workspace
    ```
@@ -332,7 +332,7 @@ allure open allure-report/
    ```bash
    # Check network connectivity
    curl -I registry.alauda.cn:60070
-
+   
    # Configure image registry authentication
    docker login registry.alauda.cn:60070
    ```
@@ -391,7 +391,7 @@ docker run --entrypoint /bin/bash -it \
    # Collect cluster status
    kubectl get all --all-namespaces
    kubectl describe pods --all-namespaces
-
+   
    # Collect logs
    kubectl logs -l app=tektoncd-operator -n tektoncd-operator
    ```
diff --git a/docs/en/development/update-component/index.md b/docs/en/development/update-component/index.md
@@ -1,9 +1,3 @@
----
-created: '2025-07-07'
-updated: '2025-07-13'
-weight: 20
----
-
 # Component Update Guide
 
 This document describes how to update components in the TektonCD Operator project using the automated update system. The project now uses an automated script to download and process component releases, eliminating the need for manual updates.
@@ -28,21 +22,21 @@ All component configurations are managed in the `components.yaml` file at the pr
 ```yaml
 tektoncd-pipeline:
   revision: main
-  releases:
+  releases: 
     - remote_path: pipeline
       local_path: tekton-pipeline
 
 tektoncd-hub:
   revision: main
-  releases:
+  releases: 
     - remote_path: api
       local_path: tekton-hub/api
     - remote_path: hub-info
       local_path: tekton-hub/hub-info
 
 tektoncd-trigger:
   revision: main
-  releases:
+  releases: 
     - remote_path: trigger
       local_path: tekton-triggers
     - remote_path: bindings
@@ -85,7 +79,7 @@ To use releases from your own branch or specific commit:
 ```yaml
 tektoncd-hub:
   revision: your-feature-branch  # or specific commit hash
-  releases:
+  releases: 
     - remote_path: api
       local_path: tekton-hub/api
     - remote_path: hub-info
@@ -118,7 +112,7 @@ To add a new component to the automated update process:
 ```yaml
 your-new-component:
   revision: main  # or your target branch
-  releases:
+  releases: 
     - remote_path: main
       local_path: your-component/main
     - remote_path: sidecar
@@ -152,7 +146,7 @@ For a component to work with the automated system, it must:
 ```yaml
 tektoncd-new-component:
   revision: v0.1.0
-  releases:
+  releases: 
     - remote_path: controller
       local_path: tekton-new-component/controller
     - remote_path: webhook
@@ -282,5 +276,6 @@ If you were previously updating components manually:
 
 ## Related Documentation
 
-- [Build System Architecture](../../overview/architecture.mdx)
+- [Component Configuration Reference](../configure/components.yaml.md)
+- [Build System Architecture](../architecture/build-system.md)
 - [Development Environment Setup](../component-quickstart/index.md)
diff --git a/docs/en/development/update-frontend/index.md b/docs/en/development/update-frontend/index.md
@@ -1,7 +1,6 @@
 ---
 created: '2025-01-10'
-updated: '2025-01-10'
-weight: 30
+sourceSHA: 423aae74086ccd5e58bf95963dba1872dde2b1e215377c15812fd75e0246284b
 ---
 
 # Update Frontend Images
diff --git a/docs/en/overview/lifecycle_policy.mdx b/docs/en/overview/lifecycle_policy.mdx
@@ -11,7 +11,7 @@ Below is the lifecycle schedule for released versions of the `Alauda DevOps Pipe
 | 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.1.x | 2025-07-16 | 2025-11-16 | 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)
diff --git a/docs/en/results/configure/database_configuration.mdx b/docs/en/results/configure/database_configuration.mdx
@@ -58,7 +58,7 @@ Tekton Results supports using external PostgreSQL databases. The configuration i
 | `db_name` | Database name | `tekton-results` | Yes |
 | `db_sslmode` | SSL connection mode | `disable` | No |
 | `db_sslrootcert` | SSL root certificate path | Empty | No (required when using SSL) |
-| `db_secret_name` | Secret name for database credentials | Empty  | Yes |
+| `secret_name` | Secret name for database credentials | Empty  | Yes |
 
 > The valid options for `db_sslmode` are explained here https://www.postgresql.org/docs/current/libpq-ssl.html#LIBPQ-SSL-PROTECTION.
 
@@ -109,9 +109,14 @@ spec:
   db_host: your-postgres-host.example.com
   db_port: 5432
   db_name: tekton_results
-  db_secret_name: tekton-results-postgres
+  db_sslmode: allow
+  secret_name: tekton-results-postgres
 ```
 
+:::tip
+This document only lists the database-related configuration fields. For the complete list of fields, please refer to [Quick Start](../quick_start.mdx#installing-using-operator-crd).
+:::
+
 ### 3. Verify Configuration
 
 ```bash
@@ -184,7 +189,7 @@ spec:
   db_sslmode: verify-full
   db_sslrootcert: /etc/tls/db/ca.crt
   # Secret configuration
-  db_secret_name: tekton-results-postgres
+  secret_name: tekton-results-postgres
   # Options for mounting CA certificate
   options:
     deployments:
@@ -251,6 +256,14 @@ kubectl get pods -n tekton-pipelines -l app.kubernetes.io/name=tekton-results-ap
 kubectl get pods -n tekton-pipelines -l app.kubernetes.io/name=tekton-results-retention-policy-agent
 ```
 
+:::warning
+If you update the `db_sslmode` field, you may need to recreate the `TektonResult` resource for the changes to take effect.
+
+```bash
+kubectl get tektonresults.operator.tekton.dev result -o yaml | kubectl replace --force -f -
+```
+:::
+
 ### Troubleshooting
 
 #### Common Issues
@@ -297,7 +310,9 @@ kubectl get secret -n <ns-of-postgresql-instance> -l middleware.instance/type=Po
 
 :::info
 
-This Secret contains `host`, `port`, `username`, `password` information. You need to supplement `database` and `sslmode` (set to `allow` or `prefer`) information based on this Secret, and create a new secret in the namespace where the Tekton Results instance is located.
+This Secret contains `host`, `port`, `username`, `password` information. You need to supplement `database` information based on this Secret, and create a new secret in the namespace where the Tekton Results instance is located.
+
+If you need to set `sslmode`, please set `db_sslmode` in `TektonResult` to `allow` or `prefer` etc.
 
 For more PostgreSQL deployment parameters and requirements, please refer to <ExternalSiteLink name="postgresql" href="/installation.html" children="PostgreSQL Deployment Documentation" />.
 :::
