pulumi-kubernetes-kotlin/com.pulumi.kubernetes.resource.v1alpha3.kotlin.inputs/DeviceRequestArgsBuilder/firstAvailable

firstAvailable

@JvmName(name = "novlnvjhyaagwkxh")
suspend fun firstAvailable(value: Output<List<DeviceSubRequestArgs>>)
@JvmName(name = "cysllsufsnjraqph")
suspend fun firstAvailable(value: List<DeviceSubRequestArgs>?)

Parameters

value

FirstAvailable contains subrequests, of which exactly one will be satisfied by the scheduler to satisfy this request. It tries to satisfy them in the order in which they are listed here. So if there are two entries in the list, the scheduler will only check the second one if it determines that the first one cannot be used. This field may only be set in the entries of DeviceClaim.Requests. DRA does not yet implement scoring, so the scheduler will select the first set of devices that satisfies all the requests in the claim. And if the requirements can be satisfied on more than one node, other scheduling features will determine which node is chosen. This means that the set of devices allocated to a claim might not be the optimal set available to the cluster. Scoring will be implemented later.

@JvmName(name = "mcblaxfbvywtiikf")
suspend fun firstAvailable(vararg values: Output<DeviceSubRequestArgs>)

@JvmName(name = "raggcfhuyjaemotu")
suspend fun firstAvailable(values: List<Output<DeviceSubRequestArgs>>)
@JvmName(name = "ljyhuyvjhioxtxfx")
suspend fun firstAvailable(vararg values: DeviceSubRequestArgs)

Parameters

values

FirstAvailable contains subrequests, of which exactly one will be satisfied by the scheduler to satisfy this request. It tries to satisfy them in the order in which they are listed here. So if there are two entries in the list, the scheduler will only check the second one if it determines that the first one cannot be used. This field may only be set in the entries of DeviceClaim.Requests. DRA does not yet implement scoring, so the scheduler will select the first set of devices that satisfies all the requests in the claim. And if the requirements can be satisfied on more than one node, other scheduling features will determine which node is chosen. This means that the set of devices allocated to a claim might not be the optimal set available to the cluster. Scoring will be implemented later.

@JvmName(name = "rmfdlhswxksuilve")
suspend fun firstAvailable(argument: List<suspend DeviceSubRequestArgsBuilder.() -> Unit>)
@JvmName(name = "vkhghhitexphcnid")
suspend fun firstAvailable(vararg argument: suspend DeviceSubRequestArgsBuilder.() -> Unit)
@JvmName(name = "cvmtoauqslikocta")
suspend fun firstAvailable(argument: suspend DeviceSubRequestArgsBuilder.() -> Unit)

Parameters

argument

FirstAvailable contains subrequests, of which exactly one will be satisfied by the scheduler to satisfy this request. It tries to satisfy them in the order in which they are listed here. So if there are two entries in the list, the scheduler will only check the second one if it determines that the first one cannot be used. This field may only be set in the entries of DeviceClaim.Requests. DRA does not yet implement scoring, so the scheduler will select the first set of devices that satisfies all the requests in the claim. And if the requirements can be satisfied on more than one node, other scheduling features will determine which node is chosen. This means that the set of devices allocated to a claim might not be the optimal set available to the cluster. Scoring will be implemented later.