Upgrade Volume Manager with the Plugin
This page describes how to upgrade an existing Volume Manager by directly upgrading the binary or using the kubectl
plugin.
MinIO recommends using Helm for upgrading Volume Manager. You can upgrade from release 4.1.5 or later using Helm, even if Volume Manager was not originally installed using Helm. See upgrade using Helm for instructions.
kubectl directpv migrate
to migrate the old resources to a new installation.
Prerequisites
Kubernetes environment
-
Kubernetes installed with an in-support, active release.
In general, Kubernetes provides security releases for releases for a period of up to 1 year. Volume Manager requires Kubernetes version 1.29 or later.
Back up the existing Helm configuration
helm get values -n volume-manager
Test Upgrades Before Applying To Production
Volume Manager uses a testing and validation suite as part of all releases. However, no testing suite can account for unique combinations and permutations of hardware, software, and workloads of your production environment.
You should always validate any Volume Manager upgrades in a lower environment (such as Dev/QA/Staging) before applying those upgrades to production deployments, or any other environment containing critical data. Performing updates to production environments without first validating in lower environments is done at your own risk.
Consider using SUBNET for additional support and guidance during the upgrade procedure.
Upgrade Volume Manager to latest
Follow the steps below to perform an offline upgrade where Volume Manager is not actively running:
-
Uninstall the Volume Manager CSI driver.
This does not remove any existing resources.
kubectl directpv uninstall
-
Download the Volume Manager plugin for your operating system and architecture from https://dl.min.io/aistor/directpv/release/.
Move the downloaded file to your system PATH. Refer to the documentation for your operating system for where to place the file.
-
Mark the downloaded plugin as executable.
chmod a+x /path/to/kubectl-directpv
Executables on macOSmacOS typically blocks unsigned binaries from running. If thekubectl-directpv
command fails, go to System Settings, then Privacy and Security. Scroll to the Security section and select Allow Anyway for thekubectl-directpv
application. -
Install the latest Volume Manager driver.
kubectl-directpv install
Upgrade Volume Manager Plugin
-
Download the Volume Manager plugin for your operating system and architecture from https://dl.min.io/aistor/directpv/release/.
Move the downloaded file to your system PATH. Refer to the documentation for your operating system for where to place the file.
-
Mark the downloaded plugin as executable.
chmod a+x /path/to/kubectl-directpv
Executables on macOSmacOS typically blocks unsigned binaries from running. If thekubectl-directpv
command fails, go to System Settings, then Privacy and Security. Scroll to the Security section and select Allow Anyway for thekubectl-directpv
application.