-
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
EventType auto-create for MTChannelBasedBroker backed by KafkaChannel creates two event types #4075
Comments
@mgencur I guess for |
Correct. For InMemoryChannel this was already fixed. |
@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. |
/close |
@mgencur: Closing 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 is similar to knative/eventing#7154
A MTChannelBasedBroker that is configured to use KafkaChannel generates two events, one with
spec.reference.kind:KafkaChannel
and one withspec.reference.kind:Broker
. It should create only one withkind:Broker
.Describe the bug
Broker definition that generates the two event type objects:
Related ConfigMap:
Generated event types:
Expected behavior
Only one event type is created, with
kind: Broker
.To Reproduce
The reproducer test is in this PR.
Would be nice to attach the test with a possible fix later and commit it into the repository.
Knative release version
1.14
Additional context
The text was updated successfully, but these errors were encountered: