Value Statement

We can see that there are some requirements from TALM to collect the events for other objects. if we can configure it in CR, that is easy to be extended in the future.

Definition of Done for Engineering Story Owner (Checklist)

• Introduce a new field in CR to configure the involvedobject for events. maybe
  • eventing:
  •     involvedObjects:
  •     - ClusterGroupUpgrade
• the global hub agent takes this field to collect the events for the involvedobjects

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the Customer

Portal Doc template that you can access from [The Playbook](

https://docs.google.com/document/d/1YTqpZRH54Bnn4WJ2nZmjaCoiRtqmrc2w6DdQxe_yLZ8/edit#heading=h.9fvyr2rdriby),

and ensure doc acceptance criteria is met.

• Call out this sentence as it's own action:

• [ ] Link the development issue to the doc issue.

Support Readiness

• [ ] The must-gather script has been updated.