e2e-test: verify reference values #2585
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is in preperation of a verification of reference values that we can populate with signed measurements in OCI.
The kbs config is altered to support the LocalJSON ref store and we attach a reference-values.json file to the kustomize patch so the file is mounted into the kbs pod.
By default, there is a dummy reference-values.json. This can be overridden in a TEE's e2e test if we have reference values available. Trustee should then automatically verify the values in a test that uses remote attestation and consider this in the claim.
Here would be an azure e2e-test run that is setting reference values from OCI.