|
2 | 2 | title: Confidential Containers pattern |
3 | 3 | date: 2024-10-03 |
4 | 4 | tier: sandbox |
5 | | -summary: This pattern helps you get started with deploying confidential containers in OpenShift Container Platform |
| 5 | +summary: This pattern helps you get started with deploying confidential containers in OpenShift Container Platform. |
6 | 6 | rh_products: |
7 | 7 | - Red Hat OpenShift Container Platform |
8 | 8 | - Red Hat Advanced Cluster Management |
9 | 9 | - Red Hat OpenShift Sandbox Containers |
10 | 10 | industries: |
11 | 11 | - General |
12 | 12 | aliases: /coco-pattern/ |
13 | | -pattern_logo: multicloud-gitops.png |
| 13 | +pattern_logo: coco-logo.png |
14 | 14 | links: |
15 | 15 | install: coco-getting-started |
16 | 16 | help: https://groups.google.com/g/validatedpatterns |
17 | 17 | bugs: https://github.com/validatedpatterns/coco-pattern/issues |
18 | | - repo: https://github.com/validatedpatterns/coco-pattern |
19 | | - |
20 | 18 | --- |
21 | 19 | :toc: |
22 | 20 | :imagesdir: /images |
23 | 21 | :_content-type: ASSEMBLY |
24 | 22 | include::modules/comm-attributes.adoc[] |
25 | 23 |
|
26 | | -include::modules/mcg-about-multicloud-gitops.adoc[leveloffset=+1] |
| 24 | += About coco-pattern |
| 25 | + |
| 26 | +Confidential computing is a technology for securing data in use. It uses a https://en.wikipedia.org/wiki/Trusted_execution_environment[Trusted Execution Environment] provided within the hardware of the processor to prevent access from others who have access to the system. |
| 27 | +https://confidentialcontainers.org/[Confidential containers] is a project to standardize the consumption of confidential computing by making the security boundary for confidential computing to be a Kubernetes pod. [Kata containers](https://katacontainers.io/) is used to establish the boundary via a shim VM. |
| 28 | + |
| 29 | +This pattern uses https://docs.redhat.com/en/documentation/openshift_sandboxed_containers/1.7/html/user_guide/deploying-on-azure#deploying-cc_azure-cc[Red Hat OpenShift Sandbox Containers] to deploy and configure confidential containers on Microsoft Azure. |
| 30 | + |
| 31 | +It deploys three copies of 'Hello OpenShift' to demonstrate some of the security boundaries that enforced with confidential containers. |
| 32 | + |
| 33 | +== Requirements |
| 34 | + |
| 35 | +- An an azure account with the link:./coco-pattern-azure-requirements/[required access rights] |
| 36 | + |
| 37 | + |
| 38 | +== Security considerations |
| 39 | + |
| 40 | +**This pattern is a demonstration only and contains configuration that is not best practice** |
| 41 | + |
| 42 | +- The default configuration deploys everything in a single cluster for testing purposes. The https://www.ietf.org/archive/id/draft-ietf-rats-architecture-22.html[RATS] architecture mandates that the Key Broker Service (e.g. https://github.com/confidential-containers/trustee[Trustee]) is in a trusted security zone. |
| 43 | +- The https://github.com/confidential-containers/trustee/tree/main/attestation-service[Attestation Service] has wide open security policies. |
| 44 | + |
| 45 | +== Future work |
| 46 | + |
| 47 | +* Deploying the environment the 'Trusted' environment including the KBS on a separate cluster to the secured workloads |
| 48 | +* Deploying to alternative environments supporting confidential computing including bare metal x86 clusters; IBM Cloud; IBM Z |
| 49 | +* Finishing the sample AI application |
| 50 | + |
| 51 | +== Architecture |
| 52 | + |
| 53 | +=== Single Cluster |
| 54 | + |
| 55 | + |
| 56 | +=== Multi-cluster architecture |
| 57 | + |
| 58 | +Work in progress |
| 59 | + |
27 | 60 |
|
28 | | -include::modules/mcg-architecture.adoc[leveloffset=+1] |
29 | 61 |
|
30 | 62 | [id="next-steps_mcg-index"] |
31 | 63 | == Next steps |
|
0 commit comments