Problem and Goal

Minio had officially announced that the gateway and filesystem mode were deprecated after the release of RELEASE.2022-10-29T06-21-33Z, for which we must address because of the upgrade of minio version in PrimeHub v4.1.0.

In this article, we will show you how to migrate your PrimeHub shared files data from an older version of minio to the minio released after 2022-10.

If you are using a fresh install of PrimeHub 4.1.0, you don’t need to take any action since the minio version is already using a new mode inside minio server.

If you plan to upgrade PrimeHub v4.0.x to v4.1.0, you must follow the instructions in this article to migrate your data to the new minio server.

Environment

1. A PrimeHub v4.0.x installation.
2. Already uploaded files to PrimeHub shared files.
3. Plan to upgrade PrimeHub to v4.1.0 or newer.

Step-by-step Method

Log in to the node with the kubectl installed to operate the k8s cluster.

Install kubectl-mountpvc

Install kubectl-mountpvc command:

cd $HOME
mkdir $HOME/bin
curl -LO <https://storage.googleapis.com/primehub-release/bin/primehub-tools.tar.gz>
tar -xvf primehub-tools.tar.gz
ls -d primehub-tools
primehub-tools

cp primehub-tools/kubectl-mountpvc $HOME/bin
ls $HOME/bin | grep kubectl-mountpvc
kubectl-mountpvc
chmod 755 $HOME/bin/kubectl-mountpvc

Check the kubectl-mountpvc can be executed:

# Source the bin folder.
echo "export PATH=$HOME/bin:$PATH" >> ~/.bashrc
source ~/.bashrc

# Check the version of yq
yq --version

# Check the command is successfully configure
kubectl mountpvc --help

Stop primehub-minio service

Stop the primehub-minio pod

kubectl -n hub scale sts primehub-minio --replicas 0

Make sure the pod is not running