Overview Volume Manager provisions drives for pods that provide a PersistentVolumeClaim for the Volume Manager storage class. Volume Manager includes a storage class named directpv-min-io with volume binding mode WaitForFirstConsumer. This mode delays volume binding and provisioning of a PersistentVolume until the creation of a Pod using the PersistentVolumeClaim. Volume Manager then selects or provisions PersistentVolumes that match the topology specified in the Pod’s scheduling constraints.

Prerequisites Working Volume Manager plugin. To install the plugin, refer to the plugin installation guide. Working Volume Manager CSI driver in Kubernetes. To install the driver, refer to the driver installation guide. Added drives in Volume Manager. Refer to the drive management guide.

Driver Specification CSIDriver Key Value name directpv-min-io fsGroupPolicy ReadWriteOnceWithFSType requiresRepublish false podInfoOnMount true attachRequired false storageCapacity false modes Persistent, Ephemeral StorageClass Key Value name directpv-min-io provisioner directpv-min-io reclaimPolicy Delete allowVolumeExpansion true volumeBindingMode WaitForFirstConsumer Volume ManagerDrives CRD Key Value name directpvdrives apigroup directpv.min.io Volume ManagerVolumes CRD Key Value name directpvvolumes apigroup directpv.min.io Volume ManagerNodes CRD Key Value name directpvnodes apigroup directpv.min.io Volume ManagerInitRequests CRD Key Value name directpvinitrequests apigroup directpv.min.io Driver Role Based Access Control (RBAC) apiGroup Resources Verbs (core) endpoints get, list, watch, create, update, delete (core) events list, watch, create, update, patch (core) nodes get, list, watch (core) persistentvolumes get, list, watch, create, delete (core) persistentvolumeclaims get, list, watch, update (core) pods,pod get, list, watch policy podsecuritypolicies use apiextensions.k8s.io customresourcedefinitions get, list, watch, create, update, delete coordination.k8s.io leases get, list, watch, update, delete, create directpv.min.io directpvdrives get, list, watch, create, update, delete directpv.min.io directpvvolumes get, list, watch, create, update, delete directpv.min.io directpvnodes get, list, watch, create, update, delete directpv.min.io directpvinitrequests get, list, watch, create, update, delete snapshot.storage.k8s.io volumesnapshotcontents get, list snapshot.storage.k8s.io volumesnapshots get, list storage.k8s.io csinodes get, list, watch storage.k8s.io storageclasses get, list, watch storage.k8s.io volumeattachments get, list, watch The service account bound to the above clusterrole is directpv-min-io in the directpv namespace and the corresponding clusterrolebinding is directpv-min-io

Prerequisites Working Volume Manager plugin. To install the plugin, refer to the plugin installation guide. Working Volume Manager CSI driver in Kubernetes. To install the driver, refer to the driver installation guide. Drives Add drives Volume Manager must have access to drives to provision volumes. This involves a two step process:

Prerequisites Working Volume Manager plugin To install the plugin, refer to the plugin installation guide. Working Volume Manager CSI driver in Kubernetes To install the driver, refer to the driver installation guide. Add node Add a node to the Volume Manager DaemonSet, then run the discover command.

Description Remove unused drives from Volume Manager. Syntax directpv remove [DRIVE ...] [flags] Parameters Flags Flag Description --dry-run See the results of the command without making any actual changes to drives. -n, --nodes <string> Select drives from specified node(s). Use ellipsis expansion notation, such as node{1...10}. -d, --drives <string> Select drives by given names. Use ellipsis expansion notation, such as sd{a...z}. --status <string> Select drives by drive status. Valid statuses are error, lost, moving, ready, or removed. --all If present, select all unused drives Global Flags Flag Description --kubeconfig <string> Path to the kube.config file to use for CLI requests --quiet Suppress printing error messages Examples Remove an unused drive from all nodes The following command removes a drive named nvme1n1 found on any node.

What type of disks are recommended for Volume Manager? Volume Manager is specifically meant for Direct Attached Storage such as hard drives and solid-state drives in a “JBOD” configuration (Just a Bunch of Disks).

AIStor Key Manager supports installation onto Upstream Kubernetes and Red Hat OpenShift infrastructures. The Upstream instructions work for any Kubernetes flavor that maintains a strict implementation of the native Kubernetes API and behaviors.

Overview The kes key command creates, utilizes, displays, and deletes cryptographic keys (Secrets) through the AIStor Key Encryption Service (KES). KES stores created secrets on the configured Key Management System (KMS) target. You can also use these commands to encrypt/decrypt messages or generate new data encryption keys.

AIStor Key Manager controls access through a combination of Enclaves and Identities. Enclaves An Enclave is an isolated namespace in which Key Manager stores cryptographic keys. A single Key Manager instance can have multiple enclaves, where a user with access to one enclave cannot perform operations on another.