Skip to content
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

Trigger BrokerRef and Cross namespace references #4080

Open
cmellard opened this issue Aug 22, 2024 · 1 comment · May be fixed by #4060
Open

Trigger BrokerRef and Cross namespace references #4080

cmellard opened this issue Aug 22, 2024 · 1 comment · May be fixed by #4060
Labels
kind/feature-request triage/accepted Issues which should be fixed (post-triage)

Comments

@cmellard
Copy link

Problem
Kafka Broker does not currently support cross namespace triggers

Persona:
Event Consumer - Development teams trying to manage their own triggers/consumer groups

Exit Criteria
We can create a Trigger for a Kafka Broker in a namespace other than the Broker namespace and reconciliation of the Trigger/CG etc succeeds.

Had a quick scan/search of the issues and code base but couldn't find anything discussing this. For reference I'm talking about this BrokerRef field in the Trigger

type TriggerSpec struct {
	// Broker is the broker that this trigger receives events from.
	Broker string `json:"broker,omitempty"`

	// BrokerRef is the broker that is used for cross-namespace referencing.
	BrokerRef *duckv1.KReference `json:"brokerRef,omitempty"`

https://knative.dev/docs/eventing/features/cross-namespace-event-links/

@pierDipi
Copy link
Member

pierDipi commented Aug 22, 2024

@cmellard thanks for reporting!

Would you be interested in contributing this feature?
If you’re interested, I’d be happy to provide any additional information or resources you might need to get started. We have documentation available (contributing doc), and I’m also here or on CNCF Slack to answer any questions you might have.

/triage accepted

@knative-prow knative-prow bot added the triage/accepted Issues which should be fixed (post-triage) label Aug 22, 2024
@pierDipi pierDipi linked a pull request Aug 22, 2024 that will close this issue
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature-request triage/accepted Issues which should be fixed (post-triage)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants