Skip to content
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

⚠️ [0.1] Cluster, machine controller: support concurrency #1302

Merged
merged 1 commit into from
Aug 21, 2019

Conversation

ncdc
Copy link
Contributor

@ncdc ncdc commented Aug 21, 2019

What this PR does / why we need it:
Allow the concurrency to be configurable for the cluster and machine controllers. This is a breaking change to the AddWithActuator functions, but it's minor (the addition of a new concurrency parameter). Providers will need to adjust their manager main.go files accordingly (ideally by adding flags to control the concurrency).

I have not dealt with the MachineSet and MachineDeployment controllers in this PR because that requires some more surgery - we'd essentially need to remove the init()-based AddToManagerFuncs approach to make that happen. If there is interest, I can do it, but I think reconciling MachineSets and MachineDeployments one by one is probably ok for now, given that each iteration should be fast compared to single-threading cluster & machine.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

@ncdc ncdc added the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Aug 21, 2019
@ncdc ncdc added this to the v0.1.x milestone Aug 21, 2019
@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Aug 21, 2019
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ncdc

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Aug 21, 2019
@ncdc ncdc changed the title ⚠️ Cluster, machine controller: support concurrency ⚠️ [0.1] Cluster, machine controller: support concurrency Aug 21, 2019
Signed-off-by: Andy Goldstein <goldsteina@vmware.com>
@k8s-ci-robot k8s-ci-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Aug 21, 2019
Copy link
Member

@vincepri vincepri left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Aug 21, 2019
@detiber
Copy link
Member

detiber commented Aug 21, 2019

@ncdc are you planning on adding support for MachineSet/MachineDeployment controllers in a separate PR?

@ncdc
Copy link
Contributor Author

ncdc commented Aug 21, 2019

@detiber see what I wrote above in the description

@k8s-ci-robot k8s-ci-robot merged commit c80f6e5 into kubernetes-sigs:release-0.1 Aug 21, 2019
@ncdc
Copy link
Contributor Author

ncdc commented Aug 21, 2019

Do you want me to do MS & MD too?

@detiber
Copy link
Member

detiber commented Aug 21, 2019

I'm good with skipping MS & MD for now

@vincepri
Copy link
Member

@ncdc Can you open a tracking issue about it? So we won't forget later

@ncdc
Copy link
Contributor Author

ncdc commented Aug 21, 2019

@vincepri I'm doing a PR for master that will cover all the controllers. I can open a 0.1 issues for MS & MD

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants