kubernetes_asyncio.client.models.v1_resource_claim_status module
Kubernetes
No description provided (generated by Openapi Generator https://github.com/openapitools/openapi-generator) # noqa: E501
The version of the OpenAPI document: v1.34.3 Generated by: https://openapi-generator.tech
- class kubernetes_asyncio.client.models.v1_resource_claim_status.V1ResourceClaimStatus(allocation=None, devices=None, reserved_for=None, local_vars_configuration=None)
Bases:
objectNOTE: This class is auto generated by OpenAPI Generator. Ref: https://openapi-generator.tech
Do not edit the class manually.
- property allocation
Gets the allocation of this V1ResourceClaimStatus. # noqa: E501
- Returns:
The allocation of this V1ResourceClaimStatus. # noqa: E501
- Return type:
- attribute_map = {'allocation': 'allocation', 'devices': 'devices', 'reserved_for': 'reservedFor'}
- property devices
Gets the devices of this V1ResourceClaimStatus. # noqa: E501
Devices contains the status of each device allocated for this claim, as reported by the driver. This can include driver-specific information. Entries are owned by their respective drivers. # noqa: E501
- Returns:
The devices of this V1ResourceClaimStatus. # noqa: E501
- Return type:
list[V1AllocatedDeviceStatus]
- openapi_types = {'allocation': 'V1AllocationResult', 'devices': 'list[V1AllocatedDeviceStatus]', 'reserved_for': 'list[V1ResourceClaimConsumerReference]'}
- property reserved_for
Gets the reserved_for of this V1ResourceClaimStatus. # noqa: E501
ReservedFor indicates which entities are currently allowed to use the claim. A Pod which references a ResourceClaim which is not reserved for that Pod will not be started. A claim that is in use or might be in use because it has been reserved must not get deallocated. In a cluster with multiple scheduler instances, two pods might get scheduled concurrently by different schedulers. When they reference the same ResourceClaim which already has reached its maximum number of consumers, only one pod can be scheduled. Both schedulers try to add their pod to the claim.status.reservedFor field, but only the update that reaches the API server first gets stored. The other one fails with an error and the scheduler which issued it knows that it must put the pod back into the queue, waiting for the ResourceClaim to become usable again. There can be at most 256 such reservations. This may get increased in the future, but not reduced. # noqa: E501
- Returns:
The reserved_for of this V1ResourceClaimStatus. # noqa: E501
- Return type:
- to_dict(serialize=False)
Returns the model properties as a dict
- to_str()
Returns the string representation of the model