-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Event Discovery: EventType Autocreate on replies to subscriptions should reference the subscription #4076
Comments
The TestChannelSubscriptionEventTypeAutoCreate test from https://github.com/knative-extensions/eventing-kafka-broker/pull/4074/files still shows that the eventtype references a KafkaChannel instead of Subscription. See https://prow.knative.dev/view/gs/knative-prow/pr-logs/pull/knative-extensions_eventing-kafka-broker/4074/channel-reconciler-tests-sasl-plain_eventing-kafka-broker_main/1833439756705337344 Reference:Kind = KafkaChannel, Namespace = test-shtvzyyt, Name = channel-rkavthwn /reopen |
@mgencur: Reopened this issue. In response to this:
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-sigs/prow repository. |
This issue is stale because it has been open for 90 days with no |
/triage accepted |
Describe the bug
This is similar to knative/eventing#7699 , just for KafkaChannel instead of InMemoryChannel.
There should be an event type that references a Subscription but the only event type that is produced references the KafkaChannel:
I have attached a reproducer `TestChannelSubscriptionEventTypeAutoCreate to #4074
Expected behavior
It's not clear if there should be two events types created in this case. The expectation is that one event type would reference the Subscription and one would reference KafkaChannel.
To Reproduce
Run the reproducer test attached to #4074
Knative release version
1.14
Additional context
The text was updated successfully, but these errors were encountered: