-
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
Add info about Equinix Metal Reserved hardware usage in the main Readme file. #223
Comments
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
/lifecycle frozen |
It's worth noting the functionality has changed a lot. Machines need to be owned by a cluster now, which makes using the PacketMachine object to do this nearly unmanageable. However, PacketMachineTemplate now supports the reservation IDs, so I'm adding documentation about how you should edit the packetmachinetemplate that clusterctl generates for you. |
Fixed in #409 |
User Story
As a user I would like to see info about Equinix Metal reserved hardware usage with clusterAPI in the main readme description.
Detailed Description
Currently info about reserved hardware usage is located here:
https://github.com/kubernetes-sigs/cluster-api-provider-packet/blob/master/docs/concepts/machine.md#reserved-instances
I would like to see that info in the main readme file along with the addition of info about passing
next-available
to the hardwarereservationID field.Anything else you would like to add:
Not that I can think of.
/kind feature
The text was updated successfully, but these errors were encountered: