The following is an overview of the different installation methods available.
Kata Containers requires nested virtualization or bare metal. Check hardware requirements to see if your system is capable of running Kata Containers.
The packaged installation method uses your distribution's native package format (such as RPM or DEB).
Note:
We encourage you to select an installation method that provides automatic updates, to ensure you get the latest security updates and bug fixes.
| Installation method | Description | Automatic updates | Use case |
|---|---|---|---|
| Using official distro packages | Kata packages provided by Linux distributions official repositories | yes | Recommended for most users. |
| Automatic | Run a single command to install a full system | No! | For those wanting the latest release quickly. |
| Using kata-deploy | The preferred way to deploy the Kata Containers distributed binaries on a Kubernetes cluster | No! | Best way to give it a try on kata-containers on an already up and running Kubernetes cluster. |
Kata Deploy provides a Dockerfile, which contains all of the binaries and artifacts required to run Kata Containers, as well as reference DaemonSets, which can be utilized to install Kata Containers on a running Kubernetes cluster.
Use Kata Deploy to install Kata Containers on a Kubernetes Cluster.
Kata packages are provided by official distribution repositories for:
| Distribution (link to installation guide) | Minimum versions |
|---|---|
| CentOS | 8 |
| Fedora | 34 |
Use kata-manager to automatically install a working Kata Containers system.