The mc idp openid update command modifies an existing set of configurations for an OIDC provider. Example and syntax Example The following example changes two of the configuration settings for the myaistor deployment as defined in the test-config setup for Dex integration.

The mc retention clear command removes the Write-Once Read-Many (WORM) locking settings for an object or object(s) in a bucket. You can also remove the default object lock settings for a bucket. To change the retention status of an object under legal hold, use mc legalhold clear. Syntax Example The following command removes the default object lock configuration for the mydata bucket on the myaistor AIStor deployment:

Remove an existing set of configurations for an OIDC provider. Example and syntax Example The following example removes the oidc-config settings for the myaistor deployment.

The mc mirror command synchronizes content to an AIStor deployment, similar to the rsync utility. mc mirror supports filesystems, AIStor deployments, and other S3-compatible hosts as the synchronization source. The target synchronization site file names are normalized using the shortest equivalent name. For example, s3/miniocloud//this/./object becomes miniocloud-backup/this/object. mc mirror only synchronizes the current object without any version information or metadata other than tags. To synchronize an object’s version history and other metadata, consider using mc replicate for bucket replication or mc admin replicate for site replication.

The mc ping command performs a liveness check on a specified target. Syntax Example The following sends a response request to the target(s) and outputs the minimum, maximum, average, and roundtrip times of the response, as well as the number of errors encountered when processing the request.

The mc replicate command configures and manages per-bucket Server-Side Bucket Replication for an AIStor deployment, including active-active replication configurations and resynchronization. For site-level replication, see mc admin replicate. Subcommands mc replicate includes the following subcommands: Subcommand Description add Create a new server-side replication rule for a bucket on an AIStor deployment. backlog Show a list of unreplicated new or deleted objects. export Export the JSON-formatted replication rules for an AIStor bucket to STDOUT. import Import JSON-formatted replication rules for an AIStor bucket from STDIN. ls List all replication rules on an AIStor bucket. resync Resynchronize all objects in the specified AIStor bucket to a remote replication target. rm Remove a replication rule from an AIStor bucket. status Display the replication status of an AIStor bucket. The status also lists the remote target path or location. update Modify an existing bucket replication rule.

The mc support top disk command displays current drive statistics. Syntax Example The following command displays the current disk usage and performance on the alias myaistor.

This page documents the installation and management of AIStor object storage using MinIO’s Red Hat OpenShift-certified operator. This procedure assumes that the user interacting with the OpenShift 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 the AIStor Operator This section installs the OpenShift-certified AIStor Operator. You must complete this section before proceeding to deploying AIStor.

AIStor implements Transport Layer Security (TLS) 1.2+ encryption with support for Server Name Indication (SNI) for selecting relevant TLS certificates in response to client requests. AIStor supports two types of certificate management: Automatic TLS certificate provisioning (default) User-provided TLS certificates When deploying an AIStor Object Store resource, the CRD definition provides a certificates field for controlling certificate generation and behavior. This field is also available in the object store Helm chart.

This procedure explains how to specify the TLS certificates your AIStor deployment requires and configure your deployment to work with the certificates. See also Enable Network Encryption for explanations of how AIStor requires TLS and which cipher suites AIStor supports. Prerequisites The appropriate X.509 certificates for your environment.