-
Notifications
You must be signed in to change notification settings - Fork 172
Create a default HNCConfiguration singleton when starting HNC if the singleton does not exist #471
Create a default HNCConfiguration singleton when starting HNC if the singleton does not exist #471
Conversation
…singleton does not exist This PR creates a default HNCConfiguration singleton when starting HNC if the singleton does not exist. The feature is achieved by adding a channel in reconciler watch to trigger the reconciliation at startup. The reconciliation will ensure the default singleton will be created if it does not exist. Tested: GKE cluster; unit tests. Design doc: http://bit.ly/hnc-type-configuration Issue: kubernetes-retired#411
Hi @sophieliu15. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
This PR adds Conditions in HNCConfiguration.Status to indicate error scenarios. Condition specifies error code and message for a specific error. Currently we support following error code: - critSingletonNameInvalid: the specified singleton name is invalid. - objectReconcilerCreationFailed: an error exists when creating the object reconciler for a specific type. This PR includes changes introduced in kubernetes-retired#471 Tested: GKE cluster; unit tests. Design doc: http://bit.ly/hnc-type-configuration Issue: kubernetes-retired#411
This PR adds Conditions in HNCConfiguration.Status to indicate error scenarios. Condition specifies error code and message for a specific error. Currently we support following error code: - critSingletonNameInvalid: the specified singleton name is invalid. - objectReconcilerCreationFailed: an error exists when creating the object reconciler for a specific type. This PR includes changes introduced in kubernetes-retired#471 Tested: GKE cluster; unit tests. Design doc: http://bit.ly/hnc-type-configuration Issue: kubernetes-retired#411
/ok-to-test |
Hi @rjbez17 Feel free to take a look at this PR when you have time. Adrian and Yiqi did the first round of the code review. Since I have a chain of PRs for review, it would be great if we can merge this in to reduce the code review burden for subsequent PRs. Thanks so much for your help! Sophie |
/lgtm |
@sophieliu15: 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. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: adrianludwin, rjbez17, sophieliu15 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 |
/hold Holding it since #462 that contained changes in this PR was already merged. We should probably consider close this PR. |
Close this PR because the changes are already merged in #462 |
1 similar comment
Close this PR because the changes are already merged in #462 |
This PR creates a default HNCConfiguration singleton when starting HNC if the singleton does not exist. The feature is achieved by adding a channel in reconciler watch to trigger the reconciliation at startup. The reconciliation will ensure the default singleton will be created if it does not exist.
Tested: GKE cluster; unit tests.
Design doc: http://bit.ly/hnc-type-configuration
Issue: #411