-
Notifications
You must be signed in to change notification settings - Fork 231
Allow to enable/disable machine healtch-check controller #291
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 to enable/disable machine healtch-check controller #291
Conversation
|
/test integration |
Machine-api-operator controller will watch FeatureGate resources and update the deployment accordingly. Currently the only one feature that can be enabled via the FeatureGate object is MachineHealthCheck. To enable it you will need to create FeatureGate object with the content: ```yaml apiVersion: config.openshift.io/v1 kind: FeatureGate metadata: name: machine-api spec: featureSet: "TechPreviewNoUpgrade" ```
By running 'dep ensure'
ebb547e to
74246b7
Compare
|
@cynepco3hahue PTAL, I have integrated your feature gate PR, modified it a bit, added unit tests. |
|
/retest |
|
@ingvagabund: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. DetailsInstructions 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. |
|
/test e2e-aws |
|
/lgtm |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: michaelgugino The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
So we can use feature gate mechanism to enable/disable the controller.
One needs to deploy:
to enable the HC deployment. Tested through unit tests where a fake clientset with the feature gate is provided.
Feature gate building pieces took from #279