Este conteúdo não está disponível no idioma selecionado.
Chapter 1. Overview
Learn about confidential containers and ensure that your OpenShift Container Platform environment is compatible.
1.1. About confidential containers Copiar o linkLink copiado para a área de transferência!
Confidential containers provides a confidential computing environment to protect containers and data by leveraging Trusted Execution Environments.
For more information, see Exploring the OpenShift confidential containers solution.
1.2. Compatibility with OpenShift Container Platform Copiar o linkLink copiado para a área de transferência!
The required functionality for Red Hat OpenShift Container Platform is supported by two main components:
- Kata runtime
- The Kata runtime is included with Red Hat Enterprise Linux CoreOS (RHCOS) and receives updates with every OpenShift Container Platform release. When enabling peer pods with the Kata runtime, the OpenShift sandboxed containers Operator requires external network connectivity to pull the necessary image components and helper utilities to create the pod virtual machine (VM) image.
- OpenShift sandboxed containers Operator
- The OpenShift sandboxed containers Operator is a Rolling Stream Operator, which means the latest version is the only supported version. It works with all currently supported versions of OpenShift Container Platform.
The Operator depends on the features that come with the RHCOS host and the environment it runs in.
You must install RHCOS on the worker nodes. Red Hat Enterprise Linux (RHEL) nodes are not supported.
The following compatibility matrix for OpenShift sandboxed containers and OpenShift Container Platform releases identifies compatible features and environments.
| Architecture | OpenShift Container Platform version |
|---|---|
| x86_64 | 4.17 or later |
| s390x | 4.17 or later |
There are two ways to deploy the Kata containers runtime:
- Bare metal
- Peer pods
You can deploy OpenShift sandboxed containers by using peer pods on Microsoft Azure, AWS Cloud Computing Services, or Google Cloud. With the release of OpenShift sandboxed containers 1.11, the OpenShift sandboxed containers Operator requires OpenShift Container Platform version 4.17 or later.
| Major release version | 4.17 | 4.18 | 4.19 | 4.20 | |
|---|---|---|---|---|---|
| Minor release version | 4.17.45+ | 4.18.30+ | 4.19.20+ | 4.20.6+ | |
| Feature | Platform | ||||
| Confidential containers | Bare metal | — | — | — | TP |
| Azure peer pods | GA | GA | GA | GA | |
| IBM Z peer pods | TP | TP | TP | TP | |
| IBM Z bare metal | — | — | — | TP | |
| GPU support | Bare metal | — | — | — | — |
| Azure | DP | DP | DP | DP | |
| AWS | DP | DP | DP | DP | |
| Google Cloud | DP | DP | DP | DP | |
GPU support for peer pods is a Developer Preview feature only. Developer Preview features are not supported by Red Hat in any way and are not functionally complete or production-ready. Do not use Developer Preview features for production or business-critical workloads. Developer Preview features provide early access to upcoming product features in advance of their possible inclusion in a Red Hat product offering, enabling customers to test functionality and provide feedback during the development process. These features might not have any documentation, are subject to change or removal at any time, and testing is limited. Red Hat might provide ways to submit feedback on Developer Preview features without an associated SLA.
| Platform | GPU | Confidential containers |
|---|---|---|
| Azure | DP | GA |
| AWS | DP | — |
| Google Cloud | DP | — |
| Platform | GPU | Confidential containers |
|---|---|---|
| Bare metal | — | TP |
| IBM Z | — | TP |
1.3. Providing feedback on Red Hat documentation Copiar o linkLink copiado para a área de transferência!
You can provide feedback or report an error by submitting the Create Issue form in Jira:
- Ensure that you are logged in to Jira. If you do not have a Jira account, you must create a Red Hat Jira account.
- Launch the Create Issue form.
Complete the Summary, Description, and Reporter fields.
In the Description field, include the documentation URL, chapter or section number, and a detailed description of the issue.
- Click Create.