-
Notifications
You must be signed in to change notification settings - Fork 598
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
Auto Enabled Events only show up for InMemory channel #7154
Comments
Actually: If events are routed to a channel created/owned by the broker controller, we should not create these event types |
@matzew pls do you have a quick hint where is the routing happening to check if we can infer the ownership? |
@dsimansk are you working on this? If not, I can take it :) |
@Cali0707 go ahead I was just poking around, but haven't found a good starting point. :) |
/assign |
@matzew it looks like this is happening because the eventing/pkg/broker/ingress/ingress_handler.go Lines 126 to 130 in 7636997
the Broker object stored in the indexer changes to have no TypeMeta set, so when we access the broker object when creating events there is no TypeMeta anymore. Also, on subsequent http requests, there is no TypeMeta - only on the first request it is set.
Temporarily, we can fix this by just hardcoding the |
Describe the bug
Create a broker like:
and than send some random event to it, like:
kn-event-linux-amd64 send \ --to Broker:eventing.knative.dev/v1:my-broker\ --type com.corp.integration.warning \ -f message="fooss"
You will not see an
EventType
for the broker: just the channel. However, the channel is just an implementation detail, and is OK that it is listed there, on the ingress, but for sure it should also show this for the Broker.Result:
The text was updated successfully, but these errors were encountered: