ACM-21338 FleetResourceEventStream

[vishsanghishetty]

📝 Summary

Ticket Summary (Title):

Add FleetResourceEventStream component for multicluster event streaming

Overview

This PR introduces a multicluster-aware version of the ResourceEventStream component. Instead of only showing events from the hub cluster, it can now display real-time Kubernetes events for resources running on any managed cluster in your fleet.

The component intelligently falls back to the standard OpenShift console ResourceEventStream when viewing hub cluster resources, so existing functionality remains unchanged while adding new multicluster capabilities..

Key Features

• Smart Fallback: Automatically falls back to OpenShift console's ResourceEventStream for hub cluster resources
• Multicluster Support: Uses WebSocket connections to stream events from managed clusters
• Event Filtering: Filters events by involvedObject.uid, involvedObject.name, and involvedObject.kind
• Real-time Streaming: Displays up to 50 most recent events with live updates
• Interactive Controls: Play/pause functionality for event streaming
• Error Handling: Comprehensive error states and reconnection logic

Technical Implementation

• Uses FleetK8sResourceCommon type which extends K8sResourceCommon with optional cluster property
• Leverages existing fleet API infrastructure (fleetWatch, useFleetK8sAPIPath, useHubClusterName)
• Includes test coverage for all scenarios

Ticket Link:

https://issues.redhat.com/browse/ACM-21338

Type of Change:

• 🐞 Bug Fix
• ✨ Feature
• 🔧 Refactor
• 💸 Tech Debt
• 🧪 Test-related
• 📄 Docs

---

✅ Checklist

General

• PR title follows the convention (e.g. ACM-12340 Fix bug with...)
• Code builds and runs locally without errors
• No console logs, commented-out code, or unnecessary files
• All commits are meaningful and well-labeled
• All new display strings are externalized for localization (English only)
• (Nice to have) JSDoc comments added for new functions and interfaces

If Feature

• UI/UX reviewed (if applicable)
• All acceptance criteria met
• Unit test coverage added or updated
• Relevant documentation or comments included

If Bugfix

• Root cause and fix summary are documented in the ticket (for future reference / errata)
• Fix tested thoroughly and resolves the issue
• Test(s) added to prevent regression

---

🗒️ Notes for Reviewers

[KevinFCormier]

Hey Vishali,

I left a few inline comments. In addition:

• It would be great if you could move the component directly under src/components and then move the src/components/FleetResourceEventStream folder under src/internal... I'm trying to have a flat structure under src/api and src/components having 1 file per exported API.
• I had asked you to incorporate some recent updates from Ugo into your work. See #4746 (comment)
• It looks like the event stream is not actually working (and it wasn't before your changes either). Can you investigate this and try to resolve?

[vishsanghishetty]

/retest

[KevinFCormier]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: KevinFCormier, vishsanghishetty

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [KevinFCormier,vishsanghishetty]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[KevinFCormier]

/test unit-tests-sonarcloud

[sonarqubecloud]

Quality Gate passed

Issues
13 New issues
0 Accepted issues

Measures
0 Security Hotspots
85.7% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud