chore: update dependencies & longhorn to 1.8.1 #1709
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Despire
added
the
test-set-ordinary
Despire
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
General dependencies update across the repository.
Updates longhorn to 1.8.1. Closes #1707
This was tested by creating a deployment with pvc with loghorn 1.7.0 (the current version)
Upgrade to longhorn 1.8.1, all pods were deployed successfully, perform additional operation on the cluster without issues.
The hash of the replicas were the same after the upgrade.
Further longhorn also specifies in the release that 1.8.x is backwards compatible with 1.7.x https://github.com/longhorn/longhorn/releases/tag/v1.8.1
For volumes created with the old instance one can follow: https://longhorn.io/kb/troubleshooting-some-old-instance-manager-pods-are-still-running-after-upgrade/
It's possible to set via the Longhorn UI
Settings > Concurrent Automatic Engine Upgrade Per Node Limitto a value higher than 0 to upgrade old volumes to the newly deployed managerOld engine-image pods will be terminated after ~60 minutes of not being used (after all volumes are upgraded to the newest longhorn version)
Updates go to 1.24.
Updates go dependencies