Epic Goal

Install the global hub agent controlled by the ACM hub cluster. the global hub agent is a standalone agent, it can report the events (cloudevents format) to the Kafka as well as send data to REST API (webhook)

Why is this important?

To comply with ORAN O2-IMS  interface requirements

Scenarios

1. As a cluster admin, I can see a new field in MCH CR to indicate it can enable the standalone global hub agent in hub cluster.
2. As a cluster admin, I can see the global hub agent to send the events to Kafka and/or Webhook (http)
3. As a cluster admin, I can see the global hub agent can send the events to global hub owned Kafka and/or Webhook (http) as well if we import this ACM hub cluster as a managed hub cluster of global hub

Acceptance Criteria

...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. ...

Open questions:

1. what kinds of events we need to support
2. Do we really need to support publish events to webhook?

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 - Doc issue opened with a completed template. Separate doc issue
  opened for any deprecation, removal, or any current known
  issue/troubleshooting removal from the doc, if applicable.