From c5eb082a4602dc9b458fa0bae692c714dbd38d0d Mon Sep 17 00:00:00 2001 From: Asier Gutierrez Date: Thu, 12 Jan 2023 17:57:08 +0800 Subject: [PATCH] Removed old left overs about IMA policies --- keps/sig-node/3702-ima-namespace-support/README.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/keps/sig-node/3702-ima-namespace-support/README.md b/keps/sig-node/3702-ima-namespace-support/README.md index 3741072fbad..14b846efdea 100644 --- a/keps/sig-node/3702-ima-namespace-support/README.md +++ b/keps/sig-node/3702-ima-namespace-support/README.md @@ -138,8 +138,6 @@ The linux kernel IMA namespace support is based on user namespaces. Therefore, t Should we enable IMA namespaces by default when enabling user namespaces? -There will be a CRI API change which will allow the pod to use IMA namespaces and specify the namespace policy. - ### Linux kernel IMA is only available in Linux hosts and Linux containers. Unfortunately, IMA is not a separate namespace, which is needed in order to isolate it and be used inside containers. Upcoming kernel patches should add support for IMA namespaces.