io.k8s.api.storage.v1
Type members
Classlikes
CSIDriver captures information about a Container Storage Interface (CSI) volume driver deployed on the cluster. Kubernetes attach detach controller uses this object to determine whether attach is required. Kubelet uses this object to determine whether pod information needs to be passed on mount. CSIDriver objects are non-namespaced.
CSIDriver captures information about a Container Storage Interface (CSI) volume driver deployed on the cluster. Kubernetes attach detach controller uses this object to determine whether attach is required. Kubelet uses this object to determine whether pod information needs to be passed on mount. CSIDriver objects are non-namespaced.
- Companion:
- object
- Source:
- CSIDriver.scala
CSIDriverList is a collection of CSIDriver objects.
CSIDriverList is a collection of CSIDriver objects.
- Companion:
- object
- Source:
- CSIDriverList.scala
CSIDriverSpec is the specification of a CSIDriver.
CSIDriverSpec is the specification of a CSIDriver.
- Companion:
- object
- Source:
- CSIDriverSpec.scala
CSINode holds information about all CSI drivers installed on a node. CSI drivers do not need to create the CSINode object directly. As long as they use the node-driver-registrar sidecar container, the kubelet will automatically populate the CSINode object for the CSI driver as part of kubelet plugin registration. CSINode has the same name as a node. If the object is missing, it means either there are no CSI Drivers available on the node, or the Kubelet version is low enough that it doesn't create this object. CSINode has an OwnerReference that points to the corresponding node object.
CSINode holds information about all CSI drivers installed on a node. CSI drivers do not need to create the CSINode object directly. As long as they use the node-driver-registrar sidecar container, the kubelet will automatically populate the CSINode object for the CSI driver as part of kubelet plugin registration. CSINode has the same name as a node. If the object is missing, it means either there are no CSI Drivers available on the node, or the Kubelet version is low enough that it doesn't create this object. CSINode has an OwnerReference that points to the corresponding node object.
- Companion:
- object
- Source:
- CSINode.scala
CSINodeDriver holds information about the specification of one CSI driver installed on a node
CSINodeDriver holds information about the specification of one CSI driver installed on a node
- Companion:
- object
- Source:
- CSINodeDriver.scala
CSINodeList is a collection of CSINode objects.
CSINodeList is a collection of CSINode objects.
- Companion:
- object
- Source:
- CSINodeList.scala
CSINodeSpec holds information about the specification of all CSI drivers installed on a node
CSINodeSpec holds information about the specification of all CSI drivers installed on a node
- Companion:
- object
- Source:
- CSINodeSpec.scala
CSIStorageCapacity stores the result of one CSI GetCapacity call. For a given StorageClass, this describes the available capacity in a particular topology segment. This can be used when considering where to instantiate new PersistentVolumes.
CSIStorageCapacity stores the result of one CSI GetCapacity call. For a given StorageClass, this describes the available capacity in a particular topology segment. This can be used when considering where to instantiate new PersistentVolumes.
For example this can express things like: - StorageClass "standard" has "1234 GiB" available in "topology.kubernetes.io/zone=us-east1" - StorageClass "localssd" has "10 GiB" available in "kubernetes.io/hostname=knode-abc123"
The following three cases all imply that no capacity is available for a certain combination: - no object exists with suitable topology and storage class name - such an object exists, but the capacity is unset - such an object exists, but the capacity is zero
The producer of these objects can decide which approach is more suitable.
They are consumed by the kube-scheduler when a CSI driver opts into capacity-aware scheduling with CSIDriverSpec.StorageCapacity. The scheduler compares the MaximumVolumeSize against the requested size of pending volumes to filter out unsuitable nodes. If MaximumVolumeSize is unset, it falls back to a comparison against the less precise Capacity. If that is also unset, the scheduler assumes that capacity is insufficient and tries some other node.
- Companion:
- object
- Source:
- CSIStorageCapacity.scala
CSIStorageCapacityList is a collection of CSIStorageCapacity objects.
CSIStorageCapacityList is a collection of CSIStorageCapacity objects.
- Companion:
- object
- Source:
- CSIStorageCapacityList.scala
StorageClass describes the parameters for a class of storage for which PersistentVolumes can be dynamically provisioned.
StorageClass describes the parameters for a class of storage for which PersistentVolumes can be dynamically provisioned.
StorageClasses are non-namespaced; the name of the storage class according to etcd is in ObjectMeta.Name.
- Companion:
- object
- Source:
- StorageClass.scala
StorageClassList is a collection of storage classes.
StorageClassList is a collection of storage classes.
- Companion:
- object
- Source:
- StorageClassList.scala
TokenRequest contains parameters of a service account token.
TokenRequest contains parameters of a service account token.
- Companion:
- object
- Source:
- TokenRequest.scala
VolumeAttachment captures the intent to attach or detach the specified volume to/from the specified node.
VolumeAttachment captures the intent to attach or detach the specified volume to/from the specified node.
VolumeAttachment objects are non-namespaced.
- Companion:
- object
- Source:
- VolumeAttachment.scala
VolumeAttachmentList is a collection of VolumeAttachment objects.
VolumeAttachmentList is a collection of VolumeAttachment objects.
- Companion:
- object
- Source:
- VolumeAttachmentList.scala
VolumeAttachmentSource represents a volume that should be attached. Right now only PersistenVolumes can be attached via external attacher, in future we may allow also inline volumes in pods. Exactly one member can be set.
VolumeAttachmentSource represents a volume that should be attached. Right now only PersistenVolumes can be attached via external attacher, in future we may allow also inline volumes in pods. Exactly one member can be set.
- Companion:
- object
- Source:
- VolumeAttachmentSource.scala
VolumeAttachmentSpec is the specification of a VolumeAttachment request.
VolumeAttachmentSpec is the specification of a VolumeAttachment request.
- Companion:
- object
- Source:
- VolumeAttachmentSpec.scala
VolumeAttachmentStatus is the status of a VolumeAttachment request.
VolumeAttachmentStatus is the status of a VolumeAttachment request.
- Companion:
- object
- Source:
- VolumeAttachmentStatus.scala
VolumeError captures an error encountered during a volume operation.
VolumeError captures an error encountered during a volume operation.
- Companion:
- object
- Source:
- VolumeError.scala
VolumeNodeResources is a set of resource limits for scheduling of volumes.
VolumeNodeResources is a set of resource limits for scheduling of volumes.
- Companion:
- object
- Source:
- VolumeNodeResources.scala