Event discovery
Problem Event discovery have been a needed feature with many attempts to implement it. There's a need that users can discover various existing eventing components. One attempt to solve it was via the event registry and EventType CRD #929. The new Discovery API offers a more promising approach.
We need a more unified story for discovery in eventing that potentially leverages the Discovery API and aligns the event registry and EventType features accordingly.
Additional context
@n3wscott @grantr I created this as the overarching event discovery roadmap item. Feel free to co-assign yourselves with @matzew if that's an issue under your focus.
perfect!
This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.
/remove-lifecycle stale /triage accepted /reopen
@devguyio: Reopened this issue.
In response to this:
/remove-lifecycle stale /triage accepted /reopen
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
/assign @matzew
Project tracking the Event discovery issues: https://github.com/orgs/knative/projects/62