-
Notifications
You must be signed in to change notification settings - Fork 41
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
Targeting Array of Reserved Servers #255
Comments
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
Taking a look at this now, I'm thinking of just adding support for comma separated reservation ids for now to the existing field for now to avoid changing up the API at this point, but will likely look to clean up the API down the line (possibly along with the larger rebranding effort for the provider). |
Would be great to get the comma separated support if the v1alpha4 release is still a ways off. |
I've created a PR for backporting the changes to v0.3.x, and am currently working on some initial validation of the changes now. |
User has reserved servers of both a stock configuration and a stock configuration that's been customized, in this case an m3.large.x86.
In order to avoid having a machine provision into an incorrect node pool, a user needs to pass a list of reservation ids, and not use
next-available
. Line 51 in packetmachine_types.go..Currently, Cluster API only supports a string, single reservation ID or
next-available.
This would need to be updated to support lists.This behavior can also help distribute reserved servers deliberately across a data center to better support things like BGP ECMP load balancing.
The text was updated successfully, but these errors were encountered: