docs: Add Tekton Results to docs

Author: Kostiantyn Krykun

docs/assets/operator-guide/ci/diagram-tekton-results.png

@@ -1,7 +1,7 @@
 ---
-title: "Tekton Long-Term Log Storage"
-description: "Learn how to configure and access long-term logs for Tekton pipelines in KubeRocketCI using OpenSearch, enhancing log management and observability."
-sidebar_label: "Tekton Long-Term Log Storage"
+title: "Tekton Results Integration"
+description: "Tekton Results helps you logically group CI/CD workload history and separate long-term result storage from the Pipeline controller: add custom Result metadata (e.g. post-run actions), group related TaskRuns and PipelineRuns, keep result history independent of the Pipeline CRD controller to free etcd resources, and store logs so completed Runs can be cleaned."
+sidebar_label: "Tekton Results Integration"
 ---
 <!-- markdownlint-disable MD025 -->
 
@@ -14,151 +14,63 @@ import TabItem from '@theme/TabItem';
   <link rel="canonical" href="https://docs.kuberocketci.io/docs/operator-guide/ci/tekton-long-term-storage" />
 </head>
 
-KubeRocketCI Portal provides the capability to view long-term logs for pipelines. The long-term logs are stored in the OpenSearch cluster and can be viewed in the KubeRocketCI Portal after pipeline cleanup or deletion. This guide describes how to configure and view long-term logs in the KubeRocketCI Portal.
+Tekton Results aims to help users logically group CI/CD workload history and separate out long term result storage away from the Pipeline controller. This allows you to:
+
+- Provide custom Result metadata about your CI/CD workflows not available in the Tekton TaskRun/PipelineRun CRDs (for example: post-run actions)
+- Group related workloads together (e.g. bundle related TaskRuns and PipelineRuns into a single unit)
+- Make long-term result history independent of the Pipeline CRD controller, letting you free up etcd resources for Run execution.
+- Store logs produced by the TaskRuns/PipelineRuns so that completed Runs can be cleaned to save resources.
 
 ## Long-Term Log Access Workflow
 
 The following diagram illustrates the workflow for accessing long-term logs for pipelines in the KubeRocketCI Portal:
 
-```mermaid
-sequenceDiagram
-    actor U as User
-    participant KR as KubeRocketCI Portal
-    participant PC as Pipeline Controller
-    participant RW as Fluent Bit Agent
-    participant KD as KrakenD API Gateway
-    participant RA as OpenSearch
-
-    U->>KR: Trigger or create a pipeline
-    KR->>PC: Start pipeline execution
-    RW-->>PC: Collect pipeline logs
-    RW->>RA: Send logs to OpenSearch
-    Note over KR,RA: Pipeline is deleted or cleaned up
-    U->>KR: View pipeline logs
-    KR-->>KD: Request long-term logs
-    KD-->>RA: Fetch long-term logs
-    KR->>U: Return long-term logs
-```
-
-## Configuration
-
-To configure long-term log storage for pipelines in the KubeRocketCI Portal, follow the steps below:
-
-1. Install and configure OpenSearch cluster:
-
-    :::note
-    To install OpenSearch cluster, we recommend to use the [edp-cluster-add-ons](https://github.com/epam/edp-cluster-add-ons/tree/main/clusters/core/addons/opensearch) repository, which contains already prepared configurations for OpenSearch installation.
-    :::
-
-    To install OpenSearch cluster using the add-ons repository, follow the steps below:
-
-    1. Clone the forked [edp-cluster-add-ons](https://github.com/epam/edp-cluster-add-ons/) repository.
-
-    2. Navigate to the `clusters/core/addons/opensearch` directory and configure the `values.yaml` file with the necessary values for OpenSearch cluster installation.
-
-        :::note
-        Ensure that [Fluent Bit](https://github.com/epam/edp-cluster-add-ons/blob/44ca88c079d464c826fcae38f3f03fe983d1f984/clusters/core/addons/opensearch/values.yaml#L391) is configured to send container logs to the `logstash-edp` index in the OpenSearch cluster, as the KubeRocketCI Portal uses this index to retrieve long-term logs.
-        :::
-
-    3. Install the OpenSearch cluster using Helm or [Argo CD](../add-ons-overview.md) methods.
-
-2. Install and configure KrakenD API Gateway:
-
-    :::note
-    To install KrakenD API Gateway with OpenSearch connection, we recommend to use the [edp-cluster-add-ons](https://github.com/epam/edp-cluster-add-ons/tree/main/clusters/core/addons/krakend) repository, which contains already prepared configurations for KrakenD installation.
-    For more details, refer to the [KrakenD Integration](../extensions/krakend.md) guide.
-    :::
-
-    To install KrakenD API Gateway with OpenSearch connection, follow the steps below:
-
-    1. Clone the forked [edp-cluster-add-ons](https://github.com/epam/edp-cluster-add-ons/) repository.
-
-    2. Navigate to the `clusters/core/addons/krakend` directory and configure the `values.yaml` file with the necessary values for KrakenD installation.
-
-        :::note
-        Ensure that the KrakenD endpoint object for OpenSearch has the `/search/logs` endpoint name, as the KubeRocketCI Portal uses this endpoint to fetch long-term logs.
-        :::
+![KubeRocketCI Portal Diagram](../../assets/operator-guide/ci/diagram-tekton-results.png "KubeRocketCI Portal Diagram")
 
-    3. Ensure that the KrakenD [configuration secret](https://github.com/epam/edp-cluster-add-ons/blob/main/clusters/core/addons/krakend/templates/external-secrets/krakend.yaml) contains the OpenSearch connection variables.
+## Install Tekton Results
 
-        <Tabs
-          defaultValue="externalsecret"
-          values={[
-            {label: 'Manifests', value: 'manifests'},
-            {label: 'External Secrets Operator', value: 'externalsecret'},
-          ]}>
+Tekton Results is deployed as part of the Tekton Pipelines installation. For installing Tekton Pipelines, we recommend using the [add-ons approach](https://github.com/epam/edp-cluster-add-ons/blob/4456631feb6510ff875b5b839534968c3846da7a/clusters/core/apps/values.yaml#L286C1-L289C30). Here's an example of how to configure values.yaml before installation:
 
-          <TabItem value="manifests">
+    ```yaml
+    tekton:
+        createNamespace: true
+        enable: true
+        namespace: tekton-pipelines
+    ```
 
-          ```yaml
-          apiVersion: v1
-          kind: Secret
-          metadata:
-            name: krakend
-            namespace: krakend
-          type: Opaque
-          stringData:
-            OPENSEARCH_URL: https://opensearch-cluster-master.logging:9200
-            OPENSEARCH_CREDS: <base64-encoded-credentials>
-          ```
-
-          </TabItem>
-
-          <TabItem value="externalsecret">
-
-          ```json
-          {
-            "OPENSEARCH_URL": "https://opensearch-cluster-master.logging:9200",
-            "OPENSEARCH_CREDS": "<base64-encoded-credentials>"
-          }
-          ```
-          </TabItem>
-
-        </Tabs>
-
-    4. Install the KrakenD API Gateway using Helm or [Argo CD](../add-ons-overview.md) methods.
-
-## Viewing Long-Term Logs
-
-After configuring long-term log storage for Pipelines in the KubeRocketCI Portal, follow the steps below to view long-term logs:
-
-1. Navigate to the KubeRocketCI Portal and sign in with appropriate credentials.
-
-    ![KubeRocketCI Portal](../../assets/operator-guide/ci/kuberocketci-portal.png "KubeRocketCI Portal")
-
-2. In the **Components** section, navigate to the appropriate component (if component is not created yet, refer to the [Add Application](../../user-guide/add-application.md) guide to create a new one).
-
-    ![KubeRocketCI Portal Components](../../assets/operator-guide/ci/portal-components.png "KubeRocketCI Portal Components")
-
-3. In the component window, in the right upper corner, click the **GIT** button to navigate to the component repository (e.g., GitHub repository).
-
-    ![Component Git Repository](../../assets/operator-guide/ci/component-git-repository.png "Component Git Repository")
-
-4. In the component repository, create a Pull Request to trigger the review pipeline execution.
-
-    ![Create Pull Request](../../assets/operator-guide/ci/create-pull-request.png "Create Pull Request")
-
-5. In the Pull Request checks section, click the **Show all checks** button and navigate to the review pipeline in the KubeRocketCI Portal by clicking the **Details** button.
+## Configuration
 
-    ![PR Checks](../../assets/operator-guide/ci/pr-checks.png "PR Checks")
+To configure long-term log storage for pipelines in the KubeRocketCI Portal, follow the steps below:
 
-6. In the pipeline window, check the pipeline status. Ensure that the pipeline is successfully executed and the logs are available.
+1. Storage sizes in the [results-pg.yaml](https://github.com/epam/edp-cluster-add-ons/blob/main/clusters/core/addons/tekton/results-pg.yaml) file define the allocated volumes for the Tekton Results PostgreSQL cluster:
 
-    ![Pipeline Logs](../../assets/operator-guide/ci/pipeline-logs.png "Pipeline Logs")
+    * Database instance storage
+spec.instances.dataVolumeClaimSpec.resources.requests.storage
+(default: 2Gi) — Specifies the size of the main PostgreSQL data volume.
 
-7. Navigate to the **Pipelines** section and find the executed review pipeline. Delete the pipeline by clicking the **Delete** button.
+    * Backup repository storage
+spec.backups.pgbackrest.repos.volume.volumeClaimSpec.resources.requests.storage
+(default: 2Gi) — Specifies the size of the pgBackRest backup repository volume.
 
-    ![Delete Pipeline](../../assets/operator-guide/ci/delete-pipeline.png "Delete Pipeline")
+2. Storage and retention settings in the results.yaml [results.yaml](https://github.com/epam/edp-cluster-add-ons/blob/main/clusters/core/addons/tekton/results.yaml) file define how Tekton Results logs and data are stored and managed:
 
-8. Return to the Pull Request and click the **Show all checks** button. Navigate to the review pipeline again by clicking the **Details** button.
+    - Log storage size
+PersistentVolumeClaim.spec.resources.requests.storage
+(default: 5Gi) — Specifies the allocated disk size for storing pipeline logs.
 
-    ![PR Checks](../../assets/operator-guide/ci/pr-checks.png "PR Checks")
+    - Retention period
+ConfigMap.data.defaultRetention in tekton-results-config-results-retention-policy
+(default: "30" days) — Defines how long log files are retained before being automatically removed.
 
-9. After the pipeline deletion, the long-term logs are displayed in the pipeline window.
+    - Cleanup schedule
+ConfigMap.data.runAt in tekton-results-config-results-retention-policy
+(default: "5 5 * * 0") — Specifies the cron expression that determines when automated log cleanup runs (every Sunday at 5:05 AM).
 
-    ![Long Term Logs](../../assets/operator-guide/ci/reserved-logs.png "Long Term Logs")
+:::warning
+The retention policy agent removes only database records from PostgreSQL. It does not delete associated log files stored on persistent volumes, S3, or GCS backends. As a result, log data may remain on disk and consume storage even after the corresponding records are expired.
 
-This example demonstrates how to view long-term logs for review pipeline, but the same approach can be applied to other pipeline types.
+Users are currently responsible for manually cleaning up unused log files from the underlying storage backends.
+:::
 
 ## Related Articles