add disaster-recovery component

[filariow]

• add disaster-recovery to the development overlay
• add eventlistener and cronjob

This only affects the development overlay

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: filariow
Once this PR has been reviewed and has the lgtm label, please assign simonbaird for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[github-actions]

🤖 Gemini AI Assistant Available

Hi @filariow! I'm here to help with your pull request. You can interact with me using the following commands:

Available Commands

• @gemini-cli /review - Request a comprehensive code review

  • Example: @gemini-cli /review Please focus on security and performance

• @gemini-cli <your question> - Ask me anything about the codebase

  • Example: @gemini-cli How can I improve this function?
  • Example: @gemini-cli What are the best practices for error handling here?

How to Use

1. Simply type one of the commands above in a comment on this PR
2. I'll analyze your code and provide detailed feedback
3. You can track my progress in the workflow logs

Permissions

Only OWNER, MEMBER, or COLLABORATOR users can trigger my responses. This ensures secure and appropriate usage.

---

This message was automatically added to help you get started with the Gemini AI assistant. Feel free to delete this comment if you don't need assistance.

[github-actions]

🤖 Hi @filariow, I've received your request, and I'm working on it now! You can track my progress in the logs for more details.

[meyrevived]

Hey @filariow, so adding disaster recovery to the development overlay is for the e2e-tests. In the e2e-tests, the backup and recovery are all done programmatically through Ginkgo code - it just needs the infrastructure to be available (MinIO + OADP sitting there, ready) not an automatic DR action.
The backup action has its own ApplicationSet, with cluster label selectors here. This PR does things in a completely different model - could you explain more about why this was is how you proposed to do things?

What e2e-tests needs for the DR effort is just to have a development/ dir here with MinIO + OADP manifests and also to ensure the existing backup ApplicationSet routes dev clusters to that overlay.