Value Statement

Plugin content often uses the ResourceEventStream component to show events for a resource. In the multicluster case, we must provide a version of this component that can use data from a managed cluster.

Definition of Done for Engineering Story Owner (Checklist)

• Implementation should be copied from OpenShift console into the multicluster SDK
• Type of resource prop becomes FleetK8sResourceCommon, adding a cluster prop to it
• When cluster is not set or the cluster is the hub, fall back to ResourceEventStream from dynamic plugin SDK
• This may be a short-term implementation as the dynamic plugin SDK implementation may be refactored to allow the data to be provided separately; no full testing required

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.