Show / Hide Table of Contents

Class V1ResourceClaimStatus

ResourceClaimStatus tracks whether the resource has been allocated and what the result of that was.

Inheritance
object
V1ResourceClaimStatus
Implements
IEquatable<V1ResourceClaimStatus>
Inherited Members
object.GetType()
object.MemberwiseClone()
object.Equals(object, object)
object.ReferenceEquals(object, object)
Namespace: k8s.Models
Assembly: KubernetesClient.dll
Syntax
public record V1ResourceClaimStatus : IEquatable<V1ResourceClaimStatus>

Constructors

V1ResourceClaimStatus()

Declaration
public V1ResourceClaimStatus()

V1ResourceClaimStatus(V1ResourceClaimStatus)

Declaration
protected V1ResourceClaimStatus(V1ResourceClaimStatus original)
Parameters
Type Name Description
V1ResourceClaimStatus original

Properties

Allocation

Allocation is set once the claim has been allocated successfully.

Declaration
[JsonPropertyName("allocation")]
public V1AllocationResult Allocation { get; set; }
Property Value
Type Description
V1AllocationResult

Devices

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.

Declaration
[JsonPropertyName("devices")]
public IList<V1AllocatedDeviceStatus> Devices { get; set; }
Property Value
Type Description
IList<V1AllocatedDeviceStatus>

EqualityContract

Declaration
protected virtual Type EqualityContract { get; }
Property Value
Type Description
Type

ReservedFor

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.

Declaration
[JsonPropertyName("reservedFor")]
public IList<V1ResourceClaimConsumerReference> ReservedFor { get; set; }
Property Value
Type Description
IList<V1ResourceClaimConsumerReference>

Methods

Equals(object?)

Declaration
public override bool Equals(object? obj)
Parameters
Type Name Description
object obj
Returns
Type Description
bool
Overrides
object.Equals(object)

Equals(V1ResourceClaimStatus?)

Declaration
public virtual bool Equals(V1ResourceClaimStatus? other)
Parameters
Type Name Description
V1ResourceClaimStatus other
Returns
Type Description
bool

GetHashCode()

Declaration
public override int GetHashCode()
Returns
Type Description
int
Overrides
object.GetHashCode()

PrintMembers(StringBuilder)

Declaration
protected virtual bool PrintMembers(StringBuilder builder)
Parameters
Type Name Description
StringBuilder builder
Returns
Type Description
bool

ToString()

Declaration
public override string ToString()
Returns
Type Description
string
Overrides
object.ToString()

Operators

operator ==(V1ResourceClaimStatus?, V1ResourceClaimStatus?)

Declaration
public static bool operator ==(V1ResourceClaimStatus? left, V1ResourceClaimStatus? right)
Parameters
Type Name Description
V1ResourceClaimStatus left
V1ResourceClaimStatus right
Returns
Type Description
bool

operator !=(V1ResourceClaimStatus?, V1ResourceClaimStatus?)

Declaration
public static bool operator !=(V1ResourceClaimStatus? left, V1ResourceClaimStatus? right)
Parameters
Type Name Description
V1ResourceClaimStatus left
V1ResourceClaimStatus right
Returns
Type Description
bool

Implements

IEquatable<T>
In this article
Back to top Generated by DocFX