Description Show overall information about the Volume Manager installation in the cluster Syntax directpv info [flags] Parameters Global Flags You can use the following global Volume Manager flags with kubectl directpv info:

AIStor Key Manager supports installation on to Linux and Kubernetes infrastructures. Key Manager Requires TLS Encryption Key Manager requires using TLS for all connections to ensure complete security of transmitted cryptographic data. For production environments, generate certificates signed by a trusted or managed Certificate Authority. If the CA is internal, private, or otherwise not typically included in a Global Trust List, the full chain of CA certificates must be available for facilitating TLS validation.

Overview Import a cryptographic key. Syntax kes key import \ <name> \ <key> \ [--insecure, -k] Parameters name Required

Description Cordoning drives makes them unschedulable. Volume Manager does not schedule volumes on drives that have been cordoned. Use kubectl directpv uncordon to make cordoned drives accessible for scheduling again. Syntax kubectl directpv cordon [DRIVE ...] [flags] Parameters kubectl directpv cordon requires a way to define the drive(s) to cordon. The command does not require any specific parameter. All parameters are optional, as long as you include a way to select one or more drives in the command.

Updating Custom Installations Custom installations do not support client-side upgrade functionality. Use kubectl directpv migrate to migrate the old resources to a new installation. Pod Security Policies Kubernetes deprecated the PodSecurityPolicy feature in v1.21, then removed it entirely in v1.25. Use Pod Security Admission as a replacement, as recommended in the Kubernetes documentation.

Description Use this command to discover the block devices present in the cluster. The command outputs a yaml file listing the available drives. After generating the yaml, modify the file to select the drive(s) you wish to use with Volume Manager. Ensure that any drives that should not be erased by Volume Manager have not been selected in the yaml file.

The mc idp ldap policy detach command detaches one or more polices from an entity. Syntax Example The following example detaches the policy userpolicy from the user bobfisher on the myaistor deployment.

Required release version This command is available in AIStor Client RELEASE.2025-03-31T22-38-30Z or later. The functionality requires AIStor RELEASE.2025-03-27T23-09-45Z or later. The mc idp ldap accesskey sts-revoke command removes security token service (sts) credentials associated with an account. Revoke all STS tokens for an account, or specify the type(s) of STS tokens to revoke for an account.

This page summarizes how a DELETE operation affects objects depending on the configuration of the bucket that contains the object. Any combination of the following factors may impact how DELETE operations function: Bucket versioning Object locking rules Object Lifecycle Management rules Object tiering Site or bucket replication Scanner Permissions AIStor uses a policy based access control system for access management. The user or service account must provide the correct policy action and conditions to allow a DELETE for the bucket and object.

Overview AIStor supports keeping multiple “versions” of an object in a single bucket. When enabled, versioning allows AIStor to keep multiple iterations of the same object. Write operations which would normally overwrite an existing object instead result in the creation of a new version of the object. AIStor versioning protects from unintended overwrites and deletions while providing support for “undoing” a write operation. Bucket versioning is a prerequisite for configuring object locking and retention rules.