Structs

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.

CSIDriverSpec is the specification of a CSIDriver.

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.

CSINodeDriver holds information about the specification of one CSI driver installed on a node

CSINodeSpec holds information about the specification of all CSI drivers installed on a node

StorageClass describes the parameters for a class of storage for which PersistentVolumes can be dynamically provisioned.

TokenRequest contains parameters of a service account token.

VolumeAttachment captures the intent to attach or detach the specified volume to/from the specified node.

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.

VolumeAttachmentSpec is the specification of a VolumeAttachment request.

VolumeAttachmentStatus is the status of a VolumeAttachment request.

VolumeError captures an error encountered during a volume operation.

VolumeNodeResources is a set of resource limits for scheduling of volumes.

Enums

Use <ReadCSIDriverResponse as Response>::try_from_parts to parse the HTTP response body of CSIDriver::read_csi_driver

Use <ReadCSINodeResponse as Response>::try_from_parts to parse the HTTP response body of CSINode::read_csi_node

Use <ReadStorageClassResponse as Response>::try_from_parts to parse the HTTP response body of StorageClass::read_storage_class

Use <ReadVolumeAttachmentResponse as Response>::try_from_parts to parse the HTTP response body of VolumeAttachment::read_volume_attachment

Use <ReadVolumeAttachmentStatusResponse as Response>::try_from_parts to parse the HTTP response body of VolumeAttachment::read_volume_attachment_status