Jack Lin

Will provide a knowledge base doc in our website first. The further improvement action items are not decided yet, we will still keep this issue open until further discussion.

I have created another ticket to track the backend progress: https://github.com/longhorn/longhorn/issues/8068 Will try to finish the backend part this sprint. cc @scures

Hi @scures The backend api PR has been created and might need some time to get it merged. You can use my longhorn-manager image for the development. `jackfantasy/longhorn-manager:backupbacking`

Here is a simple using flow of BackupBackingImage 1. Create BackingImage ``` name: parrot downloadURL: https://longhorn-backing-image.s3-us-west-1.amazonaws.com/parrot.raw ``` Note: keep the `checksum` 2. Test Create BackupBackingImage ``` curl -X POST http://localhost:8080/v1/backingimages/parrot?action=backupBackingImageCreate...

E2E test: https://ci.longhorn.io/job/private/job/longhorn-tests-regression/6460/console

`-vs test_settings.py` E2E test **PASSED**: https://ci.longhorn.io/job/private/job/longhorn-tests-regression/6521/

`-m coretest` E2E test **PASSED**: https://ci.longhorn.io/job/private/job/longhorn-tests-regression/6528/

> This pull request is now in conflict. Could you fix it @ChanYiLin? 🙏 Conflicts resolved.

ref: https://github.com/longhorn/longhorn/issues/7845

We backport this change to instance-manager v1.4.x https://github.com/longhorn/longhorn-instance-manager/pull/382#issuecomment-1911186398 but we didn't backport it in manager https://github.com/longhorn/longhorn-manager/pull/2533 cc @derekbit @innobead