When testing luks and using a non static clevis binding as developer I would like to know that not only does the device get encrypted; But I want to verify the binding I used is what is reported after ignition runs.
Add support for ClevisBinding verification in the blackbox tests.
Feature Request
When testing luks and using a non static clevis binding as developer I would like to know that not only does the device get encrypted; But I want to verify the binding I used is what is reported after ignition runs.
Add support for ClevisBinding verification in the blackbox tests.
As an example,
Would be verified by