User Story

As a Global Hub admin, I want to collect all provision-related events from cluster namespaces on the hub, so that I can track the complete cluster provisioning lifecycle.

Description

This user story implements the event collection mechanism for cluster provision events based on the spike investigation in ACM-26624.

Acceptance Criteria* Collect all provision-related events from cluster namespace on managed hubs

• Events are collected during provision and destroy phases (, provisioning, etc.)
• Events include timestamps, reasons, messages, and source information
• Event collection does NOT extract from ClusterDeployment state
• Events are sent to Global Hub manager via Kafka transport
• Unit tests cover event collection logic
• Integration tests verify events are properly collected

Implementation Notes

Based on discussion with Chunlin:

• Focus on namespace-level event collection for provision phases
• Capture comprehensive event coverage during cluster lifecycle
• Do NOT report events from ClusterDeployment state for now

  Related Issues

• Spike: ACM-26624 - Investigation of existing cluster provision and destroy events
• Parent Story: ACM-26550 - Cluster lifecycle event tracking

Technical Details

• Component: Global Hub Agent
• Event source: Cluster namespace events
• Transport: Kafka (CloudEvents format)
• Storage: PostgreSQL (via manager)