Cross-namespace triggering

58 views
Skip to first unread message

Joni Rap

unread,
Jul 20, 2023, 1:36:50 AM7/20/23
to Knative Users
Hi all,
I'm writing regarding a feature that i've noticed is missing (or perhaps even a bug with an existing feature).
When defining a Trigger, I am able to specify a namespace under the subscriber spec. However, this namespace is ignored.
The message is: Unable to get the Subscriber's URI : failed to get object eventing/error-handler: services "error-handler" not found. One can clearly see the namespace used is eventing whereas the namespace specified was different.
Since the Trigger must exist in the same namespace as the Broker (there is no spec for specifying a namespace in which the Broker resides), in order to separate the location of the Broker and our Service, we must have the ability to specify the namespace as part of the Ref.
The spec includes a uri however when applying that, it seems this uri is only meant for sub-routing within the Service.

Anyone have any suggestions?
I really don't want to have a Broker in each namespace where I have services, I want to be able to communicate between services across namespaces.
Thanks!

Xiong Liu

unread,
Jul 20, 2023, 10:23:31 PM7/20/23
to Knative Users
1. What's your eventing version? From knative eventing 0.22 on, cross-namespace triggering is supported.

2. According to the official docs,  URI can be an absolute URL(non-empty scheme and non-empty host) pointing to the target or a relative URI.

Joni Rap

unread,
Jul 20, 2023, 10:37:21 PM7/20/23
to Xiong Liu, Knative Users
I'm using version 1.10 (latest).
When setting namespace of subscriber, it always defaults back to the namespace the trigger is defined in. (As I mentioned above and quoted).
You can't specify a different namespace for a broker either.


--
You received this message because you are subscribed to a topic in the Google Groups "Knative Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/knative-users/_WiX5AEMNic/unsubscribe.
To unsubscribe from this group and all its topics, send an email to knative-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/knative-users/9004820c-36c4-433a-9fed-5478a27e4463n%40googlegroups.com.

Xiong LIU

unread,
Jul 20, 2023, 11:09:41 PM7/20/23
to Joni Rap, Knative Users
https://github.com/knative/eventing/issues/4994 fixed the problem. 

If the problem still persists in the latest version, maybe you should submit an issue or check the source code.

Pierangelo Di Pilato

unread,
Jul 21, 2023, 3:23:25 AM7/21/23
to Joni Rap, Knative Users
Hi Joni,

this is not expected, it might be a bug, which Broker class are you using?

Thanks,
Pierangelo
> --
> You received this message because you are subscribed to the Google Groups "Knative Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to knative-user...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/knative-users/d73f3763-7269-4e1a-8d5d-082b3d21cba2n%40googlegroups.com.



--

Pierangelo Di Pilato
Senior Software Engineer
Red Hat, Inc
https://www.redhat.com/

Joni Rap

unread,
Jul 21, 2023, 3:31:53 AM7/21/23
to Pierangelo Di Pilato, Knative Users
Hi Pierangelo,
I'm using the RabbitMQ broker class.
I just read what Xiong wrote, and looked at the issue and commente, and perhaps this broker doesn't support this feature?
Thanks,
Joni

Pierangelo Di Pilato

unread,
Jul 21, 2023, 4:08:03 AM7/21/23
to Joni Rap, Knative Users
Hi Joni,

This was recently fixed
https://github.com/knative-sandbox/eventing-rabbitmq/issues/1117, next
week we will cut a 1.11 release that will include the fix, or
otherwise you can open an issue or add a comment to the issue to
advocate for a backport for a 1.10.* patch release.

Hope this helps,
Pierangelo

On Fri, Jul 21, 2023 at 9:31 AM Joni Rap <joni.r...@gmail.com> wrote:
>
> Hi Pierangelo,
Reply all
Reply to author
Forward
0 new messages