-
Notifications
You must be signed in to change notification settings - Fork 205
WIP: CVO configuration: Minor refactoring and changes #1234
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
base: main
Are you sure you want to change the base?
WIP: CVO configuration: Minor refactoring and changes #1234
Conversation
Utilize a new structure, which holds the relevant information regarding the desired CVO configuration and its status to encapsulate this information to a simple data structure.
Using the field we can avoid changing the actual logging during testing by assigning a different function to the field if necessary. We can now also verify that the handler field is being executed.
The information regarding enabled feature gates is now available sooner in the code. Utilize this information to conditionally initialize the configuration controller at a one specific place. If no configuration controller is needed, this information is clearly stated by the noninitialized configuration field. The subsequent code can then easily check for existence of the configuration using a nil.
An error in the start logic will now result in the immediate shutdown of the CVO, rather than in the CVO catching the failed controller and continuing to work by ignoring the failed start.
Due to recent changes, the two test functions can now be safely merged together. The second function verified the overall synchronization of the configuration, which is now also being exercised in the first function. The tests cases were migrated over to the first function or were already present.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: DavidHurta 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 |
@DavidHurta: 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-sigs/prow repository. I understand the commands that are listed here. |
Blocked by #1232 |
/cc |
/uncc |
No description provided.