[UI][FEATURE] Add backing image encryption and clone support about longhorn HOT 6 CLOSED

@mantissahz Can you help verify the ticket? Feel free to check with @roger-ryao and @a110605. Thank you.

from longhorn.

The third point is blocked by [FEATURE] Add BackupBackingImage UI. I will add Secret and SecretNamespace fields when restore lhbbi after I have done back backing image table. cc @ChanYiLin

from longhorn.

Pre Ready-For-Testing Checklist

• Where is the reproduce steps/test steps documented?
  The reproduce steps/test steps are at:
  Apply below secret on LH cluster

apiVersion: v1
kind: Secret
metadata:
  name: longhorn-crypto
  namespace: longhorn-system
stringData:
  CRYPTO_KEY_VALUE: "Your encryption passphrase"
  CRYPTO_KEY_PROVIDER: "secret"
  CRYPTO_KEY_CIPHER: "aes-xts-plain64"
  CRYPTO_KEY_HASH: "sha256"
  CRYPTO_KEY_SIZE: "256"
  CRYPTO_PBKDF: "argon2i"

Clone BI

1. Go to backing image page
2. Click Create Backing Image
3. Select clone from existing backing image
4. Try different select encrypt/decrypt / ignore options
5. input secret : longhorn-crypto, namespace: longhorn-system if choose encrypt or decrypt
6. Click ok -> encrypted bi should show a icon before name

Restore BBI to BI

1. Create a BBI by clicking backup operation menu in backing image table.
2. Wait for BBI creation.
3. Click restore operation menu in BBI table
4. Input namespace and secret if needed.
5. Should restore successfully (same name BI will cause restore failed, can remove same name BI first)

Test BI created from
Since code is refactoring, please help test create BI from download/ upload /export volume work as usual. thx

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

• Does the PR include the explanation for the fix or the feature?

• 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:

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

• Which areas/issues this PR might have potential impacts on?
  Area
  Issues

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

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

• If labeled: require/doc Has the necessary document PR submitted or merged (including backport-needed/*)?
  The documentation issue/PR is at longhorn/website#943

• 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)

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

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

• 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

from longhorn.

@a110605 Can it be moved to ready for testing?

from longhorn.

Will move once longhorn/longhorn-ui#763 is approved and merged. The third point is implement in that PR.

from longhorn.

Verified PASSED on longhorn master(longhorn-manager 79f794) with test steps

from longhorn.