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
Device Binding Conditions allow for the setting of BindingConditions and BindingFailureConditions, which help determine if a device needs preparation before proceeding to the Bind Phase.
332
+
This is particularly useful in systems where devices must be attached to nodes. The DRA driver sets these conditions based on the specific characteristics of the device it manages.
333
+
334
+
A key feature is the ability to wait for device attachment during the PreBind Phase.
335
+
The scheduler ensures that all conditions in BindingConditions are met before moving forward.
336
+
This involves updating the ResourceClaim with the necessary conditions and monitoring the status of the device. If a device requires preparation, the DRA driver handles these tasks and updates the conditions accordingly.
337
+
Additionally, if any BindingFailureConditions are met, the system identifies an error and terminates the waiting process.
338
+
339
+
If you want to set a timeout period for waiting during the PreBind phase, you can specify the desired number of seconds in `BindingTimeoutSeconds`.
340
+
Furthermore, by setting `UsageRestrictedToNode` to `true`, you can configure the nodeSelector to match only a single node.
341
+
327
342
## Enabling dynamic resource allocation
328
343
329
344
Dynamic resource allocation is a *beta feature* which is off by default and only enabled when the
@@ -378,6 +393,12 @@ and only enabled when the `DRAResourceClaimDeviceStatus`
0 commit comments