-
Notifications
You must be signed in to change notification settings - Fork 597
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
Allow default broker controller to reconcile unset brokerclass. #2761
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: liu-cong The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
The following is the coverage report on the affected files.
|
@liu-cong: The following tests failed, say
Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
It is too easy to get the function wrong. Best to not allow an unset broker class. Use the webhook to set a default. |
Yes we can use webhook for new brokers. However, for existing brokers without an annotation, the reconciler won't pick it up. I think we should make it backwards compatible to ensure a seamless upgrade. cc @vaikas |
For existing brokers, the defaulting webhook from the conversion will handle them. If we want seamless upgrades, we need an upgrade test first. |
Yes agree we should have some upgrade tests. I don't think I will be able to add one this week but I will be interested to work on it.
What I noticed on my cluster is that the conversion seems to only work on client side, not server side. Although I can see the annotation being added by |
@liu-cong: PR needs rebase. 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. |
The proper approach is probably to have an upgrade job that handles upgrades for all resources wherever applicable. However we don't have time to design and implement such an upgrade job before 0.14 freezes. This approach is a quick fix for the issue. |
Yes, proper conversion job would definitely be the proper fix. I do wonder however if in lieu of that work, we could just provide a script that's only going to update brokers because that seems very straightforward and won't have future package with it? |
@vaikas Do you expect users to manually run this script? |
Yes, that was my thinking. One time upgrade script. |
Proposed Changes
Depends on knative/pkg#1163.
Release Note
Docs
cc @vaikas