You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the solution you'd like
Currently, we choose the first HetznerBareMetalHost of the list that fits the criteria. This leads to the fact that a host might be chosen that does not have rootDeviceHints set. This is not a problem per se, as the user will get the necessary information printed in the status of HetznerBareMetalHost and can use it to specify the rootDeviceHints.
However, this is not optimal in the case where other HetznerBareMetalHosts are available that have the rootDeviceHints specified. The provisioning of those hosts is naturally faster than if the user has to do some manual work.
Therefore, I propose to choose those HetznerBareMetalHosts first that have the rootDeviceHints specified.
The text was updated successfully, but these errors were encountered:
/kind feature
Describe the solution you'd like
Currently, we choose the first
HetznerBareMetalHost
of the list that fits the criteria. This leads to the fact that a host might be chosen that does not haverootDeviceHints
set. This is not a problem per se, as the user will get the necessary information printed in the status ofHetznerBareMetalHost
and can use it to specify therootDeviceHints
.However, this is not optimal in the case where other
HetznerBareMetalHosts
are available that have therootDeviceHints
specified. The provisioning of those hosts is naturally faster than if the user has to do some manual work.Therefore, I propose to choose those
HetznerBareMetalHosts
first that have therootDeviceHints
specified.The text was updated successfully, but these errors were encountered: