This section documents steps for installing and managing AIStor Volume Manager on Kubernetes infrastructure using a distribution that follows the upstream API and functionality. This procedure assumes that the user interacting with the Kubernetes cluster has authorization to: Install Kubernetes operators and associated resources including CustomResourceDefinitions, Statefulsets, and secrets into new or existing namespaces. Perform operations as a user that has broad permissions to create resources within multiple namespaces. Install Volume Manager using Helm Charts Download your SUBNET license key

The pages in this section help you the various resource types part of a Volume Manager deployment. These resources include: Nodes These are the computing devices to which you directly attach the drives managed by Volume Manager. Drives The physical drives mounted on to nodes. Volumes Volume Manager creates and provisions volumes on drives and assigns the volumes to Persistent Volume Claims. Manage volumes Provision volumes Schedule volumes Schedule by labels

Description List the volumes provisioned and managed by Volume Manager. Syntax kubectl directpv list volumes [VOLUME ...] [flags] You can use the following commands to perform the same functions as kubectl directpv list volumes

Description Suspend volumes and mark as read only. Suspending volumes mounts a volume to an empty temporary directory, allowing a StatefulSet to start up. To resume, use the resume volumes command. Syntax directpv suspend volumes [VOLUME ...] [flags] Parameters Flags While all flags are optional, you must specify at least one drive by ID, name, or node.

Description Uninstall Volume Manager from the kubernetes cluster. Syntax kubectl directpv uninstall [flags] Parameters Global Flags You can use the following global Volume Manager flags with kubectl directpv uninstall:

Administration

An Enclave is an isolated collection of cryptographic keys. This provides a means to separate groups of keys stored in Key Manager, such as all of the keys for a specific object store. MinIO recommends a separate enclave for each object store. AIStor KMS can host as many different enclaves as needed. Access to enclaves are restricted to identities created for the enclave. In this way, AIStor prevents identities for one object store’s enclave from accessing the keys or secrets for a different object store’s enclave.

Overview Outputs either audit logs or error logs. The output logs the time, status, identity, IP, endpoint, and latency of each request. Logs continue to output until you stop the process. The output resembles the following: Time Status Identity IP API Latency 14:07:15 404 3ecfcdf38fcbe141ae26 8.8.8.8 /v1/key/decrypt/my-first-key 142µs 14:07:38 200 3ecfcdf38fcbe141ae26 8.7.8.7 /v1/key/decrypt/minio-sse-key 299µs Syntax kes log \ [--audit] \ [--error] \ [--insecure, -k] \ [--json] Parameters --audit Outputs audit logs.

This section provides guidance around recommended hardware configurations in production AIStor Server deployments. Hardware Recommendations The following checklist follows our Recommended Configuration for each physical or virtual host supporting the AIStor Server deployment. Use the Erasure Code Calculator to provide baseline guidance for the number of hosts and drives necessary to meet your storage and availability requirements.

Kes