Cause: Sink for event sources and Trigger/Subscription shows all the resources(which we support as a sink) irrespective of they are standalone or an underlying resource created as part of backing KSVC, Broker, KameletBinding, etc
Consequence: User could even sink to the underlying addressable resources as it shows up in sink dropdown
Fix: Added resource filter to show only standalone resources as sink and not the one's owned by another resource
Result: User could sink to standalone addressable resources
Descriptionspathak@redhat.com
2022-02-14 15:27:54 UTC
Created attachment 1860997[details]
Every service shows as KSVC
Description of problem:
Subscriber/Trigger like kamelet binding shows as KSVC
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Create a kamelet binding
2. Create a broker/channel
3. In topology click on add trigger/subscriber through context menu
Actual results:
kamelet binding shows as ksvc
Expected results:
proper label should be there
Additional info:
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
Created attachment 1860997 [details] Every service shows as KSVC Description of problem: Subscriber/Trigger like kamelet binding shows as KSVC Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Create a kamelet binding 2. Create a broker/channel 3. In topology click on add trigger/subscriber through context menu Actual results: kamelet binding shows as ksvc Expected results: proper label should be there Additional info: