Skip to content

Conversation

@jiuker
Copy link
Contributor

@jiuker jiuker commented Mar 11, 2025

remove upgrade for version below 5.0.0
fix #2397

@jiuker jiuker force-pushed the remove-upgrade-for-version-blew-5.0.0 branch from f550d91 to 6274e39 Compare March 11, 2025 04:07
remove upgrade version blew 5.0.0
@jiuker jiuker force-pushed the remove-upgrade-for-version-blew-5.0.0 branch from d74a62f to feb6b2b Compare March 11, 2025 04:19
cniackz
cniackz previously approved these changes Mar 11, 2025
Copy link
Contributor

@cniackz cniackz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Correct, no automatic upgrade if you are coming from version 4. If in version 4, then update manually

@ramondeklein ramondeklein changed the title remove upgrade for version blew 5.0.0 remove upgrade for version below 5.0.0 Mar 11, 2025
@ramondeklein
Copy link
Contributor

@cniackz Please verify if a PR passes the checks before approving it.

@jiuker I have upgraded to GitHub workflows to use Go v1.23 to ensure it is able to use the upgraded packages.

@ramondeklein ramondeklein force-pushed the remove-upgrade-for-version-blew-5.0.0 branch from eb1af4d to 772a16c Compare March 11, 2025 10:29
allanrogerr
allanrogerr previously approved these changes Mar 11, 2025
@feorlen
Copy link
Contributor

feorlen commented Mar 12, 2025

What, specifically, does "update manually" mean? Migration?

@ramondeklein
Copy link
Contributor

When you want to upgrade from a pre-v5 operator, then you need to upgrade to Operator v5 and then upgrade to a newer version. We don't support upgrading directly from operator v4 to v7. If you have a better description, then please suggest it.

@feorlen
Copy link
Contributor

feorlen commented Mar 12, 2025

When you want to upgrade from a pre-v5 operator, then you need to upgrade to Operator v5 and then upgrade to a newer version. We don't support upgrading directly from operator v4 to v7. If you have a better description, then please suggest it.

Ah ok. It's like the current situation, where you have to upgrade in steps. But you can upgrade in place. 👍🏻

The relevant docs are here:

https://min.io/docs/minio/kubernetes/upstream/operations/install-deploy-manage/upgrade-minio-operator-4.5.7-earlier.html#upgrade-legacy-minio-operators

This page has details of how to progressively upgrade from very old versions. The text will need some minor adjustments to make sure the before/after versions are correct for each step in the sequence.

@pjuarezd pjuarezd merged commit 83cff0f into minio:master Mar 13, 2025
21 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

sts secret not being created

6 participants