Troubleshoot common upgrade issues including KES certificates, PolicyBinding errors, OperatorHub subpath problems, and object store failures.

This page describes how to upgrade MinIO AIStor Helm clusters that use a private container registry but have internet access to helm.min.io for chart updates. If your cluster uses public registries or is in an airgapped environment, see: Upgrade with Public Registries Upgrade in Airgapped Environment Overview MinIO AIStor Helm upgrades involve updating two components:

The mc admin accesskey enable command enables an existing access key. The command requires the access key to exist and be currently disabled. Syntax Example The following command enables the access key myuseraccesskey on the myaistor deployment:

MinIO AIStor supports expanding an existing distributed cluster by adding a new server pool. Each pool expands the total available storage capacity of the cluster. MinIO AIStor does not support increasing storage through logical volume expansion, rolling drive replacement, or other filesystem-level approaches. Expansion does not provide Business Continuity/Disaster Recovery (BC/DR)-grade protections. While each pool is an independent set of servers with distinct erasure sets for availability, the complete loss of one pool results in MinIO stopping I/O for all pools in the cluster. Similarly, an erasure set which loses quorum in one pool represents data loss of objects stored in that set, regardless of the number of other erasure sets or pools.

This section provides reference documentation for MinIO AIStor components. The AIStor Server reference provides extensive details of how AIStor Server works. As you build or expand your infrastructure, look here for requirements for compute, network, memory, and storage, as well as thresholds and limits. Find recommended hardware tests, detailed explanations of how the scanner works and how to implement S3 express. MinIO AIStor provides extensive set of options to customize how MinIO AIStor runs. Configure the many options through either environment variables or configuration settings.

This page documents upgrade procedures for AIStor Server clusters on bare-metal Linux infrastructure. All MinIO AIStor software supports non-disruptive upgrades with zero downtime. In optimal environments, cluster-wide upgrades typically complete in under 500 milliseconds with large clusters (1000+ nodes) completing in less than 5 seconds. In site-replicated deployments, Security Token Service (STS) tokens are signed with the site replicator service account credentials rather than the root credentials.

The mc admin cluster iam import command imports IAM metadata as created by the mc admin cluster iam export command. You can use this command to manually restore IAM metadata settings for an MinIO AIStor deployment. The command outputs the results of the import, including the following: count of individual entities imported by entity type list of policies imported by entity type they imported to list of entities that failed to import Syntax Example The following command imports the IAM metadata of the specified file onto the myaistor deployment.

Description The mc admin config command manages configuration settings for the AIStor Server. Examples Syntax mc admin config set Sets a configuration key on the MinIO AIStor deployment. Configurations defined by environment variables override configurations defined by this command.

Sets or replaces the cluster name for an MinIO AIStor deployment. This command cannot override a cluster name set with the MINIO_SITE_NAME environment variable. Syntax Example The following command sets the cluster name for the deployment at alias myaistor:

Use mc admin maintenance hosts to create lists of maintenance groups. The command generates lists of hosts that do not share erasure sets. Hosts that do not share a erasure sets can go into maintenance at the same time without causing service disruptions. Syntax The mc admin maintenance hosts command DESCRIPTION