[Tracking] Add collectors to Integration tests

[RealAnna]

Given the good first example 🚀 of how to add a collectors to kuttl tests #1834, we should add collectors in each test that:

1. collect logs of operators
2. run a kubectl describe for each involved CRDS

Listing the tests here with what would be nice to collect so that we can have multiple contributions 🥇

• Add collectors to Analysis Integration Tests #2697
• Add collectors to Lifecycle Operator Integration Tests #2698
• Add collectors to Metrics Integration Tests #2699
• Add collectors to Scheduling Gate Integration Tests #2700
• Remove Integration Test Reports from the pipeline #2702

[prakrit55]

As for the previous task of adding collectors to testasserts, I would like to take this up.

[rakshitgondwal]

I believe there can be multiple contributors to this particular issue. Anyone can work on this and raise a separate PR for a separate test so that it becomes easy to review and easy to track. Just mention here before what test/tests you are currently working on.

[prakrit55]

I believe there can be multiple contributors to this particular issue. Anyone can work on this and raise a separate PR for a separate test so that it becomes easy to review and easy to track. Just mention here before what test/tests you are currently working on.

So, I committed for the tests

• annotated-namespace-not-enabled
• simple-daemonset-annotated

and wd like to improve other tests too.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be
closed if no further activity occurs. Thank you for your contributions.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be
closed if no further activity occurs. Thank you for your contributions.

[RealAnna]

Updated the ticket to reflect the current status of our Integration tests, this is now divided into 4. I believe this would reduce our test time of 2min ca. in case of test failure if not more

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be
closed if no further activity occurs. Thank you for your contributions.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be
closed if no further activity occurs. Thank you for your contributions.