docs/doc/source/usertasks/kubernetes/known-limitations.rst
Ron Stone f125a8b892 Remove spurious escapes (r8,dsR8)
This change addresses a long-standing issue in rST documentation imported from XML.
That import process added backslash escapes in front of various characters. The three
most common being '(', ')', and '_'.
These instances are removed.

Signed-off-by: Ron Stone <ronald.stone@windriver.com>
Change-Id: Id43a9337ffcd505ccbdf072d7b29afdb5d2c997e
2023-03-01 11:19:04 +00:00

53 lines
1.5 KiB
ReStructuredText

.. ihj1591797204756
.. _known-limitations:
================================
Known Kata Container Limitations
================================
.. note::
Kata Containers will not be supported in |prod-long| |prod-ver|.
This section describes the known limitations when using Kata containers.
.. _known-limitations-section-tsh-tl1-zlb:
--------------
SR-IOV Support
--------------
A minimal **kernel** and **rootfs** for Kata containers are shipped with
|prod-long|, and are present at /usr/share/kata-containers/. To enable certain
kernel features such as :abbr:`IOMMU (I/O memory management unit)`, and desired
network kernel modules, a custom kernel image, and rootfs has to be built. For
more information, see `https://katacontainers.io/
<https://katacontainers.io/>`__.
.. _known-limitations-section-ngp-ty3-bmb:
-------------------
CPU Manager Support
-------------------
Kata containers currently occupy only the platform cores. There is no
:abbr:`CPU (Central Processing Unit)` manager support.
.. _known-limitations-section-wcd-xy3-bmb:
---------
Hugepages
---------
.. _known-limitations-ul-uhz-xy3-bmb:
- Similar to the SR-IOV limitation, hugepage support must be configured in a
custom Kata kernel.
- The size and number of hugepages must be written using the
:command:`io.katacontainers.config.hypervisor.kernel_params` annotation.
- Creating a **hugetlbfs** mount for hugepages in the Kata container is
specific to the end user application.