-
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 channel based broker #3212
Remove channel based broker #3212
Conversation
Skipping CI for Draft Pull Request. |
/test all |
/test pull-knative-eventing-integration-tests |
/test all |
/test all |
/test all |
/assign |
let's remove this too: https://github.com/vaikas/eventing/blob/remove-channel-based-broker/hack/release.sh#L24 |
labels: | ||
eventing.knative.dev/release: devel | ||
spec: | ||
replicas: 1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we keep this with replicas: 0
?
We have done this before with other "deprecated" PRs.
Thoughts?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So, if we do this, we can't remove this?
https://github.com/vaikas/eventing/blob/remove-channel-based-broker/hack/release.sh#L24
Just have the deployment there, set to 0 replicas?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so remove this file and move to mt-channel-broker? Or? :) Confused :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we want to delete the file outright and add a followup to do a cluster update for deleting a deployment
in the knative-eventing
namespace called broker-controller
I've tested this PR, using: https://github.com/matzew/knative-eventing-samples/tree/master/03-source_broker worked fine! A few nits? the filter/ingress are called while the controller is so, than the three deployments would all start with |
The following is the coverage report on the affected files.
|
Thanks, I think I addressed all your comments, PTAL :) |
@@ -20,6 +22,7 @@ metadata: | |||
labels: | |||
eventing.knative.dev/release: devel | |||
spec: | |||
replicas: 0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ahem... in the "MT broker" ?
I think we should keep the bits for the ST broker ? (at replica 0)
Or am I missing something here ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, are you saying that we have this deployment in the config/brokers/mt-channel-broker/ where we set the ChannelBroker deployment to 0?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought that when we rename the deployment, we should bring the old MT deployments to replicas: 0. Then the one below creates a new deployment?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So, you end up with something like this:
note broker-filter, broker-ingress have been brought to 0 and mt-broker-filter and mt-broker-ingress are up and running.
broker-controller is similarly brought to 0.
vaikas-a01:eventing vaikas$ kubectl -n knative-eventing get deployments
NAME READY UP-TO-DATE AVAILABLE AGE
broker-controller 0/0 0 0 43m
broker-filter 0/0 0 0 34d
broker-ingress 0/0 0 0 34d
eventing-controller 1/1 1 1 34d
eventing-webhook 1/1 1 1 34d
imc-controller 1/1 1 1 34d
imc-dispatcher 1/1 1 1 34d
kafka-ch-controller 1/1 1 1 16d
kafka-webhook 1/1 1 1 16d
mt-broker-controller 1/1 1 1 34d
mt-broker-filter 1/1 1 1 77m
mt-broker-ingress 1/1 1 1 76m
/test pull-knative-eventing-unit-tests |
For the UT tests above, filed: |
I think this would be fine to do as a followup, but we should fold in the mt-broker-controller into the eventing controller and keep all the class filtering it does to avoid the deployment. It costs almost nothing to be idle... |
I was under the impression that we mosdef wanted the broker to be a separately installable component which means it wouldn't be part of the core eventing controller. But maybe I misunderstand what you mean? |
I created an issue to track the clean up of the old brokers. Seems like a bigger issue, and perhaps we should have a job that cleans up the old Brokers, service accounts, etc.? In any case, bigger than this PR imho? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: matzew, vaikas The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Addresses #3139
Proposed Changes
Release Note
Docs
knative/docs#2516