Targeting Array of Reserved Servers

[dsieczko]

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.

[k8s-triage-robot]

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:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[detiber]

/remove-lifecycle stale
/assign

[detiber]

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).

[jhead-slg]

Would be great to get the comma separated support if the v1alpha4 release is still a ways off.

[detiber]

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.