Value Statement

For the initial release we will not make any changes to the CR. Therefore, installation of Common Inventory using the Global Hub operator will by adding an annotation in the CR (which is tracked as a API change).  With this annotation being added -

1. common inventory code must be deployed and configured
2. global hub agents must be configured with rest end points of the common inventory

Another closely related requirement would be just to install the Global Hub without ACM. Going by the rule - no changes to API - this calls for an addition annotation to be supported. (should this be a separate story)

Definition of Done for Engineering Story Owner (Checklist)

• fork kessel inventory to stolostron
• build kessel inventory via Konflux
• deploy kessel inventory
• I need to ensure that my currently deployment of Global Hub continues to work when the Mgmt Fabric is enabled

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.