Jack Yu
Jack Yu
The workaround is to modify the secret value after creating the storage class.
For other fields value, I think we could skip validation. We just need to validate the `CRYPTO_KEY_SIZE` and `CRYPTO_KEY_HASH`. Or even we remove all validation of value, only keep key...
Okay, I find that we could use following available value to validate all fields. CRYPTO_PBKDF: https://github.com/search?q=repo:mbroz/cryptsetup+%22argon2i%22&type=code&p=1 CRYPTO_KEY_HASH: https://github.com/search?q=repo:mbroz/cryptsetup+%22sha256%22&type=code CRYPTO_KEY_CIPHER: https://github.com/search?q=repo:mbroz/cryptsetup+%22aes-xts-plain64%22&type=code
BTW, we should add available options of LUKS in our documentation.
> we are calculating cluster wide cpu models, would it not make sense to have this be available in the cluster object? we already do something similar for vGPU profiles...
hi @SanjayM0han could you upload the entire support bundle file or send it to `[email protected]` with issue number? Thanks!
I noticed you use rook-ceph storage class. You can refer this documentation(https://docs.harvesterhci.io/v1.5/advanced/csidriver). Backup isn't supported by third part storage.
@SanjayM0han Sorry, there is no way to backup via unsupported third part storage because it involves some complex logic under the hood. But, we support snapshot as in-cluster backup in...
After investigation, it seems that Longhorn might have an issue. To reproduce it: 1. Create a Longhorn RWX or RWO volume (backing image is okay as well) with replica count...
HI @WebberHuang1118 It's still rc1 now, rc2 is not released yet.