Welcome to the upcoming version of the MinIO Documentation! The content on this page is under active development and may change at any time. If you can't find what you're looking for, check our legacy documentation. Thank you for your patience.

Upgrade a MinIO Deployment

Test Upgrades Before Applying To Production

MinIO strongly discourages performing blind updates to production clusters. You should always test upgrades in a lower environment (dev/QA/staging) before applying upgrades to production deployments.

Exercise particular caution if upgrading to a release that has backwards breaking changes. MinIO includes warnings in release notes for any version known to not support downgrades.

For MinIO deployments that are significantly behind latest stable (6+ months), consider using MinIO SUBNET for additional support and guidance during the upgrade procedure.

Use the mc admin update command to update a Standalone or Distributed MinIO deployment to the latest stable release.

mc admin update ALIAS

Replace ALIAS with the alias of the MinIO deployment.

mc admin update affects all MinIO servers in the target deployment at the same time. The update procedure interrupts in-progress API operations on the MinIO deployment. Exercise caution before issuing an update command on production environments.

You can specify a custom URL for updating the MinIO deployment using a specific MinIO server binary:

mc admin update ALIAS https://minio-mirror.example.com/minio

You should upgrade your mc binary to match or closely follow the MinIO server release. You can use the mc update command to update the binary to the latest stable release:

mc update