mirror of
https://github.com/minio/docs.git
synced 2025-08-06 14:42:56 +03:00
Partially addresses #1190 No staged build unless someone requests it. # Summary After some thinking, we've leaned towards just making a note of the upgrade step and calling it done. We do not typically make extended discussion of backward-breaking changes at this time, and have no where to keep that sort of guidance. Maybe in the future or as part of a larger re-arch we can consider where we would best keep that kind of guidance. As far as the rest: - We are not covering s3zip today, so that's a no-op. We should leave the ticket open in the event we have bandwidth to document the feature later - No changes to Console that need documentation at this time - Added a quick callout on the warning behavior to the Versioning page - Metrics v3 is also still In progress, come back to this once the project is fully baked.
32 lines
911 B
ReStructuredText
32 lines
911 B
ReStructuredText
.. _minio-upgrade:
|
|
|
|
==========================
|
|
Upgrade a MinIO Deployment
|
|
==========================
|
|
|
|
.. default-domain:: minio
|
|
|
|
.. contents:: Table of Contents
|
|
:local:
|
|
:depth: 2
|
|
|
|
.. important::
|
|
|
|
For deployments older than :minio-release:`RELEASE.2024-03-30T09-41-56Z` running with :ref:`AD/LDAP <minio-ldap-config-settings>` enabled, you **must** read through the release notes for :minio-release:`RELEASE.2024-04-18T19-09-19Z` before starting this procedure.
|
|
You must take the extra steps documented in the linked release as part of the upgrade.
|
|
|
|
.. cond:: linux
|
|
|
|
.. include:: /includes/linux/steps-upgrade-minio-deployment.rst
|
|
|
|
.. cond:: container
|
|
|
|
.. include:: /includes/container/steps-upgrade-minio-deployment.rst
|
|
|
|
.. cond:: windows
|
|
|
|
.. include:: /includes/windows/steps-upgrade-minio-deployment.rst
|
|
|
|
.. cond:: macos
|
|
|
|
.. include:: /includes/macos/steps-upgrade-minio-deployment.rst |