Upgrade MinIO AIStor on Kubernetes (Helm)

This page provides guidance for upgrading MinIO AIStor Helm clusters on Kubernetes infrastructure.

MinIO AIStor Helm installations consist of two primary components:

1. Operator Chart - Controls resources like CustomResourceDefinitions and core operator functionality
2. Object Store Chart - Deploys and manages MinIO AIStor instances

Upgrades involve updating these charts and deploying new container images. The exact procedure depends on your cluster environment’s network configuration and registry access.

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.

S3 SDKs and applications typically implement retry mechanisms that mitigate the impact of any reduced availability.

Before upgrading in any environment:

• Review the upgrade prerequisites
• Back up your existing Helm configurations
• Ensure you have a valid, current MinIO AIStor license
• Verify the health of your current cluster
• Review release notes for breaking changes

See the scenario-specific guides above for detailed prerequisites and step-by-step instructions.

Select the upgrade guide that matches your environment:

Regardless of your cluster scenario, MinIO AIStor upgrades follow this general workflow:

1. Update Operator Chart - Upgrade the operator chart and deploy the new operator image
2. Update Object Store Chart - Upgrade the object store chart and deploy new object store images
3. Bump the API version - Synchronize the API version across all nodes after the upgrade

You can also upgrade only the MinIO AIStor image version without updating the chart itself if you only need to update the running software version.