Epic Goal

• Enhance the ManifestWork CR to be able to sync back the created resource's status back to the origin ManifestWork

Community issue:  https://github.com/open-cluster-management-io/community/issues/78  

Why is this important?

• Users need a way to understand the status of resources created through ManifestWork without reaching out directly to the cluster.

Scenarios

1. 1. End user wants to run a Job (e.g. tf job) in OCM.
   2. End user created a manifestwork in one managed cluster namespace.
   3. Managed cluster pull the manifestwork and run on the job.
   4. End user wants to know what is the status of the Job (e.g. tf job).
      OCM should provide a way to let end user know the status of the real workload (tf job in above scenario).

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions::

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>