de1e5bbde1
Replace the kustomize-based Trustee deployment with the upstream Trustee Helm chart (deployment/helm-chart) for every platform, including TDX and s390x, which the previous iteration still left on kustomize. The chart deploys KBS, AS and RVPS as three separate images, so versions.yaml pins image_kbs/image_as/image_rvps (from the upstream staged-images registry) alongside the trustee revision, and bumps trustee to a build that carries the IBM SE material mounting support and the SHA-512 report-data change. guest-components is bumped in lockstep so IBM SE attestation agrees on the SHA-512 runtime-data digest. KBS runs with authorization_mode = "AuthenticatedAuthorization", so admin requests from kbs-client carry the bearer token minted by the chart's bootstrap job instead of relying on an anonymous, allow-all admin API. As reused CI runners may still carry a kbs-client from an older Trustee that predates the --admin-token-file flag, the client is rebuilt from the pinned sources unless the installed one already understands it. On the Intel TDX CI runner only the Attestation Service reaches the public Intel DCAP collateral endpoint, so it is the sole component that needs the corporate proxy. We set https_proxy on the AS alone: the KBS <-> AS <-> RVPS traffic is plain HTTP/gRPC and in-cluster, and routing it through the proxy breaks those connections. The Intel DCAP and NVIDIA verifiers are configured by the chart out of the box, so TDX and SNP need no extra verifier knobs. For IBM SE (s390x) the SE verifier now runs inside the gRPC Attestation Service, so the SE materials are mounted on the AS Pod (not KBS) through the chart's as.ibmse.* knobs, which create a node-local PV/PVC. The AS runs as a non-root user with CAP_DAC_OVERRIDE dropped, hence fsGroup=1000 and a group-readable hdr.bin so it can read the mounted materials. The chart's default CPU requests reserve more of the small single-node CI runners than the old single-Pod deployment did, starving test workloads that ask for a couple of Guaranteed CPUs. Trustee requests are shrunk (limits kept generous) so those Pods schedule again. Debug logging is enabled on all components (log_level=debug) to ease triaging attestation / resource-retrieval failures in CI, and the release is rolled out with 'helm upgrade --install' so re-runs on long-lived CI clusters reconcile in place. Signed-off-by: Fabiano Fidêncio <ffidencio@nvidia.com> Assisted-by: Cursor <cursoragent@cursor.com>
Kata Containers
Welcome to Kata Containers!
This repository is the home of the Kata Containers code for the 2.0 and newer releases.
If you want to learn about Kata Containers, visit the main Kata Containers website.
Introduction
Kata Containers is an open source project and community working to build a standard implementation of lightweight Virtual Machines (VMs) that feel and perform like containers, but provide the workload isolation and security advantages of VMs.
License
The code is licensed under the Apache 2.0 license. See the license file for further details.
Platform support
Kata Containers currently runs on 64-bit systems supporting the following technologies:
| Architecture | Virtualization technology |
|---|---|
x86_64, amd64 |
Intel VT-x, AMD SVM |
aarch64 ("arm64") |
ARM Hyp |
ppc64le |
IBM Power |
s390x |
IBM Z & LinuxONE SIE |
Hardware requirements
The Kata Containers runtime provides a command to determine if your host system is capable of running and creating a Kata Container:
$ kata-runtime check
Notes:
This command runs a number of checks including connecting to the network to determine if a newer release of Kata Containers is available on GitHub. If you do not wish this to check to run, add the
--no-network-checksoption.By default, only a brief success / failure message is printed. If more details are needed, the
--verboseflag can be used to display the list of all the checks performed.If the command is run as the
rootuser additional checks are run (including checking if another incompatible hypervisor is running). When running asroot, network checks are automatically disabled.
Getting started
See the installation documentation.
Documentation
See the official documentation including:
Configuration
Kata Containers uses a single configuration file which contains a number of sections for various parts of the Kata Containers system including the runtime, the agent and the hypervisor.
Hypervisors
See the hypervisors document and the Hypervisor specific configuration details.
Community
To learn more about the project, its community and governance, see the community repository. This is the first place to go if you wish to contribute to the project.
Getting help
See the community section for ways to contact us.
Raising issues
Please raise an issue in this repository.
Note: If you are reporting a security issue, please follow the vulnerability reporting process
Developers
See the developer guide.
Components
Main components
The table below lists the core parts of the project:
| Component | Type | Description |
|---|---|---|
| runtime | core | Main component run by a container manager and providing a containerd shimv2 runtime implementation. |
| runtime-rs | core | The Rust version runtime. |
| agent | core | Management process running inside the virtual machine / POD that sets up the container environment. |
dragonball |
core | An optional built-in VMM brings out-of-the-box Kata Containers experience with optimizations on container workloads |
| documentation | documentation | Documentation common to all components (such as design and install documentation). |
| tests | tests | Excludes unit tests which live with the main code. |
Additional components
The table below lists the remaining parts of the project:
| Component | Type | Description |
|---|---|---|
| packaging | infrastructure | Scripts and metadata for producing packaged binaries (components, hypervisors, kernel and rootfs). |
| kernel | kernel | Linux kernel used by the hypervisor to boot the guest image. Patches are stored here. |
| osbuilder | infrastructure | Tool to create "mini O/S" rootfs and initrd images and kernel for the hypervisor. |
| kata-debug | infrastructure | Utility tool to gather Kata Containers debug information from Kubernetes clusters. |
agent-ctl |
utility | Tool that provides low-level access for testing the agent. |
kata-ctl |
utility | Tool that provides advanced commands and debug facilities. |
trace-forwarder |
utility | Agent tracing helper. |
ci |
CI | Continuous Integration configuration files and scripts. |
ocp-ci |
CI | Continuous Integration configuration for the OpenShift pipelines. |
katacontainers.io |
Source for the katacontainers.io site. |
|
Webhook |
utility | Example of a simple admission controller webhook to annotate pods with the Kata runtime class |
Packaging and releases
Kata Containers is now available natively for most distributions.
General tests
See the tests documentation.
Glossary of Terms
See the glossary of terms related to Kata Containers.