-
Notifications
You must be signed in to change notification settings - Fork 159
Add Flag to Driver for Controller or Node Mode #34
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
Comments
Could potentially also look into building them into separate binaries too |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
/lifecycle frozen |
#449 fixed it. |
@Jiawei0227: Closing this issue. In response to this:
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. |
/open Shouldn't we actually use this flag as well to not run the controller on the node pods? |
Yep. I thought this issue is about adding the flag. We can use the issue to track changing the deployment for sure. |
SG, I started #702.
…On Thu, Feb 4, 2021 at 7:04 PM Jiawei Wang ***@***.***> wrote:
Yep. I thought this issue is about adding the flag. We can use the issue
to track changing the deployment for sure.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#34 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIJCBAG525I7CC7TLMKY2O3S5NN5TANCNFSM4FHPRKJQ>
.
|
OCPBUGS-11000: UPSTREAM: 988: Simplify node backoff logic
Add a flag
--node
to turn on the node server,--controller
to turn on the controller server. They should both default to false.Currently every driver runs all the node, controller, and identity servers by default.
The text was updated successfully, but these errors were encountered: