From eefa0e34adfc35ef013e1aeb382612d8d4febf8b Mon Sep 17 00:00:00 2001 From: Markus Lehtonen Date: Tue, 22 Feb 2022 16:35:10 +0200 Subject: [PATCH] KEP-3008: clarify goals --- .../sig-node/3008-cri-class-based-resources/README.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/keps/sig-node/3008-cri-class-based-resources/README.md b/keps/sig-node/3008-cri-class-based-resources/README.md index 50682d96325d..30c452eeedeb 100644 --- a/keps/sig-node/3008-cri-class-based-resources/README.md +++ b/keps/sig-node/3008-cri-class-based-resources/README.md @@ -230,10 +230,11 @@ List the specific goals of the KEP. What is it trying to achieve? How will we know that this has succeeded? --> -- Introduce RDT support comparable to the OCI runtime-spec to CRI protocol. -- Make it possible to specify the RDT class of containers on CRI level. -- Make it possible to specify the blockio class of containers on CRI level. -- Make the extensions flexible, enabling easy addition of other class-based +- Make it possible to request class resources + - Support RDT class assignment of containers. This is already supported by + the containerd and CRI-O runtime and part of the OCI runtime-spec + - Support blockio class assignment of containers. +- Make the extensions flexible, enabling simple addition of other class-based resource types in the future. ### Non-Goals @@ -304,7 +305,7 @@ Go in to as much detail as necessary here. This might be a good place to talk about core concepts and how they relate. --> -This is only the first in getting class-based resources supported in +This is only the first step in getting class-based resources supported in Kubernetes. Important pieces like resource status, resource disovery and permission control are [non-goals](#non-goals) not solved here. However, these aspects are briefly discussed in [future work](#future-work). However, the risk