Description of problem: As a user, I want to have a performant topology graph. There is a rendering loop when displaying a Http EventSink (KameletBinding). At the moment, it doesn't break the performance, but we might find the root cause of this rerender loop! Version-Release number of selected component (if applicable): 4.11 How reproducible: Always Steps to Reproduce: 1. Install Serverless and Camel K operator 2. Create required eventing resources 3. Open the developer perspective 4. Navigate to Add > Event Sinks and search for HTTP 5. Select "HTTP Sink" and press on "Create Event Sink" 6. Enter any URL and press Create 7. Navigate to the topology graph, open the react dev tools (browser extension) 8. Select the React Components tab and enable "Highlight updates when component render." Locally you can also add a console.log into EventSink in packages/knative-plugin/src/topology/components/nodes/EventSink.tsx Actual results: The component is rendered hundred of times. Expected results: The component should not be rerendered so often... Additional info:
Created attachment 1891582 [details] event-sink-rerender-loop.mp4
Verified on build version 4.11.0-0.nightly-2022-06-25-081133 Verified on browser version 103.0 chrome
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: OpenShift Container Platform 4.11.0 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:5069