github.com/instana/go-sensor@v1.62.2-0.20240520081010-4919868049e1/.tekton/README.md (about)

     1  # Tekton Pipelines for Instana Go Tracer
     2  
     3  ## Tekton Setup on a Cluster
     4  
     5  - You need access to a cluster with full admin privileges.
     6  - Allocate enough RAM and CPU so that all the pods, including sidecar pods, will run smoothly on a single node.
     7  - Add multiple nodes to increase parallel pipeline runs.
     8  
     9  ### Tekton Setup
    10  
    11  ```sh
    12  # Install Tekton pipelines
    13  kubectl apply --filename https://storage.googleapis.com/tekton-releases/pipeline/latest/release.yaml
    14  
    15  # Install Tekton triggers
    16  kubectl apply --filename https://storage.googleapis.com/tekton-releases/triggers/latest/release.yaml
    17  
    18  # Install Tekton interceptors
    19  kubectl apply --filename https://storage.googleapis.com/tekton-releases/triggers/latest/interceptors.yaml
    20  
    21  # Install Tekton dashboard - full installation is needed for read/write capabilities. eg: to make changes in the pipeline, such as re-running a pipeline run or deleting a pipeline run.
    22  kubectl apply --filename https://storage.googleapis.com/tekton-releases/dashboard/latest/release-full.yaml
    23  
    24  # Make sure all pods are in the ready state before proceeding further by issuing the following command.
    25  kubectl get pods --namespace tekton-pipelines --watch
    26  
    27  # To access the dashboard in localhost
    28  kubectl proxy
    29  ```
    30  
    31  - If you have successfully completed the above mentioned steps, you should be able to access the Tekton Dashboard from [here](http://localhost:8001/api/v1/namespaces/tekton-pipelines/services/tekton-dashboard:http/proxy/)
    32  
    33  ## Pipelines present in Go Tracer
    34  - Individual pipelines can be found in their respective directories here. You will find detailed usage instructions in a README file within each directory.
    35  
    36    1. [CI Build](./ci-build/README.md)
    37    2. [Tracer Reports](./tracer-reports/README.md)
    38  
    39  ## Deleting old pipeline run resources
    40  
    41  - Deletion of old pipeline run resources will be automatically handled by a cron job by default. You can review the configuration in `cleanup-cron-job.yaml`. Feel free to edit the `NUM_TO_KEEP` variable to specify the number of old pipeline runs you wish to retain. The default value is `50`.
    42  
    43  ## Helpful resources
    44  
    45  - [Ingress in IBM Cloud](https://cloud.ibm.com/docs/containers?topic=containers-managed-ingress-about)
    46  - [Tekton: Getting Started](https://tekton.dev/docs/getting-started/)
    47  - [Accessing clusters through the public cloud service endpoint on ibm cloud](https://cloud.ibm.com/docs/containers?topic=containers-access_cluster#access_public_se)
    48  - [Creating webhooks on Github](https://docs.github.com/en/webhooks/using-webhooks/creating-webhooks)
    49  - [Create a commit status](https://docs.github.com/en/rest/commits/statuses?apiVersion=2022-11-28#create-a-commit-status)
    50  - [CronJob in Tekton](https://github.com/tektoncd/triggers/tree/main/examples/v1beta1/cron)