Trigger unable to deliver to different namespace
zhongduo opened this issue · 0 comments
zhongduo commented
Describe the bug
Currently the trigger always set the sink namespace to its own namespace, so there is no way to deliver to sink in other namespace. Note that according to the spec, the destination can be a k8s service, which is cluster wide.
Expected behavior
When the namespace is set in subscriber spec, it should be respected.
To Reproduce
Try adding a namespace to the subscriber in trigger and check the resolved URI.