PersistentVolumeClaimSpec class

PersistentVolumeClaimSpec describes the common attributes of storage devices and allows a Source for provider-specific attributes.

Constructors

PersistentVolumeClaimSpec({List<String>? accessModes, TypedLocalObjectReference? dataSource, TypedObjectReference? dataSourceRef, ResourceRequirements? resources, LabelSelector? selector, String? storageClassName, String? volumeMode, String? volumeName})

Default constructor.

const

PersistentVolumeClaimSpec.fromJson(Map<String, dynamic> json)

Creates a PersistentVolumeClaimSpec from JSON data.

factory

Properties

accessModes → List<String>?

accessModes contains the desired access modes the volume should have. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#access-modes-1.

final

dataSource → TypedLocalObjectReference?

dataSource field can be used to specify either: * An existing VolumeSnapshot object (snapshot.storage.k8s.io/VolumeSnapshot) * An existing PVC (PersistentVolumeClaim) If the provisioner or an external controller can support the specified data source, it will create a new volume based on the contents of the specified data source. When the AnyVolumeDataSource feature gate is enabled, dataSource contents will be copied to dataSourceRef, and dataSourceRef contents will be copied to dataSource when dataSourceRef.namespace is not specified. If the namespace is specified, then dataSourceRef will not be copied to dataSource.

final

dataSourceRef → TypedObjectReference?

dataSourceRef specifies the object from which to populate the volume with data, if a non-empty volume is desired. This may be any object from a non-empty API group (non core object) or a PersistentVolumeClaim object. When this field is specified, volume binding will only succeed if the type of the specified object matches some installed volume populator or dynamic provisioner. This field will replace the functionality of the dataSource field and as such if both fields are non-empty, they must have the same value. For backwards compatibility, when namespace isn't specified in dataSourceRef, both fields (dataSource and dataSourceRef) will be set to the same value automatically if one of them is empty and the other is non-empty. When namespace is specified in dataSourceRef, dataSource isn't set to the same value and must be empty. There are three important differences between dataSource and dataSourceRef: * While dataSource only allows two specific types of objects, dataSourceRef allows any non-core object, as well as PersistentVolumeClaim objects.

final

hashCode → int

The hash code for this object.

no setter, inherited

resources → ResourceRequirements?

resources represents the minimum resources the volume should have. If RecoverVolumeExpansionFailure feature is enabled users are allowed to specify resource requirements that are lower than previous value but must still be higher than capacity recorded in the status field of the claim. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#resources.

final

runtimeType → Type

A representation of the runtime type of the object.

no setter, inherited

selector → LabelSelector?

selector is a label query over volumes to consider for binding.

final

storageClassName → String?

storageClassName is the name of the StorageClass required by the claim. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#class-1.

final

volumeMode → String?

volumeMode defines what type of volume is required by the claim. Value of Filesystem is implied when not included in claim spec.

final

volumeName → String?

volumeName is the binding reference to the PersistentVolume backing this claim.

final

Methods

noSuchMethod(Invocation invocation) → dynamic

Invoked when a nonexistent method or property is accessed.

inherited

toJson() → Map<String, Object>

Converts a PersistentVolumeClaimSpec instance to JSON data.

toString() → String

A string representation of this object.

inherited

Operators

operator ==(Object other) → bool

The equality operator.

inherited