From c8d4ea84e3d9da20e9a2ab8f8c35046792919da4 Mon Sep 17 00:00:00 2001 From: Chelsea Mafrica Date: Thu, 4 Aug 2022 14:27:08 -0700 Subject: [PATCH] docs: Improve SGX documentation Remove line about annotations support in CRI-O and containerd since it has been supported for a couple years. Fixes #4819 Signed-off-by: Chelsea Mafrica --- docs/use-cases/using-Intel-SGX-and-kata.md | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/docs/use-cases/using-Intel-SGX-and-kata.md b/docs/use-cases/using-Intel-SGX-and-kata.md index b08e3c765c..9b721f1bc4 100644 --- a/docs/use-cases/using-Intel-SGX-and-kata.md +++ b/docs/use-cases/using-Intel-SGX-and-kata.md @@ -25,9 +25,6 @@ CONFIG_X86_SGX_KVM=y ### Kata Containers Configuration -Before running a Kata Container make sure that your version of `crio` or `containerd` -supports annotations. - For `containerd` check in `/etc/containerd/config.toml` that the list of `pod_annotations` passed to the `sandbox` are: `["io.katacontainers.*", "sgx.intel.com/epc"]`. @@ -99,4 +96,4 @@ because socket passthrough is not supported. An alternative is to deploy the `ae container. * Projects like [Gramine Shielded Containers (GSC)](https://gramine-gsc.readthedocs.io/en/latest/) are also known to work. For GSC specifically, the Kata guest kernel needs to have the `CONFIG_NUMA=y` -enabled and at least one CPU online when running the GSC container. The Kata Containers guest kernel currently has CONFIG_NUMA=y enabled by default. +enabled and at least one CPU online when running the GSC container. The Kata Containers guest kernel currently has `CONFIG_NUMA=y` enabled by default.