github/kata-containers
1
0
Fork 2
mirror of https://github.com/kata-containers/kata-containers.git synced 2025-10-22 04:18:53 +00:00
Code Issues Projects Releases Wiki Activity
Files
8c4bad68a8e305d121527f761ad08425569f09ba
kata-containers/docs/how-to/how-to-use-virtio-fs-with-kata.md
Fabiano Fidêncio 8c4bad68a8 kata-deploy: Remove kustomize yamls, rely on helm-chart only 
As the kata-deploy helm chart has been the only way we've been testing
kata-containers deployment as part of our CI, it's time to finally get
rid of the kustomize yamls and avoid us having to maintain two different
methods (with one of those not being tested).

Here I removed:
* kata-deploy yamls and kustomize yamls
* kata-cleanup yamls and kustomize yamls
* kata-rbac yals and kustomize yamls
* README.md for the kustomize yamls was removed

Signed-off-by: Fabiano Fidêncio <ffidencio@nvidia.com>
2025-10-08 16:54:19 +02:00

861 B
Raw Blame History

Kata Containers with virtio-fs

Introduction

Container deployments utilize explicit or implicit file sharing between host filesystem and containers. From a trust perspective, avoiding a shared file-system between the trusted host and untrusted container is recommended. This is not always feasible. In Kata Containers, block-based volumes are preferred as they allow usage of either device pass through or virtio-blk for access within the virtual machine.

As of the 2.0 release of Kata Containers, virtio-fs is the default filesystem sharing mechanism.

virtio-fs support works out of the box for cloud-hypervisor and qemu, when Kata Containers is deployed using kata-deploy. Learn more about kata-deploy and how to use kata-deploy in Kubernetes here.