-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Consider using remote.NodeProviderIDIndex in MachinePool controller #8856
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
/help wanted |
/triage accepted |
That seems reasonable. I'll take a look once I'm wrapped up with the DockerMachinePool Machines implementation. |
/kind cleanup |
opened a PR for this, per @sbueringer closing this as "won't do" /close |
@cahillsf: 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-sigs/prow repository. |
Thx for working on this! Sorry should have realized this earlier :) |
np 👍 |
The MachinePool controller currently looks for specific node references by first looping through all of the nodes in the cluster and then checking to see if the ProviderID is among those listed on the MachinePool object.
This could be made more efficient by using the
remote.NodeProviderIDIndex
which is how the Machine controller currently looks up nodes by provider ID.Doing this would require refactoring the code in the MachinePool controller's
getNodeReferences
:cluster-api/exp/internal/controllers/machinepool_controller_noderef.go
Line 155 in 051b006
To look more like the Machine controller implementation and use
index.NodeProviderIDField
cluster-api/internal/controllers/machine/machine_controller_noderef.go
Line 196 in f62294e
/help-wanted
/area machinepool
The text was updated successfully, but these errors were encountered: