Files
kata-containers/tests
Fabiano Fidêncio 6fc74ee112 tests: reduce k0s host memory footprint on CI runners
Unlike k3s and rke2, the k0s deployment never trimmed its default stack,
so it ran metrics-server, autopilot, etc. in addition to the components
the tests actually need. On the free GitHub runners this leaves too
little host memory headroom: the large in-guest image pull test
launches a 4GB Kata QEMU and, while unpacking the image into trusted
block storage, the host OOM-kills QEMU. This surfaces as
"ttrpc: closed" / "QEMU exited ... signal: killed", even though the
very same test passes on k3s, rke2 and microk8s on the same runner
(all of which we already trim).

Disable the components the tests don't rely on (metrics-server,
autopilot) to bring k0s in line with the other distros, while keeping
coredns, kube-proxy/network-provider and konnectivity-server.

Signed-off-by: Fabiano Fidêncio <ffidencio@nvidia.com>
Assisted-by: Cursor <cursoragent@cursor.com>
2026-07-24 12:21:08 +02:00
..
2026-07-09 13:40:17 +01:00
2026-06-03 09:56:54 +01:00

Kata Containers Tests

This directory contains various types of tests for testing the Kata Containers repository.

Test Content

We provide several tests to ensure Kata-Containers run on different scenarios and with different container managers.

  1. Integration tests to ensure compatibility with:
  2. Stability tests
  3. Functional

GitHub Actions

Kata Containers uses GitHub Actions in the Kata Containers repository.