WIP: CVO configuration: Introduce a config provider interface #1233
+279
−226
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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. 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. The subsequent code can then easily check for existence of the configuration using a nil.
openshift-ci
bot
added
the
do-not-merge/work-in-progress
|
[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 |
openshift-ci
bot
added
the
approved
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.
Introduce a configuration provider interface. The goal of the interface is to abstract the underlying system of fetching the CVO configuration. Be it a Kubernetes API server, or a configuration file. For the moment, the Kubernetes API server is the sole provider. Refactor the code to adhere to the new logic. Apply a default configuration on a NotFound error (was previously noted as a TODO in the source code).
Due to recent changes, the two tests can now be safely merged together. The second test verified the overall synchronization, which is now also being exercised in the first test. The tests cases were copied or were already present.
DavidHurta
force-pushed
the
configuration-refactor-and-config-providers
branch
from
06b6212 to
89c4930
Compare
|
@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. |
DavidHurta
changed the title
DavidHurta
changed the title
|
/cc |
|
/uncc |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I want to run a CI. I will likely break up the PR into smaller ones.