You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Scenario: Can create an attested pod from an encrypted signed container image
Given I have a version of CoCo deployed on Kubernetes with this operator And The environment is configured with simple-kbs When I try and create a pod with kata-qemu-sev runtime from a public encrypted signed container image Then The pod is successfully created
Questions
Q1: Should it use an encrypted signed container or simply an unencrypted image?
Q2: Will the environment be configured with policy to exercise that integration too?
Q3: Same question for CDH (Confidential Data Hub)
Q4: Will we try to make the tests shareable with other projects (e.g. Kata Containers and peer pods)?
Trying to respond to your questions:
Q1: Maybe we handle all cases?
Q2: Great question. Probably we need this variation, too.
Q3: Not sure I understand; all of these cases would require CDH, no?
Q4: This part is beyond me still; reusing some of these deployment and testing components is ideal, if possible.
Q5: Great question. I assume this script is battle-tested, so if we don't use it, we need to take a lot from it.
Test cases
Scenario: Can create an attested pod from an encrypted signed container image
Given I have a version of CoCo deployed on Kubernetes with this operator
And The environment is configured with simple-kbs
When I try and create a pod with
kata-qemu-sev
runtime from a public encrypted signed container imageThen The pod is successfully created
Questions
Additional information
The text was updated successfully, but these errors were encountered: