Proposal for COCO use case for creating scenarios

[ariel-adam]

What are we proposing?

• We would like to bring forward a proposal for defining a simple use case we can then demo at different complexity levels at periodic milestones
• Anything we demo will need to be deployed and used via the COCO operator and reproducible by anyone
• This is different than the CCV0 demos where the focus was on showing something even if patched

Why do we think this is needed?

Helping our community provide deliverables which are deployable and stable

Proposed use case (other ideas are welcome):

Nginx web server with a simple interface to store a credit card number (stored in a file)

Scenarios for use case demo (incrementing):

Scenario#1: COCO on a standard server - deploying COCO with k8s on any machine with no encryption involved

• This will help stabilize the key flows and building blocks such as the operator, pulling the image etc…
• This includes creating a CI which can be run locally

Scenario#2: COCO on a TEE guest with offline attestation - running COCO with a k8s TEE capable server using offline attestation

• The attestation doesn’t reach out to an attestation server.
• This will help with the E2E configuration for TEE capable servers
• The entire flow is presented although not safe (thus still bring value)

Scenario#3: COCO on a TEE guest with full attestation - running COCO with k8s on TEE capable servers using an attestation server.

• Most of the flow components are partially working and we’d like to get a simple stable E2E flow working
• We need to decide what HW is accessible early for a user to try this out
• A subtask here would be to create a matrix table of what HW is supported