Value Statement

the global hub operator is deployed into an existing ACM hub to leverage some global hub provided features. Other existing ACM hubs also want to use those features. But for some reasons, the customers do not want to import the clusters (OCP Cluster - 1 / OCP Cluster - 2) as managed hub clusters of global hub (OCP Cluster - 0). The reasons can be:

1. They do not want to have some extra agent/addon running in OCP Cluster - 1 and OCP Cluster - 2
2. They do not want to have OCP Cluster - 1 and OCP Cluster - 2 managed by OCP Cluster - 0
3. The __ kube API server of OCP Cluster - 0  may not be accessible from other hub clusters

Definition of Done for Engineering Story Owner (Checklist)

• Implement New API - MulticlusterGlobalHubAgent
• Create the MulticlusterGlobalHubAgent CR can have the global hub agent installed in the same namespace of global hub operator
• Create a secret so that the global hub agent can report the data to the global hub cluster
• Provide a shell script to generate the secret content. refer to https://docs.google.com/document/d/1sf1LUQIDxwhmMO-nczvmQA1SF7ZOXBEOzDtJ-2jx_GU/edit?tab=t.0

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.