[BACKPORT][v1.4.5][TASK] Bump the versions of dependent libs or components

[github-actions[bot]]

backport https://github.com/longhorn/longhorn/issues/7001

[c3y1huang]

~Please don't merge the PRs yet. I need to run some tests on them first.~ done

cc @longhorn/dev

[innobead]

@c3y1huang as discussed, let's make those PRs drafted first.

[c3y1huang]

Test result:

• Full: https://ci.longhorn.io/job/private/job/longhorn-tests-regression/5287/
• CSI: https://ci.longhorn.io/job/public/job/v1.4.x/job/v1.4.x-longhorn-tests-sles-amd64/383/

Note that the test_csi_snappshotter cases failed in full regression test due to an incompatibility between the private pipeline's csi-snapshotter (v6.2.1) and Longhorn v1.4.x.

I've re-run the related case using the public pipeline since I couldn't find an option to configure the csi-snapshotter version.

[longhorn-io-github-bot]

Pre Ready-For-Testing Checklist

• [x] ~Where is the reproduce steps/test steps documented?~ The reproduce steps/test steps are at:

• [x] ~Is there a workaround for the issue? If so, where is it documented?~ The workaround is at:

• [x] ~Does the PR include the explanation for the fix or the feature?~

• [x] ~Does the PR include deployment change (YAML/Chart)? If so, where are the PRs for both YAML file and Chart?~ The PR for the YAML change is at: The PR for the chart change is at:

• [x] Have the backend code been merged (Manager, Engine, Instance Manager, BackupStore etc) (including backport-needed/*)? The PR is at

  • https://github.com/longhorn/longhorn-engine/pull/948
  • https://github.com/longhorn/longhorn-instance-manager/pull/318
  • https://github.com/longhorn/longhorn-share-manager/pull/102
  • https://github.com/longhorn/backing-image-manager/pull/143
  • https://github.com/longhorn/longhorn-manager/pull/2306

• [x] Which areas/issues this PR might have potential impacts on? Area kubernetes, csi, dependencies Issues

• [x] ~If labeled: require/LEP Has the Longhorn Enhancement Proposal PR submitted?~ The LEP PR is at

• [x] ~If labeled: area/ui Has the UI issue filed or ready to be merged (including backport-needed/*)?~ The UI issue/PR is at

• [x] ~If labeled: require/doc Has the necessary document PR submitted or merged (including backport-needed/*)?~ The documentation issue/PR is at

• [x] ~If labeled: require/automation-e2e Has the end-to-end test plan been merged? Have QAs agreed on the automation test case? If only test case skeleton w/o implementation, have you created an implementation issue (including backport-needed/*)~ The automation skeleton PR is at The automation test case PR is at The issue of automation test case implementation is at (please create by the template)

• [x] ~If labeled: require/automation-engine Has the engine integration test been merged (including backport-needed/*)?~ The engine automation PR is at

• [x] ~If labeled: require/manual-test-plan Has the manual test plan been documented?~ The updated manual test plan is at

• [x] ~If the fix introduces the code for backward compatibility Has a separate issue been filed with the label release/obsolete-compatibility?~ The compatibility issue is filed at

[innobead]

https://github.com/longhorn/longhorn/pull/6920#issuecomment-1831808276 @c3y1huang will we update the CSI sidecars as well?

[c3y1huang]

#6920 (comment) @c3y1huang will we update the CSI sidecars as well?

https://github.com/longhorn/longhorn/pull/6920#issuecomment-1841870431

[innobead]

@c3y1huang so, CSI sidecars are only updated to master without backporting to 1.5/1.4, right?

[c3y1huang]

@c3y1huang so, CSI sidecars are only updated to master without backporting to 1.5/1.4, right?

We've backported to v1.5 but not 1.4. The reason for backporting to v1.5 was that it only involved minor version upgrades, unlike v1.4, which involved major version upgrades. And I've also gone through regression testing.

[c3y1huang]

We've backported to v1.5 but not 1.4. The reason for backporting to v1.5 was that it only involved minor version upgrades, unlike v1.4, which involved major version upgrades. And I've also gone through regression testing.

@innobead do you have any concerns?

[innobead]

No concerns if we have done the testing.

[c3y1huang]

No concerns if we have done the testing.

v1.5.x full regression test result: https://github.com/longhorn/longhorn/issues/7150#issuecomment-1823896795

[derekbit]

v1.4.x is EOL.