-
Notifications
You must be signed in to change notification settings - Fork 592
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
Remove the Single tenant Broker #3139
Comments
👍 for targeting 0.16 |
/assign @matzew |
I think we should also set the Broker status as deprecated with pointer to upgrade to other broker. |
I'll remove the ChannelBasedBroker |
oops, just was going to comment, not close and comment :( :) |
I keep it open util last two are merged. doc and operator are pending |
/close all done |
@matzew: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
For release 0.16 we remove the single tenant broker.
Background
With the advent of the multitenant broker class in v0.14 of Eventing, we now have an easier to use and less resource consuming broker. The creation for the mt broker is mostly done via injection/labeling and applying CR files, backing different implementations. No special ClusterRoles are needed for the “non default” broker.
Problem
Single-tenant broker creation is much harder if not using the “default” broker, as stated here. While with the multi-tenant
Proposal
0.15
(see PR: Set MT based broker the default choice #3137)deprecated
:0.15
knative/operator
to reflect the new default config (see PR: With 0.15 the MTChannelBasedBroker is the new default broker operator#118)knative/docs
repo to reflect the removal of theChannelBasedBroker
class (see PR: Remove ST Broker docs from master docs#2533)The text was updated successfully, but these errors were encountered: