Install on Kubernetes Deploy AIStor on Kubernetes

This procedure downloads and installs the AIStor Server onto a bare-metal host running Microsoft Windows Server or Windows 11 Professional Edition. Review the Hardware and System Requirements to ensure your target infrastructure meets our guidance. You can also open a SUBNET issue to request an architecture review or assistance during deployment. Procedure Download the AIStor Server binary Invoke-WebRequest https://dl.min.io/aistor/minio/release/windows-amd64/minio -OutFile C:\minio.exe Create a data directory for use with the server The following example uses the path $HOME/minio/data. Changes this path to reflect the folder, storage volume, or drive intended for use with the server.

This procedure deploys AIStor Object Store on Kubernetes clusters in an airgapped environment. An airgapped environment is a network environment that has no direct connection to external networks or the internet. Installing AIStor in an airgapped environment requires copying all required container images and Helm charts to private registries accessible within the airgapped network. Airgap deployment consists of two phases: External Preparation (requires internet access): Download Helm charts and copy container images to your private registries from a system with network access to both the internet and your private registries. Airgapped Deployment (within airgapped environment): Install AIStor using the mirrored resources from within your airgapped Kubernetes environment. This procedure assumes you or your organization have existing procedures and tooling for facilitating such copying. Defer to your organization’s procedures on importing data from the internet into the airgapped environment. You cannot complete the first phase without tooling to facilitate the download-and-copy steps.

AIStor supports deploying resources onto Linux infrastructures and provides packages for Red Hat Enterprise Linux and Ubuntu Server platforms. Setting up AIStor on Linux involves these steps: Install AIStor Configure load balancing Set up network encryption Set up server-side encryption

This tutorial explains how to setup a KES Server to use Azure Key Vault as the persistent key store: K E S C l i e n t K E S S e r v e r A z u r e K e y V a u l t Azure Key Vault Azure Key Vault is a managed KMS service that provides a secret store that can be used by KES.

The mc replicate resync command resynchronizes all objects in the specified AIStor bucket to a remote replication target. This command requires first configuring the remote bucket target using the mc replicate add command. You must specify the resulting remote ARN as part of running mc replicate resync. This command supports rebuilding an AIStor deployment using an active-active replication remote as the “backup” source. See the following tutorials for more information on active-active replication.

Use the mc share commands to manage presigned URLs for downloading and uploading objects to a bucket. Subcommands mc share includes the following subcommands: Subcommand Description mc share download The mc share download command creates URLs for performing GET operations mc share list The mc share list command lists active share URLs mc share upload The mc share upload command creates URLs for performing PUT operations

The mc tag set command sets one or more tags to a bucket or object. AIStor supports adding up to 10 custom tags to an object. Example The following command sets tags for the mydata bucket on the myaistor AIStor deployment: mc tag set myaistor/mydata "tag1=value1&tag2=value2" Syntax The command has the following syntax:

The mc support telemetry proxy command streams API events from all nodes on the AIStor deployment to the specified remote OpenTelemetry Protocol (OTLP)-compatible collector. Use the --sample flag to modify the number of calls traced and adjust the impact on performance. By default, the command runs in the current shell session until manually stopped. Syntax Example The following command streams the S3 API calls on the alias myaistor to an OTLP-compatible tracing service running on localhost.

The following section documents environment variables for configuring AIStor to publish audit logs to a Kafka broker. The top-level configuration key for defining a Kafka broker target for publishing AIStor audit logs. Example Environment Variables export MINIO_AUDIT_KAFKA_BROKERS="https://kafka-endpoint.example.net:9092" Configuration Settings Use mc admin config set to set or update a Kafka audit target. Specify additional optional arguments as a whitespace (" ")-delimited list.