As part of our disaster recovery strategy, we need to evaluate whether OADP ( OpenShift API for Data Protection ) can effectively back up and restore Tekton resources. This will help us ensure data integrity and provide a smoother recovery process for our CI/CD pipelines.

Background

https://redhat-internal.slack.com/archives/CSPS1077U/p1727214349826799

Approach 

1. Resource Identification:

Identify all Tekton resources that need to be backed up (e.g., tasks, pipelines, triggers).

Ensure that the method for selecting resources is documented (e.g., using labels).

2. Backup Process:

Execute a backup of the identified Tekton resources using OADP.

Document the steps taken during the backup process, including any configurations or labels used.

3. Restore Process:

Test restoring the backed-up resources to a fresh cluster.

Document the steps and any issues encountered during the restoration process.

4. Validation:

Validate that the restored resources function as expected and that their states reflect the backup.

Confirm that any completed pipeline runs or approvals are appropriately managed.

5. Documentation:

Create a comprehensive report detailing findings, including potential limitations and best practices for using OADP with Tekton.

Acceptance Criteria 

1. Are we able to successfully backup all tekton resources
2. In case of disaster let us suppose the primary openshift cluster is down does the DR cluster restore OpenShift Pipelines in same state as in primary cluster.

Done Checklist

• Code is completed, reviewed, documented and checked in
• Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
• Continuous Delivery pipeline(s) is able to proceed with new code included
• Customer facing documentation, API docs etc. are produced/updated, reviewed and published
• Acceptance criteria are met