The mc admin heal command scans for objects that are damaged or corrupted and heals those objects. mc admin heal is resource intensive and typically not required as a manual process, even after drive failures or corruption events. As a part of normal operations, AIStor: automatically heals objects damaged by silent bit rot corruption, drive failure, or other issues on each POST or GET operation. performs periodic background object healing using the scanner. aggressively heals objects after drive replacement. Refer to Object Healing for more details on how AIStor heals objects.

This page covers settings for the AIStor Client mc. You can establish or modify settings by defining: an environment variable on the host system prior to starting or restarting the AIStor Server. Refer to your operating system’s documentation for how to define an environment variable. a configuration setting using mc admin config set. If you define both an environment variable and the similar configuration setting, AIStor uses the environment variable value.

The following page includes the full contents of the AIStor Server Operator Helm Chart default values.yaml and all accompanying documentation. # Default values for AIStor Operators chart # The Following annotations/labels are applied to all resources created by the Helm chart annotations: {} labels: {} # Allow override the namespace for all resources #namespaceOverride: "test" # The repositories allow overriding the default repositories that # are used to determine the full images names. When left empty, # the default repository will be used. repositories: {} # aistor: # hostname: quay.io # pathPrefix: minio/aistor/ # minio: # hostname: quay.io # pathPrefix: minio/ # prometheus: # hostname: quay.io # pathPrefix: prometheus/ # The MinIO license can be set directly from the Helm chart. Note that it is not advised # to expose the license key in the Helm chart. Instead, it is recommended to create a # secret manually. It's just here for convenience. license: "" # global settings are settings that will be applied to all operators # unless explicitly overridden in the operator settings. global: # The Helm chart will try to auto-detect OpenShift. If it cannot detect OpenShift # (i.e. when running helm template), then it will default to false. You can # override this setting to force OpenShift mode. #forceOpenShift: true # Specify the default cluster domain. When it's not set, then it # will try to auto-detect the cluster. But you may want to set it # explicitly # clusterDomain: "cluster.xxx" # The following settings will be set for all operators. They can # be overridden per operator by setting the same key in the # .operator.<operator> section. operator: # Specify number of replicas replicas: 1 # Specify `annotations <https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/>`__ to associate to pods. podAnnotations: {} # Specify `labels <https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/>`__ to associate to pods. podLabels: {} # This will add extra environment variables to the operator # containers. extraEnv: [] # Image pull policy (empty uses the default registry policy). imagePullPolicy: "" ### # You may need to set the image pull secrets when using a private registry. # Need to be set as an array of LocalObjectReference. # .. code-block:: yaml # # imagePullSecrets: # - name: minio-registry-secret # type: kubernetes.io/dockerconfigjson imagePullSecrets: [] # Resources for the operator containers. resources: requests: cpu: 200m ephemeral-storage: 100Mi memory: 256Mi # Security context for the operator containers (ignored on OpenShift) securityContext: allowPrivilegeEscalation: false capabilities: drop: - ALL runAsGroup: 1000 runAsNonRoot: true runAsUser: 1000 seccompProfile: type: RuntimeDefault # Security context for the operator pods (ignored on OpenShift) podSecurityContext: {} # fsGroup: 2000 # All operators will be using the global setting, unless overridden # in the section below. All keys in `.global.operators` can also be # used here and will override (not extend) the global setting. # # All operators will be disabled by default, with the exception of # the object-store. operators: adminjob: disabled: false aihub: disabled: true inference: disabled: true object-store: disabled: false # STS can now be used on MinIO endpoints, so there is no need to # enable STS for the object-store. This is kept for backward # compatibility, but will be removed in the future. enableSTS: false prompt: disabled: true warp: disabled: true

These sections contain reference material for the AIStor Server Operator.

This tutorial shows how to setup a KES server that uses Fortanix SDKMS as a persistent and secure key store: K E S C l i e n t K E S S e r v e r F o r t a n i x S D K M S Fortanix SDKMS Create Application

AIStor supports decommissioning and removing server pools from a deployment with two or more pools. To decommission, there must be at least one remaining pool with sufficient available space to receive the objects from the decommissioned pools. AIStor supports queueing multiple pools in a single decommission command. Each listed pool immediately enters a read-only status, but draining occurs one pool at a time. Decommissioning is designed for removing an older server pool whose hardware is no longer sufficient or performant compared to the pools in the deployment. AIStor automatically migrates data from the decommissioned pools to the remaining pools in the deployment based on the ratio of free space available in each pool.

Removes one or more IAM policies from an AIStor-managed user or group. This command is intended for managing policy associations for AIStor-managed users only. For detaching policies to OpenID-managed users, see OpenID Connect Access Management. For detaching policies to Active Directory/LDAP users or groups, use mc idp ldap policy detach.

Syntax The mc admin decommission command starts the decommissioning process for an AIStor server pools. Decommissioning is designed for removing an older server pool whose hardware is no longer sufficient or performant compared to the pools in the deployment. AIStor automatically migrates data from the decommissioned pool to the remaining pools in the deployment based on the ratio of free space available in each pool. The process ignores unreadable objects, such as those that have lost read quorum, and continues with remaining objects in the pool.

The AIStor Client (mc) is a drop-in replacement for the Open Source MinIO client. AIStor mc has exclusive functionality intended to support licensed AIStor Server deployments. mc has the following syntax: mc [GLOBALFLAGS] COMMAND --help See Command quick reference for a list of supported commands. Version alignment with AIStor Server The AIStor Client releases separately from AIStor Server.

AIStor supports publishing an audit log of all operations to a remote receiver. The audit logging feature meets security and compliance requirements around granular tracking of operations within an AIStor deployment. AIStor does not by default publish audit logs to any destination. Audit logs can contain private and internal details such as hostnames, IP addresses, and object names. The remote receiver takes responsibility for processing, storing, and securing all incoming audit logs.