knative / knative/eventing

Cross Namespace Event Links

Open
#7,530 14 comments 3 reactions 1 assignee Claimed by @yijie-04 View on GitHub
area/eventing Epic kind/api-change kind/enhancement kind/feature-request kind/proposal priority/important-longterm roadmap triage/accepted
Dominant language
Go
Stars
1.6k
Forks
631
Avg merge
2d 1h
Merged PRs (30d)
6

Description

**Problem**
There have been many requests for triggers to be in different namespaces than brokers (see #7439, #6577, #5139). If we are to add this feature, it makes sense to add it for the other main "event link": the subscription.

The feature track [can be seen here](https://docs.google.com/document/d/14R0tn6bPoiLuq40M9fYB_ery8vR13k5TF2LBnaUXOrc/edit?usp=sharing&resourcekey=0-elPw62plOTvtrezsLoeI1Q)

**[Persona:](https://github.com/knative/eventing/blob/main/docs/personas.md)**
Administrators, developers

**Exit Criteria**
Alpha:
- [ ] Feature flag is added
- [ ] Triggers are able to refer to brokers in another namespace
- [ ] Subscriptions are able to refer to channels in another namespace
- [ ] Basic E2E tests showing the creation of triggers and subscriptions with appropriate auths and events flowing
- [ ] Basic E2E tests showing that creation of triggers and subscriptions without appropriate auths fails

Beta:
- [ ] More comprehensive E2E testing
- [ ] Enable the new RBAC verb by default, without enabling the authentication of the RBAC verb
- [ ] Communications with community members on how they will need to add the new RBAC “knsubscribe” verb to their RBAC setup

GA:
- [ ] Conformance tests
- [ ] Enabled by default

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.